New HomeKit Controller

Okay, so not AQI, but just a generic your air is good/fair/bad based primarily on one pollutant metric (tVOC) and then how much CO2 it thinks we added to a room. My concern is the value doesn't really mean anything. Yes you can say it tells you something is wrong, but doesn't really tell you what. The only solution is to open a window.

I also realized this morning i was possibly thinking about why it may be missing wrong. It is possible it isn't included because of some limitation with Homekit. Think of it like the thermostat device in Homekit don't have a way to interpret VOC's or Air Quality. Then including it in a homekit response wouldn't make sense.

OfCourse, i am reaching with that, but I have also taken this thread off topic to much with my ramblings about Air Quality.

1 Like

I've added an air quality sensor implementation, it will likely appear as a separate device. Looks for homekit devices, there may be a new one out of the blut. Also, I don't have an actual Ecobee device with that air quality sensor functionality to test it against, so there is a bit of educated guessing involved.

3 Likes

Woke up this morning and my loft temperature was wrong. Checked Hk integration app and looks good.

Looked n Devices and found it was OFFLINE.

Any idea how to get it back without removing it (it’s used in a lot of rules)?

@gopher.ny Help!

Added: Still working fine with Ecobee iOS app.

When was the last event recieved for that device? If you click the events tab across the top you can see what was last reported.

Nothing unusual:

I think the “offline” is from a refresh I did.

More concerned as to HOW to get it back online!

@gopher.ny Victor,
I just going to re-pair it as a new device and fix all the references.

If it happens again, I will see if you want to check any logs before I get it back online.

A factory reset of the thermostat did indeed work. Word of warning to those doing this, it resets EVERYTHING so make sure you take record of your maintenance schedules, thresholds if you set them and all that other advanced stuff.

1 Like

Sorry if i didn't make that clear.

1 Like

No worries. I took a lot of pictures before I did it :grin:

2 Likes

I wonder if an Info option could be added for logging, instead of just Debug?
Thanks.
@gopher.ny ?

Can I connect HOOBS to hubitat using the homekit controller. I have some Eufy cameras connected to HOOBS, and then through HOOBS to Apple Home. I tried connecting my homebase 3 to the apple home ecosystem,but the cameras do not show up. Since I am blind, I use the home app to check their battery levels since the battery level in the Eufy app is not accessible to the blind. But if I can read the battery levels in hubitat, I would be able to do more with that information.

thanks

I think in theory you could, but I am not sure how the cameras would come over into Hubitat as I doubt there is a "camera" driver. Also I think you would have to disconnect HOOBS from Apple Home in order to pair it with Hubitat instead. I am pretty sure you can only have a bridge (HOOBS) paired with one "Home" (Hubitat Homekit Controller) at a time.

The best alternative solution I can think of would probably be to integrate the cameras through Home Assistant, then you could push the battery levels over to Hubitat with the HADB app. I assume there is a Eufy Home Assistant integration, if there is one for HOOBS already.

Does anyone know if August lock is supported?

I'm having an issue with Ecobee thermostats via this integration.
When I migrated I have noticed that there is no thermostatSetpoint state like it used to have. This is a bit of a headache, because on integrations I had an increased logic complexity to check the current set point.

I'm not sure if it is related to the issue above, but the main problem is that I turn on heating for instance, and it uses the coolingSetpoint instead of the heatingSetpoint.

I couldn't find a pattern for this problem, but it happens a lot, at least 30% of the time. It seems to occur more with heating, but eventually it affects cooling too.

I have tried to invert my automation, to first set the mode to heating, then set the heatingSetpoint. I even added a 5 seconds delay between these 2 actions, but regardless of the order and delay, the problem remains.

What platform version is your hub on?

2.4.2.158 on a C-8 Pro.

It happened again today. Looking at the events, there is something odd:

  • At 8:21:00 I have pushed a button that triggered 2 commands, setHeatingSetpoint(23.5) and heat().
    Please note that those 2 commands came from my Node-RED integration.

  • I didn't give any other input to the hub, either directly or via Node-RED.

  • I didn't touch the physical thermostat.

  • About 39 seconds after my input, a setHeatingSetpoint(25.5) came from "nowhere".

Unlike I have previously thought, the value 25.5 wasn't the coolingSetpoint, it was the previous heatingSepoint I have used the night before.

Is there any way to check from which IP address the unexpected command came from?

It came from outside of Hubitat and any Hubitat app, which excludes your Node-RED integration. This means it came from one of these three places:

  1. Directly from the thermostat
  2. From the ecobee cloud but initiated via the ecobee app (or a comfort setting)
  3. From the ecobee cloud via some other ecobee integration you have in place

I don't use any automation/comfort settings/schedule from the thermostats nor Ecobee cloud.

I had 4 apps connected to the Ecobee cloud that I wasn't using. I have excluded those. I kept only Hubitat and beestat.io (read only). Thanks for point that out.

Let's see how it goes.

I'd also suggest updating to the latest platform. There are some changes in the Homekit Controller app - might as well as have the latest.

Also, FWIW, I have not seen anything like this from the ecobee Homekit Controller integration.