I’ve been struggling to figure out how to create and link a Device to an existing Entity for easy automation via UI. I’ve managed to follow some tutorials to load HACs and AlexxIT to search and find my Sonoff (non flashed) plus get my Tile devices to show up on the Entity list. Unfortunately the Automation (via UI) requires these Entities to have a linked Device.
I was unable to find literature on how to edit the configuration.yaml to create a Device on the HA site or in the forums here. maybe i just need help figuring out the right key words to search the answer here???
Can someone point me in the right direction? thanks in advance for your help.
It seems that a lot of the literature references older builds that don’t resemble the latest build i’m running.
Hello! I’m having the same quesion, but due to a bit different reason:
I have a lamp “Xiaomi Philips Smart Candle Light” added to the system through configuration.yaml file and I want to add it to the particular area. I did not find any way to achive this via UI.
@francisp am I correct to imply as well that devices cannot be created from or linked to entities from within the UI or yaml as well?
On that assumption, I decided to emulate an MQTT device for HA discovery of the group. Seems to work. Used one of the zigbee2mqtt group member devices as the json template to publish a retained record and voila - I now have a zigbee2mqtt group in HA as both device and entity, allowing me to set the area. At some point I guess a script would be needed to check for its existing and re-publish if missing (e.g. MQTT database dropped, deletion of retained record, etc.).
Open to suggestions if there’s a better / more efficient way to tackle this. I like the idea of leveraging Area metadata consistently across all objects without these manual misfits. Would be awesome to see a future release of HA which closes the gap on the inability to attribute Area to non-UI / config workflow created entities.
I’ve been bumping against the same thing: Via MQTT Auto discovery I can define entities and define/link them to devices which then opens up functionality in the UI.
However, As far as I can tell there is no way to that from YAML. So I can’t get the same UI benefits for MQTT or REST sensors defined that way.
Hi, not sure if I follow this. Im running into the same problem. Can you explain what you mean with non device automation editor? Like the yaml editor?
Thanks from me, this is the right way, it works for me. I have a Sonoff TH16 with the original firmware and I did automation that monitoring the temperature of its sensor and turns off its switch when exceeded. This function is available in eWelink, but in the HASS you have to create it. Also with the original firmware the relay works independently of the cloud service, so these settings are kept inside it. I have another such relay with Espurna firmware working with MQTT integration - the relay is added as a device and that’s fine, but it cannot be used independently of a home assistant. I don’t know what about the integration and firmware of the Tasmotа - sonoff devices are seen as a device or entities? Sorry for my bad english.
