hmm, your right. It seems the stick cannot be reached.
You could directly enter /dev/ttyUSB0 in configuration.yaml.
Have you tried a different usb port? Did the stick work before?
as well as using a different USB-port. Results are the same.
Don’t know what you are asking for. I get the sensor states via Zigbee and they are displayed (although I’m not quite sure about their update interval). Therefore I would say “It worked before” - but in sense of the Mqtt - I didn’t test before because this is my first install of the broker.
sudo cat /etc/systemd/system/zigbee2mqtt.service
[sudo] Passwort für openhabian:
[Unit]
Description=Zigbee2MQTT
After=network.target
[Service]
ExecStart=/usr/bin/npm start
WorkingDirectory=/opt/zigbee2mqtt
StandardOutput=inherit
# Or use StandardOutput=null if you don't want Zigbee2MQTT messages filling syslog, for more options see systemd.exec(5)
StandardError=inherit
Restart=always
User=openhabian
[Install]
WantedBy=multi-user.target
with the followup details
groups openhabian
openhabian : openhab adm tty dialout cdrom sudo audio video plugdev games users input render bluetooth netdev spi i2c gpio openhabian mosquitto
Honestly I don’t know. I was thinking that I can run Zigbee coordinator AND the mosquitto broker at the same time, meaning connect what I can connect with Zigbee and in case I need MQTT I connect with the MQTT broker.
Hmmm… don’t know if the stick has its own UI. I was guessing that the Z2M would rather use it - but honestly that’s more guessing and I don’t know if my ideas could be working perfectly together.
Matter of fact is that the Zigbee2Matter broker doesn’t run.
Of course, you even have to. But there seems to be a misunderstanding. The coordinator is your hardware. z2m connects your coordinator to the mqtt broker which connects to openhab.
You said you can see the sensor states. Where? In openhab? Which OS are you on? Are you using openhabian? Docker? …
You cannot run the zigbee binding and z2m in parallel on the same stick.
But without knowing the setup it’s hard to understand.
edit: Another way is of course to use the autodetect option in mqtt. But I tried it long time ago without success. So I have no experience how it’s working now.
I have installed on my Pi4, 8GB, Openhabian 5.0.1. Although the intro message says
Platform = BCM43455 37.4MHz Raspberry Pi 3+-0190
I double checked that its version 1.4. I’ve plugged into the Pi the SLZB-07 directly but moved it now to an extra USB-hub since it seems like it losses after a certain time the connection to my temperature sensor. The temperature is displayed within Openhabian and I don’t know where else to display the values.
The temperature sensor is connected via Zigbee binding from Openhabian.
Please let me know what kind of additional information is required or useful.
The reasons why I tried to run z2m is that I want to display the LinkQuality of my sensors (to see how good they are reachable). If there is another way to get that kind of information I can ask in another thread or perhaps it exists one already.
But I don’t know definitely which config is possible and which makes sense. Since I’ve just chosen the option on the openhabian-configwithout any further notice that it won’t make any sense I’m still assuming that its possible.
You cannot use both at the same time. it’s either the zigbee binding or zigbee2mqtt.
You have to decide. Both want the zigbee stick exclusively. If you de-install the binding and restart zigbee2mqtt it will probably start
zigbee2mqtt has more functions, more control and supports more hardware but is harder to configure as you’ve got the additional mqtt-layer.
