OH3: ZigBeeThingHandler] - No supported clusters found (70 down lights down the drain?!)

Max_G · September 14, 2023, 4:25am

Platform information:
- Hardware: Raspberry Pi 4 Model B Rev 1.1 ; 4GB memory
- Host: Linux openhabian 5.15.76-v7l+ #1597 SMP Fri Nov 4 12:14:58 GMT 2022 armv7l GNU/Linux
- Distro: Raspbian GNU/Linux 11 (bullseye)
- openjdk version “11.0.18” 2023-01-17
- OpenJDK Runtime Environment (build 11.0.18+10-post-Raspbian-1deb11u1)
- OpenJDK Server VM (build 11.0.18+10-post-Raspbian-1deb11u1, mixed mode)
OH Version: 3.4.3 (Build)
- Installation method: openhabian
Ember coordinator

openhab> bundle:list | grep -i zigbee
241 │ Active │  80 │ 1.4.7                  │ com.zsmartsystems.zigbee
242 │ Active │  80 │ 1.4.7                  │ com.zsmartsystems.zigbee.console
243 │ Active │  80 │ 1.4.7                  │ com.zsmartsystems.zigbee.console.ember
244 │ Active │  80 │ 1.4.7                  │ com.zsmartsystems.zigbee.console.telegesis
245 │ Active │  80 │ 1.4.7                  │ com.zsmartsystems.zigbee.dongle.cc2531
246 │ Active │  80 │ 1.4.7                  │ com.zsmartsystems.zigbee.dongle.ember
247 │ Active │  80 │ 1.4.7                  │ com.zsmartsystems.zigbee.dongle.telegesis
248 │ Active │  80 │ 1.4.7                  │ com.zsmartsystems.zigbee.dongle.xbee
282 │ Active │  80 │ 3.4.3                  │ openHAB Add-ons :: Bundles :: ZigBee Binding
283 │ Active │  80 │ 3.4.3                  │ openHAB Add-ons :: Bundles :: ZigBee CC2531 Bridge
284 │ Active │  80 │ 3.4.3                  │ openHAB Add-ons :: Bundles :: ZigBee Console
285 │ Active │  80 │ 3.4.3                  │ openHAB Add-ons :: Bundles :: ZigBee Console Ember
286 │ Active │  80 │ 3.4.3                  │ openHAB Add-ons :: Bundles :: ZigBee Console Telegesis
287 │ Active │  80 │ 3.4.3                  │ openHAB Add-ons :: Bundles :: ZigBee Ember Bridge
288 │ Active │  80 │ 3.4.3                  │ openHAB Add-ons :: Bundles :: ZigBee Firmware Provider
289 │ Active │  80 │ 3.4.3                  │ openHAB Add-ons :: Bundles :: ZigBee Serial Driver
290 │ Active │  80 │ 3.4.3                  │ openHAB Add-ons :: Bundles :: ZigBee Telegesis Bridge
291 │ Active │  80 │ 3.4.3                  │ openHAB Add-ons :: Bundles :: ZigBee XBee Bridge

I think I shot myself in the foot by buying 70 10 Watt RGBCW LED down lights, without testing one first, and which as it turns out, produce a No supported clusters found error, when trying to add these to OH.

I read somewhere on the forum that Chris posted, that some Chinese Zigbee devices (despite claiming to be Zigbee v2 or v3 compliant) do not implement the standard protocol… with Chris also saying (in 2022) he is refactoring the code to cater for this as well.

However, the questions I have:

Will zigbee2mqtt have the same problem? Or can someone say that it works better with these Chinese bulbs?!
Is zigbee2mqtt the better binding compared to the Zigbee binding? I understand it has a ‘long press’ functionality, which the Zigbee binding does not have.

I have attached the openhab.log with the necessary console commands enabled.

log:set debug org.openhab.binding.zigbee
log:set debug com.zsmartsystems.zigbee
log:set info com.zsmartsystems.zigbee.dongle.ember.internal.ash

I can’t make sense of the log; even when using this log viewer… other than it looks pretty.

Actually the log file is too big, over the 1 MB allowed; the .zip it not allowed either, so I have attached a grep extract with device ID that does not get initialised.
AC66.txt (425.2 KB)

Happy to provide any other info that could be required.

Any hints appreciated.

Adding the device config:

I have since checked the fingerprint of the device (which also doesn’t tell me much).

openhab> zigbee fingerprint A4C1387F50BD34A0
|>| Node Descriptor
| |> Logical Type               ROUTER
| |> MAC Capabilities           [FULL_FUNCTION_DEVICE, MAINS_POWER, RECEIVER_ON_WHEN_IDLE]
| |> Stack Compliance           21
| |> Server Capabilities        []
| |> Buffer Size                66
| |> Incoming Transfer Size     66
| |> Outgoing Transfer Size     66
|
|>| Power Descriptor
| |> Available Power Sources    [MAINS]
| |> Current Power Source       MAINS
| |> Current Power Mode         RECEIVER_ON_IDLE
| |> Power Level                FULL
|
|>| ZDO
| |> ManagementBindRequest      SUCCESS
| |> IeeeAddressRequest         SUCCESS
| |> ManagementLqiRequest       SUCCESS
| |> ManagementRoutingRequest   NOT_SUPPORTED
|
|>| Basic Information
| |> Generic Device Class       
| |> Generic Device Type        
| |> Manufacturer Name          _TZ3210_s9lumfhn
| |> Model Indentifier          TS0505B
| |> Product Code               
| |> Product URL                
| |> Date Code                  
| |> Application Version        112
| |> Software Build ID          z.1.0
| |> Hardware Version           0
| |> Zcl Version                3
| |> Stack Version              2
| |
| |>| Endpoint 1
| | |> Profile                  0104  ZIGBEE_HOME_AUTOMATION
| | |> Device Type              010D  EXTENDED_COLOR_LIGHT
| | |> Device Version           1
| | |
| | |>| Input Clusters
| | | |
| | | |>| Cluster 0000 Basic
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |
| | | | |>| Commands Generated
| | | | | |> FAILURE
| | | | |
| | | | |>| Commands Received
| | | | |> FAILURE
| | | | |
| | | | |>| Attributes Supported
| | | | | |> 0000  ZCL Version                               >> UNSIGNED_8_BIT_INTEGER          3
| | | | | |> 0001  Application Version                       >> UNSIGNED_8_BIT_INTEGER          112
| | | | | |> 0002  Stack Version                             >> UNSIGNED_8_BIT_INTEGER          2
| | | | | |> 0003  HW Version                                >> UNSIGNED_8_BIT_INTEGER          0
| | | | | |> 0004  Manufacturer Name                         >> CHARACTER_STRING                _TZ3210_s9lumfhn
| | | | | |> 0005  Model Identifier                          >> CHARACTER_STRING                TS0505B
| | | | | |> 0007  Power Source                              >> ENUMERATION_8_BIT               0
| | | | | |> 0012  Device Enabled                            >> BOOLEAN                         true
| | | | | |> 4000  SW Build ID                               >> CHARACTER_STRING                z.1.0
| | | | | |> FFFD  Cluster Revision                          >> UNSIGNED_16_BIT_INTEGER         1
| | | |
| | | |>| Cluster 0003 Identify
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster 0004 Groups
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster 0005 Scenes
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |
| | | | |>| Commands Generated
| | | | | |> FAILURE
| | | | |
| | | | |>| Commands Received
| | | | |> FAILURE
| | | | |
| | | | |>| Attributes Supported
| | | | | |> 0000  Scene Count                               >> UNSIGNED_8_BIT_INTEGER          0
| | | | | |> 0001  Current Scene                             >> UNSIGNED_8_BIT_INTEGER          0
| | | | | |> 0002  Current Group                             >> UNSIGNED_16_BIT_INTEGER         0
| | | | | |> 0003  Scene Valid                               >> BOOLEAN                         false
| | | | | |> 0004  Name Support                              >> BITMAP_8_BIT                    0
| | | | | |> FFFD  Cluster Revision                          >> UNSIGNED_16_BIT_INTEGER         1
| | | |
| | | |>| Cluster 0006 On/Off
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |
| | | | |>| Commands Generated
| | | | | |> FAILURE
| | | | |
| | | | |>| Commands Received
| | | | |> FAILURE
| | | | |
| | | | |>| Attributes Supported
| | | | | |> 0000  On Off                                    >> BOOLEAN                         true
| | | | | |> 4000  Global Scene Control                      >> BOOLEAN                         true
| | | | | |> 4001  On Time                                   >> UNSIGNED_16_BIT_INTEGER         0
| | | | | |> 4002  Off Wait Time                             >> UNSIGNED_16_BIT_INTEGER         0
| | | | | |> 4003  Start Up On Off                           >> ENUMERATION_8_BIT               255
| | | | | |> F000                                            >>                                 
| | | | | |> FFFD  Cluster Revision                          >> UNSIGNED_16_BIT_INTEGER         1
| | | |
| | | |>| Cluster 0008 Level Control
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |
| | | | |>| Commands Generated
| | | | | |> FAILURE
| | | | |
| | | | |>| Commands Received
| | | | |> FAILURE
| | | | |
| | | | |>| Attributes Supported
| | | | | |> 0000  Current Level                             >> UNSIGNED_8_BIT_INTEGER          254
| | | | | |> 0001  Remaining Time                            >> UNSIGNED_16_BIT_INTEGER         0
| | | | | |> 4000  Start Up Current Level                    >> UNSIGNED_8_BIT_INTEGER          254
| | | | | |> F000                                            >> UNSIGNED_16_BIT_INTEGER         1000
| | | | | |> FFFD  Cluster Revision                          >> UNSIGNED_16_BIT_INTEGER         1
| | | |
| | | |>| Cluster 000A Time
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster 0300 Color Control
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster 1000 
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster 1888 
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster FFEE 
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | |
| | |>| Output Clusters
| | | |
| | | |>| Cluster 0019 Ota Upgrade
| | | | |> Type                 Client [Output]
| | | | |> Manufacturer Spec.   No
| | | | |
| | | | |>| Commands Generated
| | | | | |> FAILURE
| | | | |
| | | | |>| Commands Received
| | | | |> FAILURE
| | | | |
| | | | |>| Attributes Supported
| | | | | |> 0000  Upgrade Server ID                         >> IEEE_ADDRESS                    FFFFFFFFFFFFFFFF
| | | | | |> 0001  File Offset                               >> UNSIGNED_32_BIT_INTEGER         -1
| | | | | |> 0002  Current File Version                      >> UNSIGNED_32_BIT_INTEGER         268514823
| | | | | |> 0003  Current ZigBee Stack Version              >> UNSIGNED_16_BIT_INTEGER         2
| | | | | |> 0004  Downloaded File Version                   >> UNSIGNED_32_BIT_INTEGER         -1
| | | | | |> 0005  Downloaded ZigBee Stack Version           >> UNSIGNED_16_BIT_INTEGER         65535
| | | | | |> 0006  Image Upgrade Status                      >> ENUMERATION_8_BIT               0
| | | | | |> 0007  Manufacturer ID                           >> UNSIGNED_16_BIT_INTEGER         4107
| | | | | |> 0008  Image Type ID                             >> UNSIGNED_16_BIT_INTEGER         65535
| | | | | |> 0009  Minimum Block Request Period              >> UNSIGNED_16_BIT_INTEGER         0
| | | | | |> FFFD  Cluster Revision                          >> UNSIGNED_16_BIT_INTEGER         1
| | | |
| | | |>| Cluster 1000 
| | | | |> Type                 Client [Output]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster FFEE 
| | | | |> Type                 Client [Output]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally

chris · September 14, 2023, 6:08am

These devices look like they should work fine. The reported clusters are standard, and the binding is detecting them just fine, and is also receiving reports from the device.

The reporting coming from the device is however being received too often - I’m not sure why that is as I don’t see any configuration setting this from the binding. There’s possibly also some non-standard attributes being reported - these are possibly Tuya specific, but the binding should ignore these.

ubeaut · September 14, 2023, 7:35am

Why don’t you just try zigbee2mqtt yourself and see if it works for you?

Max_G · September 14, 2023, 8:04am

Thank you Chris. I am stoked to get a reply from the man himself
The issue is; and I haven’t listed this (but should have), the thing is indiciated with a red Error:Handler.

The openhab.log also shows this error:

AshFrameHandler Exception processing EZSP frame: 
java.lang.IllegalArgumentException: No reader defined in ZigBeeDeserializer for DATA_40_BIT (0x0C)

To prove the point that something is not right, I added an ON|OFF switch to the colour channel that was seemingly detected, and it does not function.

Well, I have to get another coordinator, set it up and all… the problem is at least two-fold:

you are not solving a problem for one tech by switching to another tech
I would be a poorer man if I had to buy or invest in alternatives every time when something that ought to work doesn’t.

Thank you for your suggestion; I am not indicating with my response that I am ungrateful for it.

I was hoping someone has already experimented with both and chose one over the other, and tell, whether, the zigbee2mqtt binding is more forgiving or not with seemingly non-standard Zigbee implementations.

However, since, I do not plan to send the LEDs back, I may well try this route, rather than wasting a thousand dollars.

ubeaut · September 14, 2023, 8:17am

I only use zigbee2mqtt and find it’s great for what I do. I like the web UI it has.
I would just use the same ZigBee coordinator just to test it out.
Anyway hope it works out for you.

Max_G · September 14, 2023, 8:24am

Thanks, like I said, if not solution is forthcoming I have no other choice.

I better order another coordinator, as I only have a production system I do not want to mess with.
Actually maybe it is a good idea to get a test system

It’s funny MQTT comes up, as 80% of my system runs on MQTT…

ubeaut · September 14, 2023, 8:29am

I have spares and test systems. I don’t like to break my working system and I also like to have spare hardware in case.
I have the spare hardware so I can also use it on the test system.

chris · September 14, 2023, 9:09am

Yep - that’s kinda important

This should be an easy fix - I’ll try and update the library and binding over the next few days.

Max_G · September 14, 2023, 10:24am

I do have spares for all but the Ember Zigbee dongle; which is currently not available for purchase. Otherwise I’d bought one. I am thinking of replacing the Ember dongle with another brand that is recommended and compatible with OH, but get two of those; one for prod and one for test.

Yes, the mistakes of the uninitiated
Thank you very much for looking into this.
How will I learn the a new version of the add-on has become available?

Also, please do not hesitate to contact me for any additional info/test you need.

rlkoshak · September 14, 2023, 4:42pm

You’ll have to look at the list of supported devices there to see if they are supported.

It’s not a binding. It’s a separate service that exposes Zigbee devices over MQTT. It is not a part of the openHAB project.

Because it is it’s own separate project I suspect it has better support for “not quite Zigbee” devices than OH does. They have more developers and more people with diverse sets of devices contributing to it than OH does.

Watch GitHub - openhab/org.openhab.binding.zigbee: openHAB binding for ZigBee for PRs/updates. It will be a part of the next OH 4.1 snapshot build after the changes are merged.

anon71759204 · September 14, 2023, 10:04pm

| Zigbee2MQTT doesn’t look too promising, but your devices might work neverthless …

chris · September 15, 2023, 5:50am

Please keep an eye on this issue -:

It requires some changes to the distro before it can be merged, so it might take a few days to go through. Hopefully once this is done, it should provide support for the data type that was causing the exception, and the exception will go away and the device will work ok - hopefully

Jonas_Plaum · September 27, 2023, 7:21pm

I have the same Problem with Openhab 4.0.3, but with a different device.
I am running Openhabian 4.0.3 on an Raspberry Pi 4 with

Linux openhabian 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
openjdk 17.0.7 2023-04-18
OpenJDK Runtime Environment (build 17.0.7+7-Debian-1deb11u1)
OpenJDK 64-Bit Server VM (build 17.0.7+7-Debian-1deb11u1, mixed mode, sharing)

openhab> zigbee fingerprint A4C138D4C2F18BC3
|>| Node Descriptor
| |> Logical Type               ROUTER
| |> MAC Capabilities           [FULL_FUNCTION_DEVICE, MAINS_POWER, RECEIVER_ON_WHEN_IDLE]
| |> Stack Compliance           21
| |> Server Capabilities        []
| |> Buffer Size                66
| |> Incoming Transfer Size     66
| |> Outgoing Transfer Size     66
|
|>| Power Descriptor
| |> Available Power Sources    [MAINS]
| |> Current Power Source       MAINS
| |> Current Power Mode         RECEIVER_ON_IDLE
| |> Power Level                FULL
|
|>| ZDO
| |> ManagementBindRequest      SUCCESS
| |> IeeeAddressRequest         SUCCESS
| |> ManagementLqiRequest       SUCCESS
| |> ManagementRoutingRequest   TIMEOUT
|
|>| Basic Information
| |> Generic Device Class       
| |> Generic Device Type        
| |> Manufacturer Name          _TZE204_sxm7l9xa
| |> Model Indentifier          TS0601
| |> Product Code               
| |> Product URL                
| |> Date Code                  
| |> Application Version        74
| |> Software Build ID          
| |> Hardware Version           1
| |> Zcl Version                3
| |> Stack Version              0
| |
| |>| Endpoint 1
| | |> Profile                  0104  ZIGBEE_HOME_AUTOMATION
| | |> Device Type              0051  SMART_PLUG
| | |> Device Version           1
| | |
| | |>| Input Clusters
| | | |
| | | |>| Cluster 0000 Basic
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |
| | | | |>| Commands Generated
| | | | | |> FAILURE
| | | | |
| | | | |>| Commands Received
| | | | | |> FAILURE
| | | | |
| | | | |>| Attributes Supported
| | | | | |> 0000  ZCL Version                               >> UNSIGNED_8_BIT_INTEGER          3
| | | | | |> 0001  Application Version                       >> UNSIGNED_8_BIT_INTEGER          74
| | | | | |> 0002  Stack Version                             >> UNSIGNED_8_BIT_INTEGER          0
| | | | | |> 0003  HW Version                                >> UNSIGNED_8_BIT_INTEGER          1
| | | | | |> 0004  Manufacturer Name                         >> CHARACTER_STRING                _TZE204_sxm7l9xa
| | | | | |> 0005  Model Identifier                          >> CHARACTER_STRING                TS0601
| | | | | |> 0006  Date Code                                 >> CHARACTER_STRING                
| | | | | |> 0007  Power Source                              >> ENUMERATION_8_BIT               1
| | | | | |> FFDE                                            >> UNSIGNED_8_BIT_INTEGER          13
| | | | | |> FFFD  Cluster Revision                          >> UNSIGNED_16_BIT_INTEGER         2
| | | | | |> FFFE  Attribute Reporting Status                >> ENUMERATION_16_BIT              0
| | | |
| | | |>| Cluster 0004 Groups
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster 0005 Scenes
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |
| | | | |>| Commands Generated
| | | | | |> FAILURE
| | | | |
| | | | |>| Commands Received
| | | | | |> FAILURE
| | | | |
| | | | |>| Attributes Supported
| | | | | |> 0000  Scene Count                               >> UNSIGNED_8_BIT_INTEGER          0
| | | | | |> 0001  Current Scene                             >> UNSIGNED_8_BIT_INTEGER          0
| | | | | |> 0002  Current Group                             >> UNSIGNED_16_BIT_INTEGER         0
| | | | | |> 0003  Scene Valid                               >> BOOLEAN                         false
| | | | | |> 0004  Name Support                              >> BITMAP_8_BIT                    0
| | | | | |> FFFD  Cluster Revision                          >> UNSIGNED_16_BIT_INTEGER         2
| | | |
| | | |>| Cluster EF00 
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | |
| | |>| Output Clusters
| | | |
| | | |>| Cluster 000A Time
| | | | |> Type                 Client [Output]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster 0019 Ota Upgrade
| | | | |> Type                 Client [Output]
| | | | |> Manufacturer Spec.   No
| | | | |
| | | | |>| Commands Generated
| | | | | |> FAILURE
| | | | |
| | | | |>| Commands Received
| | | | | |> FAILURE
| | | | |
| | | | |>| Attributes Supported
| | | | | |> 0000  Upgrade Server ID                         >> IEEE_ADDRESS                    FFFFFFFFFFFFFFFF
| | | | | |> 0001  File Offset                               >> UNSIGNED_32_BIT_INTEGER         -1
| | | | | |> 0002  Current File Version                      >> UNSIGNED_32_BIT_INTEGER         74
| | | | | |> 0003  Current ZigBee Stack Version              >> UNSIGNED_16_BIT_INTEGER         2
| | | | | |> 0004  Downloaded File Version                   >> UNSIGNED_32_BIT_INTEGER         -1
| | | | | |> 0005  Downloaded ZigBee Stack Version           >> UNSIGNED_16_BIT_INTEGER         65535
| | | | | |> 0006  Image Upgrade Status                      >> ENUMERATION_8_BIT               0
| | | | | |> 0007  Manufacturer ID                           >> UNSIGNED_16_BIT_INTEGER         4417
| | | | | |> 0008  Image Type ID                             >> UNSIGNED_16_BIT_INTEGER         65535
| | | | | |> 0009  Minimum Block Request Period              >> UNSIGNED_16_BIT_INTEGER         0
| | | | | |> FFFD  Cluster Revision                          >> UNSIGNED_16_BIT_INTEGER         3
| |
| |>| Endpoint 242
| | |> Profile                  A1E0  ZIGBEE_GREEN_POWER
| | |> Device Type              0061
| | |> Device Version           0

Do you thinks this is the same problem or is something wrong with my device?