-
|
Hi! First off, thanks so much for creating and maintaining this add-on! Its people like you that make open source software so great!! I'm struggling to figure out how to make HA & HE share device updates. I have seen a couple other threads but haven't found a solution that works for me. I have 3 Aqara Temp & Humidty devices that are working fine from a HE perspective, I can see all the ~hourly updates in the logs, but that data isn't making it into HA, it only updates if I change something or restart instances. The readme calls this out as a known thing to contend with, however I'm really struggling to solve it although i generally understand what its trying to get me to do. Specifics are HE & HA are on the same LAN, but HA is in a docker container so has a different local subnet from HE. I am also running a Caddy proxy and so am forwarding HA traffic. HE: 192.168.88.133 When I try to add the 8123 port to the HE integration config in HA, it crashes the instance. I tried adding a 2nd port forward (8124) to see if that would work but no luck. HE Config: HA Config: docker-compose: Caddyfile: |
Beta Was this translation helpful? Give feedback.
Replies: 10 comments
-
|
Let me know what logs or other things are helpful/necessary. Here is a snippet of the log from one of the sensors from HE as well as the graph in HA showing only 1 temp change registered in the last 24 hours.
|
Beta Was this translation helpful? Give feedback.
-
|
The overall goal is for Hubitat to end up with an address (including a port number) that it can use to post events to the event server started by the integration. The event server is running on the same machine as Home Assistant itself, so the event server will have HA's IP address (or whatever address Hubitat can use to get to HA). By default, the event server will run at a random port. This is fine when the integration is able to configure things itself -- it will auto-discover its public IP, and tell Hubitat to use In that case, you need to configure both the event server URL and the event server port. 
The URL is what the integration will tell Hubitat to use to post events. The port value tells the integration to always bind the event server to a specific port rather than choosing a random one. The URL is a separate config option from the port (rather than the URL always using whatever value is given for "Event server port") to allow for port mapping. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @jason0x43 so I think it may have just clicked that I'm setting the event listener port in HA in the HE addon configuration? So I just picked 10484 at random, added it as the event server port in HA, and added it as a forwarded docker port in my docker-compose. Does that sound about right? |
Beta Was this translation helpful? Give feedback.
-
|
Yup. The port you pick in the integration configuration will be used by the event server started by the integration. So when you pick port 10484, the integration is going to start a server on the HA host listening on port 10484. |
Beta Was this translation helpful? Give feedback.
-
|
Sadly this didn't work. Got updates due to the changes but haven't had anything since i made the changes yesterday. Are there any logs I can pull to try to figure out why its not working? |
Beta Was this translation helpful? Give feedback.
-
|
Are you sure that the device is trying to report updates? Do any other devices from Hubitat work, particularly ones that generate immediate updates like switches, work? |
Beta Was this translation helpful? Give feedback.
-
|
The data is coming into Hubitat, I suppose its possible the Maker API isn't pushing the updates, but the config for that seemed pretty straighforward? |
Beta Was this translation helpful? Give feedback.
-
|
Have you tried some other device in Hubitat? Maybe try setting up a virtual contact sensor in Hubitat, add it to the Maker API, and try changing its state in Hubitat and see if it updates in HA. |
Beta Was this translation helpful? Give feedback.
-
|
I'm going to close this out as its started working, but sadly I do not know what the actual solution was. I updated Hubitat, the Maker API, this integration, and moved HA from the For completeness, this is now the current, working state:
|
Beta Was this translation helpful? Give feedback.
-
|
Very much appreciate your efforts to get me sorted @jason0x43 🙏 |
Beta Was this translation helpful? Give feedback.
I'm going to close this out as its started working, but sadly I do not know what the actual solution was. I updated Hubitat, the Maker API, this integration, and moved HA from the
Stableversion toLatest. No of those were big jumps, I think I was only 1 minor version behind on everything, but guess it was in there somewhere 🤷♂️ I did also enableAllow Access via Remote/Cloudb/c I was thinking that since they're on different IP subnets maybe was causing issues? Didn't make much sense b/c the integration was able to update the listener port, but getting desperate.For completeness, this is now the current, working state:
HA
Hubitat