Zigbee2MQTT
Moderator: leecollings
-
- Posts: 742
- Joined: Saturday 30 May 2015 22:40
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Contact:
Re: Zigbee2MQTT
And your zigbee settings are allowing new connections? You can follow the steps on zigbee2mqtt.io at pairing devices
- Varazir
- Posts: 360
- Joined: Friday 20 February 2015 22:23
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Contact:
Re: Zigbee2MQTT
Yes it's enabled and you see the log I disable and then enable it
Raspberry PI 2 with RaZberry Controller 2016 ZWave+ and CC2531(zigbee)
Several IKEA devices/z-wave devices
Several IKEA devices/z-wave devices
-
- Posts: 742
- Joined: Saturday 30 May 2015 22:40
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Contact:
Re: Zigbee2MQTT
Well, I am out of options, my suspicion is still that those lights are not properly disconnected from the Ikea hub. You see the light flashing as soon as you have the proper pattern of on and off.
- Varazir
- Posts: 360
- Joined: Friday 20 February 2015 22:23
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Contact:
Re: Zigbee2MQTT
Hmm the hub is offline. I could turn it on again.
Raspberry PI 2 with RaZberry Controller 2016 ZWave+ and CC2531(zigbee)
Several IKEA devices/z-wave devices
Several IKEA devices/z-wave devices
-
- Posts: 12
- Joined: Tuesday 03 December 2019 8:37
- Target OS: NAS (Synology & others)
- Domoticz version:
- Contact:
Re: Zigbee2MQTT
Hi everybody,
I'm trying to get MQTT working on my Synology, but I'm running into some issues. After installing the package from synocommunity, everything seems fine, the package runs. If I putty into the box, netstat gives me this output:
tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN
tcp6 0 0 :::1883 :::* LISTEN
Which seems to indicate things are working. However, from Domoticz, I cannot get a connection.
adding the http interface with the settings recommended gives me this:
2020-03-24 14:52:06.297 Status: MQTT: Connecting to localhost:1833
2020-03-24 14:52:06.298 Error: MQTT: Failed to start, return code: 14 (Check IP/Port)
I tried editing the config to allow anonymous access and even adding a user, but no luck.
Can anybody help point me in the right direction?
I'm trying to get MQTT working on my Synology, but I'm running into some issues. After installing the package from synocommunity, everything seems fine, the package runs. If I putty into the box, netstat gives me this output:
tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN
tcp6 0 0 :::1883 :::* LISTEN
Which seems to indicate things are working. However, from Domoticz, I cannot get a connection.
adding the http interface with the settings recommended gives me this:
2020-03-24 14:52:06.297 Status: MQTT: Connecting to localhost:1833
2020-03-24 14:52:06.298 Error: MQTT: Failed to start, return code: 14 (Check IP/Port)
I tried editing the config to allow anonymous access and even adding a user, but no luck.
Can anybody help point me in the right direction?
-
- Posts: 153
- Joined: Wednesday 02 October 2019 7:37
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2024.4
- Location: Netherlands
- Contact:
Re: Zigbee2MQTT
Just installed the new version. It seemed to be running smooth until i checked the error-log.
It shows: "zigbee2mqtt connection refused not authorized"
I reverted to the previous version, now it is working again.
(also posted here https://www.domoticz.com/forum/viewtopi ... tt#p240506 )
[edit] retried the upgrade, all working fine now [/edit]
It shows: "zigbee2mqtt connection refused not authorized"
I reverted to the previous version, now it is working again.
(also posted here https://www.domoticz.com/forum/viewtopi ... tt#p240506 )
[edit] retried the upgrade, all working fine now [/edit]
Last edited by azonneveld on Thursday 02 April 2020 11:03, edited 1 time in total.
rpi4 - zigbee2mqtt - roborock - espeasy - rfxcom - homewizard p1 - otgw - homebridge - surveillance station - egardia - goodwe - open weather map - wol - BBQ detection - rsync backup
-
- Posts: 12
- Joined: Tuesday 03 December 2019 8:37
- Target OS: NAS (Synology & others)
- Domoticz version:
- Contact:
Re: Zigbee2MQTT
I seem to be an idiot myself:
This part is solved. Still unable to install zigbee2mqtt itself, but working on that.frankwijers wrote: ↑Tuesday 24 March 2020 15:03 tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN
tcp6 0 0 :::1883 :::* LISTEN
2020-03-24 14:52:06.297 Status: MQTT: Connecting to localhost:1833
- Hesitated
- Posts: 42
- Joined: Monday 04 June 2018 21:40
- Target OS: Raspberry Pi / ODroid
- Domoticz version: V4.11665
- Location: Ede
- Contact:
Re: Zigbee2MQTT
Since a week I have troubles to get zigbee2mqtt going.
I've since then started with a new raspberry pi 3B+ with buster and installed Domoticz on it with zigbee2mqtt. (And mosquitto and Node-RED and ...)
I've used the backup of the old Domoticz to get me going on the new pi.
But although I can send messages from Node-RED to the broker, and zigbee2mqtt receives commands from the zigbee, zigbee2mqtt does not send messages to the broker.
Strangly though it, the log file says it is connected:
I've since then started with a new raspberry pi 3B+ with buster and installed Domoticz on it with zigbee2mqtt. (And mosquitto and Node-RED and ...)
I've used the backup of the old Domoticz to get me going on the new pi.
But although I can send messages from Node-RED to the broker, and zigbee2mqtt receives commands from the zigbee, zigbee2mqtt does not send messages to the broker.
Strangly though it, the log file says it is connected:
Why are the message not send to the broker?info 2020-04-13 16:08:30: Logging to console and directory: 'data/log' filename: zigbee2mqtt.log
debug 2020-04-13 16:08:31: Loaded state from file /opt/zigbee2mqtt/data/state.json
info 2020-04-13 16:08:31: Starting zigbee2mqtt version 1.12.2 (commit #911cd58)
info 2020-04-13 16:08:31: Starting zigbee-herdsman...
debug 2020-04-13 16:08:31: Using zigbee-herdsman with settings: '{"network":{"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11],"networkKey":"HIDDEN"},"databasePath":"/opt/zigbee2mqtt/data/database.db","databaseBackupPath":"/opt/zigbee2mqtt/data/database.db.backup","backupPath":"/opt/zigbee2mqtt/data/coordinator_backup.json","serialPort":{"baudRate":115200,"rtscts":true,"path":"/dev/ttyCC2531"},"adapter":{"concurrent":null}}'
info 2020-04-13 16:08:33: zigbee-herdsman started
info 2020-04-13 16:08:33: Coordinator firmware version: '{"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190608}}'
debug 2020-04-13 16:08:33: Zigbee network parameters: {"panID":6754,"extendedPanID":"0xdddddddddddddddd","channel":11}
info 2020-04-13 16:08:33: Currently 3 devices are joined:
info 2020-04-13 16:08:33: Switch2 (0x00158d00034925f0): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
info 2020-04-13 16:08:33: Switch3 (0x00158d00033efd25): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
info 2020-04-13 16:08:33: MotionSensor3 (0x00158d00044d60fc): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
warn 2020-04-13 16:08:33: `permit_join` set to `true` in configuration.yaml.
warn 2020-04-13 16:08:33: Allowing new devices to join.
warn 2020-04-13 16:08:33: Set `permit_join` to `false` once you joined all devices.
info 2020-04-13 16:08:33: Zigbee: allowing new devices to join.
info 2020-04-13 16:08:33: Connecting to MQTT server at mqtt://localhost:1883
debug 2020-04-13 16:08:33: Using MQTT client ID: 'zigbee2mqtt'
info 2020-04-13 16:08:33: Connected to MQTT server
info 2020-04-13 16:08:33: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
info 2020-04-13 16:08:33: MQTT publish: topic 'zigbee2mqtt/Switch2', payload '{"battery":100,"voltage":3022,"linkquality":94}'
info 2020-04-13 16:08:33: MQTT publish: topic 'zigbee2mqtt/Switch3', payload '{"linkquality":84,"battery":100,"voltage":3042}'
info 2020-04-13 16:08:33: MQTT publish: topic 'zigbee2mqtt/MotionSensor3', payload '{"battery":100,"voltage":3025,"illuminance":42,"illuminance_lux":42,"linkquality":97,"occupancy":false}'
info 2020-04-13 16:08:33: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.12.2","commit":"911cd58","coordinator":{"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190608}},"log_level":"debug","permit_join":true}'
Domoticz 2020.2 - RPi3B+ - RFXtrx433XL - P1 - CC2531 - Somfy - Xiaomi - Hue - Omron - MQTT
-
- Posts: 528
- Joined: Saturday 02 June 2018 11:05
- Target OS: Raspberry Pi / ODroid
- Domoticz version: V2022.1
- Location: Echt, Netherlands
- Contact:
Re: Zigbee2MQTT
I want to remove a device in zigbee2mqtt, but only removing in the configuration.yaml is not the solution, it is comming back.
What is the way to do it.
Found some information on zigbee2mqtt, but i don't understand what to do whit it. (zigbee2mqtt/bridge/config/remove #)
Have read something about domoticz/in command. But can't find the website where i found that.
Just looking for a nice way to remove it.
Just some info, i don't have the GUI in domoticz, to use that. Needs to be an other way to remove it.
Somebody here with a nice instruction?
What is the way to do it.
Found some information on zigbee2mqtt, but i don't understand what to do whit it. (zigbee2mqtt/bridge/config/remove #)
Have read something about domoticz/in command. But can't find the website where i found that.
Just looking for a nice way to remove it.
Just some info, i don't have the GUI in domoticz, to use that. Needs to be an other way to remove it.
Somebody here with a nice instruction?
Thin-client --> Docker Domoticz main environment
Pi3A+ --> Google home (GAssistPi)
Pi3B+ --> Docker (P1monitor, Domoticz test environment, Ubiquity controller)
Pi3A+ --> Google home (GAssistPi)
Pi3B+ --> Docker (P1monitor, Domoticz test environment, Ubiquity controller)
-
- Posts: 70
- Joined: Monday 14 December 2015 22:16
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: Mierlo
- Contact:
Re: Zigbee2MQTT
Hi Hoeby,
Maybe i now can return the favor.
In installed the MQTTLens plugin in google chrome
Connect from the MQTTLens to your mosquitto server.
Publish :
Message :
Then push Publish.
Your device has to be on and not sleeping (battery devices are a hell to remove).
If this is not working try : (for battery devices)
Publish :
Message :
Then push Publish
You have to factory reset the specific device afterwards.
(i noticed for my aquara temp sensor and Ikea on/off switch this was the same as including it again)
Hope this helps
Regards Peer
Maybe i now can return the favor.
In installed the MQTTLens plugin in google chrome
Connect from the MQTTLens to your mosquitto server.
Publish :
Code: Select all
zigbee2mqtt/bridge/config/remove
Code: Select all
the number of your device e.g. 0x680ae2fffe785feb
Your device has to be on and not sleeping (battery devices are a hell to remove).
If this is not working try : (for battery devices)
Publish :
Code: Select all
zigbee2mqtt/bridge/config/force_remove
Code: Select all
the number of your device e.g. 0x680ae2fffe785feb
Then push Publish
You have to factory reset the specific device afterwards.
(i noticed for my aquara temp sensor and Ikea on/off switch this was the same as including it again)
Hope this helps
Regards Peer
-
- Posts: 528
- Joined: Saturday 02 June 2018 11:05
- Target OS: Raspberry Pi / ODroid
- Domoticz version: V2022.1
- Location: Echt, Netherlands
- Contact:
Re: Zigbee2MQTT
Man you are great.peerkersezuuker wrote: ↑Saturday 02 May 2020 14:32 In installed the MQTTLens plugin in google chrome
Connect from the MQTTLens to your mosquitto server.
I was al little impatience with starting MQTTLens, it takes a little time before the buttons are shown.
But after that, a few clicks with the mouse and finished.
Thanks Peer, for the information
greetings Paul
Thin-client --> Docker Domoticz main environment
Pi3A+ --> Google home (GAssistPi)
Pi3B+ --> Docker (P1monitor, Domoticz test environment, Ubiquity controller)
Pi3A+ --> Google home (GAssistPi)
Pi3B+ --> Docker (P1monitor, Domoticz test environment, Ubiquity controller)
-
- Posts: 528
- Joined: Saturday 02 June 2018 11:05
- Target OS: Raspberry Pi / ODroid
- Domoticz version: V2022.1
- Location: Echt, Netherlands
- Contact:
Re: Zigbee2MQTT
For 2 weeks ago i did a fresh install on domoticz with stable V2022.2
With that i also installed latest versions of zigbee2mqtt
Everything went fine. And it took me 2 weeks to rebuild (and a few modifications), to have everything back working how i would like.
So it was time to make a backup of the SD card.
Did a "sudo poweroff" command and waited for a few minutes. Made a backup of the SD and restarted the pi 3B+ again.
And then the zigbee2mqtt stopped working. After a little searching, it was the USB port which was moved. Not the hardware position on the pi, but the software position. Changed that in de configuration and restarted everything. But still nothing worked.
I needed to go to the custom page, all paired devices where there, but not working
checked the "Allow new zigbee devices to join" box and clicked on "pair device"
Then each devices needed to pair again. Nothing is added in domoticz. No new devices in device-list. No new devices in de custom page.
But after doing this, everything is working again.
Only the smoke detectors where not re-paired. They make to much noice now and the kids are sleeping.
But what went wrong. Or what did i wrong, that this happend?
I know the pi something changes the USB port discription. But why was zigbee2mqtt reacting like this?
With that i also installed latest versions of zigbee2mqtt
Everything went fine. And it took me 2 weeks to rebuild (and a few modifications), to have everything back working how i would like.
So it was time to make a backup of the SD card.
Did a "sudo poweroff" command and waited for a few minutes. Made a backup of the SD and restarted the pi 3B+ again.
And then the zigbee2mqtt stopped working. After a little searching, it was the USB port which was moved. Not the hardware position on the pi, but the software position. Changed that in de configuration and restarted everything. But still nothing worked.
I needed to go to the custom page, all paired devices where there, but not working
checked the "Allow new zigbee devices to join" box and clicked on "pair device"
Then each devices needed to pair again. Nothing is added in domoticz. No new devices in device-list. No new devices in de custom page.
But after doing this, everything is working again.
Only the smoke detectors where not re-paired. They make to much noice now and the kids are sleeping.
But what went wrong. Or what did i wrong, that this happend?
I know the pi something changes the USB port discription. But why was zigbee2mqtt reacting like this?
Thin-client --> Docker Domoticz main environment
Pi3A+ --> Google home (GAssistPi)
Pi3B+ --> Docker (P1monitor, Domoticz test environment, Ubiquity controller)
Pi3A+ --> Google home (GAssistPi)
Pi3B+ --> Docker (P1monitor, Domoticz test environment, Ubiquity controller)
Re: Zigbee2MQTT
First handle this https://www.domoticz.com/wiki/PersistentUSBDevices
Then your port(names) will stay the same.
Then your port(names) will stay the same.
- Varazir
- Posts: 360
- Joined: Friday 20 February 2015 22:23
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Contact:
Re: Zigbee2MQTT
Is it the plugin that prevent groups to be dimmable ?
Raspberry PI 2 with RaZberry Controller 2016 ZWave+ and CC2531(zigbee)
Several IKEA devices/z-wave devices
Several IKEA devices/z-wave devices
-
- Posts: 528
- Joined: Saturday 02 June 2018 11:05
- Target OS: Raspberry Pi / ODroid
- Domoticz version: V2022.1
- Location: Echt, Netherlands
- Contact:
Re: Zigbee2MQTT
please help me, i don't know what to do anymore.
The power needed to switch off.
Before doing this, the zigbee2mqtt worked beautifull. Before cutting the power, i have given a shut down command to the pi.
Everything else is working after powering up, but the zigbee2mqtt not.
I checked to CC2531, which is ok.
Checked the USB port, this is correct with the configuration.
The writting permision is checked and ok.
restarted the service a couple of times and a compleet reboot.
The green led on the CC2531 keeps going off, that zigbee2mqtt doesn't communicate with it. But where is the issue?
But it still gives that the zigbee bridge is offline, but i don't know why
i hope somebody has some idea.
Need to say, i was running zigbee2mqtt on domoticz V4.9700
Never had problems after reboot. But on the V2020.2 i only experiance problems when the power went off
The power needed to switch off.
Before doing this, the zigbee2mqtt worked beautifull. Before cutting the power, i have given a shut down command to the pi.
Everything else is working after powering up, but the zigbee2mqtt not.
I checked to CC2531, which is ok.
Checked the USB port, this is correct with the configuration.
The writting permision is checked and ok.
restarted the service a couple of times and a compleet reboot.
The green led on the CC2531 keeps going off, that zigbee2mqtt doesn't communicate with it. But where is the issue?
But it still gives that the zigbee bridge is offline, but i don't know why
i hope somebody has some idea.
Need to say, i was running zigbee2mqtt on domoticz V4.9700
Never had problems after reboot. But on the V2020.2 i only experiance problems when the power went off
Thin-client --> Docker Domoticz main environment
Pi3A+ --> Google home (GAssistPi)
Pi3B+ --> Docker (P1monitor, Domoticz test environment, Ubiquity controller)
Pi3A+ --> Google home (GAssistPi)
Pi3B+ --> Docker (P1monitor, Domoticz test environment, Ubiquity controller)
Re: Zigbee2MQTT
Put this in the configuration.yaml and post what is in the logfile.
And if npm is running under user pi, make sure that rights are correct, or change the place of the log_directory
Code: Select all
log_level: debug
log_directory: /var/log
log_file: zigbee.log
-
- Posts: 528
- Joined: Saturday 02 June 2018 11:05
- Target OS: Raspberry Pi / ODroid
- Domoticz version: V2022.1
- Location: Echt, Netherlands
- Contact:
Re: Zigbee2MQTT
Yesterday i put back a sd card backup from last week.
Everything is working again.
Don't know what happend. I did shutdown the pi and let it rest for a few minutes before cutting the power.
Everything is working again.
Don't know what happend. I did shutdown the pi and let it rest for a few minutes before cutting the power.
Thin-client --> Docker Domoticz main environment
Pi3A+ --> Google home (GAssistPi)
Pi3B+ --> Docker (P1monitor, Domoticz test environment, Ubiquity controller)
Pi3A+ --> Google home (GAssistPi)
Pi3B+ --> Docker (P1monitor, Domoticz test environment, Ubiquity controller)
-
- Posts: 70
- Joined: Monday 14 December 2015 22:16
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: Mierlo
- Contact:
Re: Zigbee2MQTT
Hi,
I have a strange problem.
After pairing an Gledopto Smart 4W E14 RGB / CCT LED bulb (GL-B-001ZS) :
https://i.imgur.com/lCDm8nL.png
But is not creating any devices in Domoticz. (set accept new hardware device on !)
https://i.imgur.com/eF1M1Wz.png
Any suggestions ?
Regards Peer
I have a strange problem.
After pairing an Gledopto Smart 4W E14 RGB / CCT LED bulb (GL-B-001ZS) :
- Spoiler: show
https://i.imgur.com/lCDm8nL.png
But is not creating any devices in Domoticz. (set accept new hardware device on !)
https://i.imgur.com/eF1M1Wz.png
Any suggestions ?
Regards Peer
-
- Posts: 12
- Joined: Sunday 23 February 2020 19:11
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Zigbee2MQTT
I recently bought this zigbee dimmer https://www.zigbee2mqtt.io/devices/Eco-Dim.07.html.
Its paired with a local running zigbee2mqtt server and recognised by the zigbee2mqtt plugin, but here comes the strange part.
But its not adding the correct devices. I think the cause is, its recognised as a router and not as a light switch.
Attached a screenshot of the zigbee2mqtt plugin administration panel. As you can see no devices are presented under the selected hardware.
Does anybody know a solution?
Its paired with a local running zigbee2mqtt server and recognised by the zigbee2mqtt plugin, but here comes the strange part.
But its not adding the correct devices. I think the cause is, its recognised as a router and not as a light switch.
Attached a screenshot of the zigbee2mqtt plugin administration panel. As you can see no devices are presented under the selected hardware.
Does anybody know a solution?
- Attachments
-
- 2020-07-22 21_27_53-Window.png (35.5 KiB) Viewed 4686 times
-
- Posts: 12
- Joined: Sunday 23 February 2020 19:11
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Zigbee2MQTT
Fixed it myself
The answer was adding the following line to [your directory]/domoticz/plugins/zigbee2mqtt/adapters/__init__.py
For anyone struggling with this, a simple explanation.
The file adapters__init__.py defines how to interpret the devices. In my case, the dimmer wasnt recognised and so i had to define how the plugin should see the new device.
Steps:
1. Search for the model (not modelid) of the new device in the zigbee2mqtt log file. In my case 'Dimmer-Switch-ZB3.0'.
2. Define the type of device it should act as. In my case 'DimmableBulbAdapter'
3. Restart domoticz.
4. The plugin should now see the new devices.
The answer was adding the following line to [your directory]/domoticz/plugins/zigbee2mqtt/adapters/__init__.py
Code: Select all
#ECO.DIM (S10)
'Dimmer-Switch-ZB3.0': DimmableBulbAdapter # ECO.DIM dimmer
The file adapters__init__.py defines how to interpret the devices. In my case, the dimmer wasnt recognised and so i had to define how the plugin should see the new device.
Steps:
1. Search for the model (not modelid) of the new device in the zigbee2mqtt log file. In my case 'Dimmer-Switch-ZB3.0'.
2. Define the type of device it should act as. In my case 'DimmableBulbAdapter'
3. Restart domoticz.
4. The plugin should now see the new devices.
- Attachments
-
- 2020-07-25 10_38_30-Window.png (65.71 KiB) Viewed 4658 times
Last edited by S10NL on Wednesday 28 July 2021 8:27, edited 1 time in total.
Who is online
Users browsing this forum: No registered users and 1 guest