| 11 Jan 2025 |
|  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 |
