Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Plus PM switch output toggles forever #1117

Open
3 tasks done
SaimenSays opened this issue Jan 19, 2025 · 2 comments
Open
3 tasks done

[Bug]: Plus PM switch output toggles forever #1117

SaimenSays opened this issue Jan 19, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@SaimenSays
Copy link

I'm sure that

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

Shelly device

Plus PM2 & PM1

Shelly firmware version

1.4.4

Protocol

MQTT

The problem

Among many others, I have two Gen 2 devices (Plus2PM and Plus1PM). Everything worked fine until an update yesturday. I wanted to start using BLE gateway functionality, but this did not work. So I did an Update to latest stable firmware 1.4.4 on these Shelly.
Also updated iobroker adapter to latest 8.5.1.
Now these two devices behave strange! I can turn the on the output switch on. But first time switching output off, the ouput starts toggling on and off in second interval forever. Only restarting the shelly stops this toggling.

Tried reverting back to adapter 8.4.0, but this did not fix anything. (Unfortunatelly I don't know the verison I started with)
Tried going back to 0.14.x firmware on shelly, but was unable to downgrade. Also tried rc 1.5.0, but did not fix the behavior.

Is this a known error?
Why are there so many "pubrec for unknown messageId"?

iobroker.current.log (in debug mode!)

2025-01-19 22:44:54.333 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubcomp for unknown messageId: 3

2025-01-19 22:44:54.349 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubrec for unknown messageId: 3
2025-01-19 22:44:54.434 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubcomp for unknown messageId: 3
2025-01-19 22:44:54.454 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubrec for unknown messageId: 3
2025-01-19 22:44:54.493 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 3
2025-01-19 22:44:54.500 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubrec for unknown messageId: 3
2025-01-19 22:44:59.350 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubcomp for unknown messageId: 3
2025-01-19 22:44:59.367 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubrec for unknown messageId: 3
2025-01-19 22:44:59.450 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubcomp for unknown messageId: 3
2025-01-19 22:44:59.469 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubrec for unknown messageId: 3
2025-01-19 22:44:59.592 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 3
2025-01-19 22:44:59.615 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:03.020 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 4
2025-01-19 22:45:04.378 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:04.395 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:04.462 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:04.482 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:04.595 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:04.624 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:06.271 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 5
2025-01-19 22:45:07.973 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 4
2025-01-19 22:45:08.000 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubrec for unknown messageId: 4
2025-01-19 22:45:09.386 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:09.402 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:09.477 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:09.496 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:09.506 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:09.530 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:11.249 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 5
2025-01-19 22:45:11.268 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubrec for unknown messageId: 5
2025-01-19 22:45:12.987 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 4
2025-01-19 22:45:13.008 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubrec for unknown messageId: 4
2025-01-19 22:45:14.505 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:14.515 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:14.521 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:14.522 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:14.534 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:14.545 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:16.261 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 5
2025-01-19 22:45:16.282 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubrec for unknown messageId: 5
2025-01-19 22:45:18.005 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 4
2025-01-19 22:45:18.025 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubrec for unknown messageId: 4
2025-01-19 22:45:19.408 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:19.421 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:19.427 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:19.437 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:19.538 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:19.562 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:21.277 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 5
2025-01-19 22:45:21.295 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubrec for unknown messageId: 5
2025-01-19 22:45:23.018 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 4
2025-01-19 22:45:23.042 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubrec for unknown messageId: 4
2025-01-19 22:45:24.304 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:24.333 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:24.422 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:24.442 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:24.551 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:24.574 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:26.290 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 5
2025-01-19 22:45:26.312 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubrec for unknown messageId: 5
2025-01-19 22:45:28.032 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 4
2025-01-19 22:45:28.053 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubrec for unknown messageId: 4
2025-01-19 22:45:29.353 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:29.370 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:29.443 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:29.496 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:29.566 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:29.602 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:30.593 - info: shelly.0 (2160023) [MQTT] Client Close: 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) (false)
2025-01-19 22:45:34.131 - info: shelly.0 (2160023) [MQTT] Device with client id "shellyplus2pm-b8d61a870f54" connected!
2025-01-19 22:45:34.373 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:34.380 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:34.492 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:34.510 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:35.507 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubrec for unknown messageId: 2
2025-01-19 22:45:35.585 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.139 (shellyplus2pm / shellyplus2pm-b8d61a870f54 / shellyplus2pm#b8d61a870f54#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:39.437 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:39.454 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.130 (shellyblugw / shellyblugw-fcb46700c294 / shellyblugw#fcb46700c294#1) received pubrec for unknown messageId: 3
2025-01-19 22:45:39.465 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubcomp for unknown messageId: 3
2025-01-19 22:45:39.484 - info: shelly.0 (2160023) [MQTT] Client 192.168.11.138 (shellyplus1pm / shellyplus1pm-80646fe5a480 / shellyplus1pm#80646fe5a480#1) received pubrec for unknown messageId: 3

Version of nodejs

20.13.1

Version of ioBroker js-controller

7.0.6

Version of adapter

8.5.1

@SaimenSays SaimenSays added the bug Something isn't working label Jan 19, 2025
Copy link

Thanks for reporting a new issue @SaimenSays!

  1. Please ensure your topic is not covered in the documentation
  2. Please attach all necessary log files (in debug mode!), screenshots and other information to reproduce this issue.
  3. Search for the issue topic in other/closed issues to avoid duplicates!
  4. Check the changelog if the issue has already been covered in a previous release

Otherwise this issue will be closed!

@SaimenSays
Copy link
Author

Found an intermediate workaround. Setting QOS = 1 in adapters expert settings seems to help. After a restart, the output is no longer toggled like it is described in the bug report. As soon as I set it back to QOS = 2, the problem apperas again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant