MQTT - unkown messageId

[Gunduran]

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 (used the search)
• [X] This issue is not described in the adapter documentation / FAQ

Shelly device

Shelly Plus2PM | Id: B8D61A8B8E54 | Firmware: 0.14.1 | Web: 767992a8

Protocol (CoAP / MQTT)

MQTT

The problem

Hallo Zusammen, klasse Adapter. Danke dafür. Jedoch bekomme ich von vorgenanntem Gerät, 2 verschiedene Fehlermeldungen.

shelly.0 | 2023-07-10 19:04:17.623 | warn | [Mqtt.topicPrefix] 192.168.10.200 (shellyplus2pm / shellyplus2pm-b8d61a8b8e54 / shellyplus2pm#b8d61a8b8e54#1): Configured mqtt topic prefix "shellyplus2pm-b8d61a8b8e54" and actual topic prefix "undefined" do not match. Please check configuration Nachdem ich die MQTT Verbindung nochmal eingestellt habe und den notwendigen Reboot verbleibt bei dem Re-Connect jedoch immer noch eine komische Meldung:

shelly.0 | 2023-07-10 19:12:54.148 | info | [MQTT] Client 192.168.10.200 (shellyplus2pm / shellyplus2pm-b8d61a8b8e54 / shellyplus2pm#b8d61a8b8e54#1) received puback for unknown messageId: 2
shelly.0 | 2023-07-10 19:12:53.419 | info | [MQTT] Device with client id "shellyplus2pm-b8d61a8b8e54" connected!
shelly.0 | 2023-07-10 19:12:50.717 | info | [MQTT] Client Disconnect: 192.168.10.200 (shellyplus2pm / shellyplus2pm-b8d61a8b8e54 / shellyplus2pm#b8d61a8b8e54#1)

Letzteres stör mich nicht, wenn jedoch die .... unkown messageId 2 ... nicht der Grund ist, dass irgendetwas nicht stimmt.

Version of nodejs

v16.19.0

Version of ioBroker js-controller

4.0.24

Version of Adapter

v6.4.1

Operating system running ioBroker

Linux on Diskstation Docker

Checklist of files to include below

• [X] iobroker.current.log (Please share the logs in debug mode)
• [ ] Contents of the JavaScript browser console (always include in cases of issues with the user interface)

Additional information & file uploads

2023-10-07 iobroker log.txt

[github-actions[bot]]

Thanks for reporting @Gunduran!

1. Check if this topic is not covered in the documentation
2. Ensure that you use the latest beta version:
3. 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!

[Gunduran]

Hi all, sorry not responding to your answer by time. I've checked the documentation again and do not find any specific hint hwat this could cause... Obviously there are several devices causing it:

2023-11-26 16:22:54.898 | info | [MQTT] Client Disconnect: 192.168.2.33 (shellyplusht / shellyplusht-08b61fcb4938 / shellyplusht#08b61fcb4938#1)
-- | -- | --
shelly.0 | 2023-11-26 16:22:52.404 | info | [MQTT] Client 192.168.2.33 (shellyplusht / shellyplusht-08b61fcb4938 / shellyplusht#08b61fcb4938#1) received puback for unknown messageId: 2
shelly.0 | 2023-11-26 16:22:50.329 | info | [MQTT] Device with client id "shellyplusht-08b61fcb4938" connected!
shelly.0 | 2023-11-26 16:14:35.025 | info | [MQTT] Client 192.168.2.60 (shellyplus1 / shellyplus1-4855199d8d70 / shellyplus1#4855199d8d70#1) received puback for unknown messageId: 2
shelly.0 | 2023-11-26 16:14:33.210 | info | [MQTT] Device with client id "shellyplus1-4855199d8d70" connected!
shelly.0 | 2023-11-26 16:11:48.735 | info | [MQTT] Client Disconnect: 192.168.2.3 (shellyplusht / shellyplusht-08b61fccef9c / shellyplusht#08b61fccef9c#1)
shelly.0 | 2023-11-26 16:11:46.244 | info | [MQTT] Client 192.168.2.3 (shellyplusht / shellyplusht-08b61fccef9c / shellyplusht#08b61fccef9c#1) received puback for unknown messageId: 2
shelly.0 | 2023-11-26 16:11:44.693 | info | [MQTT] Device with client id "shellyplusht-08b61fccef9c" connected!
shelly.0 | 2023-11-26 16:03:00.434 | info | [MQTT] Device with client id "shellytrv-842E14FFC94C" connected!
shelly.0 | 2023-11-26 16:02:58.280 | info | [MQTT] Client Close: 192.168.2.40 (shellytrv / shellytrv-842E14FFC94C / SHTRV-01#842E14FFC94C#1) (false)
shelly.0 | 2023-11-26 15:58:52.434 | info | [MQTT] Client Disconnect: 192.168.2.33 (shellyplusht / shellyplusht-08b61fcb4938 / shellyplusht#08b61fcb4938#1)
shelly.0 | 2023-11-26 15:58:49.940 | info | [MQTT] Client 192.168.2.33 (shellyplusht / shellyplusht-08b61fcb4938 / shellyplusht#08b61fcb4938#1) received puback for unknown messageId: 2
shelly.0 | 2023-11-26 15:58:48.216 | info | [MQTT] Device with client id "shellyplusht-08b61fcb4938" connected!
admin.0 | 2023-11-26 15:55:20.089 | info | ==> Connected system.user.admin from ::ffff:192.168.1.1
shelly.0 | 2023-11-26 15:52:21.439 | info | [MQTT] Client Disconnect: 192.168.2.51 (shellyplusht / shellyplusht-d4d4da7c9a54 / shellyplusht#d4d4da7c9a54#1)
shelly.0 | 2023-11-26 15:52:18.138 | info | [MQTT] Client 192.168.2.51 (shellyplusht / shellyplusht-d4d4da7c9a54 / shellyplusht#d4d4da7c9a54#1) received puback for unknown messageId: 2
shelly.0 | 2023-11-26 15:52:15.050 | info | [MQTT] Device with client id "shellyplusht-d4d4da7c9a54" connected!
shelly.0 | 2023-11-26 15:50:47.445 | info | [MQTT] Client Disconnect: 192.168.2.33 (shellyplusht / shellyplusht-08b61fcb4938 / shellyplusht#08b61fcb4938#1)
shelly.0 | 2023-11-26 15:50:44.950 | info | [MQTT] Client 192.168.2.33 (shellyplusht / shellyplusht-08b61fcb4938 / shellyplusht#08b61fcb4938#1) received puback for unknown messageId: 2
shelly.0 | 2023-11-26 15:50:43.587 | info | [MQTT] Device with client id "shellyplusht-08b61fcb4938" connected!
shelly.0 | 2023-11-26 15:48:16.450 | info | [MQTT] Device with client id "shellytrv-842E14FFC94C" connected!
shelly.0 | 2023-11-26 15:48:14.374 | info | [MQTT] Client Close: 192.168.2.40 (shellytrv / shellytrv-842E14FFC94C / SHTRV-01#842E14FFC94C#1) (false)
shelly.0 | 2023-11-26 15:45:43.021 | info | [MQTT] Client Disconnect: 192.168.2.33 (shellyplusht / shellyplusht-08b61fcb4938 / shellyplusht#08b61fcb4938#1)
shelly.0 | 2023-11-26 15:45:40.528 | info | [MQTT] Client 192.168.2.33 (shellyplusht / shellyplusht-08b61fcb4938 / shellyplusht#08b61fcb4938#1) received puback for unknown messageId: 2
shelly.0 | 2023-11-26 15:45:39.108 | info | [MQTT] Device with client id "shellyplusht-08b61fcb4938" connected!

Looking again to each configuration: ...2.33 and 2.3 are plus ht ==> Perhaps the communication is too fast / the timing is not correct during the uptime of this device. ... for the 2.60 it is outside and the wifi is not the best there -70 to -80 dBM RSSI.

So, from my point of view, it could be a sequence / timing issue.

Funny: The error message is "received puback"... instead of "received pushback" If I could support you to find the issue, please let me know. Best wishes, Gunduran

[Gunduran]

the bot :-) The message is still there...

shelly.0 | 2024-03-17 19:28:35.925 | info | [MQTT] Client Disconnect: 192.168.2.51 (shellyplusht / shellyplusht-d4d4da7c9a54 / shellyplusht#d4d4da7c9a54#1) -- | -- | -- | -- shelly.0 | 2024-03-17 19:28:33.428 | info | [MQTT] Client 192.168.2.51 (shellyplusht / shellyplusht-d4d4da7c9a54 / shellyplusht#d4d4da7c9a54#1) received puback for unknown messageId: 2 shelly.0 | 2024-03-17 19:28:31.671 | info | [MQTT] Device with client id "shellyplusht-d4d4da7c9a54" connected!