Hello.
I have an issue, that the current status from my devices not showing correct value after sending command (on/off)
Latest z-way version 2.2.5 on rpi and UZB as controller.
I have included a clip so that it will be easier to understand what I mean.
Let me just explain what you are seeing.
Iam sending on and off command from Node-Red to the MQTT Module in Z-Way, the commands is sent to the devices, both Set and Get, that is the reason I display the queue.
Every time I send command like this, one or more device is not reporting back the correct state.
But if i force an update of the device then it will be correct.
This is a very annoying issue. And I hope there is someone that have any ideas how to solve this.
Here is my proof
https://youtu.be/F62MK86A-Eo
Current status is not correct
Re: Current status is not correct
of course, sorry about thatPoltoS wrote:log?
The log is one hour off compared to the time you see in expert UI when i make update
- Attachments
-
- z-way-server.zip
- (12.16 KiB) Downloaded 371 times
Re: Current status is not correct
Pretty strange to see that devices do answer after a while - not instantly. Looks you have collisions in the network - they all try to report at the same time. What devices do you have?
Re: Current status is not correct
But if I do not manually update the status from expert UI then they does not report back the correct state.
Well I use many different devices, and this behavior always accure when I send to multiple devices. I use Fibaro, Qubino, Everspring and Aeon Labs.
I could reproduce this error with other devices then I used in the video.
As soon as I send commands to multiple devices then things like this happens.
Well I use many different devices, and this behavior always accure when I send to multiple devices. I use Fibaro, Qubino, Everspring and Aeon Labs.
I could reproduce this error with other devices then I used in the video.
As soon as I send commands to multiple devices then things like this happens.
Re: Current status is not correct
Looks like collisions in the network - return packets get lost. Only a sniffer can help here. Or the new CIT tool announced by the Z-Wave Alliance
Re: Current status is not correct
Could it be issues with my UZB?
What kind of sniffer?
What kind of sniffer?
Re: Current status is not correct
Z-Wave radio sniffer to see what devices are trying to send.
Re: Current status is not correct
I did not have this issues with my Razberry, and I am using same devices now with my UZB, what do you think? could that be the issue here?
Re: Current status is not correct
You mean it happens on UZB but not on RaZ?