My bad, I didn’t read the log info provided. I got through the first paragraph and assumed they knew what they were talking about.
1 Like
The latest update seems to have broke the connection between Hubitat and HA. Anybody else having issues?
Is this the 0.10.0-pre0 release?
Yes, it is. I tried rolling back, but it still won’t connect. All my devices are unavailable.
If you haven’t already, enable debug logging for the integration, then restart Home Assistant and see if any errors are displayed in the log.
1 Like
There wasn’t any error messages that stood out, but there was a bunch of warnings about not being able to connect to devices, I don’t have the time to figure out what is going on right now so I just restored a backup from this morning and everything is working again. If I get more time later on I’ll try this again and get you some specific log info.
That would be helpful, thanks! The 0.10 release makes some internal changes to how devices and entities are identified to make the integration more configurable. I tested a few different upgrade scenarios locally and everything worked properly, but I was worried issues might come up in other situations (hence the pre-release status).
Hi Jason,
I finally had time to look at this again and I reloaded 0.10 release. After the reboot it took a few minutes and then all of my Hubitat devices reconnected to HA. Maybe I was just being impatient the first time I updated.
Thanks for all the work and support you’ve done on this integration!
1 Like
Anyone know if HE’s hub mode should be working? Because I’ve finally gotten around to setting it up and I’m getting strange behavior that I have repro’d.
- hub mode enabled in Maker API
- select and sensor entity shows up in integration Hubitat integration within HA (once it’s reloaded)
- If I run an action from HA to change the mode, the change is reflected in HE as expected
- If I use the select entity from HA to change the mode, no change is reflected in either HA or HE
- If I change the mode from HE, no change is reflected in HA
Been messing around with this all morning and I’m stumped. Now I’m wondering if maybe modes aren’t even implemented in this integration since they are a special class of events in HE. And I don’t see anything in the OP’s documentation let alone this thread even.
OK thank you for that feedback.
I figured out what I did wrong and am posting here for the benefit of others to follow. Two things I didn’t realize:
- it is not enough to enable “allow control of modes” in Maker API if you want bidirectional sync of hub modes. You also have to enable “POST location events”, duh.
- secondly, and more subtly, if you change the mode from HA, no mode change will be apparent in Hubitat, at least not from Settings>Mode. It looks to me like that screen does not show changes in mode unless you refresh your browser. That through me off initially because I assumed incorrectly that mode changes in HA were not being reflected in HE–when, in fact, they were.
Hope my pain helps others…
Hmmm…. Not sure which browser you are using, but mode changes are reflected instantly in HE using Chrome.
I’m using Chrome too, but I don’t see any change in Settings/Mode (unless I refresh)
Hey, Im trying this integration out for the first time and after exposing the device in HE Maker API when I try to add that info into this integration it says ‘invalid token’. I’m using the token that show up in the Maker API app on HE under “Get Device Info”.
Any suggestions?
nevermind, my mistake in interpreting what the intake form is wanting. its not the device’s “id”: “865”, it works when I use the “apps/api/50”, just like is says in the github instructions, LOL.
however, it is a bit misleading on the integration side in practical use for the first time, maybe could add syntax comments on the intake form?
it would also be great if one could select the device to expose to HA, instead of all of them in the Maker API. I suppose I can simply disable those I do not need.
If there is another way, please let me know
Thank you
That is exactly how the Hubitat Maker API works. Sure, it offers the users a convenient “Select All” option, but normally users only select the devices that they want exposed via Maker API.
1 Like
Yes, I understand, the problem is my Maker API is not exclusive for this integration. I use it for other things, but those devices have no purpose in HA. Can Hubitat create two distinct Maker API’s with different devices? I’ve never had a reason for such, but that would solve this problem
Yes, I run 4 different instances of Maker API on the same Hubitat Hub. One for this HA integration, another for HomeBridge, etc…. In fact, that is really the only way it will work correctly if you want HE to push device updates without polling. Each instance of Maker API can only POST updates to one URL.
2 Likes
Don’t get me wrong @jason0x43 this is a fantastic integration! I only have a few devices that I cannot physically bring over from HE into HA, specifically, at the moment my z-wave devices. I’m not sure if later I will buy a z-wave dongle, but this certainly makes it easy use those devices in HA.
Thanks so much!
1 Like
Awesome, I never knew… Thanks!
1 Like