Comments (5)
from lc7001.
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.
from lc7001.
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.
from lc7001.
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.
from lc7001.
... 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.
from lc7001.
Related Issues (2)
- Tag the source HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from lc7001.