I’m trying to build a simple smart home based on HomeAssistant.
So far I got a bunch of Comet-DECT (fritzbox based) thermostats, and a bunch of Sonoff S20 switches with tasmota firmware.
The thermostats are auto-enumerated by the HomeAssistant “fritzbox” component, and the sonoffs are MQTT-discovery-enabled and discovered by HomeAssistant built in MQTT broker (as long as they are restarted after every restart of the hass service).
Now they all appear in the web-UI overview, can be nicely controlled, etc.
But I’d like to add simple automation rules for the thermostats, put the switches into groups - stuff that, if I understand correctly, requires the explicit names, attributes etc. of the gadgets.
I’d also like to have the MQTT switches explicitly listed, so I don’t have to rely on the auto discovery that requires the switches to be restarted every time the hass service restarts.
Now what’s the easiest way to obtain the syntax that I have to enter into the config.yaml in order to explicitly cover the gadgets that were discovered before?
I noticed that there is some info about the discovered devices in the .homeassistant/.storage/core.device_registry & entity_registry but it seems to be all over the place and in a different format than the config.yaml.
You can get the list right from the GUI. Click on the menu/hamburger button on left, and select the <> icon.
Then just manually create your sensors and switches. You don’t need to do anything in that case. Take the devices that are autodiscovered, put them in the appropriate sections of the config yaml. That’s it.
You don’t need to do anything to stop auto discovery
You mean the “states” view?
It gives me the info shown below, for one of the switches.
So what exactly do I have to enter into configuration.yaml to have this switch explicitly covered?
(Sorry if this a stupid question, but I’d be surprised if hass can set up this switch with the info “friendly_name” alone).
Yeah I was wondering if there was a way to derive the missing Etc, etc stuff from existing files, since that information must already be there from the auto-discovery. Seems that there isn’t and that stuff must be obtained using trial and error. But thanks anyway!