Closed falkorichter closed 5 years ago
It´s reproduceable. I have to push the update twice before getting the updated value.
Also turning the dimmer off - only getting the update when tapping update twice.
looking at the log (tail -fn 500 /var/log/z-way-server.log
):
[2019-03-26 10:20:34.557] [I] [core] --- ZWayVDev_zway_9-0-38 performCommand processing: {"0":"update","1":{}}
[2019-03-26 10:20:34.558] [I] [zway] Adding job: SwitchMultilevel Get
[2019-03-26 10:20:34.562] [D] [zway] SENDING (cb 0x38): ( 01 09 00 13 09 02 26 02 25 38 D7 )
[2019-03-26 10:20:34.565] [D] [zway] RECEIVED ACK
[2019-03-26 10:20:34.573] [D] [zway] RECEIVED: ( 01 04 01 13 01 E8 )
[2019-03-26 10:20:34.573] [D] [zway] SENT ACK
[2019-03-26 10:20:34.574] [D] [zway] Delivered to Z-Wave stack
[2019-03-26 10:20:34.589] [D] [zway] RECEIVED: ( 01 05 00 13 38 00 D1 )
[2019-03-26 10:20:34.589] [D] [zway] SENT ACK
[2019-03-26 10:20:34.590] [I] [zway] Job 0x13 (SwitchMultilevel Get): Delivered
[2019-03-26 10:20:34.590] [D] [zway] SendData Response with callback 0x38 received: received by recipient
[2019-03-26 10:20:34.590] [D] [zway] SETDATA devices.9.data.lastSendInternal = **********
[2019-03-26 10:20:34.591] [D] [zway] SETDATA devices.9.data.lastSend = 421032 (0x00066ca8)
[2019-03-26 10:20:34.591] [D] [zway] Job 0x13 (SwitchMultilevel Get): success
[2019-03-26 10:20:34.591] [I] [zway] Waiting for job reply: SwitchMultilevel Get
[2019-03-26 10:20:34.633] [D] [zway] RECEIVED: ( 01 0B 00 04 00 09 03 26 03 17 DD 00 15 )
[2019-03-26 10:20:34.634] [D] [zway] SENT ACK
[2019-03-26 10:20:34.634] [D] [zway] SETDATA devices.9.data.lastReceived = 0 (0x00000000)
[2019-03-26 10:20:34.635] [D] [zway] Received reply on job (SwitchMultilevel Get)
[2019-03-26 10:20:34.635] [D] [zway] SETDATA devices.9.instances.0.commandClasses.38.data.level = 23 (0x00000017)
[2019-03-26 10:20:34.652] [I] [core] Notification: device-info (device-status): {"dev":"Goap Dimmer (#9) Qubino Flush Dimmer","l":"23%","location":""}
[2019-03-26 10:20:36.672] [I] [zway] Adding job: SwitchMultilevel Get
[2019-03-26 10:20:36.672] [D] [zway] SENDING (cb 0x39): ( 01 09 00 13 09 02 26 02 25 39 D6 )
[2019-03-26 10:20:36.674] [D] [zway] RECEIVED ACK
[2019-03-26 10:20:36.681] [D] [zway] RECEIVED: ( 01 04 01 13 01 E8 )
[2019-03-26 10:20:36.681] [D] [zway] SENT ACK
[2019-03-26 10:20:36.681] [D] [zway] Delivered to Z-Wave stack
[2019-03-26 10:20:36.698] [D] [zway] RECEIVED: ( 01 05 00 13 39 00 D0 )
[2019-03-26 10:20:36.698] [D] [zway] SENT ACK
[2019-03-26 10:20:36.699] [I] [zway] Job 0x13 (SwitchMultilevel Get): Delivered
[2019-03-26 10:20:36.699] [D] [zway] SendData Response with callback 0x39 received: received by recipient
[2019-03-26 10:20:36.699] [D] [zway] SETDATA devices.9.data.lastSendInternal = **********
[2019-03-26 10:20:36.699] [D] [zway] SETDATA devices.9.data.lastSend = 421239 (0x00066d77)
[2019-03-26 10:20:36.699] [D] [zway] Job 0x13 (SwitchMultilevel Get): success
[2019-03-26 10:20:36.700] [I] [zway] Waiting for job reply: SwitchMultilevel Get
[2019-03-26 10:20:36.733] [D] [zway] Job 0x13: deleted from queue
[2019-03-26 10:20:36.735] [D] [zway] RECEIVED: ( 01 0A 00 04 00 09 02 98 40 DB 00 F9 )
[2019-03-26 10:20:36.735] [D] [zway] SENT ACK
[2019-03-26 10:20:36.735] [D] [zway] SETDATA devices.9.data.lastReceived = 0 (0x00000000)
[2019-03-26 10:20:36.735] [I] [zway] Node 9:0 CC Security: sending Nonce Report
[2019-03-26 10:20:36.736] [I] [zway] Adding job: Nonce Report
[2019-03-26 10:20:36.736] [D] [zway] SENDING (cb 0x3a): ( 01 11 00 13 09 0A 98 80 0A 94 0A 2F 6E 1C 26 CE 25 3A D8 )
looks good to me.
This is a known bug of Qubino dimmers (and other devices). Please go to Expert UI->Configuration->Device 9->Expert Commands and set plain Association to 1 (Z-Way controller) in group 1. Remove MultiChannelAssociation 1:0 from group 1.
After this the dimmer will report instant changes
We are experiencing issues getting the current values of connected z-wave actuators.
As there is usually a manual way of controlling them we were researching, how long it takes for the z-way UI/API to yield the updated values.
For instance we have a shade demonstrator on our desk. The shades roll down in like 10 seconds. We can manually roll down the shades the it is very hard to get the current status of the shades using the API/smarthome frontend.
We have also tried including the MQTT plugin in order so see the updated values faster. Same problem there so we assume a deepeer bug
Here is an example:
update
api call. We understand this might be neccesary.update
API call as you can see in the screenshot of the z-wave web debugging session.Questions: Is there a way to
update
all devices? We are currently polling the current state of devices, or using MQTT plugin to avoid polling. But callingupdate
on the devices individually would defeat the purpose of trying to get a constant stream of udpate.