Open LarsKumbier opened 1 month ago
Hey there @balloob, @bieniu, @thecode, @chemelli74, @bdraco, mind taking a look at this issue as it has been labeled with an integration (shelly
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
shelly documentation shelly source (message by IssueLinks)
The minimum supported firmware version for Shelly Plug S is 1.9.0 (20201124). You need to update your device.
there is no update available. If this device is too old for the integration, it would be great to have a check and informative message for endusers about that in home assistant
I don't know how to get the hardware revision out of the plug - could you give me a hint on how to see that information? From the invoice I know that I bought the plug in 05/2020.
If the device does not offer an update, you probably need to check your gateway, DNS, or NTP server settings. Another good way to update is to connect the device to a mobile hotspot.
For whatever reason, my shellyplug was stuck on the old firmware and would not find a new firmware on its own - there were no network issues or similar problems. Here's the steps to update anyway, should anyone stumble over this issue with any shelly cloud device.
For reference, you can check out the shelly API manual.
1. Check for a newer firmware available via ota
A status of unknown should never happen.
$ curl http://<shelly-ip>/ota/check
{"status":"unknown","has_update":false,"new_version":"","old_version":"20200601-123307/v1.7.0@d7961837"}%
2. Generate firmware address
Head over to http://archive.shelly-tools.de/ - it will create a link in the form of http://<shelly-ip>/ota?url=http://archive.shelly-tools.de/version/v1.14.0/SHPLG-S.zip
3. Perform update
$ curl 'http://<shelly-ip>/ota?url=http://archive.shelly-tools.de/version/v1.14.0/SHPLG-S.zip'
{"status":"updating","has_update":false,"new_version":"","old_version":"20200601-123307/v1.7.0@d7961837"}
4. Check for successful update
$ curl http://<shelly-ip>/ota
{"status":"idle","has_update":false,"new_version":"20230913-113421/v1.14.0-gcb84623","old_version":"20230913-113421/v1.14.0-gcb84623","beta_version":"20231107-164219/v1.14.1-rc1-g0617c15"}%
This way, you can make the devices compatible with Home-Assistant again.
@bieniu Thank you for your help. What do you think of the suggestion of checking for the minimal supported version of the shelly device during the initialization phase? It should be a simple check against the firmware status, which can be acquired with one api call:
This would make it easier for non-technical users to get around this problem and would future-proof the implementation. Although I have to admit that this might be a fringe problem not happening often enough to warrant this.
What do you think?
When you tried to configure the device you did not see the repair issue in Settings with the content Unsupported firmware for device XXXX
?
No, the error message was "Einrichtung fehlgeschlagen, wird erneut versucht: None" (rough english translation: "setup failed, will try again: None". I can't find the correct translation string in this github repo or organization, but the untranslated "None" at the end seems to indicate something completely different than the "unsupported firmware" you've suggested.
The error message also just occured on the addons-page on the top. I could downgrade to an unsupported version again tomorrow, if it helps with the debugging?
No, the error message was "Einrichtung fehlgeschlagen, wird erneut versucht: None" (rough english translation: "setup failed, will try again: None". I can't find the correct translation string in this github repo or organization, but the untranslated "None" at the end seems to indicate something completely different than the "unsupported firmware" you've suggested.
The repair issue will be created together with showing this error.
The error message also just occured on the addons-page on the top. I could downgrade to an unsupported version again tomorrow, if it helps with the debugging?
Would be good to know if the issue was created so we understand if there is something difference in your case, if not I will try to downgrade a device over the weekend and see if I can reproduce this.
I downgraded one of my devices and the repair issue occurs when I try to configure the device.
Here's how it looks like for me in the shelly integration settings:
So, the message shows up for me too under "repair". However, it never registered for me, since I always check the integration first. I'd suggest to have the much more informative repair-error-message in there as well. What do you think?
So the integration works as intended. IMO the message is quite clear. I don't know what more you would like to see here.
Having a better error-message in the shelly-integration section (instead of the non-sensical "Failed setup, will retry: None", I'd like to get exactly the message that the Repair-Section presents).
From a user-perspective, I've just done an action on the shelly-integration page, the message says "Success!", but the integration page says something about a failed setup, which does not help me in any way. I'd have to stumble upon the much more helpful repair-section in a completely different part of the interface.
A better UX would be to
The problem
I have a shelly plug-s, which I can not integrate into my home assistant:
Environment:
What version of Home Assistant Core has the issue?
core-2024.10.1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
shelly
Link to integration documentation on our website
https://www.home-assistant.io/integrations/shelly/
Diagnostics information
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
I have no knowledge, when the plug worked with the shelly integration, but I know that I did incorporate it into homeassistant somehow. However, this might have been through mqtt.