Can anyone look at this and tell me why FP61. Pillar Left and FP63. Pillar Right are merging into my Kitchen Cabinets? They are separate controllers, and to my knowledge, don’t have anything “shared” or “synced.” When I delete the grouping, it finds them, adds them back separated, but then within a few hours merges them back together. I can’t figure out why they are grouping.
#WLED: merging entities?
1 messages · Page 1 of 1 (latest)
Can you share diagnostic data for these devices?
Hi, thanks, can you point me in the right direction? I assume I'm getting HA logs from the WLED integration? Also, I can just do the Kitchen Left and Pillar Left since the issue seems to be identical for the Right side of things.
Ok, first is the KITCHEN LEFT diagnostics. Then, I'm going to share a screen shot for the PILLAR LEFT, which oddly has TWO entries for WLED, then I'll share the TWO diagnostics for it (one for each entry).
I should specify that the screen shot that has two entries is for PILLAR LEFT (which is on the Front Porch)
bump?
Can you set a static IP address for these devices? Various routers provide DHCP Lease in different way.
If this confirms the problem, the next step is to create a GitHub Issue and describe the ticket.
omg i never saw this update! im going to read about it now and see whats up!
ok, so first, i do dhcp reservation for ALL my devices, especially anything in home assistant, as much as i hate using wifi, its a necessary evil for wled usage
will this PR potentially be in a future release? this is awesome
as im sitting here thinking, it is entirely possible that i used this controller in the past for the kitchen lights and then when i upgraded the kitchen and the wled controller, i moved the old one to the front porch. i had two white controllers, did the upgrade, installed black ones, and the white ones went back into my inventory until i did my front porch. i do have many controllers, so the chances that they aligned PERFECTLY with kitchen 61 becoming front porch 61 (and kitchen 63 becoming front porch 63) is NOT impossible. unlikely but not impossible.
you obviously saw something in the logs that presented this bug and are proposing a change in the PR, possible to give me a high level explanation of what you saw? is there something i should be doing in my network? i'm pretty sure i wiped or at the very least, removed all the names and did new IPs. but maybe home assistant is seeing the old mac somewhere?
I didn't quite know what the solution was, but I was guessing, and then I looked at the code and actually noticed that there was no check for MAC addresses. I also had this problem because I have all my devices connected via DHCP, which confirmed that it's not an isolated problem just on your end.
The problem may only occur temporarily, because Home Assistant first tries to connect via IP address, but then thanks to DHCP Discovery it gets updates and then everything should return to normal.
Here is related to:
https://github.com/home-assistant/core/blob/9668a68c288959f9ed9a1cf9ed5579c59a16914a/homeassistant/components/wled/config_flow.py#L75-L80
It updates CONF_HOST for given mac address.
I'm afraid it won't be merged because the integration maintainer is currently busy.
how do i get them to merge it? do i have to reach out to them directly
I have already written to him, but we just have to wait.
is there a way to force this separation in the meantime? clearly the integration is picking up old information.
You can now delete the configuration and then add it again, and if you have the correct static IP addresses, everything will work.