I’ve added another Zigbee extended color light (OSRAM RGBW Lightstrip). The appearance in MainUI is the same as for the HUE Bulbs (no control widget shown):
BUT: The color channel works as expected when I send the commands e.g from the console:
openhab> send ZIGRGBWStripBuero_Color ON
Command has been sent successfully.
openhab> send ZIGRGBWStripBuero_Color 120,75,41
Command has been sent successfully.
openhab>
(and the light strip changes the color )
I’m going to open an issue in openhab-webui too to get the visibility there too (as long as the root cause is unclear).
EDIT2:
More testing showed me, although the command got accepted (and the color of the actual device changed accordingly), the items state remains UNDEF, notice last line:
openhab> send ZIGRGBWStripBuero_Color 120,75,45
Command has been sent successfully.
openhab> items list ZIGRGBWStripBuero_Color
ZIGRGBWStripBuero_Color (Type=ColorItem, State=UNDEF, Label=Color, Category=ColorLight, Tags=[Point], Groups=[ZIGRGBWStripBuero])
This may indicate, that the reason for the issue is rather on the binding or the core than on the ui side though … or?
From my POV the PR for deCONZ which changes the channel types does not fix your - or any other - issue. Afair the UI elements are derived from a combination of item.type and Semantics. Did you try to use Point > Control for the color item?
I have a Sonoff SNXN-02 that is identified as eWeLink by the binding. It is a temperature and humidity sensor. It seems to pair correctly but no data ever comes in all I ever get is NULL. Based on documentation and people using zigbee2Mqtt there also should be a battery channel that is not showing up.
I am running OpenHAB 3.0.1 and the latest built in version of the binding. What data do you need from me to get this sensor working? Log file or anything else?
Hi,
the thread started with WSDCGQ01LM device. I can discover it and create a thing. Channels are also available. But the device stops after several hours to update the temperature and humidity values.
I’m using OH3 and a telegesis stick to connect directly via zigbee to the sensor. Any recommendation?
No - the PTI trace comes from the coordinator - it’s basically a debug output from the NCP and if there’s an assert (which happens when the NCP gets into a state from which it can’t recover) then it will print a bunch of stuff out this port so that Silabs can work out what happened.
for the update. It seems only to happen if I reinitialize the controller and do not restart openhab.
So it also looks like it creates an Error code 3 before.
Yes, but to be honest, it doesn’t provide you much information. This is already provided in the debug log - ie the binding, or more specifically the zigbee library, already uses this table to log the error.
That was fast. I tried this 6 gang Zemismart with the Zigbee bidding, but I got the " HANDLER_INITIALIZING_ERROR
No supported clusters found" on the thing. I can see lots of information, but no channels in paper UI. I just figured it was not supported yet.
From what I can see in the link you provided, this is just provided standard ON/OFF services, so it should work fine. That said, it doesn’t explicitly state this although it does talk about ON/OFF and TOGGLE which are features of the OnOffCluster and should be supported.
However maybe it is really something custom and not the standard clusters - I’m not really sure. Does it produce an XML file (in the userdata/zigbee/network folder) for the node? If so, please post this - or use the console command zigbee fingerprint for the node and post the results.
)
