Home Assistant integration

[akhudek]

Hey,

I packaged up your home assistant integration so that I could install it easier. It links to your repo, hope you don't mind. Happy to transfer this to you if you want.

https://github.com/akhudek/legrand_rflc

[rtyle]

Thank you Alexander! I am glad someone is using it. I trust that everything is working well for you. I am trying to get this accepted into the core so that this step is unnecessary. Unfortunately/apparently, the work queue of reviewers is quite long and they haven't got to mine yet.

Sadly, the mDNS host LCM1.local doesn't work due to mDNS not working inside home assistant docker containers.

Yes, that is sad. I did not test this. I will not be able to look at this until I return from a trip that I am on. I would have expected the docker container would just do a native name resolution on the hosting platform. So, YMMV depending on the docker implementation and the hosting platform. For Linux, I would have expected this just to work. In my home, I have configured a DNS server with mDNS resolution capability and pointed everything to it through DHCP configuration. Anyway, that is why I allowed for user entry for a name (or IP address). If you do that (apparently, you did), make sure that you set up a static DHCP lease on your DHCP server so that your manually entered name resolution (to IP address) does not break if/when the DHCP server decides to change the IP address. BTW, I also designed it this way so that you can use multiple LC7001s on your LAN. These will collide on the same mDNS name but this collision can be solved as you described. Thanks again. Please keep in touch.

…

On Mon, Oct 25, 2021 at 5:29 AM Alexander Hudek ***@***.***> wrote: Hey, I packaged up your home assistant integration so that I could install it easier. It links to your repo, hope you don't mind. Happy to transfer this to you if you want. https://github.com/akhudek/legrand_rflc — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD2IUFTF5XJY3HV4RFJGJ7DUIVZVLANCNFSM5GVSK4JA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[akhudek]

Seeing this open and close reminded me, I do have some feedback. The light entities this produces don't have an associated device. This makes creating automations with the UI impossible as the UI for whatever reason forces you to select a device for an action. You can of course drop to json to create an automation, but it probably should create a device representing the hub and have the lights associated with it.

I was starting to look into doing that patch myself, but so far haven't figured it out.

[rtyle]

Sadly, the mDNS host LCM1.local doesn't work due to mDNS not working inside home assistant docker containers.

Yes, it seems that the homeassistant docker container only uses its /etc/hosts file and DNS to resolve names. DNS appears to be configured by using the same /etc/resolv.conf as its host.

You can add to the container's /etc/hosts file with the "docker run --add-host" option (see docker documentation).

Alternately, you could configure the docker host's /etc/resolv.conf to a properly configured systemd-resolved implementation which can resolve DNS queries using mDNS.

[akhudek]

Alternately, you could configure the docker host's /etc/resolv.conf to a properly configured systemd-resolved implementation which can resolve DNS queries using mDNS.
Yeah, I may try this. Sadly the home assistant OS doesn't come configured this way, though I recently switched to ubuntu + docker container.

On the topic of devices, I did manage to add both a device for each switch as well as a device for the hub. Originally I was just going to have a device for the hub and have all the light entities attached to it. I couldn't figure out how to link the entities to the hub device though.

What I currently have is each light entity creating a light device (e.g. Porch Switch, Bedroom Dimmer), and those are linked to the hub device using the "via_device" property. That said I'm not at all sure what the hub device adds here, so maybe it's better if I just delete it and have one device for each light?

I could probably spend a bit more time and get the entities linked to the hub device too. Then it would be one device with all entities attached. I'm not sure which approach is better.

[rtyle]

... devices ...

Yes, I see that this is an issue but it is not an issue against this repository.

As I mentioned, I am trying to get the legrand_rflc integration accepted into the home-assistant core.
Reviews are now in progress but I'd rather not complicate them with this unless there is good reason.