!QhvgabMQzwEQeWehhZ:lossy.network

NixOS Home Automation

517 Members
Declarative Home Automation and other Sidequests | https://wiki.nixos.org/wiki/Home_Assistant136 Servers

Load older messages


SenderMessageTime
1 Jan 2025
@urbas:matrix.orgMatej Urbas And thanks hexa for the help! 21:15:08
@hexa:lossy.network@hexa:lossy.networknp21:15:24
@hexa:lossy.network@hexa:lossy.network
2025-01-01 22:23:38.645 ERROR (MainThread) [homeassistant.setup] Error during setup of component conversation
Traceback (most recent call last):
  File "/nix/store/441n2qxjgw4sbkvszgxdd6lxljivk01f-homeassistant-2024.12.5/lib/python3.12/site-packages/homeassistant/setup.py", line 416, in _async_setup_component
    result = await task
             ^^^^^^^^^^
  File "/nix/store/441n2qxjgw4sbkvszgxdd6lxljivk01f-homeassistant-2024.12.5/lib/python3.12/site-packages/homeassistant/components/conversation/__init__.py", line 246, in async_setup
    from homeassistant.components.assist_pipeline import (  # pylint: disable=import-outside-toplevel
  File "/nix/store/441n2qxjgw4sbkvszgxdd6lxljivk01f-homeassistant-2024.12.5/lib/python3.12/site-packages/homeassistant/components/assist_pipeline/__init__.py", line 27, in <module>
    from .pipeline import (
  File "/nix/store/441n2qxjgw4sbkvszgxdd6lxljivk01f-homeassistant-2024.12.5/lib/python3.12/site-packages/homeassistant/components/assist_pipeline/pipeline.py", line 54, in <module>
    from .audio_enhancer import AudioEnhancer, EnhancedAudioChunk, MicroVadSpeexEnhancer
  File "/nix/store/441n2qxjgw4sbkvszgxdd6lxljivk01f-homeassistant-2024.12.5/lib/python3.12/site-packages/homeassistant/components/assist_pipeline/audio_enhancer.py", line 7, in <module>
    from pymicro_vad import MicroVad
  File "/nix/store/m9is6wi7d3xgdfhxk6qir7iipl8pi2zz-python3.12-pymicro-vad-1.0.1/lib/python3.12/site-packages/pymicro_vad/__init__.py", line 3, in <module>
    from micro_vad_cpp import MicroVad
ImportError: /nix/store/ybjcla5bhj8g1y84998pn4a2drfxybkv-gcc-13.3.0-lib/lib/libstdc++.so.6: version `CXXABI_1.3.15' not found (required by /nix/store/m9is6wi7d3xgdfhxk6qir7iipl8pi2zz-python3.12-pymicro-vad-1.0.1/lib/python3.12/site-packages/micro_vad_cpp.cpython-312-x86_64-linux-gnu.so)
22:28:27
@hexa:lossy.network@hexa:lossy.networkma27, just the person I want to see 😄 22:28:41
@hexa:lossy.network@hexa:lossy.networkfeels like we can't run home-assistant from master on 24.11 due to the gcc bump22:29:11
@ma27:nicht-so.sexyma27
In reply to @hexa:lossy.network
ma27, just the person I want to see 😄
what?
22:30:15
@hexa:lossy.network@hexa:lossy.networkhm, I thought of glibc, but said gcc and this is gcc 🤦‍♂️22:31:08
@hexa:lossy.network@hexa:lossy.networkargh22:35:46
@hexa:lossy.network@hexa:lossy.networkld preloaded an incompatible libjemalloc22:35:57
@hexa:lossy.network@hexa:lossy.networkshould bring this upstream22:36:10
2 Jan 2025
@hexa:lossy.network@hexa:lossy.network
┃ ├─ ⚠ python3.13-google-auth-2.36.0 on [3] failed with exit code 1 after ⏱ 1m9s
┃ ⏸ home-assistant-chip-wheels-2024.9.0
15:42:45
@hexa:lossy.network@hexa:lossy.networkif you're wondering how google libs fail in 202515:42:55
@hexa:lossy.network@hexa:lossy.network

FAILED tests/test__oauth2client.py::test__convert_appengine_app_assertion_credentials - ModuleNotFoundError: No module named 'cgi'

15:43:01
@hexa:lossy.network@hexa:lossy.networkthey're using dead and removed batteries15:43:09
@hexa:lossy.network@hexa:lossy.networkthis happens because google-auth depends on oauth2client15:47:20
@hexa:lossy.network@hexa:lossy.networkhttps://github.com/googleapis/oauth2client15:47:23
@hexa:lossy.network@hexa:lossy.network

This repository has been archived by the owner on Nov 5, 2019. It is now read-only. You can check out its forks.

15:47:27
@hexa:lossy.network@hexa:lossy.network seems like the author is happy to move forward. https://github.com/NixOS/nixpkgs/pull/369945#pullrequestreview-2527918621 put your thoughts on the PR if you have strong feelings 17:16:18
@hexa:lossy.network@hexa:lossy.network
In reply to @mattleon:matrix.org

I've been using the old version of localtuya 3.5.0 because it was the last version to support yaml config.

Works fine for local control of all the switches I have, but missing some newer device types. Would recommend over any of the other cloud or local UI driven integrations if it has all the needed device types.

*
17:23:16
@urbas:matrix.orgMatej Urbas changed their display name from urbas to Matej Urbas.17:38:22
@laurynasp:matrix.orglaurynasp

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:matrix.orglaurynasp *

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@hexa:lossy.networkreally depends on whether the relevant component offers support for yaml configuration20:04:59
@hexa:lossy.network@hexa:lossy.networkthey are moving device pairings more and more over to configuration flows20:05:30
@laurynasp:matrix.orglaurynasp

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:matrix.orglaurynasp *

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@hexa:lossy.networkyes20:13:49
@laurynasp:matrix.orglaurynasp *

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@kfears:matrix.org left the room.23:57:48
3 Jan 2025
@hexa:lossy.network@hexa:lossy.network qbit: with home-assistant 2025.1.0 the dirigera component will be unbroken 00:57:59

Show newer messages


Back to Room ListRoom Version: 6