Dimming via automation does not work

Hi, I am having ikea blubs connected with my aeotec hub. Suddenly my automation to Set the dimmer to 100% when opening the door does not Work. The automation worked for years.

What I’ve analyzed:

  • The automation gets triggered
  • The bulbs appear in reallife dimmed to about 30%
  • In the App the Bulbs Shows up as dimmed to 100%
  • When I the try to dimm the light manually via app to e.g 80%, the slider jumps for a second to about 30% and the Instantly jumps to 80%, the bulbs change in reallife to real 80%
  • Restarting the hub does not help
  • Restarting the bulbs does not Work

I would suggest doing driver logging to see what is being to and received from the device. You can use the ST CLI on a Windows/Linux/macOS computer and run the command “smartthings edge:drivers:logcat” and cut and paste the output here using the pre-formatted text option.

2024-12-17T22:56:22.214179335Z TRACE Zigbee Contact  Received event with handler zigbee
2024-12-17T22:56:22.217993751Z INFO Zigbee Contact  <ZigbeeDevice: d7c75c08-6404-4040-9980-4d928aa6dabf [0xEBB2] (Klo Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xEBB2, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xD2, rssi: -61, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x9E, ZCLCommandId: 0x00 >, < ZoneStatusChangeNotification || zone_status: 0x0001, extended_status: 0x00, zone_id: 0x01, delay: 0x0000 > > >
2024-12-17T22:56:22.233856960Z TRACE Zigbee Contact  Found ZigbeeMessageDispatcher handler in zigbee_contact
2024-12-17T22:56:22.234812918Z INFO Zigbee Contact  Executing ZclClusterCommandHandler: cluster: IASZone, command: ZoneEnrollResponse
2024-12-17T22:56:22.239929793Z INFO Zigbee Contact  <ZigbeeDevice: d7c75c08-6404-4040-9980-4d928aa6dabf [0xEBB2] (Klo Sensor)> emitting event: {"attribute_id":"contact","capability_id":"contactSensor","component_id":"main","state":{"value":"open"}}
2024-12-17T22:56:22.370403960Z INFO Zigbee Switch  hub handled command: e0db06c7-8817-411a-925a-68f5eff96e98:main:switch:on []
2024-12-17T22:56:22.372300710Z INFO Zigbee Switch  hub sending: Zigbee message (e0db06c7-8817-411a-925a-68f5eff96e98): <src_addr: 0x00, src_endpoint: 0x1, dest_addr: 0x664d, dest_endpoint: 0x1, profile: 0x104, cluster: 0x06, data: [01, 00, 01]>
2024-12-17T22:56:22.375774293Z DEBUG Zigbee Contact  Klo Sensor device thread event handled
2024-12-17T22:56:22.378643168Z INFO Zigbee Switch  hub handled command: e0db06c7-8817-411a-925a-68f5eff96e98:main:colorTemperature:setColorTemperature [3000]
2024-12-17T22:56:22.393449293Z INFO Zigbee Switch  hub sending: Zigbee message (e0db06c7-8817-411a-925a-68f5eff96e98): <src_addr: 0x00, src_endpoint: 0x1, dest_addr: 0x664d, dest_endpoint: 0x1, profile: 0x104, cluster: 0x06, data: [01, 00, 01]>
2024-12-17T22:56:22.394815293Z INFO Zigbee Switch  hub handled command: e0db06c7-8817-411a-925a-68f5eff96e98:main:switchLevel:setLevel [100]
2024-12-17T22:56:22.396559668Z INFO Zigbee Switch  hub sending: Zigbee message (e0db06c7-8817-411a-925a-68f5eff96e98): <src_addr: 0x00, src_endpoint: 0x1, dest_addr: 0x664d, dest_endpoint: 0x1, profile: 0x104, cluster: 0x08, data: [01, 00, 04, fe, ff, ff, 00, 00]>
2024-12-17T22:56:22.397539835Z INFO Zigbee Switch  hub sending: Zigbee message (e0db06c7-8817-411a-925a-68f5eff96e98): <src_addr: 0x00, src_endpoint: 0x1, dest_addr: 0x664d, dest_endpoint: 0x1, profile: 0x104, cluster: 0x300, data: [01, 00, 0a, 4d, 01, 00, 00, 00, 00]>
2024-12-17T22:56:22.404120210Z INFO Zigbee Switch  hub handled command: 46585eef-c10f-493a-9b49-de9019e4a2eb:main:switch:on []
2024-12-17T22:56:22.405157252Z INFO Zigbee Switch  hub sending: Zigbee message (46585eef-c10f-493a-9b49-de9019e4a2eb): <src_addr: 0x00, src_endpoint: 0x1, dest_addr: 0xdda2, dest_endpoint: 0x1, profile: 0x104, cluster: 0x06, data: [01, 00, 01]>
2024-12-17T22:56:22.415774210Z INFO Zigbee Switch  hub handled command: 46585eef-c10f-493a-9b49-de9019e4a2eb:main:colorTemperature:setColorTemperature [3000]
2024-12-17T22:56:22.418087377Z TRACE Zigbee Switch  Received event with handler device_lifecycle
2024-12-17T22:56:22.419073127Z INFO Zigbee Switch  hub sending: Zigbee message (46585eef-c10f-493a-9b49-de9019e4a2eb): <src_addr: 0x00, src_endpoint: 0x1, dest_addr: 0xdda2, dest_endpoint: 0x1, profile: 0x104, cluster: 0x06, data: [01, 00, 01]>
2024-12-17T22:56:22.420423127Z INFO Zigbee Switch  hub handled command: 46585eef-c10f-493a-9b49-de9019e4a2eb:main:switchLevel:setLevel [100]
2024-12-17T22:56:22.422167377Z INFO Zigbee Switch  hub sending: Zigbee message (46585eef-c10f-493a-9b49-de9019e4a2eb): <src_addr: 0x00, src_endpoint: 0x1, dest_addr: 0xdda2, dest_endpoint: 0x1, profile: 0x104, cluster: 0x08, data: [01, 00, 04, fe, ff, ff, 00, 00]>
2024-12-17T22:56:22.433625043Z INFO Zigbee Switch  hub sending: Zigbee message (46585eef-c10f-493a-9b49-de9019e4a2eb): <src_addr: 0x00, src_endpoint: 0x1, dest_addr: 0xdda2, dest_endpoint: 0x1, profile: 0x104, cluster: 0x300, data: [01, 00, 0a, 4d, 01, 00, 00, 00, 00]>
2024-12-17T22:56:22.436825793Z INFO Zigbee Switch  hub handled command: fe27a94e-7371-4ffa-b806-7f7c1dc8f48a:main:switch:on []
2024-12-17T22:56:22.438214793Z INFO Zigbee Switch  hub sending: Zigbee message (fe27a94e-7371-4ffa-b806-7f7c1dc8f48a): <src_addr: 0x00, src_endpoint: 0x1, dest_addr: 0x1083, dest_endpoint: 0x1, profile: 0x104, cluster: 0x06, data: [01, 00, 01]>
2024-12-17T22:56:22.441084835Z INFO Zigbee Switch  hub handled command: fe27a94e-7371-4ffa-b806-7f7c1dc8f48a:main:colorTemperature:setColorTemperature [3000]
2024-12-17T22:56:22.464237210Z INFO Zigbee Switch  hub sending: Zigbee message (fe27a94e-7371-4ffa-b806-7f7c1dc8f48a): <src_addr: 0x00, src_endpoint: 0x1, dest_addr: 0x1083, dest_endpoint: 0x1, profile: 0x104, cluster: 0x06, data: [01, 00, 01]>
2024-12-17T22:56:22.465498835Z INFO Zigbee Switch  hub handled command: fe27a94e-7371-4ffa-b806-7f7c1dc8f48a:main:switchLevel:setLevel [100]
2024-12-17T22:56:22.467152252Z INFO Zigbee Switch  hub sending: Zigbee message (fe27a94e-7371-4ffa-b806-7f7c1dc8f48a): <src_addr: 0x00, src_endpoint: 0x1, dest_addr: 0x1083, dest_endpoint: 0x1, profile: 0x104, cluster: 0x08, data: [01, 00, 04, fe, ff, ff, 00, 00]>
2024-12-17T22:56:22.468122835Z INFO Zigbee Switch  hub sending: Zigbee message (fe27a94e-7371-4ffa-b806-7f7c1dc8f48a): <src_addr: 0x00, src_endpoint: 0x1, dest_addr: 0x1083, dest_endpoint: 0x1, profile: 0x104, cluster: 0x300, data: [01, 00, 0a, 4d, 01, 00, 00, 00, 00]>
2024-12-17T22:56:22.522191877Z TRACE Zigbee Switch  Received event with handler device_lifecycle
2024-12-17T22:56:22.858870002Z TRACE Zigbee Switch  Received event with handler device_lifecycle
2024-12-17T22:56:23.098772627Z TRACE Zigbee Switch  Received event with handler zigbee
2024-12-17T22:56:23.099738627Z INFO Zigbee Switch  <ZigbeeDevice: e0db06c7-8817-411a-925a-68f5eff96e98 [0x664D] (Klo 1.3)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x664D, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xCA, rssi: -79, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x1F, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2024-12-17T22:56:23.323257918Z TRACE Zigbee Switch  Found ZigbeeMessageDispatcher handler in zigbee_switch
2024-12-17T22:56:23.330704377Z INFO Zigbee Switch  Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2024-12-17T22:56:23.332222835Z INFO Zigbee Switch  <ZigbeeDevice: e0db06c7-8817-411a-925a-68f5eff96e98 [0x664D] (Klo 1.3)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2024-12-17T22:56:23.354455835Z DEBUG Zigbee Switch  Klo 1.3 device thread event handled
2024-12-17T22:56:23.355420377Z TRACE Zigbee Switch  Received event with handler zigbee
2024-12-17T22:56:23.367961835Z INFO Zigbee Switch  <ZigbeeDevice: e0db06c7-8817-411a-925a-68f5eff96e98 [0x664D] (Klo 1.3)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x664D, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xCE, rssi: -79, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x34, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2024-12-17T22:56:23.466433002Z TRACE Zigbee Switch  Found ZigbeeMessageDispatcher handler in zigbee_switch
2024-12-17T22:56:23.469124293Z INFO Zigbee Switch  Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2024-12-17T22:56:23.473421168Z INFO Zigbee Switch  <ZigbeeDevice: e0db06c7-8817-411a-925a-68f5eff96e98 [0x664D] (Klo 1.3)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2024-12-17T22:56:23.494490960Z DEBUG Zigbee Switch  Klo 1.3 device thread event handled
2024-12-17T22:56:23.495487918Z TRACE Zigbee Switch  Received event with handler zigbee
2024-12-17T22:56:23.496398543Z INFO Zigbee Switch  <ZigbeeDevice: e0db06c7-8817-411a-925a-68f5eff96e98 [0x664D] (Klo 1.3)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x664D, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xC2, rssi: -79, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x35, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2024-12-17T22:56:23.586234877Z TRACE Zigbee Switch  Found ZigbeeMessageDispatcher handler in zigbee_switch
2024-12-17T22:56:23.588931710Z INFO Zigbee Switch  Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2024-12-17T22:56:23.593245460Z INFO Zigbee Switch  <ZigbeeDevice: e0db06c7-8817-411a-925a-68f5eff96e98 [0x664D] (Klo 1.3)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2024-12-17T22:56:23.614084043Z DEBUG Zigbee Switch  Klo 1.3 device thread event handled
2024-12-17T22:56:23.615078043Z TRACE Zigbee Switch  Received event with handler zigbee
2024-12-17T22:56:23.615984585Z INFO Zigbee Switch  <ZigbeeDevice: e0db06c7-8817-411a-925a-68f5eff96e98 [0x664D] (Klo 1.3)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x664D, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Level >, lqi: 0xD0, rssi: -81, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x36, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x04, ZclStatus: SUCCESS > > >
2024-12-17T22:56:23.695336960Z DEBUG Zigbee Switch  Klo 1.3 device thread event handled
2024-12-17T22:56:23.698247752Z TRACE Zigbee Switch  Received event with handler zigbee
2024-12-17T22:56:23.706842002Z INFO Zigbee Switch  <ZigbeeDevice: e0db06c7-8817-411a-925a-68f5eff96e98 [0x664D] (Klo 1.3)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x664D, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: ColorControl >, lqi: 0xC8, rssi: -78, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x37, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x0A, ZclStatus: SUCCESS > > >
2024-12-17T22:56:23.803550293Z DEBUG Zigbee Switch  Klo 1.3 device thread event handled
2024-12-17T22:56:23.808935210Z TRACE Zigbee Switch  Received event with handler zigbee
2024-12-17T22:56:23.816098168Z INFO Zigbee Switch  <ZigbeeDevice: 46585eef-c10f-493a-9b49-de9019e4a2eb [0xDDA2] (Klo 1.2)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xDDA2, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xD0, rssi: -77, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x1D, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2024-12-17T22:56:23.909818668Z TRACE Zigbee Switch  Found ZigbeeMessageDispatcher handler in zigbee_switch
2024-12-17T22:56:23.912482210Z INFO Zigbee Switch  Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2024-12-17T22:56:23.916824418Z INFO Zigbee Switch  <ZigbeeDevice: 46585eef-c10f-493a-9b49-de9019e4a2eb [0xDDA2] (Klo 1.2)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2024-12-17T22:56:23.944514502Z DEBUG Zigbee Switch  Klo 1.2 device thread event handled
2024-12-17T22:56:23.945531668Z TRACE Zigbee Switch  Received event with handler zigbee
2024-12-17T22:56:23.946462335Z INFO Zigbee Switch  <ZigbeeDevice: 46585eef-c10f-493a-9b49-de9019e4a2eb [0xDDA2] (Klo 1.2)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xDDA2, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xCE, rssi: -76, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x39, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2024-12-17T22:56:24.063796543Z TRACE Zigbee Switch  Found ZigbeeMessageDispatcher handler in zigbee_switch
2024-12-17T22:56:24.066707127Z INFO Zigbee Switch  Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2024-12-17T22:56:24.071193168Z INFO Zigbee Switch  <ZigbeeDevice: 46585eef-c10f-493a-9b49-de9019e4a2eb [0xDDA2] (Klo 1.2)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2024-12-17T22:56:24.094070835Z DEBUG Zigbee Switch  Klo 1.2 device thread event handled
2024-12-17T22:56:24.095079377Z TRACE Zigbee Switch  Received event with handler zigbee
2024-12-17T22:56:24.096008043Z INFO Zigbee Switch  <ZigbeeDevice: 46585eef-c10f-493a-9b49-de9019e4a2eb [0xDDA2] (Klo 1.2)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xDDA2, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xCE, rssi: -76, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x38, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2024-12-17T22:56:24.180311377Z TRACE Zigbee Switch  Found ZigbeeMessageDispatcher handler in zigbee_switch
2024-12-17T22:56:24.183101960Z INFO Zigbee Switch  Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2024-12-17T22:56:24.187930627Z INFO Zigbee Switch  <ZigbeeDevice: 46585eef-c10f-493a-9b49-de9019e4a2eb [0xDDA2] (Klo 1.2)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2024-12-17T22:56:24.203965210Z DEBUG Zigbee Switch  Klo 1.2 device thread event handled
2024-12-17T22:56:24.204941043Z TRACE Zigbee Switch  Received event with handler zigbee
2024-12-17T22:56:24.208375960Z INFO Zigbee Switch  <ZigbeeDevice: 46585eef-c10f-493a-9b49-de9019e4a2eb [0xDDA2] (Klo 1.2)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xDDA2, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Level >, lqi: 0xC2, rssi: -75, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x3A, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x04, ZclStatus: SUCCESS > > >
2024-12-17T22:56:24.296422210Z DEBUG Zigbee Switch  Klo 1.2 device thread event handled
2024-12-17T22:56:24.299262543Z TRACE Zigbee Switch  Received event with handler zigbee
2024-12-17T22:56:24.305846252Z INFO Zigbee Switch  <ZigbeeDevice: 46585eef-c10f-493a-9b49-de9019e4a2eb [0xDDA2] (Klo 1.2)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xDDA2, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Level >, lqi: 0xCA, rssi: -73, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x1E, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint8, CurrentLevel: 0x54 > > > >
2024-12-17T22:56:24.398509960Z TRACE Zigbee Switch  Found ZigbeeMessageDispatcher handler in zigbee_switch
2024-12-17T22:56:24.401439960Z INFO Zigbee Switch  Executing ZclClusterAttributeValueHandler: cluster: Level, attribute: CurrentLevel
2024-12-17T22:56:24.406133335Z INFO Zigbee Switch  <ZigbeeDevice: 46585eef-c10f-493a-9b49-de9019e4a2eb [0xDDA2] (Klo 1.2)> emitting event: {"attribute_id":"level","capability_id":"switchLevel","component_id":"main","state":{"value":33}}
2024-12-17T22:56:24.434505252Z DEBUG Zigbee Switch  Klo 1.2 device thread event handled
2024-12-17T22:56:24.435513377Z TRACE Zigbee Switch  Received event with handler zigbee
2024-12-17T22:56:24.436436502Z INFO Zigbee Switch  <ZigbeeDevice: 46585eef-c10f-493a-9b49-de9019e4a2eb [0xDDA2] (Klo 1.2)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xDDA2, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: ColorControl >, lqi: 0xD0, rssi: -73, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x3B, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x0A, ZclStatus: SUCCESS > > >
2024-12-17T22:56:24.520886877Z DEBUG Zigbee Switch  Klo 1.2 device thread event handled
2024-12-17T22:56:24.523992752Z TRACE Zigbee Switch  Received event with handler zigbee
2024-12-17T22:56:24.565062377Z INFO Zigbee Switch  <ZigbeeDevice: fe27a94e-7371-4ffa-b806-7f7c1dc8f48a [0x1083] (Klo 1.1)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1083, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x74, rssi: -99, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x23, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2024-12-17T22:56:24.663721460Z TRACE Zigbee Switch  Found ZigbeeMessageDispatcher handler in zigbee_switch
2024-12-17T22:56:24.666609335Z INFO Zigbee Switch  Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2024-12-17T22:56:24.670760960Z INFO Zigbee Switch  <ZigbeeDevice: fe27a94e-7371-4ffa-b806-7f7c1dc8f48a [0x1083] (Klo 1.1)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2024-12-17T22:56:24.694431335Z DEBUG Zigbee Switch  Klo 1.1 device thread event handled
2024-12-17T22:56:24.695393918Z TRACE Zigbee Switch  Received event with handler zigbee
2024-12-17T22:56:24.704221835Z INFO Zigbee Switch  <ZigbeeDevice: fe27a94e-7371-4ffa-b806-7f7c1dc8f48a [0x1083] (Klo 1.1)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1083, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x6A, rssi: -98, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x3D, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2024-12-17T22:56:24.770993835Z TRACE Zigbee Switch  Found ZigbeeMessageDispatcher handler in zigbee_switch
2024-12-17T22:56:24.773890877Z INFO Zigbee Switch  Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2024-12-17T22:56:24.778431210Z INFO Zigbee Switch  <ZigbeeDevice: fe27a94e-7371-4ffa-b806-7f7c1dc8f48a [0x1083] (Klo 1.1)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2024-12-17T22:56:24.793961085Z DEBUG Zigbee Switch  Klo 1.1 device thread event handled
2024-12-17T22:56:24.794937960Z TRACE Zigbee Switch  Received event with handler zigbee
2024-12-17T22:56:24.799533127Z INFO Zigbee Switch  <ZigbeeDevice: fe27a94e-7371-4ffa-b806-7f7c1dc8f48a [0x1083] (Klo 1.1)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1083, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x8E, rssi: -95, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x3C, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2024-12-17T22:56:24.887022835Z TRACE Zigbee Switch  Found ZigbeeMessageDispatcher handler in zigbee_switch
2024-12-17T22:56:24.889671710Z INFO Zigbee Switch  Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2024-12-17T22:56:24.894361960Z INFO Zigbee Switch  <ZigbeeDevice: fe27a94e-7371-4ffa-b806-7f7c1dc8f48a [0x1083] (Klo 1.1)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2024-12-17T22:56:24.914060627Z DEBUG Zigbee Switch  Klo 1.1 device thread event handled
2024-12-17T22:56:24.915066377Z TRACE Zigbee Switch  Received event with handler zigbee
2024-12-17T22:56:24.916000043Z INFO Zigbee Switch  <ZigbeeDevice: fe27a94e-7371-4ffa-b806-7f7c1dc8f48a [0x1083] (Klo 1.1)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1083, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Level >, lqi: 0xC6, rssi: -88, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x3E, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x04, ZclStatus: SUCCESS > > >
2024-12-17T22:56:25.001227043Z DEBUG Zigbee Switch  Klo 1.1 device thread event handled
2024-12-17T22:56:25.004300252Z TRACE Zigbee Switch  Received event with handler zigbee
2024-12-17T22:56:25.010399252Z INFO Zigbee Switch  <ZigbeeDevice: fe27a94e-7371-4ffa-b806-7f7c1dc8f48a [0x1083] (Klo 1.1)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1083, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: ColorControl >, lqi: 0xBC, rssi: -87, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x3F, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x0A, ZclStatus: SUCCESS > > >
2024-12-17T22:56:25.108622627Z DEBUG Zigbee Switch  Klo 1.1 device thread event handled

Hi @PalBeron

Could you provide support access to your account, please?

  1. Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM.
  2. Enable support access to your account:
  1. Go to the SmartThings Web (my.smartthings.com)
  2. Log in to your Samsung Account
  3. Select Menu (⋮) and choose Settings
  4. Toggle on Account Data Access
  5. Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.

Thanks!

@Itati should be the same Email Adresse

Support access is enabled now.

Thank you!

Hi @PalBeron

The engineering team has reviewed the logs and it doesn’t appear that SmartThings has sent any commands to change the level to anything other than 100.

We would like to check at the Hub core level to see if the issue lies in the communication. Could you help us replicate the error by executing the commands and routine, and then sending us the Hub logs?

Also, please share the time zone.

Provide the Hub logs through the my.smartthings.com:

  1. In the my.smartthings, enter “your hubs”
  2. Enter the corresponding Hub
  3. Click on “Dump Hub Logs”
  4. Change the reason for requesting hub logs if needed
  5. Click on “Dump Hub Logs”
  6. Confirm that the request is submitted
    Note: If you have more than one Hub, the name of the one involved in the issue.