| 4 Dec 2024 |
 @hexa:lossy.network | an MQTT device 😄 | 20:10:23 |
 CRTified | In a similar vain, you can also use e.g. esphome.io via MQTT instead of the native API, which behaves the same from the perspective of HA | 20:10:49 |
| CRTified | In reply to @hexa:lossy.network
an MQTT device 😄 true, HA will list them as device within the MQTT Integration | 20:11:16 |
| CRTified | In reply to @crtified:crtified.me
In a similar vain, you can also use e.g. esphome.io via MQTT instead of the native API, which behaves the same from the perspective of HA But for this example, HA won't "know" the difference between a device integrated via wifi on MQTT or via zigbee and z2m to MQTT | 20:11:54 |
 netpleb | In reply to @crtified:crtified.me
But for this example, HA won't "know" the difference between a device integrated via wifi on MQTT or via zigbee and z2m to MQTT ok, so when I go into HA right now and look at the MQTT integration it tells me that there is "localhost" with 1 device. When I click on that 1 device it tells me Bridge by Zigbee2MQTT Firmware: 1.41.0 Hardware: zStack3x0 20210708 | 20:17:45 |
| netpleb | so I think I'm basically done, right? now I just need to add some zigbee sensors and hopefully it will work | 20:18:13 |
| CRTified | Yeah | 20:18:18 |
| CRTified | That looks promising | 20:18:20 |
| CRTified | That what you're seeing is essentially a device that represents the state of the controller, i.e. zigbee2mqtt | 20:18:44 |
| 5 Dec 2024 |
|  Danny Gerhardt joined the room. | 09:58:09 |
|  contribulatorius joined the room. | 14:59:47 |
| 6 Dec 2024 |
|  thursdaddy joined the room. | 18:39:21 |
| 7 Dec 2024 |
|  boman19 joined the room. | 05:41:53 |
| @hexa:lossy.network | ok, I prepared home-assistant on top of staging-next for now | 15:44:09 |
| @hexa:lossy.network | 2024.12.1 | 15:44:18 |
| @hexa:lossy.network | https://www.home-assistant.io/blog/2024/12/04/release-202412/ | 17:23:03 |
|  alex-nt joined the room. | 19:17:42 |
| alex-nt | Oh, this is exactly what I was looking for (to be ran on a RPI5 + SkyConnect). Is there any repo with the last version? Were you able to use it in HA? | 19:20:39 |
| 9 Dec 2024 |
|  Coelacanthus 🆋 changed their profile picture. | 08:08:09 |
| 10 Dec 2024 |
| @hexa:lossy.network | https://github.com/home-assistant/core/issues/99218 | 17:46:08 |
| @hexa:lossy.network | fucking finally | 17:46:10 |
| @hexa:lossy.network | this will make the 3.13 migration much easier | 17:46:16 |
| @hexa:lossy.network | 3.12 support will run out in 2025.2 | 17:46:25 |
| @hexa:lossy.network | * their 3.12 support will run out in 2025.2 | 17:46:30 |
 dotlambda | In reply to @hexa:lossy.network
this will make the 3.13 migration much easier Do you have a list of HA dependencies that currently don't build on 3.13? | 22:21:37 |
| @hexa:lossy.network | sorry, I don't remember | 22:46:18 |
| 11 Dec 2024 |
| @hexa:lossy.network | https://github.com/NixOS/nixpkgs/pull/364068 😢 | 00:49:34 |
| @hexa:lossy.network | this will be a big loss to home-assistant maintenance, since people will keep bumping dependencies and nixpkgs-review will not run the related home-assistant test, thereby quietly breaking component support | 00:50:16 |
| @hexa:lossy.network | * this will be a big loss to home-assistant maintenance, since people will keep bumping dependencies and nixpkgs-review will not run the related home-assistant tests, thereby quietly breaking component support | 00:50:40 |
 ethan | Am I reading this right that the only thing that would really fix their issue is merging all the ha tests back into one causing all of them to run on small changes? (Essentially reverting #155060) | 04:35:43 |
