| 2 Jan 2025 |
|  Matej Urbas changed their display name from urbas to Matej Urbas. | 17:38:22 |
 laurynasp | Is there a way to add devices (e.g. esp32 dev boards and/or Xiaomi_ble compatible devices such as LYWSD03MMC) to home-assistant, declaratively (or at least problematically) rather than via UI?
I can see my esp32 dev board, and my LYWSD03MMC sensors on home-assistant device discovery page, but I do not want to use UI to configure it.
I have stumbled across the following message from moderator from a year ago
MQTT discovery and MQTT yaml are the only yaml integrations that can create devices.
on https://community.home-assistant.io/t/create-device-manually-via-yaml/487457/7
Am I misunderstanding smth, or is it really not possible to deploy a new working home-assistant instance without the need to manually add devices via UI?
| 20:02:49 |
| laurynasp | * Is there a way to add devices (e.g. esp32 dev boards and/or Xiaomi_ble compatible devices such as LYWSD03MMC) to home-assistant, declaratively (or at least problematically) rather than via UI?
I can see my esp32 dev board, and my LYWSD03MMC sensors on home-assistant device discovery page, but I do not want to use UI to configure it.
I have stumbled across the following message from moderator from a year ago
MQTT discovery and MQTT yaml are the only yaml integrations that can create devices.
on https://community.home-assistant.io/t/create-device-manually-via-yaml/487457/7
Am I misunderstanding smth, or is it really not possible to deploy a new working home-assistant instance without the need to manually add devices via UI?
If there is really no way in home-assistant to do this, is there a recommended way in nix(OS) to alter device registry file etc?
| 20:04:35 |
 @hexa:lossy.network | really depends on whether the relevant component offers support for yaml configuration | 20:04:59 |
| @hexa:lossy.network | they are moving device pairings more and more over to configuration flows | 20:05:30 |
| laurynasp | Does it mean that if I see the following messages, I am out of luck in both cases?
ERROR (MainThread) [homeassistant.components.sensor] The xiaomi_ble platform for the sensor integration does not support platform setup. Please remove it from your config
ERROR (MainThread) [homeassistant.helpers.config_validation] The esphome integration does not support YAML setup, please remove it from your configuration file
| 20:10:29 |
| laurynasp | * Does it mean that if I see the following messages, I am out of luck in both cases?
Or is it just me doing it at the wrong "layer"? I haven't really seen any docs about this on HA websites
ERROR (MainThread) [homeassistant.components.sensor] The xiaomi_ble platform for the sensor integration does not support platform setup. Please remove it from your config
ERROR (MainThread) [homeassistant.helpers.config_validation] The esphome integration does not support YAML setup, please remove it from your configuration file
| 20:13:35 |
| @hexa:lossy.network | yes | 20:13:49 |
| laurynasp | * Is there a way to add devices (e.g. esp32 dev boards and/or Xiaomi_ble compatible devices such as LYWSD03MMC) to home-assistant, declaratively (or at least programatically) rather than via UI?
I can see my esp32 dev board, and my LYWSD03MMC sensors on home-assistant device discovery page, but I do not want to use UI to configure it.
I have stumbled across the following message from moderator from a year ago
MQTT discovery and MQTT yaml are the only yaml integrations that can create devices.
on https://community.home-assistant.io/t/create-device-manually-via-yaml/487457/7
Am I misunderstanding smth, or is it really not possible to deploy a new working home-assistant instance without the need to manually add devices via UI?
If there is really no way in home-assistant to do this, is there a recommended way in nix(OS) to alter device registry file etc?
| 20:18:14 |
|  @kfears:matrix.org left the room. | 23:57:48 |
| 3 Jan 2025 |
| @hexa:lossy.network | qbit: with home-assistant 2025.1.0 the dirigera component will be unbroken | 00:57:59 |
 @qbit:tapenet.org | \o/ rad | 00:58:23 |
|  elikoga changed their display name from elikoga (@38c3 📞488{0,1,9}) to elikoga. | 10:28:15 |
 K900 | https://blog.davidedmundson.co.uk/blog/adding-home-automation-to-kde/ | 12:47:16 |
| @hexa:lossy.network | ohhhh, i need dis | 12:48:49 |
| K900 | Should be a pretty easy build | 12:49:54 |
| @hexa:lossy.network | except, what I actually need is to expose dcci to home-assistant | 12:50:00 |
| K900 | We've reenabled DDC backlight controls on Plasma now | 12:51:01 |
| @hexa:lossy.network | monitor control for scenes would be amazing | 12:51:02 |
| K900 | So technically it could work | 12:51:08 |
| @hexa:lossy.network | but also powering it down | 12:51:10 |
| @hexa:lossy.network | https://github.com/esphome/home-assistant-voice-pe/issues/261 | 15:22:43 |
| @hexa:lossy.network | IoT devices shoulld support IPv6, change my view | 15:23:05 |
 Frédéric Christ | I don't think you can call it IoT if it doesn't support IPv6. | 17:53:40 |
| @hexa:lossy.network | https://github.com/Koenkk/zigbee2mqtt/discussions/24198 | 22:34:41 |
| 4 Jan 2025 |
|  macaroniskengz joined the room. | 00:01:21 |
| macaroniskengz | What is recommended, OCI containers or NixOS containers with HASS NixOS module? | 00:02:48 |
 mjm | Do you need containers at all? | 02:57:02 |
| macaroniskengz | I need at least some kind of isolation since I don't trust all components of my smart home installation | 20:39:35 |
| mjm | what components are you running here that you don't trust? | 20:40:23 |
