Zwave2mqtt: [question] FGS223 Double Relay (FIBARO System) Double MQTT messages

[besynnerlig]

Running dev version of Zwave2Mqtt in Docker. just bought a couple of Fibaro FGS223 Double Relay devices.

I'm controlling the first channel with a physical wall switch (push button that is only engaged while it is being depressed) and have set up the FGS223 device parameter 20 to "Momentary switch". Pretty straightforward. Nothing else should differ from the default parameters.

If I operate the device by using the physical switch I get a single MQTT message for the switch_binary1 topic. That's expected. However if I command the device programmatically using the Zwave2Mqtt GUI or by issuing a "/set" MQTT message it responds with 2 MQTT messages, e.g.

zwave/utomhus/eluttag/switch_binary1 {"time":1600277360674,"value":false}
zwave/utomhus/eluttag/switch_binary1 {"time":1600277360693,"value":true}

where the first message represents the initial state of the Fibaro device (before sending the command) and the second (20 microseconds later) shows the new state which corresponds to the given command.

Weird isn't it? I'd expect to see a single MQTT message (the latter).

FGS223 is a new device for me so maybe there's some other parameter that I need to set, I can't say but I find it strange that it works differently depending on if I operate the device using a physical switch or sending a command to it. Wouldn't you agree?

Any ideas?

User manual

[robertsLando]

@besynnerlig Try to enable verify changes on that valueid

[besynnerlig]

@besynnerlig Try to enable verify changes on that valueid

Thanks! I've never used verify changes on a value because I don't understand what it actually does. I still don't. Anyway I enabled that for Instance 1: Switch (37-1-0) but it makes no difference. A change from false -> false still happens.

2020-09-17T07:30:53.401865914Z   z2m:Zwave zwave node 141: changed: 37-1-0:Instance 1: Switch:false -> false +63ms
2020-09-17T07:30:53.708775691Z   z2m:Zwave zwave node 141: changed: 37-1-0:Instance 1: Switch:false -> true +308ms

Anything else I can try?

[robertsLando]

What version of z2m are you using? Verify changes does exactly this,
ensures that a change is really a change (true-> false or false-> true)

Il giorno gio 17 set 2020 alle ore 09:41 B Synnerlig <
[email protected]> ha scritto:

@besynnerlig https://github.com/besynnerlig Try to enable verify
changes on that valueid

Thanks! I've never used verify changes on a value because I don't
understand what it actually does. I still don't. Anyway I enabled that for Instance
1: Switch (37-1-0) but it makes no difference. A change from false ->
false still happens.

2020-09-17T07:30:53.401865914Z z2m:Zwave zwave node 141: changed: 37-1-0:Instance 1: Switch:false -> false +63ms
2020-09-17T07:30:53.708775691Z z2m:Zwave zwave node 141: changed: 37-1-0:Instance 1: Switch:false -> true +308ms

Anything else I can try?

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/OpenZWave/Zwave2Mqtt/issues/728#issuecomment-694047798,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACXYHHZMGTJXNY5XG4YHXB3SGG4UFANCNFSM4RPGJJSA
.

--

Daniel Lando - Ufficio Tecnico R&D[email protected]
0424 1863023

Innovation System S.r.l. *
*Via Motton, 83 36061 Bassano del Grappa (VI)

Sede Operativa *
*Via San Giovanni bosco, 2 36022 Cassola (VI)

La presente comunicazione, che potrebbe contenere informazioni riservate
e/o protette da segreto professionale, è indirizzata esclusivamente ai
destinatari della medesima qui indicati. Nel caso in cui abbiate ricevuto
per errore la presente comunicazione, vogliate cortesemente darcene
immediata notizia, rispondendo a questo stesso indirizzo di e-mail/fax, e
poi procedere alla cancellazione di questo messaggio dal Vostro sistema.
Grazie.
This communication, that may contain confidential and/or legally privileged
information, is intended solely for the use of the intended addressees. If
you have received this communication in error, please notify us immediately
by responding to this email /fax and then delete it from your system.
Thanks. Rispetta l'ambiente: se non ti e' necessario, non stampare questa
mail. - Take care of the environment: do not print this mail if not
strengthly requested.

[besynnerlig]

What version of z2m are you using?

I'm using robertslando/zwave2mqtt:dev from 9/15/2020 10:45 am

Verify changes is set:

[robertsLando]

@besynnerlig I remember there was another user with the same problem and AFAIK he resolved it in this way, unfortunally I don't know any other solution, it could be a device error as the event is reported by the device if I receive it, try to check if there is a firmware update for the device

[robertsLando]

Also it could be that the deviuce configuration xml needs a fix: https://github.com/OpenZWave/open-zwave/wiki/CommandClass-Compatibility-Flags

[besynnerlig]

@besynnerlig I remember there was another user with the same problem and AFAIK he resolved it in this way, unfortunally I don't know any other solution, it could be a device error as the event is reported by the device if I receive it, try to check if there is a firmware update for the device

I tried to restart the container as well but it didn't make any difference.

Fibaro devices are only able to be updated using the Fibaro HCL or Fibaro HC2 controllers. Unfortunately I don't own any of those controllers.

Also it could be that the deviuce configuration xml needs a fix: https://github.com/OpenZWave/open-zwave/wiki/CommandClass-Compatibility-Flags

It's beyond my knowledge to fiddle with that. But thanks anyway. Maybe someone else will run into the same problem later. I close the question and try to figure out how to deal with those double messages. Thanks!

[besynnerlig]

Sorry for reopening this question.

I will try to learn how to debug ZWave tomorrow.

I was thinking though that all the MQTT messages for the FGS223 device origins from Z2M.

Z2M sees that the old status of the FGS223 is same as the new status but it still lets it pass through to the MQTT Server ... even though verify changes is set

Switch:false -> false

Why is that?

[robertsLando]

@besynnerlig As I said in my previous comments unfortunally It's not something I can handle, it could be a problem both from OZW or the device firmware.

[besynnerlig]

@besynnerlig As I said in my previous comments unfortunally It's not something I can handle, it could be a problem both from OZW or the device firmware.

OK, thanks. I'll try harder to figure out what's going on.