@jason0x43 Not sure which side has an error, but if I create a Hubitat Virtual Temperature Bulb and make an adjustment with an HA automation, I get the wrong values on HE when calling for ˚K from HA
Hmmm... HA deals internally in mireds rather than °K, and it's possible there's a rounding issue in there somewhere. I'll take a look (issue).
After looking into it a bit more, that color temp mismatch is just a function of how HA works. Kelvin temps are converted to mireds by HA before being passed to light entities, so an entity only deals with mireds (it never even sees the kelvin parameter).
2 Likes
Glad I saw your post about the HACS issue. I've been scratching my head trying to figure out why I cannot find it. Manual install also not working now, but I'm probably missing a hidden directory this time because I'm trying to install on a virtual machine over Samba.
I have no reason to bring Zigbee or Z-Wave devices from HE to HA, but the ability to share HE virtual switches with HA so easily comes in real handy. I realized this was a way to put some of my Lutron Connected Bulb Remotes back in service. Not perfect, but it works! Thanks again for this @jason0x43 !
https://community.hubitat.com/t/a-word-about-ha-he-integration/63754/110?u=smarthomeprimer
1 Like
How did you solved this? im having the exact issue. When i toggle the switch it turn on the light and then return to the off position automatically.
I just did a new install, and that's exactly what's happening to me. When I turn a lamp on, it goes on, but the icon in HA flips back to the "off" position. It seems ALL my devices are acting this way. Seems like its not receiving info back from hubitat, but I can send.
Edit: It is receiving data back from hubitat, but it takes a few hours. It shows mw temps from thermostats from a few hours ago
Any thoughts?
Hmmm...generally the problem when Hubitat can't communicate with HA is that the HA instance is running in a VM or behind a firewall or something. When the HA integration starts up, it updates the "URL to POST device events to" address in the associated Maker API instance in Hubitat. That URL must be one that Hubitat can actually reach.
By default, the integration pings Hubitat and uses the address of whatever interface it used to reach Hubitat. If your HA is running in a VM using NAT addressing, that address will be some internal IP address that Hubitat can't reach.
If you're in that situation, you'll need to manually set the event server URL and port in the Hubitat integration in HA the address or hostname of the physical host (the host visible to Hubitat), and then make sure whatever port you set there is mapped to the VM running HA.
1 Like
My HA is running in docker desktop. I'll mess around with it when I get home from work and report back. Only odd thing is that it is receiving some things. Would the event server be the hubitat ip?
Edit The only time HA is getting updated info from hubitat is when I do a HA server restart. Exactly what you said. So that confirms is definitely an issue with the inbound from hubitat to HA
Are you on a recent HA version? What you do have your HA network settings set to (configuration --> general --> network)? You may need to uncheck autoconfigure and manually select the correct (external) interface for HA to bind to.
If you uncheck "auto configure", what are the other options? That 172.x address is in the private space...
What does your docker configuration look like? You need to bind HA to an address that's actually reachable in your network (that private address is not...),
1 Like
Make sure your Windows Defender Firewall allows inbound 8123 (TCP) from outside your Windows host?
I always use the bridge networks with home assistant docker containers.. I get tired of opening up port after port as I add integrations.
But if I can already get to that address from inside my network, wouldn't that mean it isn't a firewall issue?
I wasn't sure if you were accessing HA via the windows machine you were running the container on.. so thought I'd chime in.. if you can get to it via another computer then - yeah.. shouldn't be an issue.
I am not running the HE bridge currently, are there any other ports exposed? Maybe those have to be defined if so..
