If you are refering to the Hubitat update I am not sure to be honest. It took a long while in the "installing... ...please wait" bit and after some time, before it had finsihed, I navigated to another page and then navigated back to the update or I may have pressed refresh. On return the updated gave the impression of having finished stating the new version. I am not sure if I pressed Done at that point? There is no option to install anything now. Did I mess it up?
All those messages around 11:42 were requests from your child device in Hubitat. But I don't see response from HA.
From the image you posted I can see your connection was up for 20 minutes this mornig at around 9:07. Later did you repeatedly hit Initialise in the driver or update the app because there is no error reported?
It is not clear if your saying your Aqara device is working or not
Ah, okey. I am pretty sure I did press the Done button after updating HADB.
The Aqara curtain motors are working both manually using the physical button on the devices as well as from within Home Assistant. The problem seems to be that Hubitat and HA is not communicating.
As far as I can see I am guessing this is some sort of MQTT issue as the devices work fine in HA and HADB seems to work fine as well. I am looking in HA communities to try and persue the issue there.
The thermostat device in HE and the climate entity in HA dont match. What I did is trying to approximate the capabilities for both.
It might be possible to try another approch but it would require lots of testing from different type of thermostats. I don't have any thermostat on HA, therefore I'm not able to test anything myself. This simple fact would makes refactoring the climate entity a quite combersome and lenghtly process.
So whithout the needs and willingness of at least a few, it won't be reasonably feasable.
I think this is likely the problem. If the device works ok in HA then HADB should work fine too. So you have to focus on the cause of miscommunications between HA and HE. This point to a network issue.
Is your Hubitat or Home Assistant using a wifi connection?
Can I confirm that the two states for the Connection value in the main device are open and reconnecting? I want to track when my home assistant is down. Thanks.
Thanks, and thanks for the tip for looking for these things. I don't see the Closed showing up in the wild but I assume that this occurs when you manually click the close button - which I have never done. It seems that if Home Assistant goes down it brings up the Reconnecting status - which is what I will look for. Or perhaps look for "not Open" just in case.
Between this statement and the previous post, I'm confused if your HADB integration is talking to Home Assistant properly. Note that HADB doesn't use or need MQTT.
My suggestion if you’re uncertain, would be to set aside the functioning of the curtain motors for now and just test basic connection between HADB and Home Assistant. If you create a Toggle Helper on Home Assistant and then bring it into Hubitat via HADB, can you control it from Hubitat?
I have a fork of the Sensibo App and Driver on my GitHub page - it's a barely working port of a SmartThings integration and may be helpful (Im not a Dev and have brute forced fan speed support etc into it).
I recommend you ignore all the "climate react" stuff - It's Sensibo's "smart feature" for ppl without home automation systems. I'd also ignore battery and voltage, the OG Sensibo controllers didnt run from Mains power.