| 20 Aug 2024 |
|  @benjaminedwardwebb:envs.net changed their display name from benjaminedwardwebb to benwebb. | 12:44:19 |
|  @shymega:one.ems.host left the room. | 13:17:43 |
|  alex left the room. | 19:34:38 |
| alex joined the room. | 19:42:59 |
| 21 Aug 2024 |
|  mfmcl joined the room. | 13:54:01 |
| mfmcl left the room. | 13:54:17 |
| mfmcl joined the room. | 13:55:26 |
| 22 Aug 2024 |
 hexa | https://github.com/NixOS/nixpkgs/pull/336426 | 00:00:23 |
| hexa | if anyone uses music-assistant | 00:00:28 |
| hexa | * if anyone uses music-assistant, feel free to review | 00:00:32 |
 mjm | I do and I will | 00:24:52 |
|  Alex changed their display name from Alexander Krimm to Alexander. | 13:19:25 |
| Alex changed their display name from Alexander to Alex. | 13:20:00 |
 rcambrj | howdy folks, is esphome known to work or not work on services.home-assistant ? if I put it in the YAML, hass complains that esphome doesn't support YAML, if I click add integration in the GUI, I get Config flow could not be loaded: {"message":"Invalid handler specified"} :/ | 18:45:42 |
| mjm | do you have "esphome" in services.home-assistant.extraComponents? | 18:47:21 |
| rcambrj | oh I did, but I don't, let me readd it back 🤦♂️ | 18:48:02 |
| mjm | yeah it'll make sure it has the deps available that it needs, then you should be able to add it in the GUI | 18:48:27 |
| rcambrj | I added it, but it still errors in the same way :( am I to assume that this is home-assistant's I'm lacking a dependency complaint? | 18:49:42 |
| rcambrj | Error occurred loading flow for integration esphome: No module named 'aiodhcpwatcher'
yes. yes it is.
thanks mjm ⭐️ | 18:50:23 |
| hexa | probably going to rename extraComponents to components or integrations some time soon | 18:53:05 |
| hexa | the extra prefix makes it a bit more misleading these days | 18:53:27 |
| mjm | yeah +1 for that | 18:54:26 |
| rcambrj | my problem was that I had removed default_config and enumerated the individual things I wanted
but I had to add default_config back to extraComponents to get the deps which the esphome package expected to be available already | 18:59:29 |
| rcambrj | progressing now 👍️ thanks again | 18:59:43 |
| hexa | you can enumerate default_config manually, but if you miss a crucial piece it might break | 19:00:03 |
| rcambrj | I don't mind default_config in extraComponents - it's not enabling those components, just providing the deps | 19:00:31 |
| hexa | nix```
services.home-assistant.config = {
# opinionated default_config
bluetooth = {};
config = {};
dhcp = {};
logbook = {};
history = {};
media_source = {};
mobile_app = {};
person = {};
scene = {};
system_health = {};
ssdp = {};
sun = {};
script = {};
tag = {};
timer = {};
zeroconf = {}; | 19:00:33 |
| hexa | * services.home-assistant.config = {
# opinionated default\_config
bluetooth = {};
config = {};
dhcp = {};
logbook = {};
history = {};
media\_source = {};
mobile\_app = {};
person = {};
scene = {};
system\_health = {};
ssdp = {};
sun = {};
script = {};
tag = {};
timer = {};
zeroconf = {};
| 19:00:37 |
| hexa | * services.home-assistant.config = {
# opinionated default\_config
bluetooth = {};
config = {};
dhcp = {};
logbook = {};
history = {};
media_source = {};
mobile_app = {};
person = {};
scene = {};
system_health = {};
ssdp = {};
sun = {};
script = {};
tag = {};
timer = {};
zeroconf = {};
| 19:00:45 |
| hexa | I just don't like having the cloud dep 😛 | 19:01:03 |
