Python Plugin: Zigbee2Mqtt Topic is solved

[waltervl]

Yes, First

Code: Select all

sudo git pull
sudo git reset --hard 3725a295e12531e5c5f68d03d3e6f0c1f646b1ca

Then restart Domoticz

[manjh]

Yes, First

Code: Select all

sudo git pull
sudo git reset --hard 3725a295e12531e5c5f68d03d3e6f0c1f646b1ca

Then restart Domoticz

I get this message:

Code: Select all

HEAD is now at 3725a29 Remove `devices` argument from Adapters

Is that OK?

[manjh]

Yes, First

Code: Select all

sudo git pull
sudo git reset --hard 3725a295e12531e5c5f68d03d3e6f0c1f646b1ca

Then restart Domoticz

I get this message:

Code: Select all

HEAD is now at 3725a29 Remove `devices` argument from Adapters

Is that OK?

OK, looks like it is not a problem, the plugin works and created devices (after I had enabled this in the Domoticz settings).
What puzzles me: I see battery level of my smoke detectors at 0%, but I am quite sure it is 100%!
Also, would be nice to combine the different attributes into one single device for Domoticz. I now have four devices for each smoke detector: smoke alarm, battery-low, battery-level and link-quality.

[waltervl]

Zigbee battery levels can take some time to being send by the sensor. So give it a day or so.

[manjh]

Zigbee battery levels can take some time to being send by the sensor. So give it a day or so.

OK, thanks. I'll be patient.
At the moment I already have Domoticz devices that I feed from Node-Red myself, so it is very easy to compare the zigbee2mqtt plugin devices with my own.

How about the suggestion to combine items into one Domoticz device? It would greatly improve the overview!

[waltervl]

In Domoticz there is no possibility to combine devices.
You can install an extra layer called Dashticz where you perhaps should be able to combine devices in a custom Dashboard.

But some devices you mentioned are not that interesting, eg battery and link level should not be a device but part of the device info. If you go to menu setup devices you will see a battery level and signal level. So the plugin should not have made those. You can put those devices on unused (green arrow).

But I do not use zigbee2mqtt so perhaps not the best person to answer those questions.

[manjh]

Today I purchased an Ikea Zigbee lamp. After reset it paired with my Zigbee2MQTT, but on the DOmoticz plugin it claims the bulb is unsupported.
On the R-Pi console, I can see the z2mqtt status:

Code: Select all

Zigbee2MQTT:info  2021-10-23 19:04:21: Currently 6 devices are joined:
Zigbee2MQTT:info  2021-10-23 19:04:21: garage (0x000d6f0016194686): HS3SA - HEIMAN Smoke detector (EndDevice)
Zigbee2MQTT:info  2021-10-23 19:04:21: begane grond (0x000d6f0016193e73): HS3SA - HEIMAN Smoke detector (EndDevice)
Zigbee2MQTT:info  2021-10-23 19:04:21: 1e verdieping (0x000d6f00161f9b87): HS3SA - HEIMAN Smoke detector (EndDevice)
Zigbee2MQTT:info  2021-10-23 19:04:21: 2e verdieping (0x000d6f00161f715e): HS3SA - HEIMAN Smoke detector (EndDevice)
Zigbee2MQTT:info  2021-10-23 19:04:21: berging (0x000d6f00161f96d7): HS3SA - HEIMAN Smoke detector (EndDevice)
Zigbee2MQTT:info  2021-10-23 19:04:21: 0xb4e3f9fffecb218f (0xb4e3f9fffecb218f): Not supported (Router)

Five smoke detectors, plus the new Ikea lamp as "not supported". How can I move this forward?

[EddyG]

Just make a request on https://github.com/Koenkk/zigbee2mqtt/issues/new/choose for adding the new device (bulb).
It might be that is just a new type which is (almost) the same as the already supported ones.
It could then be easily added by Koenk.

[manjh]

Just make a request on https://github.com/Koenkk/zigbee2mqtt/issues/new/choose for adding the new device (bulb).
It might be that is just a new type which is (almost) the same as the already supported ones.
It could then be easily added by Koenk.

Thanks for the suggestion, I submitted a request.

[EddyG]

B.t.w. This is my blacklist, so you can get ride of some unnecessary devices.

Code: Select all

.*_power_;.*_effect;.*_pwrmem;.*_volt;.*_ampere;.*_thb;.*_lowbtr

[manjh]

