[Bug]: adapter send command "close" twice via MQTT to shelly 2.5 (Version1)

[fred0815]

I'm sure that

• [X] This issue is still present in the current beta version of this adapter
• [X] There is no other (open) issue with the same topic (use the search!)
• [X] This issue is not described in the adapter documentation / FAQ (read the docs!)

Shelly device

shelly 2.5 (Version1)

Shelly firmware version

20230913-112234/v1.14.0-gcb84623

Protocol

MQTT

The problem

send command "close" and "open" twice to shelly adapter via VIS (jqui -ctrl - icon - state)

iobroker.current.log (in debug mode!)

2024-01-29 09:08:57.009 - debug: shelly.0 (32093) [mqtt controlFunction] Executing state.mqtt.mqtt_cmd_funct of state SHSW-25#84CCA8B11B68#1.Shutter.Close for 192.168.179.12 (shellyswitch25 / shellyswitch25-84CCA8B11B68 / SHSW-25#84CCA8B11B68#1) with value: false -> close 2024-01-29 09:08:57.009 - debug: shelly.0 (32093) [MQTT] Send state to 192.168.179.12 (shellyswitch25 / shellyswitch25-84CCA8B11B68 / SHSW-25#84CCA8B11B68#1) with QoS 1: shellies/shellyswitch25-84CCA8B11B68/roller/0/command = close (6) 2024-01-29 09:08:57.027 - debug: shelly.0 (32093) [MQTT] Publish: 192.168.179.12 (shellyswitch25 / shellyswitch25-84CCA8B11B68 / SHSW-25#84CCA8B11B68#1) - topic: shellies/shellyswitch25-84CCA8B11B68/roller/0, qos: 0, payload: close 2024-01-29 09:08:57.029 - debug: shelly.0 (32093) [MQTT] State change 192.168.179.12 (shellyswitch25 / shellyswitch25-84CCA8B11B68 / SHSW-25#84CCA8B11B68#1): shellies/shellyswitch25-84CCA8B11B68/roller/0 -> state: SHSW-25#84CCA8B11B68#1.Shutter.state, value: "close" 2024-01-29 09:08:57.030 - debug: shelly.0 (32093) [MQTT] Publish: 192.168.179.12 (shellyswitch25 / shellyswitch25-84CCA8B11B68 / SHSW-25#84CCA8B11B68#1) - topic: shellies/shellyswitch25-84CCA8B11B68/roller/0/pos, qos: 0, payload: -1 2024-01-29 09:08:57.031 - debug: shelly.0 (32093) [MQTT] Publish: 192.168.179.12 (shellyswitch25 / shellyswitch25-84CCA8B11B68 / SHSW-25#84CCA8B11B68#1) - topic: shellies/shellyswitch25-84CCA8B11B68/roller/0/stop_reason, qos: 0, payload: normal 2024-01-29 09:08:57.261 - debug: shelly.0 (32093) [httpIoBrokerState] State change 192.168.179.21 (shellyuni / shellyuni-34945477DFFD / SHUNI-1#34945477DFFD#1): state: SHUNI-1#34945477DFFD#1.uptime, value: 4143514 2024-01-29 09:08:57.819 - debug: shelly.0 (32093) [httpIoBrokerState] State change 192.168.179.22 (shellyplus1 / shellyplus1-7c87ce7257e0 / shellyplus1#7c87ce7257e0#1): state: shellyplus1#7c87ce7257e0#1.uptime, value: 8082594 2024-01-29 09:08:57.980 - debug: shelly.0 (32093) [httpIoBrokerState] State change 192.168.179.15 (shellyrgbw2 / shellyrgbw2-807FE9 / SHRGBW2#807FE9#1): state: SHRGBW2#807FE9#1.uptime, value: 207124 2024-01-29 09:08:58.017 - debug: shelly.0 (32093) [onStateChange] "shelly.0.SHSW-25#84CCA8B11B68#1.Shutter.Close" state changed: {"val":false,"ack":false,"ts":1706515738012,"q":0,"c":"script.js.common.Automatik_Zimmer_Rollos","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1706515181596} - forwarding to objectHelper 2024-01-29 09:08:58.018 - debug: shelly.0 (32093) [mqtt controlFunction] Executing state.mqtt.mqtt_cmd_funct of state SHSW-25#84CCA8B11B68#1.Shutter.Close for 192.168.179.12 (shellyswitch25 / shellyswitch25-84CCA8B11B68 / SHSW-25#84CCA8B11B68#1) with value: false -> close 2024-01-29 09:08:58.018 - debug: shelly.0 (32093) [MQTT] Send state to 192.168.179.12 (shellyswitch25 / shellyswitch25-84CCA8B11B68 / SHSW-25#84CCA8B11B68#1) with QoS 1: shellies/shellyswitch25-84CCA8B11B68/roller/0/command = close (7) 2024-01-29 09:08:58.301 - debug: shelly.0 (32093) [MQTT] Publish: 192.168.179.12 (shellyswitch25 / shellyswitch25-84CCA8B11B68 / SHSW-25#84CCA8B11B68#1) - topic: shellies/shellyswitch25-84CCA8B11B68/roller/0/pos, qos: 0, payload: -1 2024-01-29 09:08:58.304 - debug: shelly.0 (32093) [MQTT] Publish: 192.168.179.12 (shellyswitch25 / shellyswitch25-84CCA8B11B68 / SHSW-25#84CCA8B11B68#1) - topic: shellies/shellyswitch25-84CCA8B11B68/roller/0/stop_reason, qos: 0, payload: normal 2024-01-29 09:08:58.309 - debug: shelly.0 (32093) [MQTT] Publish: 192.168.179.12 (shellyswitch25 / shellyswitch25-84CCA8B11B68 / SHSW-25#84CCA8B11B68#1) - topic: shellies/shellyswitch25-84CCA8B11B68/roller/0/pos, qos: 0, payload: -1 2024-01-29 09:08:58.312 - debug: shelly.0 (32093) [MQTT] Publish: 192.168.179.12 (shellyswitch25 / shellyswitch25-84CCA8B11B68 / SHSW-25#84CCA8B11B68#1) - topic: shellies/shellyswitch25-84CCA8B11B68/roller/0/stop_reason, qos: 0, payload: normal 2024-01-29 09:08:58.315 - debug: shelly.0 (32093) [MQTT] Publish: 192.168.179.12 (shellyswitch25 / shellyswitch25-84CCA8B11B68 / SHSW-25#84CCA8B11B68#1) - topic: shellies/shellyswitch25-84CCA8B11B68/roller/0/pos, qos: 0, payload: -1 2024-01-29 09:08:58.317 - debug: shelly.0 (32093) [MQTT] Publish: 192.168.179.12 (shellyswitch25 / shellyswitch25-84CCA8B11B68 / SHSW-25#84CCA8B11B68#1) - topic: shellies/shellyswitch25-84CCA8B11B68/roller/0/stop_reason, qos: 0, payload: normal shelly command twice.log

Version of nodejs

v18.17.1

Version of ioBroker js-controller

5.0.17

Version of adapter

6.7.0

[github-actions[bot]]

Thanks for reporting a new issue @fred0815!

1. Please make sure your topic is not covered in the documentation
2. Ensure that you use the latest beta version (not the current stable version): 6.7.0
3. Please attach all necessary log files (in debug mode!), screenshots and other information to reproduce this issue
4. Search for the issue topic in other/closed issues to avoid duplicates!

---

Otherwise this issue will be closed.

[fred0815]

changed QoS to "2" and the adapter send the command only once.

[fred0815]

May be it it could be a correct technical behavior that the command will be send twice. From a perspective of the enduser, the quality of "service" is not really good, if the shelly stucks because he received the command "stop" or "up" or "down" twice.