# Zwave module state unreliable **URL:** \ **Category:** Questions & Help\ **Created:** [August 12, 2020, 1:54pm UTC](https://community.homey.app/t/zwave-module-state-unreliable/33529 "2020-08-12T13:54:48Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![HVB83](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/hvb83/32/9827_2.png) [@HVB83](https://community.homey.app/u/HVB83)\ **Post date:** [August 12, 2020, 1:54pm UTC](https://community.homey.app/t/zwave-module-state-unreliable/33529/1 "2020-08-12T13:54:48Z")
I have a Homey early 2018 with 4.2.0 installed. My zwave module state seems unreliable, at least for several devices, making it useless as a trigger or condition in flows. Homey often thinks a light is on, whereas it’s not etc. This is the case for both Fibaro as well as Qubino modules. Emailed support with logs and a more elaborate description etc in April of this year. They said they had gotten reports on this issue by several users, but weren’t able to build a test setup due to Corona. Fair enough. Sent a reminder early July and got the reply that they hadn’t been able to work on this yet, but were hoping to do so soon. Doesn’t seem to me like it’s a high-pri for them and unlikely to be fixed anytime soon. Did anybody else experience the same issue? Any pointers on what could cause this issue? ---
**Author:** ![JPe4619](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jpe4619/32/9017_2.png) [@JPe4619](https://community.homey.app/u/JPe4619)\ **Post date:** [August 13, 2020, 3:06pm UTC](https://community.homey.app/t/zwave-module-state-unreliable/33529/2 "2020-08-13T15:06:35Z")
This is indeed a problem, as I see it, the reporting of the devices status is not handled, so if a device is switched by a connected switch, this change is send to Homey but Homey ignores this new state. Only is Homey sends a command for ON or OFF, the state in Homey is changed. For me I have this problems with older Fibaro devices FGS-221 and FGS-212. Even more sad is, this has been working in the past. Last year November I reported to Athom. ---
**Author:** ![Frank\_van\_de\_Schuur](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frank_van_de_schuur/32/35882_2.png) [@Frank\_van\_de\_Schuur](https://community.homey.app/u/Frank_van_de_Schuur)\ **Post date:** [August 13, 2020, 4:06pm UTC](https://community.homey.app/t/zwave-module-state-unreliable/33529/3 "2020-08-13T16:06:15Z")
I recognize this as well. I have a flow running that checks for energy consumption after it has been switched on and if it is not above a certain level than I switch on again (and again check for energy consumption) A similar thing can be done when switching of lights of course ---
**Author:** ![JPe4619](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jpe4619/32/9017_2.png) [@JPe4619](https://community.homey.app/u/JPe4619)\ **Post date:** [August 13, 2020, 4:13pm UTC](https://community.homey.app/t/zwave-module-state-unreliable/33529/4 "2020-08-13T16:13:11Z")
According some posts on this forum, it seems, that some newer devices don’t have this problem, but I didn’t buy any new devices lately.