Zwave2mqtt: [question] Fibaro FGR-223 : a lot of messages in some topics
Hi there,
I recently bought a Z-Stick Gen5 stick and a Fibaro FGR-223.
I didn't have any trouble calibrating the device, but for some reasons, when I'm using "down", "up" and "stop" commands, I have a lot of messages coming in some topics :
38/1/5 and 38/1/9 gets a lot of messages for unknown reasons. After few minutes, I have 10 000 messages in these 2 topics...
Zwave2mqtt stops working, probably because of the volume...
Any idea why ?
Regards,
Jeoffreybauvin
All 16 comments
@Jeoffreybauvin Sincerly have no idea, could you paste some logs output from the application please?
robertsLando
on 28 Aug 2020
Yes :
2020-08-29 10:20:53.044 Detail, Node005, Removing current message
2020-08-29 10:20:53.044 Detail, Node005, Notification: ValueRefreshed CC: COMMAND_CLASS_SWITCH_MULTILEVEL Instance: 1 Index: 9
2020-08-29 10:20:53.044 Detail, Node005, Notification: ValueRefreshed CC: COMMAND_CLASS_SWITCH_MULTILEVEL Instance: 1 Index: 5
z2m:Zwave zwave node 5: changed: 38-1-9:Instance 1: Target Value:0 -> 0 +807ms
z2m:Zwave zwave node 5: changed: 38-1-5:Instance 1: Dimming Duration:-1 -> -1 +1ms
2020-08-29 10:20:53.235 Info, Timer: delayed event
2020-08-29 10:20:53.235 Info, Node005, Sending Get to Refresh Value after Target Check
2020-08-29 10:20:53.235 Detail, Node005, Queuing (Send) SwitchMultilevelCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x26, 0x02, 0x25, 0x10, 0xf3
2020-08-29 10:20:53.235 Detail, Timer: waiting with timeout 808 ms
2020-08-29 10:20:53.236 Detail,
2020-08-29 10:20:53.236 Info, Node005, Sending (Send) message (Callback ID=0x10, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x26, 0x02, 0x25, 0x10, 0xf3
2020-08-29 10:20:53.236 Info, Node005, Encrypted Flag is 0
2020-08-29 10:20:53.244 Detail, Node005, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-08-29 10:20:53.244 Detail, Node005, ZW_SEND_DATA delivered to Z-Wave stack
2020-08-29 10:20:53.290 Detail, Node005, Received: 0x01, 0x07, 0x00, 0x13, 0x10, 0x00, 0x00, 0x05, 0xfe
2020-08-29 10:20:53.290 Detail, Node005, ZW_SEND_DATA Request with callback ID 0x10 received (expected 0x10)
2020-08-29 10:20:53.290 Info, Node005, Request RTT 53 Average Request RTT 52
2020-08-29 10:20:53.290 Detail, Node005, Expected callbackId was received
2020-08-29 10:20:53.517 Detail, Node005, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x05, 0x05, 0x26, 0x03, 0x4f, 0x00, 0xfe, 0x64
2020-08-29 10:20:53.517 Detail,
2020-08-29 10:20:53.517 Info, Node005, Response RTT 281 Average Response RTT 247
2020-08-29 10:20:53.517 Info, Node005, Received SwitchMultiLevel report: level=79
2020-08-29 10:20:53.518 Detail, Node005, Value Updated: old value=99, new value=79, type=byte
2020-08-29 10:20:53.518 Detail, Node005, Target Value is Set to 0
2020-08-29 10:20:53.518 Info, Timer: adding event in 1000 ms
2020-08-29 10:20:53.518 Detail, Node005, Value Updated: old value=0, new value=0, type=byte
2020-08-29 10:20:53.518 Detail, Node005, Changes to this value are not verified
2020-08-29 10:20:53.518 Detail, Timer: waiting with timeout 526 ms
2020-08-29 10:20:53.519 Detail, Node005, Value Updated: old value=-1, new value=-1, type=int
2020-08-29 10:20:53.519 Detail, Node005, Changes to this value are not verified
2020-08-29 10:20:53.519 Detail, Node005, Expected reply and command class was received
2020-08-29 10:20:53.520 Detail, Node005, Message transaction complete
2020-08-29 10:20:53.520 Detail,
2020-08-29 10:20:53.520 Detail, Node005, Removing current message
2020-08-29 10:20:53.520 Detail, Node005, Notification: ValueRefreshed CC: COMMAND_CLASS_SWITCH_MULTILEVEL Instance: 1 Index: 9
2020-08-29 10:20:53.522 Detail, Node005, Notification: ValueRefreshed CC: COMMAND_CLASS_SWITCH_MULTILEVEL Instance: 1 Index: 5
z2m:Zwave zwave node 5: changed: 38-1-9:Instance 1: Target Value:0 -> 0 +477ms
z2m:Zwave zwave node 5: changed: 38-1-5:Instance 1: Dimming Duration:-1 -> -1 +1ms
2020-08-29 10:20:54.045 Info, Timer: delayed event
2020-08-29 10:20:54.045 Info, Node005, Sending Get to Refresh Value after Target Check
2020-08-29 10:20:54.045 Detail, Node005, Queuing (Send) SwitchMultilevelCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x26, 0x02, 0x25, 0x11, 0xf2
2020-08-29 10:20:54.045 Detail, Timer: waiting with timeout 472 ms
2020-08-29 10:20:54.045 Detail,
2020-08-29 10:20:54.045 Info, Node005, Sending (Send) message (Callback ID=0x11, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x26, 0x02, 0x25, 0x11, 0xf2
2020-08-29 10:20:54.045 Info, Node005, Encrypted Flag is 0
2020-08-29 10:20:54.053 Detail, Node005, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-08-29 10:20:54.053 Detail, Node005, ZW_SEND_DATA delivered to Z-Wave stack
2020-08-29 10:20:54.099 Detail, Node005, Received: 0x01, 0x07, 0x00, 0x13, 0x11, 0x00, 0x00, 0x05, 0xff
2020-08-29 10:20:54.099 Detail, Node005, ZW_SEND_DATA Request with callback ID 0x11 received (expected 0x11)
2020-08-29 10:20:54.099 Info, Node005, Request RTT 53 Average Request RTT 52
2020-08-29 10:20:54.099 Detail, Node005, Expected callbackId was received
2020-08-29 10:20:54.332 Detail, Node005, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x05, 0x05, 0x26, 0x03, 0x4f, 0x00, 0xfe, 0x64
2020-08-29 10:20:54.332 Detail,
2020-08-29 10:20:54.332 Info, Node005, Response RTT 286 Average Response RTT 266
2020-08-29 10:20:54.332 Info, Node005, Received SwitchMultiLevel report: level=79
2020-08-29 10:20:54.332 Detail, Node005, Value Updated: old value=99, new value=79, type=byte
2020-08-29 10:20:54.332 Detail, Node005, Target Value is Set to 0
2020-08-29 10:20:54.332 Info, Timer: adding event in 1000 ms
2020-08-29 10:20:54.333 Detail, Timer: waiting with timeout 185 ms
2020-08-29 10:20:54.333 Detail, Node005, Value Updated: old value=0, new value=0, type=byte
2020-08-29 10:20:54.333 Detail, Node005, Changes to this value are not verified
2020-08-29 10:20:54.333 Detail, Node005, Value Updated: old value=-1, new value=-1, type=int
2020-08-29 10:20:54.333 Detail, Node005, Changes to this value are not verified
2020-08-29 10:20:54.333 Detail, Node005, Expected reply and command class was received
2020-08-29 10:20:54.333 Detail, Node005, Message transaction complete
2020-08-29 10:20:54.333 Detail,
2020-08-29 10:20:54.334 Detail, Node005, Removing current message
2020-08-29 10:20:54.334 Detail, Node005, Notification: ValueRefreshed CC: COMMAND_CLASS_SWITCH_MULTILEVEL Instance: 1 Index: 9
2020-08-29 10:20:54.334 Detail, Node005, Notification: ValueRefreshed CC: COMMAND_CLASS_SWITCH_MULTILEVEL Instance: 1 Index: 5
z2m:Zwave zwave node 5: changed: 38-1-9:Instance 1: Target Value:0 -> 0 +811ms
z2m:Zwave zwave node 5: changed: 38-1-5:Instance 1: Dimming Duration:-1 -> -1 +2ms
2020-08-29 10:20:54.518 Info, Timer: delayed event
2020-08-29 10:20:54.518 Info, Node005, Sending Get to Refresh Value after Target Check
2020-08-29 10:20:54.518 Detail, Node005, Queuing (Send) SwitchMultilevelCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x26, 0x02, 0x25, 0x12, 0xf1
2020-08-29 10:20:54.519 Detail, Timer: waiting with timeout 815 ms
2020-08-29 10:20:54.519 Detail,
Look like it's trying to update itself, but too often... I can't understand what I'm doing wrong :(.
At this moment, I have 573 messages in 38/1/5, and 590 in 38/1/9, increasing... 1 message per second, maybe more...
It'll keep increasing until I restart Zwave2mqtt (last version).
Jeoffreybauvin
on 29 Aug 2020
Try to enable verify changes on those values
Daniel
On 29 Aug 2020, at 12:23, Jeoffrey B. notifications@github.com wrote:

Yes :2020-08-29 10:20:53.044 Detail, Node005, Removing current message
2020-08-29 10:20:53.044 Detail, Node005, Notification: ValueRefreshed CC: COMMAND_CLASS_SWITCH_MULTILEVEL Instance: 1 Index: 9
2020-08-29 10:20:53.044 Detail, Node005, Notification: ValueRefreshed CC: COMMAND_CLASS_SWITCH_MULTILEVEL Instance: 1 Index: 5
z2m:Zwave zwave node 5: changed: 38-1-9:Instance 1: Target Value:0 -> 0 +807ms
z2m:Zwave zwave node 5: changed: 38-1-5:Instance 1: Dimming Duration:-1 -> -1 +1ms
2020-08-29 10:20:53.235 Info, Timer: delayed event
2020-08-29 10:20:53.235 Info, Node005, Sending Get to Refresh Value after Target Check
2020-08-29 10:20:53.235 Detail, Node005, Queuing (Send) SwitchMultilevelCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x26, 0x02, 0x25, 0x10, 0xf3
2020-08-29 10:20:53.235 Detail, Timer: waiting with timeout 808 ms
2020-08-29 10:20:53.236 Detail,
2020-08-29 10:20:53.236 Info, Node005, Sending (Send) message (Callback ID=0x10, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x26, 0x02, 0x25, 0x10, 0xf3
2020-08-29 10:20:53.236 Info, Node005, Encrypted Flag is 0
2020-08-29 10:20:53.244 Detail, Node005, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-08-29 10:20:53.244 Detail, Node005, ZW_SEND_DATA delivered to Z-Wave stack
2020-08-29 10:20:53.290 Detail, Node005, Received: 0x01, 0x07, 0x00, 0x13, 0x10, 0x00, 0x00, 0x05, 0xfe
2020-08-29 10:20:53.290 Detail, Node005, ZW_SEND_DATA Request with callback ID 0x10 received (expected 0x10)
2020-08-29 10:20:53.290 Info, Node005, Request RTT 53 Average Request RTT 52
2020-08-29 10:20:53.290 Detail, Node005, Expected callbackId was received
2020-08-29 10:20:53.517 Detail, Node005, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x05, 0x05, 0x26, 0x03, 0x4f, 0x00, 0xfe, 0x64
2020-08-29 10:20:53.517 Detail,
2020-08-29 10:20:53.517 Info, Node005, Response RTT 281 Average Response RTT 247
2020-08-29 10:20:53.517 Info, Node005, Received SwitchMultiLevel report: level=79
2020-08-29 10:20:53.518 Detail, Node005, Value Updated: old value=99, new value=79, type=byte
2020-08-29 10:20:53.518 Detail, Node005, Target Value is Set to 0
2020-08-29 10:20:53.518 Info, Timer: adding event in 1000 ms
2020-08-29 10:20:53.518 Detail, Node005, Value Updated: old value=0, new value=0, type=byte
2020-08-29 10:20:53.518 Detail, Node005, Changes to this value are not verified
2020-08-29 10:20:53.518 Detail, Timer: waiting with timeout 526 ms
2020-08-29 10:20:53.519 Detail, Node005, Value Updated: old value=-1, new value=-1, type=int
2020-08-29 10:20:53.519 Detail, Node005, Changes to this value are not verified
2020-08-29 10:20:53.519 Detail, Node005, Expected reply and command class was received
2020-08-29 10:20:53.520 Detail, Node005, Message transaction complete
2020-08-29 10:20:53.520 Detail,
2020-08-29 10:20:53.520 Detail, Node005, Removing current message
2020-08-29 10:20:53.520 Detail, Node005, Notification: ValueRefreshed CC: COMMAND_CLASS_SWITCH_MULTILEVEL Instance: 1 Index: 9
2020-08-29 10:20:53.522 Detail, Node005, Notification: ValueRefreshed CC: COMMAND_CLASS_SWITCH_MULTILEVEL Instance: 1 Index: 5
z2m:Zwave zwave node 5: changed: 38-1-9:Instance 1: Target Value:0 -> 0 +477ms
z2m:Zwave zwave node 5: changed: 38-1-5:Instance 1: Dimming Duration:-1 -> -1 +1ms
2020-08-29 10:20:54.045 Info, Timer: delayed event
2020-08-29 10:20:54.045 Info, Node005, Sending Get to Refresh Value after Target Check
2020-08-29 10:20:54.045 Detail, Node005, Queuing (Send) SwitchMultilevelCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x26, 0x02, 0x25, 0x11, 0xf2
2020-08-29 10:20:54.045 Detail, Timer: waiting with timeout 472 ms
2020-08-29 10:20:54.045 Detail,
2020-08-29 10:20:54.045 Info, Node005, Sending (Send) message (Callback ID=0x11, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x26, 0x02, 0x25, 0x11, 0xf2
2020-08-29 10:20:54.045 Info, Node005, Encrypted Flag is 0
2020-08-29 10:20:54.053 Detail, Node005, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-08-29 10:20:54.053 Detail, Node005, ZW_SEND_DATA delivered to Z-Wave stack
2020-08-29 10:20:54.099 Detail, Node005, Received: 0x01, 0x07, 0x00, 0x13, 0x11, 0x00, 0x00, 0x05, 0xff
2020-08-29 10:20:54.099 Detail, Node005, ZW_SEND_DATA Request with callback ID 0x11 received (expected 0x11)
2020-08-29 10:20:54.099 Info, Node005, Request RTT 53 Average Request RTT 52
2020-08-29 10:20:54.099 Detail, Node005, Expected callbackId was received
2020-08-29 10:20:54.332 Detail, Node005, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x05, 0x05, 0x26, 0x03, 0x4f, 0x00, 0xfe, 0x64
2020-08-29 10:20:54.332 Detail,
2020-08-29 10:20:54.332 Info, Node005, Response RTT 286 Average Response RTT 266
2020-08-29 10:20:54.332 Info, Node005, Received SwitchMultiLevel report: level=79
2020-08-29 10:20:54.332 Detail, Node005, Value Updated: old value=99, new value=79, type=byte
2020-08-29 10:20:54.332 Detail, Node005, Target Value is Set to 0
2020-08-29 10:20:54.332 Info, Timer: adding event in 1000 ms
2020-08-29 10:20:54.333 Detail, Timer: waiting with timeout 185 ms
2020-08-29 10:20:54.333 Detail, Node005, Value Updated: old value=0, new value=0, type=byte
2020-08-29 10:20:54.333 Detail, Node005, Changes to this value are not verified
2020-08-29 10:20:54.333 Detail, Node005, Value Updated: old value=-1, new value=-1, type=int
2020-08-29 10:20:54.333 Detail, Node005, Changes to this value are not verified
2020-08-29 10:20:54.333 Detail, Node005, Expected reply and command class was received
2020-08-29 10:20:54.333 Detail, Node005, Message transaction complete
2020-08-29 10:20:54.333 Detail,
2020-08-29 10:20:54.334 Detail, Node005, Removing current message
2020-08-29 10:20:54.334 Detail, Node005, Notification: ValueRefreshed CC: COMMAND_CLASS_SWITCH_MULTILEVEL Instance: 1 Index: 9
2020-08-29 10:20:54.334 Detail, Node005, Notification: ValueRefreshed CC: COMMAND_CLASS_SWITCH_MULTILEVEL Instance: 1 Index: 5
z2m:Zwave zwave node 5: changed: 38-1-9:Instance 1: Target Value:0 -> 0 +811ms
z2m:Zwave zwave node 5: changed: 38-1-5:Instance 1: Dimming Duration:-1 -> -1 +2ms
2020-08-29 10:20:54.518 Info, Timer: delayed event
2020-08-29 10:20:54.518 Info, Node005, Sending Get to Refresh Value after Target Check
2020-08-29 10:20:54.518 Detail, Node005, Queuing (Send) SwitchMultilevelCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x26, 0x02, 0x25, 0x12, 0xf1
2020-08-29 10:20:54.519 Detail, Timer: waiting with timeout 815 ms
2020-08-29 10:20:54.519 Detail,
Look like it's trying to update itself, but too often... I can't understand what I'm doing wrong :(.At this moment, I have 573 messages in 38/1/5, and 590 in 38/1/9, increasing... 1 message per second, maybe more...
It'll keep increasing until I restart Zwave2mqtt (last version).
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or unsubscribe.
robertsLando
on 29 Aug 2020
Thanks for your response. I'm not sure what do you mean, I'm new to Zwave2mqtt.
Jeoffreybauvin
on 29 Aug 2020
Go to settings tab, gateway section, add those values to gateway values table and enable the flag verify changes
Daniel
On 29 Aug 2020, at 17:48, Jeoffrey B. notifications@github.com wrote:

Thanks for your response. I'm not sure what do you mean, I'm new to Zwave2mqtt.—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or unsubscribe.
robertsLando
on 29 Aug 2020
Hi @robertsLando ,
I just did this :
But I have the same behaviour.
I'm not sure what to set in topic :
Do I need to use absolute path ?
Here is what I did :
But no changes at all either.
But now I have this after few seconds :
2020-09-01 19:54:23.687 Info, Node005, Sending (Send) message (Callback ID=0x90, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x26, 0x02, 0x25, 0x90, 0x73
2020-09-01 19:54:23.687 Info, Node005, Encrypted Flag is 0
2020-09-01 19:54:23.695 Detail, Node005, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-09-01 19:54:23.695 Detail, Node005, ZW_SEND_DATA delivered to Z-Wave stack
2020-09-01 19:54:23.904 Detail, Node005, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x05, 0x03, 0x22, 0x02, 0x00, 0xd4
2020-09-01 19:54:23.904 Detail,
2020-09-01 19:54:23.904 Info, Node005, Response RTT 217 Average Response RTT 2835
2020-09-01 19:54:24.057 Detail, Node005, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x05, 0x03, 0x22, 0x02, 0x00, 0xd4
2020-09-01 19:54:24.057 Detail,
2020-09-01 19:54:24.057 Info, Node005, Response RTT 371 Average Response RTT 1603
2020-09-01 19:54:24.269 Detail, Node005, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x05, 0x03, 0x22, 0x02, 0x00, 0xd4
2020-09-01 19:54:24.269 Detail,
2020-09-01 19:54:24.269 Info, Node005, Response RTT 583 Average Response RTT 1093
2020-09-01 19:54:24.342 Detail, Node005, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x05, 0x03, 0x22, 0x02, 0x00, 0xd4
2020-09-01 19:54:24.342 Detail,
2020-09-01 19:54:24.342 Info, Node005, Response RTT 656 Average Response RTT 874
2020-09-01 19:54:28.761 Detail, Node005, Received: 0x01, 0x07, 0x00, 0x13, 0x90, 0x01, 0x01, 0xfc, 0x87
2020-09-01 19:54:28.762 Detail, Node005, ZW_SEND_DATA Request with callback ID 0x90 received (expected 0x90)
2020-09-01 19:54:28.762 Info, Node005, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2020-09-01 19:54:28.762 Warning, Node005, WARNING: Device is not a sleeping node.
2020-09-01 19:54:28.762 Detail, Node005, Expected callbackId was received
2020-09-01 19:54:33.687 Error, Node005, ERROR: Dropping command, expected response not received after 1 attempt(s). Command: "SwitchMultilevelCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x26, 0x02, 0x25, 0x90, 0x73"
2020-09-01 19:54:33.688 Detail, Node005, Removing current message
2020-09-01 19:54:33.688 Detail, Node005, Notification: Notification - TimeOut
z2m:Zwave Notification from node 5: Notification - TimeOut (1) +30s
And it stops sending messages to these 2 topics. But if I'm playing with the cover, it start again sending messages... And they stay in mosquitto :(.
Jeoffreybauvin
on 1 Sep 2020
I'm sorry but based on your logs seems not an issue with z2m, it could be a bug in ozw or your device, firstly check if there is a firmware update for the device, if not try to open this issue on ozw repo to see if someone can help you there. I'm sorry but cannot help you more then this
robertsLando
on 2 Sep 2020
Hi,
I'm quiet new to zwave2mqtt, trying to migrate away from the openhab2 zwave binding.
Since i'm migrating i've pulled one of the FGR223 modules from the wall and placed it next to me for debugging purposes.
I am running the docker "dev" (downloaded yesterday) image on my linux pc to see of things are better on the dev branch, but that seems not to matter.
What is working fine:
- Forcing callibration
- Requesting a position position in topic "zwave2mqtt/nodeID_2/38/1/0/set" with values in range of 0 and 99
What is sort of working:
- Requesting up or or down movement in there topics
* zwave2mqtt/nodeID_2/38/1/1/set (up movement) with value true
* zwave2mqtt/nodeID_2/38/1/2/set (down movement) with value true
But, when i request a STOP by sending false to the two topics above this behaviour is happening, which i try describe below:
I see the light flashing rapidly with the same interval as that the topics are updating on my "ZW090 Z-Stick Gen5 EU (AEON Labs)" .
The following two topics keep up dating indefinitely together with the rapidly flashing of the z-stick
- zwave2mqtt/nodeID_2/38/1/5 "Instance 1: Dimming Duration"
** Only the time-stamp is updating, the value keeps "-1" - zwave2mqtt/nodeID_2/38/1/9 " Instance 1: Target Value"
** Only the timestamp is updating, the value keeps "0"
I Can stop this by sending "true" to the UP or DOWN topic, or requesting a level in the level topic (zwave2mqtt/nodeID_2/38/1/0/set)
Since i am switchting from openhab, the up / stop / down / level commands are working fine there, no rappidly flasing led on the z-stick when stopping movement.
Hope this helps.
ODINServ
on 13 Nov 2020
But, when i request a STOP by sending false to the two topics above
Unfortunally I don't own this device and I don't know what's going on here, Could you enable logging and attach a log that shows this?
robertsLando
on 13 Nov 2020
Thx for the response,
I've noticed a second thing:
When the level reports 99 (up) and you set the "up" topic (38/1/1) to true and later to false, this behavior
is not there.
Same counts for when the level reports 0, and requesting down.
My test network only has one node, the FGR223 module.
Timestamp: 10:16:31.716 send "true" to down command
Timestamp; 10:16:35.105 send "false" to down command
Afthe the 10:16:35.105 timestamp it looks like some timer or something is doing a "SwitchMultilevelCmd_Get" command every 1000 ms since is see "adding event in 1000 ms" in the log.
Hope it helps, keep up the good work!
ODINServ
on 13 Nov 2020
zwave node 2: changed: 38-1-5:Instance 1: Dimming Duration:-1 -> -1
@ODINServ IMO there is a problem with OZW library, the duration shouldn't be integer and is wrongly translated to a negative number. Unfortunally I cannot fix that as it's not on my library. What you could try to do is to use the new project https://github.com/zwave-js/zwavejs2mqtt it is based on a new zwave library
robertsLando
on 13 Nov 2020
Alright!, i will give that a try later today!
ODINServ
on 13 Nov 2020
Stop command works in the zwavejs2mqtt without additional updates (no rapidly flashing led)!
But there i've noticed the new "currentValue" topic only gets updated when i send a new level request and not when it is done, i guess i will write a issue there.
ODINServ
on 13 Nov 2020
@ODINServ Glad it works :) PLease when opening an issue remember to also attach a log file so we can debug what's going on there :)
robertsLando
on 13 Nov 2020
But there i've noticed the new "currentValue" topic only gets updated when i send a new level request and not when it is done, i guess i will write a issue there.
That's Roller Shutter 3, isn't it? AFAIK it should be controlled with the Supervision CC which lets us know when the motor has stopped. If that's not working, something must have broken it, because it 100% worked a while back.
AlCalzone
on 13 Nov 2020
Yes Roller Shutter 3, ive created the issue here: https://github.com/zwave-js/zwavejs2mqtt/issues/16
ODINServ
on 13 Nov 2020
Related issues
magpern
·
7Comments
CaCu15
·
9Comments
chilicheech
·
9Comments
billiaz
·
8Comments
christoph-luebbe
·
8Comments