Shelly Plus 1PM is not supported yet
See original GitHub issueUnfortunaly I do not manage to run $ homebridge-shelly describe <ip-address>
. Otherwise I would have posted it here. In any case, I have just installed the new Shelly Plus 1 PM device in my homenetwork. But the Shelly-Plugin does not recognize the new device. All my other (older) shelly devices work just fine on Homebridge. Can you please help anyway ?
Best regards and a Merry Christmas
Björn
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Shelly Plus 1PM is not recognized - Home Assistant Community
I have bought 3 Shelly Plus 1PM devices but cannot add them to Home assistant. They are not automatically recognized. My other Shelly's...
Read more >Shelly Plus 1PM - Shelly Knowledge Base!
Shelly Plus 1PM is a small form factor smart relay with power measurement, which allows remote control of electric appliances through a mobile...
Read more >Shelly support group (English Version) - Facebook
Shelly support group (English Version) ·. Rishi Aggarwal. · May 1 ·. It seems the Shelly Plus 2PM isn't available in the UK...
Read more >CoIoT/CoAP Shelly - #4 by mzanetti - User - nymea:forum
As you already confirmed, the Shelly Plus 1 PM is not supported yet - if you like, i would offer sending you one...
Read more >Schedules not working on Shelly Plus 1PM : r/shellycloud
Hi Guys I am unable to get schedules working on two of my Shelly Plus 1PMs. Firmware: 0.10.3 The relay is supposed to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve created a new plugin for these devices called
homebridge-shelly-ng
. You should use that instead.plugin mentioned above solves the problem in this issue so I believe we can mark it as closed