I changed to my old router yesterday, could that be the issue?
Restarted Homey, router plugs and app several times yes.
I changed to my old router yesterday, could that be the issue?
Restarted Homey, router plugs and app several times yes.
Sounds like your router changed all DHCP reservations, so every Shelly probably has a different IP address.
You where a great help, and you where spot on
changed the IP in homey to the one in the Shelly App and it responded, thank you and have a great Christmas/New Year ![]()
You’re welcome! We’ve all been there
Merry Christmas!
UPDATE: worked after many more attempts … no idea that the reason was …
Cannot add a PlusPlugS with updated Firmware 1.7.1
But the link mentioned works. IP is correct. Never had any problems so far with any other Shelly Plugs (however they had an older firmware when added - maybe that’s the reason?)
{"name":"MyPlug","id":"shellyplusplugs-d4d4daf42488","mac":"D4D4DAF42488","slot":1,"model":"SNPL-00112EU","gen":2,"fw_id":"20250924-062721/1.7.1-gd336f31","ver":"1.7.1","app":"PlusPlugS","auth_en":false,"auth_domain":null}
Hello,
I’m experiencing an issue with the Shelly app where it’s automatically configuring the outbound WebSocket with a malformed URL format on my Gen 3 devices. This appears to be a bug that I am facing in my Homey SHS (self hosted server).
The Problem:
When I add Shelly Gen 3 devices (specifically Shelly 1PM Mini Gen3) to Homey, the outbound WebSocket gets automatically configured as:
ws://192.168.0.138:4:6113/
Note the :4 in the middle - this should be:
ws://192.168.0.138:6113/
The malformed URL causes significant delays in status updates (5+ seconds) because the WebSocket connection fails and Homey falls back to polling. When I manually correct the URL to the proper format, updates become instant as expected with WebSocket push notifications.
Tests Performed:
Initial discovery: Multiple Gen 3 devices all showed the same malformed :4:6113 pattern
Removed and re-added devices: Consistently produces the same malformed URL
Turned off Homey: Disabled Homey temporarily - the configuration remained unchanged during the shutdown period
Manual correction: Changing to ws://192.168.0.138:6113/ temporarily fixes the issue with instant updates
Conclusion:
The evidence points to the Homey Shelly app’s auto-configuration mechanism inserting the :4 during device pairing or WebSocket setup. The biggest problem is that manual correction doesn’t permanently fix the issue - the app continuously overwrites the WebSocket configuration back to the malformed format, making it impossible to maintain a stable WebSocket connection.
Environment:
Homey Pro (Early 2023) - Self-hosted on Unraid
Homey IP: 192.168.0.138
Device: Shelly 1PM Mini Gen3
Shelly App version: [current version as of December 2025]
Expected format: **ws://HOMEY_IP:6113/**
Can anyone understand why the URL construction is adding :4 between the IP address and port 6113, and why the app keeps overwriting manual corrections? This appears to be a string formatting bug in the auto-configuration code.
Thank you!
I’m having the same issue.
On Gen1 devices the CoIoT url is also malformed. It should be :5683, but it is :4
Exactly! That also happens to me on my Shelly dimmers that are also Gen1 devices!
Are you using Homey self host or other version?
self hosted.
I’ve e-mailed the developer of the app, but haven’t got a reply.