The current version of this driver provides support for the TRV basic functionalities. Note, that an important (at least for me) feature is missing in Aqara E1 thermostat - this is the thermostatOperatingState. Aqara does not report back to the hub when the valve is open or closed.. : ( This is to be partially compensated in a future version, simulating the state based on the difference between the set temperature and the internally measured temperature.
heat : 5.0 .. 35.0 degrees C (step is 0.5 degrees C)
away - switches the TRV to awayPresetTemperature
off - switches the TRV anti-freeze mode (TBD)
Note: the 'auto' mode (programming a weekly schedule in the TRV itself for offline operation) is not supported
childLock - allows locking the TRV manual control
windowOpenDetection - switches the window open detection on and off
valveDetection - enables/disables the valve operation diagnostics (TBD)
awayPresetTemperature - sets the temperature in 'away' mode
I had a previous thermostat, I had a rule set in Hubitat that when I open a window, turn off the heaters.
I replaced the thermonstat with an Aqara TRV - E1, used your great controller, however, I can't change my rule - because neither of the two thermostats is in the thermostat group
Tell me please, can this be the fault of the driver?
Thank you for the feedback! Can you please give some more details, this may help me to identify the issue, probably related also to the Google Home integration problem that I still can not replicate .
Can you post a screenshot of where exactly the Aqara E1 TRV is not shown in a thermstostats group?
Something like this :
I have reverted back to 2.3.6.146 software platform version, but still can not reproduce this issue.
Did you install the driver before pairing the Aqara E1 thermostat, or it was already paired to the hub?
If later, from the Configuration button parameters list, select "LOAD ALL DEFAULTS" and then click on the button above.
@widmo this driver latest version 3.0.6 already had a Thermostat capability, but I have used double quotes :
Are you saying that after using singe quotes in the capability declaration, the RM5 rules are recognizing the device, but when using double quotes it didn't ?
Please post a screenshot of the same section as it is now working in your modified code, thank you!
because I couldn't find another link (and I searched on github!).
My driver is version 2.1.5, from November this year, but it's good to know that there is already version 3.0.6!
As handling many different thermostats and TRVs in one common driver proved to be inefficient and difficult to troubleshoot, the Aqara E1 thermostat is now supported in a separate, dedicated driver.
I've found that since updating to your latest driver the devices drop off the zigbee network a lot more often and need adding back. With your initial driver they seemed much more stable. Maybe it's just my zigbee mesh although most other devices seem ok.
Whether a Zigbee device stays connected to the Zigbee network does not depend on the driver used. Also, the new generation of Aqara devices do not 'stick' to the router that they paired initially, if a Zigbee route is lost, they will automatically choose a better route.
!
?
