| 4 Dec 2024 |
 @hexa:lossy.network | from october 10th | 19:38:18 |
| @hexa:lossy.network | the latest version is 3.11.9 now | 19:38:28 |
| @hexa:lossy.network | and home-assistant and a few dependencies want it | 19:39:04 |
 netpleb | trying to get my zigbee dongle to work with HA...I added
services.zigbee2mqtt = {
enable = true;
settings = {
homeassistant = config.services.home-assistant.enable;
permit_join = true;
serial = {
port = "/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_06cdf5f0f71bef11930299d94909ffd0-if00-port0";
};
};
};
but I am confused as to whether I also need to add "zha" to services.home-assistant.extraComponents
| 19:55:35 |
 CRTified | In reply to @netpleb:matrix.org
trying to get my zigbee dongle to work with HA...I added
services.zigbee2mqtt = {
enable = true;
settings = {
homeassistant = config.services.home-assistant.enable;
permit_join = true;
serial = {
port = "/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_06cdf5f0f71bef11930299d94909ffd0-if00-port0";
};
};
};
but I am confused as to whether I also need to add "zha" to services.home-assistant.extraComponents
That's not needed. zha is an alternative for interfacing zigbee | 20:00:54 |
| CRTified | zigbee2mqtt however requires an additional mqtt broker like mosquitto | 20:01:12 |
| netpleb | In reply to @crtified:crtified.me
zigbee2mqtt however requires an additional mqtt broker like mosquitto thanks for your help. I am also now starting to understand that. In my case I already have mosquitto installed and working (used by my HA zwave integration). So do I need to just somehow tell mosquito about zigbee2mqtt? | 20:02:14 |
| CRTified | In reply to @netpleb:matrix.org
thanks for your help. I am also now starting to understand that. In my case I already have mosquitto installed and working (used by my HA zwave integration). So do I need to just somehow tell mosquito about zigbee2mqtt? You rather need to tell zigbee2mqtt about mosquitto. mosquitto is the message broker, and both HA and z2m connect to the broker as client, listening and sending messages over it | 20:03:07 |
| CRTified | So on the HA side, you'll need the MQTT component in place | 20:03:22 |
| CRTified | and for both, you need some type of credentials | 20:03:34 |
| CRTified | * and for both, you need some type of credentials to connect to mosquitto | 20:03:40 |
| netpleb | In reply to @crtified:crtified.me
So on the HA side, you'll need the MQTT component in place Ok, I am starting to finally understand. I do have the MQTT component in place on the HA side. I've (currently) disabled auth with mosquitto just while I try to get things working | 20:04:29 |
| netpleb | so basically you're saying there is some magic that I need to add to the zigbee2mqtt.settings = ... which should do the trick. And once mosquitto sees it, then HA will be able to see it too. | 20:05:31 |
| netpleb | * so basically you're saying there is some magic that I need to add to the zigbee2mqtt.settings = ... which should do the trick. And once mosquitto sees it, then HA will be able to see it too? | 20:05:36 |
| CRTified | to both, yes 🙂 | 20:06:51 |
| CRTified | relevant part from the settings attrset in my config:
mqtt = {
server = "mqtt://127.0.0.1:1883";
user = "zigbee";
password =
"!${config.sops.secrets."zigbee2mqtt.yaml".path} mqtt_pass";
};
| 20:07:46 |
| CRTified | relevant documentation from z2m: https://www.zigbee2mqtt.io/guide/configuration/mqtt.html#server-connection | 20:08:10 |
| netpleb | ok, and then from the HA side it does not even need to know or care that these devices are "zigbee" right? it just thinks these are devices that magically are in the mqtt stream (sorry, I am new to home automation in general as well as home-assistant) | 20:09:07 |
| CRTified | correct. That happens via auto discovery which you enable with services.zigbee2mqtt.settings.homeassistant = true;, and for HA it's transparently "some device" | 20:09:47 |
| @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 |
