Page 1 of 1
Problem with OZW in 2022.1 14223
Posted: Wednesday 02 March 2022 17:33
by harrykausl
Toaday I included a new Fibaro FGS 213 to my system. I'm on this beta because of problems with enocean. Including worked, devices are created. Then I wanted to change the settings of the switch in the hardware zwave panel. I change the value (for example the name) and select write configuration for this device, but nothing happens. Then tried to change another z-wave hardware, same effect. I have a sd-card with my old 2021.1 and bootet with this, to see, if the error was there too. It was. It seems, that the error was migrated. I remember, when I switched to 2021.1 I had to delete the ozwcache and wake up the devices. Then everything worked. Could this be the solution for this problem too. I stop domoticz, delete ozwcache, restart domoticz and wake up all my batterie devices.
Re: Problem with OZW in 2022.1 14223
Posted: Wednesday 02 March 2022 18:32
by harrykausl
Next problem. After several reincludes, I could change some settings. I have a toggle switch on s1 and customized it as toggle switch, contact close on, contact opened off. This works now. Light gets on, when I push my hardware switch connected to s1 to on off too. But switching from domoticz doesn't work. I push the device, it shows on, but nothing happens. Any idea?
Re: Problem with OZW in 2022.1 14223
Posted: Wednesday 02 March 2022 19:05
by waltervl
Perhaps start with clearing all your browser cache.
https://www.domoticz.com/wiki/Browser_Cache
Re: Problem with OZW in 2022.1 14223
Posted: Wednesday 02 March 2022 19:34
by harrykausl
I did this already several times. I have no cache problem, because I see everything. The problem is, that zwave seems not to work. When I push the switch from domoticz the symbol shows on, but the real light is off. With the external onoff attached to the Fibaro it works. Perhaps the switch is damaged.
Re: Problem with OZW in 2022.1 14223
Posted: Wednesday 02 March 2022 23:43
by waltervl
Domoticz UI is heavily build on Javascripts. If there was a change in these scripts they sometimes are unnoticed but could introduce unexpected behavior.
Perhaps try to open Domoticz in a browser window in private (or incognito) mode. Then all javascripts are forced to reload.