I recently moved by bulbs from the hue hub into the zigbee binding. Works really nicely but I had many switches assigned to dimmers and colors.
The conversion of color/dimmer into switches was flawless with the hue bridge but since I have the zigbee add-on, the switches do not follow the dimmers anymore. I guess this could also be linked to OH 2.5.8 which I upgraded around the same time. Any suggestions?
I have tagged tthis as zigbee for you. The binding documentation has a section for when things do not go as planned ans says to gather debug logs so the system can tell you what is happening. Have you done that? Posting an unfiltered debug log can assist others in advising you.
There is also a log viewer that may help you troubleshoot,
I do not use Zogbee personally but our developer or other senior users should be along shortly.
What do you mean by this statement? The binding should only produce one channel - either a switch, OR a dimmer. If the bulb just supports on/off, then you’ll just get a switch channel. If it supports level control, then it will only provide a dimmer channel (ie no switch). So I’m not sure what you mean when you say the switch doesn’t follow the dimmer?
I have created few groups configured as switch that have a bunch of dimmers. Also in my sitemap, I have switches assigned to dimmers. The switches do work but they have stopped following the dimmer. If I change the dimmer to 0, the switch doesn’t go to OFF anymore. Does this make more sense?
Yes I have read the logging configuration section. I’ll have another look at getting debug logs, but I have struggled to get good debug logs because the addons namespaces do not always follow the binding… especially for zigbee, there are couple other namespaces involved (putting zigbee did not generate anything useful). And I’m not always sure what to set on debug level.
Sort of, but without logs it’s going to be impossible to really work out why this is. It’s possibly not related to the binding - I really don’t know.
I’d suggest to read the binding docs - it defines exactly what to set.
So there is an error in the documentation?? I doubt the binding has changed.
log:set debug org.openhab.binding.zigbee
log:set debug com.zsmartsystems.zigbee
log:set info com.zsmartsystems.zigbee.dongle.ember.internal.ash
From
In short, Read the (Fine) Manual!
Thank you - I had not realized this was all documented inside the Zigbee binding. I was searching the log documentation 
I think you might be starting at the wrong end here. Is your initial post description about what you see and use in some UI? Maybe tell us more about that. Sitemap entries?
Well I added all the zigbee logging and not sure how that helps…
My issue is ultimately quite simple
Switch item=Garage_Occupancy
Switch item=GarageHueLight_Brightness label="Garage Light" icon="lightbulb"
The 2 line rule
rule "Garage door light"
when
Item Garage_Occupancy changed //received command
then
GarageHueLight_Brightness.sendCommand(Garage_Occupancy.state.toString)
end
The rule does work but doesn’t update Switch item=GarageHueLight_Brightness in the basic UI which used to work with the hue binding (either that or a 2.5.8 issue). I have a similar issue with groups. The basic UI is not updated. Control on the group switch works.
Actually there seems to be something odd in the logs… at the end of a switch it says "[e.transaction.ZigBeeTransactionQueue] - 001788010363575E: transactionComplete COMPLETE 0"
2020-09-15 12:25:54.439 [vent.ItemStateChangedEvent] - GarageHueLight_Brightness changed from 0 to 100
==> /var/log/openhab2/openhab.log <==
2020-09-15 12:25:54.443 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 001788010363575E: Added transaction to queue, len=1, transaction=ZigBeeTransaction [ieeeAddress=001788010363575E queueTime=0, state=WAITING, sendCnt=0, command=OnCommand [On/Off: 0000/0 -> 7357/11, cluster=0006, TID=--]]
2020-09-15 12:25:54.444 [DEBUG] [transaction.ZigBeeTransactionManager] - 7357/11: Sending ZigBeeTransaction [ieeeAddress=001788010363575E queueTime=1, state=WAITING, sendCnt=0, command=OnCommand [On/Off: 0000/0 -> 7357/11, cluster=0006, TID=DC]]
2020-09-15 12:25:54.445 [DEBUG] [transaction.ZigBeeTransactionManager] - transactionListenerAdded: 1 outstanding
2020-09-15 12:25:54.446 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: OnCommand [On/Off: 0000/0 -> 7357/11, cluster=0006, TID=DC]
2020-09-15 12:25:54.447 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX ZCL: ZclHeader [frameType=CLUSTER_SPECIFIC_COMMAND, manufacturerSpecific=false, direction=CLIENT_TO_SERVER, disableDefaultResponse=false, manufacturerCode=0, sequenceNumber=220, commandId=1]
2020-09-15 12:25:54.448 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0000/1, destinationAddress=7357/11, profile=0104, cluster=0006, addressMode=DEVICE, radius=8, apsSecurity=false, ackRequest=true, apsCounter=7E, rssi=--, lqi=--, payload=01 DC 01]
2020-09-15 12:25:54.448 [DEBUG] [31.network.impl.CommandInterfaceImpl] - -> AF_DATA_REQUEST (Packet: subsystem=null, length=13, apiId=24 01, data=FE 0D 24 01 57 73 0B 01 06 00 7E 30 08 03 01 DC 01 99, checksum=99, error=false)
2020-09-15 12:25:54.462 [DEBUG] [31.network.impl.CommandInterfaceImpl] - <- AF_DATA_SRSP (FE 01 64 01 00 64)
2020-09-15 12:25:54.463 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX STA: msgTag=DC state=TX_ACK
2020-09-15 12:25:54.463 [DEBUG] [transaction.ZigBeeTransactionManager] - notifyTransactionProgress: TID=DC, state=TX_ACK, outstanding=1
2020-09-15 12:25:54.464 [DEBUG] [zigbee.transaction.ZigBeeTransaction] - Transaction state updated: TID DC -> TX_ACK == TRANSMITTED
2020-09-15 12:25:54.482 [DEBUG] [31.network.impl.CommandInterfaceImpl] - <-- ZToolPacket (FE 03 45 C4 57 73 00 A6)
2020-09-15 12:25:54.482 [DEBUG] [31.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem=null, length=3, apiId=45 C4, data=FE 03 45 C4 57 73 00 A6, checksum=A6, error=false
2020-09-15 12:25:54.483 [DEBUG] [e.dongle.cc2531.ZigBeeDongleTiCc2531] - Unhandled ZToolPacket type 0x45c4
2020-09-15 12:25:54.563 [DEBUG] [31.network.impl.CommandInterfaceImpl] - <-- AF_DATA_CONFIRM (FE 03 44 80 00 01 7E B8)
2020-09-15 12:25:54.564 [DEBUG] [31.network.impl.CommandInterfaceImpl] - Received Async Cmd: AF_DATA_CONFIRM(Endpoint=1, Status=SUCCESS(0), TransID=126)
2020-09-15 12:25:54.564 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX STA: msgTag=DC state=RX_ACK
2020-09-15 12:25:54.565 [DEBUG] [transaction.ZigBeeTransactionManager] - notifyTransactionProgress: TID=DC, state=RX_ACK, outstanding=1
2020-09-15 12:25:54.565 [DEBUG] [zigbee.transaction.ZigBeeTransaction] - Transaction state updated: TID DC -> RX_ACK == ACKED
2020-09-15 12:25:54.583 [DEBUG] [31.network.impl.CommandInterfaceImpl] - <-- ZToolPacket (FE 03 45 C4 57 73 00 A6)
2020-09-15 12:25:54.584 [DEBUG] [31.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem=null, length=3, apiId=45 C4, data=FE 03 45 C4 57 73 00 A6, checksum=A6, error=false
2020-09-15 12:25:54.584 [DEBUG] [e.dongle.cc2531.ZigBeeDongleTiCc2531] - Unhandled ZToolPacket type 0x45c4
2020-09-15 12:25:54.665 [DEBUG] [31.network.impl.CommandInterfaceImpl] - <-- AF_INCOMING_MSG (FE 19 44 81 00 00 06 00 57 73 0B 01 00 1F 00 CD 2C 03 00 00 05 18 DC 0B 01 00 57 73 1D FB)
2020-09-15 12:25:54.665 [DEBUG] [31.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem=null, length=25, apiId=44 81, data=FE 19 44 81 00 00 06 00 57 73 0B 01 00 1F 00 CD 2C 03 00 00 05 18 DC 0B 01 00 57 73 1D FB, checksum=FB, error=false
2020-09-15 12:25:54.666 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=7357/11, destinationAddress=0000/1, profile=0104, cluster=0006, addressMode=null, radius=0, apsSecurity=false, ackRequest=false, apsCounter=--, rssi=--, lqi=--, payload=18 DC 0B 01 00]
2020-09-15 12:25:54.666 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=false, direction=SERVER_TO_CLIENT, disableDefaultResponse=true, manufacturerCode=0, sequenceNumber=220, commandId=11]
2020-09-15 12:25:54.667 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: DefaultResponse [On/Off: 7357/11 -> 0000/1, cluster=0006, TID=DC, commandIdentifier=1, statusCode=SUCCESS]
2020-09-15 12:25:54.667 [DEBUG] [transaction.ZigBeeTransactionManager] - notifyTransactionCommand: DefaultResponse [On/Off: 7357/11 -> 0000/1, cluster=0006, TID=DC, commandIdentifier=1, statusCode=SUCCESS]
2020-09-15 12:25:54.668 [DEBUG] [transaction.ZigBeeTransactionManager] - Transaction complete: ZigBeeTransaction [ieeeAddress=001788010363575E queueTime=225, state=COMPLETE, sendCnt=1, command=OnCommand [On/Off: 0000/0 -> 7357/11, cluster=0006, TID=DC]]
2020-09-15 12:25:54.668 [DEBUG] [transaction.ZigBeeTransactionManager] - transactionListenerRemoved: 0 outstanding
2020-09-15 12:25:54.668 [DEBUG] [e.dongle.cc2531.ZigBeeDongleTiCc2531] - Unhandled ZToolPacket type 0x4481
2020-09-15 12:25:54.669 [DEBUG] [e.transaction.ZigBeeTransactionQueue] - 001788010363575E: transactionComplete COMPLETE 0Can we just have an events.log of the issue?
Some zigbee devices do not immediately report new status when commanded, and the zigbee binding vetoes the usual autoupdate effect that openHAB would normally apply.
There is a workaround, apply autoupdate=“true” to your zigbee linked Item to void the veto.
Can you explain what is odd please?
Also, what did you do, and what di you expect to see.
That will tell us nothing about what is happening in the ZigBee binding. The debug log will provide all the information you get from the event log - the event log will give none of the information that you get from the debug log.