-
Notifications
You must be signed in to change notification settings - Fork 14
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 app discovers already added devices. #229
Comments
I can not reproduce. Could you post a screenshot of the details of a device in the developer console that is being discovered again. |
Hi,
An examle of two occurrences of the same device.
********From the Shelly diag*********
{
"web_id": "240213111718-ce341dc8-HEAD",
"deviceInfo": {
"name": "Multiswitch",
"id": "shellyplusi4-c049ef89dd68",
"mac": "C049EF89DD68",
"slot": 0,
...
************************
This is the original
[PastedGraphic-1.png]
This is the ”rediscovered"
[PastedGraphic-2.png]
Best Regards, Valter
27 juni 2024 kl. 19:06 skrev Jelger Haanstra ***@***.***>:
I can not reproduce. Could you post a screenshot of the details of a device in the developer console<https://tools.developer.homey.app/tools/devices> that is being discovered again.
—
Reply to this email directly, view it on GitHub<#229 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AH237O4XTC6JKC2IS45SYKDZJRBCLAVCNFSM6AAAAABJ7U2GN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJVGIZTGOBUGI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
You need to respond on Guthub if you want the images to show up. |
What version of the Shelly app on Homey are you using? I use the hostname of the device as unique ID. Some time ago Shelly changed the hostnames of the Shelly devices and added This is the first time I see an issue with this again and it seems to be because the hostname of the Your solution however is removing the device without the .local. |
Hi, |
I have restarted Homey but the issue still exist.
Best Regards, Valter
The text was updated successfully, but these errors were encountered: