| 11 Jan 2025 |
 @rick:matrix.ciphernetics.nl | Pondering to switch from ZHA to Zigbee2Mqtt after moving to my new house | 14:27:18 |
 macaroniskengz | Why is that? I come from Zigbee2MQTT Docker setup | 14:32:59 |
| macaroniskengz | * Why is that? I come from Zigbee2MQTT Docker setup and like to check whether it makes sense to move to ZHA | 14:35:53 |
| macaroniskengz | Is NixOS Home Assistant packaging enough to replace HACS? | 14:42:23 |
 K900 | You can always add things if we don't have them | 14:47:04 |
| K900 | (assuming you're willing to maintain them) | 14:47:10 |
 DavHau | My home-assistant doesn't build anymore:
getting things like
error: numpy-1.26.4 not supported for interpreter python3.13
| 15:28:58 |
| DavHau | (haven't checked master yet) | 15:29:06 |
 @hexa:lossy.network | heh 🤔 | 15:29:14 |
| @hexa:lossy.network | what commit? | 15:29:54 |
| @hexa:lossy.network | c4c07753b9eefa9798c7ea3b209dc2fec434fb8d migrated us to numpy 2 | 15:49:07 |
| @hexa:lossy.network | that was during the 2024.12.1 upgrade | 15:49:21 |
| @hexa:lossy.network | on 2024-12-09 | 15:49:28 |
| @hexa:lossy.network | d5fc8adbbe607a78fd933729570a8e6e7475dece migrated us to python313 | 15:49:59 |
| @hexa:lossy.network | around the 2025.1.0 release on 2024-01-05 | 15:50:15 |
| @hexa:lossy.network | so I'm not sure how you are before 2024-12-09 and after 2025-01-05 at the same time 🤔 | 15:50:35 |
| @hexa:lossy.network | * around the 2025.1.0 release on 2025-01-05 | 15:50:39 |
| @hexa:lossy.network | possibly some downstream components? | 15:50:58 |
|  oak 🏳️🌈♥️ changed their profile picture. | 16:45:34 |
| oak 🏳️🌈♥️ changed their profile picture. | 16:46:35 |
 uep | zha here | 23:25:05 |
| @hexa:lossy.network | z2m | 23:25:25 |
| 12 Jan 2025 |
|  strutztm joined the room. | 00:21:20 |
| @rick:matrix.ciphernetics.nl | My main reason to switch would be more device support. Had to wait for 2025.1 for better support for some devices and generally zigbee2mqtt seems more hacker-minded and hacker-friendly | 00:37:00 |
| @hexa:lossy.network | yeah, much more introspection | 00:37:34 |
| @hexa:lossy.network | * yeah, much more introspection into the zigbee network was the reason I chose z2m | 00:37:46 |
 teto | started with zha since that was the default ?! but quickly switched to z2m as it supported more of my devices (and in general it supports more from what I read). Has been pretty good so far. It took hours to draw a map of my 10 devices network but that must be an issue with the network rather than z2m, which is why I was tempted to test version 2 before reporting some feature requests | 01:29:11 |
| teto | hexa: please share your nabu case device "voice" experience onceyou've tried. I ponder getting one. | 01:29:56 |
| @hexa:lossy.network | teto: did you read this article yet? | 01:30:33 |
| @hexa:lossy.network | tinker isn't entirely clear on what his processing pipeline is, but the general picture is there | 01:35:26 |
