Info I need to provide for driver?

Hi all! I have figured out how to add devices and that went ok. (Zigbee power plugs with and without power monitoring) Then I created some apps and rules etc. And that seems to be getting along just fine so far.

Now my newest challenge:

What info do I need (and where to find it) so I can ask for help with drivers for unlisted zigbee devices? I seem to have accumulated a few now.

My first one is a zigbee door window sensor. Brand on box says OUVOPO, a simple magnetic door/window switch.

Then I also have a zigbee 4ch ac/dc 7-32v or usb powered dry contact device. (might be tuya, not sure, it says tuya support on the box)

I also picked up 3 zigbee temp/humidity sensors that are not directly compatable. Brand is Maxcio MSMMAX sensor.

And last is a zigbee mmwave presence sensor (mini human breathe sensor) usb c powered.

I know, I know that for anyone to be able to help you will need info, logs and such.

Lets start with one unit and work from there. What do you need of me?

Also, side note, i eventually want to be able to write my own drivers and be supportive of this community.

Thanks in advance.

Paul

1 Like
2 Likes

Thanks @kkossev

1 Like

Ok, then the first one is:

Third Reality presence sensor

  • endpointId: 01
  • application: 4A
  • manufacturer: _TZE204_sxm7l9xa
  • model: TS0601
  • tuyaVersion: 1.0.10

Next is:

Zigbee 4 channel 7-32v dry contact switch

  • endpointId: 01
  • application: 50
  • driver: v1.09 (7th December 2023)
  • manufacturer: _TZ3000_u3oupgdy
  • model: TS0004
  • tuyaVersion: 1.1.0

Then this one:

Maxcio Zigbee Temperature and Humidity sensor

  • endpointId: 01
  • application: 46
  • manufacturer: _TZ3000_cx6atb9s
  • model: TS0201

And last is the OUPOPO door/window sensor

  • endpointId: 01
  • application: 71
  • inClusters: 0000,0003,0001,0500,0020
  • manufacturer: eWeLink
  • model: DS01
  • outClusters: 0019
  • softwareBuild: 0122052017

Well, that is it for now.

Thanks again for the nudge in the right direction @kkossev

Paul

1 Like

After identifying the devices, the next step is to find the correct device driver if the one that was selected automatically during the initial pairing was not the correct one.

I suppose this is not a Third Reality device (except they have entered heavily into the drop shipping business :slight_smile: )

Tuya TS0601 devices will typically require a custom/community driver. The easiest way to find the correct driver is to search this forum for references to the Tuya Zigbee manufacturer :

(copy and paste the manufacturer Id string into the Hubitat forum search field : )


(looking at the custom tuyaVersion device data I see that you have already found the right driver).


Most of the Tuya non-TS0601 model devices may work with HE inbuilt system drivers.
As this is a contact sensor - you can try drivers that have 'Zigbee Contact' in the name :


I will search first for ' _TZ3000_cx6atb9s'
The result is not encouraging - no one has posted for this device in this forum.
Then I will search for the more generic 'TS0201' model :


Now, the search results show enough information to find the correct custom driver ...

But before searching for a custom driver - try whether the HE inbuilt system drivers will not work? (most probably - yes, so you won't need to worry about custom drivers) :

IMPORTANT: For most battery-powered devices (especially Tuya's), it is not enough to just change the driver and click on the Configure button!

The majority of the new Zigbee battery-powered devices are 'sleeping' most of the time. They will not accept any configuration commands except in a short time period when they wake up (e.g., when a button is pressed, a contact is closed, the temperature or humidity changes). That's why after changing the driver you may need to pair the device once again to your HE hub (without deleting the device).


Next device - the Zigbee Temperature and Humidity sensor TS0201 _TZ3000_cx6atb9s should be a typical case where changing the driver to HE inbuilt 'Generic Zigbee Temperature/Hunidity' sensor may work straight away:

  • if not working - pair the device again
  • if not working with the stock drivers - search for a community driver that refers to _TZ3000_cx6atb9s

This is a non-Tuya device (it is actually produced by Sonoff/eWeLink), but sold under another name 'brand'.
Here - assign the correct HE inbuilt driver, obligatory pair it again and it should work. If not - search for 'DS01' model references in this forum.


Good luck! :slight_smile:

7 Likes

@kkossev, thank you so much! WOW!

I have some good news. I was able to get the temp/humid sensors working correctly. Thank you thank you thank you.

I also was able to get the presence sensor working.

I will be working on the door sensor and the 4 relay device.

I will keep you informed.

1 Like

@kkossev

Ok, that door contact center, it responds to the driver for the sonoff contact sensor, but after it pairs, I can see the position open/closed and the battery percentage.

Now the problem, after it pairs, it never stops blinking. I left it flashing for a long time about an hour) before i took the battery out.

I have re-paired it without deleting it and it says it is paired, and the states change perfectly, but with it staying in pairing mode, I am afraid the battery will not last like that even though it does report to the hub states and battery.

@kkossev, thank you so much! WOW!

I have some good news. I was able to get the temp/humid sensors working correctly. Thank you thank you thank you.

I was able to get my single 3 state button working. Actually, iI finally understood that I define the state I want to be reported. That is all good.

Thank you so, so much.

Paul

2 Likes

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.