[Release] Generic Zigbee Drivers with Presence and Recovery

[markus]

"Sylvania Outlet" it is then

[neonturbo]

@markus

Thank you, I will add this fingerprint to the next release, if you have issues with this driver and that device, do tell me. There's quite a few extra clusters there, not sure if there is functionality missing?

I don't have any Zigbee devices sending power data in a standard way, but I can see about adding that functionality with the ability to turn it off as well.

Yep, it is the power reporting that is missing. I don't use that function for most of these, I primarily have them for repeaters as they are both Zigbee and Zwave. Power would be a nice addition though.

[markus]

@neonturbo

Yep, it is the power reporting that is missing.

Ok, I will see what I can sort out with that, if they are using standard clusters for power reporting it should be no issue. Maybe next weekend, this weekend I will probably not have time since I have other projects to complete.

[bobbles]

BTW and I'm not being picky I just thought I'd let you know that there is a typo.

comment : Works with Generic Outlets (pelase report your fingerprints)

[markus]

@bobbles

I just thought I'd let you know that there is a typo.

It was already fixed for the next release, but thank you I don't mind picky, it should all be perfect

[markus]

Announcement
The Generic Switch driver now support multi-gang Zigbee switches, such as the Nue Wall Switches.

There is now a Generic Zigbee Repair driver. It can be used to get the fingerprint of the device, clear Current State and Preferences as well as clean the Data section. It also has a command for removing all currently scheduled tasks for the current device.

EDIT: Added link to the Generic Zigbee Repair driver

[markus]

Link added

[bobbles]

Hi @markus
Would it be possible to add the Tuya temp/humidity sensor to your zigbee drivers.
I believe it's zigbee 3.
Here is the info you require, I think.

• endpointId: 01
• application: 41
• softwareBuild:
• inClusters: 0000,0001,0402,0405
• outClusters: 0019
• model: TS0201
• manufacturer: _TYZB01_a476raq2

[markus]

@bobbles

Tuya temp/humidity sensor to your zigbee drivers.

Could you try my Sonoff Temp/Humidity Sensor with that one first? If it works as expected I can add the fingerprint there, they are very Generic, so maybe they should be renamed.

[bobbles]

No joy I'm afraid.
It's no big deal but I like the presence capability that your drivers bring.

[markus]

@bobbles

No joy I'm afraid.

What do you get in the logs (with debug on) of my driver if you short-press the reset button on the Tuya sensor? The reason it doesn't work is likely because the configuration is only sent if the driver is already selected when pairing. That works well with Sonoff, but may need a change for the Tuya device.

[bobbles]

Aha. It's working now.
Maybe it just needed a kick with the pair button
Here are the logs anyway in case there is anything in here that you may wish to look at.

[markus]

@bobbles

Maybe it just needed a kick with the pair button

That made the driver send the init calls, couldn't be sure the device would send the same packets, but it did, so all good

[bobbles]

I'm afraid the device stopped reporting anything.
Reverted back to my old driver and it's kicked in again OK.

[simon]

I have a number of XBee 3 Pro and one XBee XStick acting as repeaters. I've installed your Zigbee Repeater driver on them all. 2 of them are reporting as present - I get GENERAL CLUSTER EVENT in the logs. The others get errors says that checkin events have been missed. I did see "GENERAL CATCHALL (0x8038" in one log. Is there any particular XBee setting I need to be looking at? In my XBee settings I dont see anything that corresponds to Send Type set to Bind

I have also installed your Tasmota driver on a SonOff Dual - working fine, but has never become present. (I have hit configure, etc)

many thanks for all your work on these drivers - much appreciated.

[mike]

@simon

I have also installed your Tasmota driver on a SonOff Dual - working fine, but has never become present.

I noticed that they dont appear as present/not present until an event occurs. This is standard. If you are worried, turn off your SonOff Dual (at the mains??) and see if it reports.

[markus]

@bobbles

I'm afraid the device stopped reporting anything.
Reverted back to my old driver and it's kicked in again OK.

What's the old driver you use for that one? This really ought to work and should not be complicated to make the required changes for.

@simon

In my XBee settings I dont see anything that corresponds to

AP = API Enabled (1)
AO = Native (0)

With that it should work with using Bind requests to check for presence. Ping Type should be set to Bind. You could also also use MicroPython to add support for responding, but I've not used that so wouldn't be much of help setting that up.

@simon

I have also installed your Tasmota driver on a SonOff Dual - working fine, but has never become present. (I have hit configure, etc)

If you use my version of Tasmota it should work. Do you get warnings in the logs about traffic not having a matching device? Please continue this part in the Tasmota thread

[Ranchitat]

Seemed to stop updating status, device page and dashboard.
The presence was happy.
Switched back to generic driver and working again.
Not sure what happened but here's some logs:

Sylvania Outlet (Osram) logs

[markus]

@Ranchitat This was an unsupported type of status report, the next release has support for it and status will update as expected.

[markus]

@Ranchitat

Not sure what happened but here's some logs:

This is now supported in the most recent Beta driver committed to the Repo today.

There are also many other updates to various drivers since when I make a change to one and that code is shared, it is updated in all of them.