After some doing, I managed to get the lamp working. I followed the instructions for pairing an unsupported device on zigbee2mqtt.io.
The instructions are quite clear and detailed. The one thing that I struggled with: it shows an external converter that did not work for me. Then I found another example, where extends were used in stead of the toZigbee, fromZigbee and exposes statements.
After experimenting with the differentpossibilities, I found one that allows me to switch, dim, and change color temp.
That's all I needed!

Thanks to all for thinking along, and especially to Koenkk for building a great tool!

[manjh]

A newbee question, no doubt...
I have been running a network of Conbee-2, with five smoke detectors across the house.
Today I added an IKEA lamp on the first floor, which should improve link-quality for some of the remote smoke detectors.
But I see that the smoke detectors hang on to the link with the controller, in stead of switching to the nearby router.

Is there a way to force a connection going to a router? I realize that re-pairing the smoke detectors might do it, but that seems like something I don't want to do...

[Creo2005]

A newbee question, no doubt...
I have been running a network of Conbee-2, with five smoke detectors across the house.
Today I added an IKEA lamp on the first floor, which should improve link-quality for some of the remote smoke detectors.
But I see that the smoke detectors hang on to the link with the controller, in stead of switching to the nearby router.

Is there a way to force a connection going to a router? I realize that re-pairing the smoke detectors might do it, but that seems like something I don't want to do...

Off out the Conbee-2 for aprox. for 10 minutes and smoke detectors connect to IKEA lamp, after ON Conbee-2

[manjh]

A newbee question, no doubt...
I have been running a network of Conbee-2, with five smoke detectors across the house.
Today I added an IKEA lamp on the first floor, which should improve link-quality for some of the remote smoke detectors.
But I see that the smoke detectors hang on to the link with the controller, in stead of switching to the nearby router.

Is there a way to force a connection going to a router? I realize that re-pairing the smoke detectors might do it, but that seems like something I don't want to do...

Off out the Conbee-2 for aprox. for 10 minutes and smoke detectors connect to IKEA lamp, after ON Conbee-2

Hmmm.. by the time I read this post, one of the smoke detectors had decided to connect to the Ikea bulb router in stead of the Conbee coordinator.. so apparently it happens without me forcing it!

[manjh]

I was too quick being happy... I am running into strange problems.
The lamp was working OK, then suddenly stopped reacting.
Restarted Z2M, checked the config, re-paired the device.
It does come up in the network map, but in the list of devices it says "unsupported".
Device name and maker are there OK.
When I look in the log, I see:

Code: Select all

2021-10-25 01:40:14.307 (Zigbee2MQTT) Received available devices list from bridge
2021-10-25 01:40:14.309 (Zigbee2MQTT) nachtlampje: device definiton not found, skipping...

Does this mean the plugin is missing something? If so, why does it sometimes work, and sometimes does not?

[manjh]

I was too quick being happy... I am running into strange problems.
The lamp was working OK, then suddenly stopped reacting.
Restarted Z2M, checked the config, re-paired the device.
It does come up in the network map, but in the list of devices it says "unsupported".
Device name and maker are there OK.
When I look in the log, I see:

Code: Select all

2021-10-25 01:40:14.307 (Zigbee2MQTT) Received available devices list from bridge
2021-10-25 01:40:14.309 (Zigbee2MQTT) nachtlampje: device definiton not found, skipping...

Does this mean the plugin is missing something? If so, why does it sometimes work, and sometimes does not?

From the Z2M frontend, I removed the device and re-paired it. Now it works, but this is how it was yesterday... at some point the device became "unsupported". Will see what happens.

[manjh]

At some point during the whole excercise, I noticed a message about the bulb: "devices requested OTA". But when I check the frontend and click OTA, it says there are no devices supporting OTA!
Is there something missing from the device definition?

[EddyG]

I see that in the latest version of zigbee2mqtt (dev branch) there is (at the end) a bulb LED1949C5 defined. So update zigbee2mqtt.

[manjh]

I see that in the latest version of zigbee2mqtt (dev branch) there is (at the end) a bulb LED1949C5 defined. So update zigbee2mqtt.

Which file can I check to see that?

[EddyG]

If you go into the zigbee2mqtt GUI you can go to Settings -> About
There you will find the version, in my case from yesterday.

Code: Select all

Zigbee2MQTT version 1.21.2-dev commit: 3f0a2fed

So if you update now from the dev branch you are good.