petertq
commented
4 years ago Now realizing that this is probably the wrong place to post my issue since qt-openzwave is "just" a wrapper for OpenZWave.
(Thought that qt-openzwave somehow included the openzwave stuff, but after glancing through the code I realized that it is probably not.)
Will post this is the OpenZWave project instead and close it when done.
Sorry, Peter
When turning on a switch in Home Assistant an MQTT message for updating the status is not always received.
When all goes well a message like this is sent from qt-openzwave:
OpenZWave/1/node/11/instance/2/commandclass/37/value/189349920/ - {"Value":true,"CommandClass":"COMMAND_CLASS_SWITCH_BINARY"}But sometimes this message is missing. The relevant logging output is in notok.txt. A similar output when it works as expected is in ok.txt.
I've tried to compare them and this is the diff output.
I upgraded to openzwave/ozwdaemon:latest today (digest d530803f6e04, so it should be build 170).
Running docker on Ubuntu (64 bits) on an R-Pi 4.
Home Assistant version is 0.113.2, with a clone from the dev branch for OpenZWave (for dealing with the slow dimming problem - as suggested in the forum).
The switch is a Fibaro FGS223 Double Relay and the controller is a Z-Wave.Me USB Stick.
I've got 30 devices in my network, and yes I know this is in beta, but decided to switch from an old Hassio/Resin-based installation and live with it.
Please tell me if there's anything more I can provide to solve this problem!
And I hope it's not a hardware issue (or that I need to upgrade the firmware for the Fibaro switch);-)
Perhaps not relevant for this issue, but I'm getting a few critical logging messages now and then. And also some Node reports for non-existing nodes (like Node 0).
Peter