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]: nach Update auf 7.0.0 funktioniert Shelly vintage Lampe nicht mehr #975

Open
3 tasks done
Biker58 opened this issue Apr 29, 2024 · 5 comments
Open
3 tasks done
Labels
bug Something isn't working fixed Issue fixed, please test

Comments

@Biker58
Copy link

Biker58 commented Apr 29, 2024

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

Shelly vintage

Shelly firmware version

1.14.0

Protocol

MQTT

The problem

Lampe kann nicht mehr gesteuert werden. Mit Adapter Version 6.9.0 funktioniert die Lampe, auch wenn ich von 7.0.0 zurückgehe.

iobroker.current.log (in debug mode!)

shelly.0
2024-04-29 23:58:59.625 error [MQTT] DO NOT CHANGE THE CLIENT-ID OF YOUR SHELLY DEVICES (see adapter documentation for details)
shelly.0
2024-04-29 23:58:59.625 error [MQTT] (Shelly?) device unknown, configuration for client with id "ShellyVintage-98CDAC1F700E" (shellyvintage / ShellyVintage-98CDAC1F700E / undefined) does not exist! Maybe this device is not supported in this adapter version.

Version of nodejs

18.20.2

Version of ioBroker js-controller

5.0.19

Version of adapter

6.17.6

@Biker58 Biker58 added the bug Something isn't working label Apr 29, 2024
Copy link

Thanks for reporting a new issue @Biker58!

  1. Please make sure 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!

Otherwise this issue will be closed.

@klein0r klein0r added the fixed Issue fixed, please test label Apr 30, 2024
klein0r added a commit that referenced this issue Apr 30, 2024
@nemodil
Copy link

nemodil commented May 1, 2024

Same issue for me for all my Shelly devices.
Here one of the error message:

2024-05-01 18:17:51.884 - error: shelly.0 (138609) [MQTT] (Shelly?) device unknown, configuration for client with id "ShellyBulbDuo-664D01" (shellybulbduo / ShellyBulbDuo-664D01 / undefined) does not exist! Maybe this device is not supported in this adapter version.

2024-05-01 18:17:51.884 - error: shelly.0 (138609) [MQTT] DO NOT CHANGE THE CLIENT-ID OF YOUR SHELLY DEVICES (see adapter documentation for details)
2024-05-01 18:17:51.888 - info: shelly.0 (138609) [MQTT] Client Close: (shellybulbduo / ShellyBulbDuo-664D01 / undefined) (false)

@mcm1957 mcm1957 changed the title nach Update auf 7.0.0 funktioniert Shelly vintage Lampe nicht mehr[Bug]: [Bug]: nach Update auf 7.0.0 funktioniert Shelly vintage Lampe nicht mehr May 1, 2024
@nemodil
Copy link

nemodil commented May 6, 2024

Hello again. I don't quite understand, is the issue fixed since marked as fixed?
Here is also a rectification regarding my previous post. Not all Shelly devices have the connection problem, but only the ShellyBulbDuo! Sorry for the incorrect statement. All my other Shelly devices, which have exactly the same MQTT settings (unless I have overlooked something), continue to work without any problem. These are the 1st gen Shelly: DM EM HT IX3 PLG SW25 SWPM, and 2nd gen Plus1 and Plus2pm. The problem does not occur with the Shelly adapter 6.9.0, as described above.
Thanks for any help.

@klein0r
Copy link
Contributor

klein0r commented May 6, 2024

I don't quite understand, is the issue fixed since marked as fixed?

Yes, it's fixed in commit c9e7089 but there was no release since this fix.
Otherwise this issue would be closed.

@nemodil
Copy link

nemodil commented May 6, 2024

Thanks for this info! I Really appreciate your efforts in addressing the issue, especially since this adapter has been incredibly useful for me!

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

No branches or pull requests

3 participants