Page 1 of 1
Updating to Domoticz version supporting Python Plugin DomoticzEx Framework results into non-working (selector)switches
Posted: Monday 13 September 2021 14:40
by Nautilus
Sorry for cross-posting. As this seems like a code bug I have posted an issue to Domoticz github repo. I will not (yet) remove this if others are experiencing the same and searching for info…
- Spoiler: show
- I am running Domoticz:
Version: 2021.1 (build 13497)
Build Hash: 2c271b6d2
Compile Date: 2021-09-10 16:25:51
dzVents Version: 3.1.8
Python Version: 3.7.3 (default, Jul 25 2020, 13:03:44) [GCC 8.3.0]
With zigbee2mqtt:
plugin: v.3.1.0-beta, zigbee2mqtt: v.1.21.1 (zStack3x0 20210120)
It seems that selector switches that are associated with python plugin framework (DomoticzEx) are not triggering their respective actions anymore. The switches as such seem to work as they should, they state changes and no error on the log. But the associated actions configure behind each level do not trigger. This shows in my setup only with selector switches controlled by zigbee2mqtt plugin which was recently updated to supporting DomoticzEx. I raise an issue about this in zigbee2mqtt project and the conclusion was that this must be something in the plugin framework that causes this. If I revert the zigbee2mqtt plugin to version that is not using DomoticzEx, the selector switches are working again.
Re: Updating to Domoticz version supporting Python Plugin DomoticzEx Framework results into non-working (selector)switch
Posted: Friday 08 October 2021 23:01
by Nautilus
I should prabably mention here, in case someone is wondering about what has happened to selectors created by python plugin framework (DomoticxEx) that while selectors do trigger the level actions after the latest repairs, they are currenty only triggered when level changes. So if you rely on stuff where e.g. each consequtive press of a button should trigger an action, it does not currently work. It will trigger once when level changes, but not after that. Also the on/off delay and device history seem to be not working. This has been reported in github so hoping there will be a fix for these soon as well...
