I updated HomeSeer 4 to the latest version today and also saw that there was an update for the Hubitat plugin so I did that as well. All seemed to go well, or so Ithought.
As evening hit my zwave lights via maker all went on and the zwave venetians closed but the tasmota blinds didn't close. I have discovered that the C7 is no longer updating the level when the position changes in HS4. The blinds still work and can be driven via changing the level on the C7 device itself. I have tried restarting both the C7 and HS4, I have also tried removing and re-adding the blinds via maker and reconfiguring in HS4.
Whilst the plugins at both ends are working for all other devices (zwave/zigbee) and I can see log messages related to polling and response of tasmota blinds, the level information seems to have gone. This setup had been working reasonably flawlessly for months, the only recent updates have been HS4 version and elevation today. The tasmota blinds use the zemsmart driver and are picked up in HS4 via elevation as light switch dimmers 0-100% range.
Is their a way to revert to the previous version of elevation to test if that has caused the issue?
As evening hit my zwave lights via maker all went on and the zwave venetians closed but the tasmota blinds didn't close. I have discovered that the C7 is no longer updating the level when the position changes in HS4. The blinds still work and can be driven via changing the level on the C7 device itself. I have tried restarting both the C7 and HS4, I have also tried removing and re-adding the blinds via maker and reconfiguring in HS4.
Whilst the plugins at both ends are working for all other devices (zwave/zigbee) and I can see log messages related to polling and response of tasmota blinds, the level information seems to have gone. This setup had been working reasonably flawlessly for months, the only recent updates have been HS4 version and elevation today. The tasmota blinds use the zemsmart driver and are picked up in HS4 via elevation as light switch dimmers 0-100% range.
Is their a way to revert to the previous version of elevation to test if that has caused the issue?
Comment