search

alexryd / node-shellies-ng

Handles communication with the next generation of Shelly devices
GNU General Public License v3.0
14 stars 33 forks source link

Shelly Plus 1 with latest version not discovered #10

Open sbender9 opened 1 year ago

sbender9 commented 1 year ago

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.

konk353535 commented 6 months ago

I'm also getting this problem and device restart is working a treat, did you ever find a work around @sbender9

sbender9 commented 6 months ago

If I recall correctly, I reverted to an older firmware on the Shelly.

bergie commented 6 months ago

@sbender9 do you have a source and a version number for a "known good" firmware?

sbender9 commented 6 months ago

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.

bergie commented 5 months ago

I can confirm that this issue exists still in gen2 firmware 1.3.2

sbender9 commented 5 months ago

We are two years since the last release.has anyone taken this over?

sbender9 commented 5 months ago

@alexryd what are your plans?

SCarns commented 1 week ago

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"?