-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Shelly Plus 1 with latest version not discovered #10
Comments
I'm also getting this problem and device restart is working a treat, did you ever find a work around @sbender9 |
If I recall correctly, I reverted to an older firmware on the Shelly. |
@sbender9 do you have a source and a version number for a "known good" firmware? |
I can't get to the device right now, but can check for sure later today. But I think it was that latest 1.x that worked, v2.x didn't. It's also possible that this has been fixed in newer 2.x, it's been a while since I tried. |
I can confirm that this issue exists still in gen2 firmware 1.3.2 |
We are two years since the last release.has anyone taken this over? |
@alexryd what are your plans? |
It still does this, even with the newest firmware. My solution was a node red flow that reboots all my shelly's upon restart of SK. Not very elegant, but it works. Is there a different command to make the shelly's re-announce themselves besides "Shelly.Reboot"? |
The device is not discovered initially. If I restart the device after discovery is started, then it is found.
the mdns discovery stuff only gets the PTR record, no A record. On restarting the device, it gets all the expected records.
Not sure if this is an issue with the new firmware or an issue with the mdns discovery library.
The text was updated successfully, but these errors were encountered: