Closed caspermltov closed 1 month ago
discovery_prefix: "shelly"
I bet this is wrong.
Using shelly
as a device ID is also a very bad idea. Device ID should be unique.
Hey,
Alright.
Both of them are listed as prefixes, (device_ids: # enter the list of device IDs (MQTT prefixes) here
), which made us hope that we didn't have to list the exact device ids manually.
I will try to remove the discovery prefix, and use unique names, and see if that helps.
That worked. Brilliant. Thanks!
Do you know if we can change the name of the client Id to include spaces and match the name of the device in Shelly?
Currently it gets added with the device type (ie Shelly Pro 3EM) instead of "Solar Panels", which it is called within Shelly.
Do you know if we can change the name of the client Id to include spaces and match the name of the device in Shelly?
Client ID also must be unique, probably it cannot contain spaces, I'm not sure. The best solution is not to change the client ID and leave it as default.
Client ID also must be unique, probably it cannot contain spaces, I'm not sure. The best solution is not to change the client ID and leave it as default.
Perfect, we've done that. We're still not getting the original name from Shelly, but that may not be possible?
It is me being daft, because I am trying to help a friend with HA/Shelly without really having worked with it before.
"Device configuration", does that mean the configuration within shelly, or the configuration of device-ids in the automations.yaml?
We did try changing the second name here "shellypro3em..." to solar panels, but still without luck unfortunately.
"Device configuration", does that mean the configuration within shelly, or the configuration of device-ids in the automations.yaml?
"Device configuration" means the device configuration in the device web panel. I think you configure the device via the Shelly cloud and the configuration looks different there, I don't know, I don't use the cloud. Go to http://<DEVICE_IP>/
and then Settings -> Device name
Awesome!
There is no way to automatically detect every device that connects to MQTT. You have to input the device-ids into the list, manually?
Currently, there is such an option (it was not there when the script was created) but implementing it would be a breaking change for all users, so I don't want to go in this direction.
I see. Thanks for the swift replies. If you end up making a guide or change to allow automatic discovery without whitelisting,can you ping me, if you remember?
Sure
Describe the bug Upon running the
Shellies Announce Gen2
automation, we can trace the output of the subsequentShellies Discovery Gen2
that is being called.We can see that the shellies are being found. The log file from MQTT itself, also suggest so:
However, no devices show up under MQTT.
Are we doing something wrong? as far as I can tell, we have followed the instructions in the readme, and have spent a few hours trying to debug it ourselves.
However, we still see no devices within MQTT.
Expected behavior The 3 shellies to show up in MQTT
Versions:
Shellies Discovery GEN2 automation:
Shelly device MQTT settings:
Debug log: