-
Notifications
You must be signed in to change notification settings - Fork 62
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]: Cache? delete "old"/already existing devices #982
Comments
Thanks for reporting a new issue @numberdotone!
Otherwise this issue will be closed. |
Please share a debug log... |
Does that help? 2024-05-14 21:36:11.561 - info: shelly.0 (7046) Got terminate signal TERMINATE_YOURSELF |
@klein0r How can this debug log help? Are there other ways to provide better information (without a roll back to old versions)? |
I'm sure that
Shelly device
Shelly Mini1PMG3
Shelly firmware version
20240430-105736/1.3.1-gd8534ee
Protocol
MQTT
The problem
The Shelly had work with Shelly adapter version 6.9.0 (or even with 6.8.0) and Shelly firmware 1.2.3 (not sure about the exact "minor" version). At least the device was shown. I tried changing to MQTT Broker/Client adapter (also for an additional Shelly Plus i4 with add-on which worked as well with some additional work). Then I tried to go back to Shelly adapter but without luck. The Shelly was not shown on the adapter (and the log showed some kind of message "device unknown").
In the meantime the Shelly was updated to the latest firmware. Now only after installing adapter version 7.0.0 (manually) I can see the Shelly again. But the device is now followed by a ...#1. Is this normal? Should it be not only shelly.0.shelly1pmminig3#aabbccdd1122 and not shelly.0.shelly1pmminig3#aabbccdd1122#1
I like the Shelly adapter for his convenience very much instead of putting in additional work, keep up this fantastic work!
BTW Client ID was never changed (only device name)
iobroker.current.log (in debug mode!)
No response
Version of nodejs
v18.20.2
Version of ioBroker js-controller
5.0.19
Version of adapter
7.0.0
The text was updated successfully, but these errors were encountered: