@mike.maxwell over at Aurora Aone Rotary Dimmer you mentioned that the built in generic ZigBee dimmer driver has hardcoded destination endpoints .... is that true for all built in generic ZigBee drivers?
I just came up against this for a cheap ZHA inline relay - SZ manufacturer, Lamp_01 product - this is mentioned in several places in the forum with various hacked community drivers to get it working, mostly successfully. For example at Cheap uk Zigbee switch for £10
I bought a bunch of these and for mine they all report endpointId of 0x0B so none of the generic ZigBee drivers would work, equally so none of the other community drivers either.
I've pulled something together for now that works, but is it worth you modifying all the generic drivers to use the reported endpoints as you mentioned in that other thread?
I would imagine that this would get many more devices working out-of-the-box with the generic drivers?
Also, somewhat related, for the shortcut commands such as:
These commands use the first reported endpoint for the advertized cluster. Some, but not all the zigbee drivers have have endpoints hardcoded.
It's an easy change on our end.
Not sure why they didn't work before, nor why none of the generic drivers I tried worked (unless just unlucky that they were all ones that have hardcoded endpointId ... I tried most of the switch / outlet / bulb ones).
Yeah, now this one also works with the generic drivers Outlet / Switch as well if I switch over to them .... on/off/refresh/config .... bizarre.
Doesn't make sense .... and it's not just me since other people report the same in those other threads too ..... oh well, least I can switch to a built-in driver now and remove mine.
I've got a bunch more of these in the boxes still so will try and reproduce on some fresh ones at a later date.
Same experience as me, the device doesn't work with any of the generic drivers ....
Which is what started me down the path of knocking up my own driver to see what was going on.
I'll try and reproduce it later with a fresh one to get the bottom of it, only thing I can think perhaps is the generic drivers try and configure it in some way that it doesn't like.