Aeotec Smart Home Hub/2018/2015 Model Hub Firmware Release Notes - 0.54.13

Announcements Hub Firmware Release Notes
1

UPDATE: Following our exciting announcement at SDC, Matter 1.3 functionality is releasing as part of this update. There has also been an increase in the firmware version number and a change in the release window since the start of the release. This post and its release notes have been updated to reflect this new information.

We will begin rolling out Samsung SmartThings Hub firmware version 0.54.13 starting on Tuesday September 24th. Once downloaded, your Hub will briefly go offline as it reboots and applies the update; most customers will experience less than one minute of downtime. We will update the status page when the release is complete.

Hub Target:

  • Samsung SmartThings Hub 2015 (Hub v2)
  • Samsung SmartThings Hub 2018 (Hub v3)
  • Aeotec Smart Home Hub

Release Date: 24 Sep 2024 ~ 18 Oct 2024

Note that this release will be spread out over multiple weeks, so you may not see your Hub update on the first day of the release period. This release period is an estimate, so the rate of hubs updated and final completion date may vary slightly within the timeframe. Please check the status page for more up to date information on this release.

Release Notes

General

  • Enhanced the hub backup feature to enable automatic switching to a secondary hub if the primary hub goes offline (the previous release required manual user intervention). This feature will require SmartThings app version 1.8.21.x (Android) / 1.7.21.x (iOS) or higher and will be enabled after our Android and iOS app updates are completely rolled out to all users, which is expected in early November.
  • Changes to support Matter enhancements that will be available with upcoming SmartThings app version 1.8.21.x (Android) / 1.7.21.x (iOS), or higher
  • Improved reliability of hub backup and hub replace features
  • Enhanced fingerprinting of Zigbee devices to accommodate long names and
    atypical formatting in manufacturer metadata
  • Added support for firmware update events related to Matter bridged devices. This should also display the software version in the information section of the bridged device card if it is made available by the bridge.
  • Fixed an issue to allow for faster boot-up time after a power-up or firmware update.
  • Fixed an issue where a device firmware update appears to be stuck in progress when the device loses power or goes offline.
  • Updated to the 1.3 Matter SDK
  • Added Matter support for multi-command invoke requests. Drivers can make use of this feature for 1.3 devices that support it as reflected in MaxPathsPerInvokeattribute of BasicInformationCluster.
    • This enables merging of requests such as the following to execute multiple commands at the same time if device is able to support them. Note that it may be important to read and cache the BasicInformationCluster::MaxPathsPerInvokeAttribute to determine device’s support for this feature, and number of paths that can be merged in such invoke requests:
      local req = clusters.OnOff.server.commands.On(device, endpoint_id_1)
      req:merge(clusters.OnOff.server.commands.On(device, endpoint_id_2))
      req:merge(clusters.OnOff.server.commands.On(device, endpoint_id_x))
      device:send(req)

Edge Drivers

  • Significantly improved the method of communication between edge drivers and the hub software leading to a decrease in latency for all communication.
  • Add handling for specific default handlers directly in the firmware and not in the Edge Driver for faster execution.
    • This feature will allow for significant latency reduction in the processing of specific (Initially Switch and SwitchLevel) Capabilities to specific protocol messages.
    • This feature will be enabled by default for the official SmartThings drivers (initially Zigbee Switch, Matter Switch, and Z-Wave Switch)
    • Any driver can have a device opt into native handler usage via the new Device:register_native_capability_cmd_handler api.
    • Currently, this is only supported for devices with a single endpoint
    • There will still be logs of the commands being sent via either method
      • Logs for commands being handled in the driver look like: INFO Zigbee Switch <ZigbeeDevice: 77cf0ae2-23f1-4035-bf22-026414b6a03f [0xF508] (SmartThings Outlet 1)> received command: {"args":{},"capability":"switch","command":"off","component":"main","positional_args":{}}
      • Logs for commands being handled with the native handler look like: INFO Zigbee Switch hub handled command: 77cf0ae2-23f1-4035-bf22-026414b6a03f:main:switch:off []
  • Matter 1.3 device type support (will require SmartThings app version 1.8.21.x (Android) / 1.7.21.x (iOS) or higher)
    • Water Valve
    • Electrical Sensor
    • Water Freeze Detector
    • Water Leak Detector
    • Rain Sensor
    • Laundry Dryer
    • Microwave Oven
    • Extractor Hood
    • Electrical Vehicle Supply Equipment
    • Cook Surface/Cooktop/Oven
26 Likes
2

I’m curious why this requires a mobile app update🤔 Shouldn’t the secondary hub take over independent of your mobile phone being home or not? Or is this “automatic” only after a user approves to do it?

3

I think it broke my Tasmota Edge integration :frowning: I lost all my Tasmota devices after this update.

4

Did you reboot your hub to see if that resolves the issue?

5

I did, I even tried to reinstall the Tasmota Edge Driver. It went worse, the Tasmota Edge cannot even find the HUB ID.

6

Two problems are missing:

  1. increase the transition of oflline time, so we won’t receive false offline states from zigbee devices that works on battery, that didn’t report status within 2 hours. I prefer 10 hours.
  2. Bring back HTML in custom capabilities edge driver to app as requested by @w35l3y here:[Feature Request] Allowing HTML in Custom Capabilities
6 Likes
7

Multiple hubs is a new feature that was only added this year. So to manage multiple hubs, failover, transfer, etc., you need the new version.

1 Like
8

I just had my primary Samsung Station Hub go offline yesterday, but the secondary Samsung Station Hub did not take over anything whatsoever. I just have one Edge device available on the primary hub in the group so it wasn’t a big deal.

1 Like
9

I am assuming that ST just omits the zeros when stating the firmware version? If so, it appears that my ST v2 hub has been updated, but the Aeotec hub has not received an update. My SmartThings v2 hub as firmware version 000.054.00010 and my Aeotec Hub as firmware version 000.053.00019

I have iOS app version 1.7.19.19. I do not see any available iOS update at this time.

Since I have my devices split between the two hubs, and I have different Edge Drivers to support the devices on the separate hubs, and based on my understanding of the “Hub group” feature, this is not a feature that I would want to employ?

That being true, once I receive all applicable updates, will my hubs be able to benefit from the…

10

that is correct.

updates run through the period stated in the first post so multiple hubs in your location may receive the firmware updates on different dates.

app updates are not part of the firmware release so they arrive on a different schedule.

3 Likes
11

I was wondering about that too, but it may simply be that the app needs updating to be able to understand that the switchover has happened.

12

Would be great if that included SmartThings hubs with Thread / Zigbee dongles that currently appear to be excluded. Any news?

1 Like
13

The Samsung Find app got affected by this update for some reason, devices shows offline even if connected to the internet and unable to ring mobile and tablet device, even smart watches, check the Samsung Find App and see for yourself

14

My Samsung DU8000 TV’s firmware was updated yesterday, but it did not include the Smartthings or Dongle update.

15

Philips Hue Hub Lights won’t work with Smartthings after update. Anyone else having issues?

16

Hi,

Until today I have not realized that they have changed the order of execution of the lifecycle when a zigbee device is installed.

Until now, the init lifecycle was executed before the doConfigure lifecycle.

I just saw in a log that a user sent me, that now Added is executed first, then doConfigure and then init.

I wanted to check it in person and I have uninstalled a device and I have reinstalled it and indeed they are executed in this order, Added then doConfigure and then init.

Device Pairing logs 
2024-09-26T22:34:06.717507195Z TRACE Zigbee Switch Mc  Received event with handler device_lifecycle
2024-09-26T22:34:07.315137487Z TRACE Zigbee Switch Mc  Zigbee Device: 344a52f6-fd87-48a6-a794-e20342adbe31
Manufacturer: _TZ3000_kdi2o9m6 Model: TS011F
        [242]: server | client: 0x0021  [11]: server: Basic, Identify, Groups, Scenes, OnOff | client: OTAUpgrade, Time
2024-09-26T22:34:07.335683154Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug)> received lifecycle event: added
2024-09-26T22:34:07.944471529Z TRACE Zigbee Switch Mc  Received event with handler device_lifecycle
2024-09-26T22:34:07.975513237Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug)> received lifecycle event: doConfigure
2024-09-26T22:34:09.231636029Z TRACE Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug)> received unhandled lifecycle event: added
2024-09-26T22:34:09.233113654Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T22:34:09.234321862Z TRACE Zigbee Switch Mc  Found DeviceLifecycleDispatcher handler in Zigbee_Switch_Mc
2024-09-26T22:34:09.235352821Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xE855, dest_endpoint: 0x0B, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: EC1BBDFFFEA88018, src_endpoint: 0x0B, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 286D97000204B680, dest_endpoint: 0x01 > > >
2024-09-26T22:34:09.243572487Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xE855, dest_endpoint: 0x0B, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2024-09-26T22:34:09.356232237Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T22:34:09.360518654Z DEBUG Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug)> doConfigure callback did not fail, transitioning device 
to "PROVISIONED"
2024-09-26T22:34:09.371582112Z TRACE Zigbee Switch Mc  Found DeviceLifecycleDispatcher handler in Zigbee_Switch_Mc
2024-09-26T22:34:09.373509362Z PRINT Zigbee Switch Mc  <<< Device do_init >>>
2024-09-26T22:34:09.419091946Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug)> emitting event: {"attribute_id":"energy","capability_id":"energyMeter","component_id":"main","state":{"unit":"kWh","value":0.0}}
2024-09-26T22:34:09.447136987Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug)> emitting event: {"attribute_id":"energyReset","capability_id":"legendabsolute60149.energyReset1","component_id":"main","state":{"value":"Last: 0.000 kWh (09/26/2024)"}}
2024-09-26T22:34:09.469698862Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug)> emitting event: {"attribute_id":"randomOnOff","capability_id":"legendabsolute60149.randomOnOff2","component_id":"main","state":{"value":"Inactive"}}
2024-09-26T22:34:09.526457279Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug)> emitting event: {"attribute_id":"randomNext","capability_id":"legendabsolute60149.randomNextStep2","component_id":"main","state":{"value":"Inactive"}}
2024-09-26T22:34:09.933959362Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T22:34:09.974060321Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T22:34:10.053285529Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-26T22:34:10.054671196Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xE855, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xC2, rssi: -59, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x0E >, < BindRequestResponse || status: 0x00 > > >
2024-09-26T22:34:11.095647571Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T22:34:11.314209862Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-26T22:34:11.319988362Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xE855, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xC2, rssi: -59, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x3B, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || ZclStatus: SUCCESS > > >
2024-09-26T22:34:11.341768904Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T22:34:11.820915654Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-26T22:34:11.847345196Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xE855, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xC8, rssi: -59, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x68, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >    
2024-09-26T22:34:11.940156029Z TRACE Zigbee Switch Mc  Found ZigbeeMessageDispatcher handler in Zigbee_Switch_Mc
2024-09-26T22:34:11.953900196Z INFO Zigbee Switch Mc  Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2024-09-26T22:34:11.956034779Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"2024/09/26 Time: 22:34, LQI: 200 ... rssi: -59"},"visibility":{"displayed":false}}
2024-09-26T22:34:12.102187988Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2024-09-26T22:34:12.229607529Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug)> emitting event: {"attribute_id":"power","capability_id":"powerMeter","component_id":"main","state":{"unit":"W","value":0}}
2024-09-26T22:34:12.248488863Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T22:34:12.355398988Z TRACE Zigbee Switch Mc  Received event with handler device_lifecycle
2024-09-26T22:34:12.369208363Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug 1)> received lifecycle event: infoChanged
2024-09-26T22:34:12.504853613Z TRACE Zigbee Switch Mc  Found DeviceLifecycleDispatcher handler in Zigbee_Switch_Mc
2024-09-26T22:34:12.508669029Z PRINT Zigbee Switch Mc  << do_Prefrences >>
2024-09-26T22:34:12.509760863Z PRINT Zigbee Switch Mc  << Preference changed name:      logDebugPrint   old value:      nil     new value:      false
2024-09-26T22:34:12.510797613Z PRINT Zigbee Switch Mc  << Preference changed name:      powerTimer      old value:      nil     new value:      5.0
2024-09-26T22:34:12.511812279Z PRINT Zigbee Switch Mc  << Preference changed name:      version old value:      nil     new value:
2024-09-26T22:34:12.512969238Z PRINT Zigbee Switch Mc  << Preference changed name:      localTimeOffset old value:      nil     new value:      0
2024-09-26T22:34:12.514148738Z PRINT Zigbee Switch Mc  << Preference changed name:      groupAdd        old value:      nil     new value:      0.0
2024-09-26T22:34:12.515472446Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug 1)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xE855, dest_endpoint: 0x0B, profile: 0x0104, cluster: Groups >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x02 >, < GetGroupMembership || group_list_length: 0x00 > > >
2024-09-26T22:34:12.520980279Z PRINT Zigbee Switch Mc  << Preference changed name:      changeProfile   old value:      nil     new value:      Plug
2024-09-26T22:34:12.532817196Z PRINT Zigbee Switch Mc  << Preference changed name:      signalMetricsVisibles   old value:      nil     new value:      No
2024-09-26T22:34:12.534068488Z PRINT Zigbee Switch Mc  << Preference changed name:      restoreState    old value:      nil     new value:      255
2024-09-26T22:34:12.534955863Z PRINT Zigbee Switch Mc  <<< Write restore state >>>
2024-09-26T22:34:12.541863696Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug 1)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xE855, dest_endpoint: 0x0B, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 
0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x4003, DataType: Enum8, data: 0xFF > > > >
2024-09-26T22:34:12.704574029Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug 1)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xE855, dest_endpoint: 0x0B, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 
0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x8002, DataType: Enum8, data: 0x02 > > > >
2024-09-26T22:34:13.002761488Z PRINT Zigbee Switch Mc  << Preference changed name:      loadPower       old value:      nil     new value:      0
2024-09-26T22:34:13.005083113Z PRINT Zigbee Switch Mc  << Preference changed name:      onOffReports    old value:      nil     new value:      300
2024-09-26T22:34:13.007186613Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug 1)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xE855, dest_endpoint: 0x0B, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 
0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2024-09-26T22:34:13.163281113Z PRINT Zigbee Switch Mc  << Preference changed name:      offTime old value:      nil     new value:      10
2024-09-26T22:34:13.167734529Z PRINT Zigbee Switch Mc  << Preference changed name:      onTime  old value:      nil     new value:      10
2024-09-26T22:34:13.168842279Z PRINT Zigbee Switch Mc  << Preference changed name:      randomMin       old value:      nil     new value:      1.0
2024-09-26T22:34:13.169863696Z PRINT Zigbee Switch Mc  << Preference changed name:      randomMax       old value:      nil     new value:      10.0
2024-09-26T22:34:13.170879154Z PRINT Zigbee Switch Mc  << Preference changed name:      groupRemove     old value:      nil     new value:      1.0
2024-09-26T22:34:13.171887238Z PRINT Zigbee Switch Mc  Remove Groups >>>>>>>>>>>>>>>>>
2024-09-26T22:34:13.172911154Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug 1)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xE855, dest_endpoint: 0x0B, profile: 0x0104, cluster: Groups >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x03 >, < RemoveGroup || group_id: 0x0001 > > >
2024-09-26T22:34:13.180594613Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug 1)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xE855, dest_endpoint: 0x0B, profile: 0x0104, cluster: Groups >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x02 >, < GetGroupMembership || group_list_length: 0x00 > > >
2024-09-26T22:34:13.269482279Z PRINT Zigbee Switch Mc  Device ID        <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug 1)>
2024-09-26T22:34:13.273470488Z PRINT Zigbee Switch Mc  Manufacturer >>> _TZ3000_kdi2o9m6        Manufacturer_Len >>>    16
2024-09-26T22:34:13.274699946Z PRINT Zigbee Switch Mc  Model >>>        TS011F  Model_len >>>   6
2024-09-26T22:34:13.275749946Z PRINT Zigbee Switch Mc  <<<<< Firmware Version >>>>>     nil
2024-09-26T22:34:13.276803071Z PRINT Zigbee Switch Mc  Memory >>>>>>>   1178.41796875    Kbytes
2024-09-26T22:34:13.277848904Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T22:34:13.607466196Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-26T22:34:13.611521321Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug 1)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xE855, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Groups >, lqi: 0xC8, rssi: -59, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x3E, ZCLCommandId: 0x02 >, < GetGroupMembershipResponse || capacity: 0xFF, group_list_length: 0x00 > > >
2024-09-26T22:34:13.624385821Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-26T22:34:13.625307904Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug 1)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xE855, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xC6, rssi: -59, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x40, ZCLCommandId: 0x04 >, < WriteAttributeReponse || < WriteAttributeResponseRecord || ZclStatus: UNSUPPORTED_ATTRIBUTE, AttributeId: 0x4003 > > > >
2024-09-26T22:34:13.804383363Z TRACE Zigbee Switch Mc  Found ZigbeeMessageDispatcher handler in Zigbee_Switch_Mc
2024-09-26T22:34:13.805433321Z INFO Zigbee Switch Mc  Executing ZclClusterCommandHandler: cluster: Groups, command: GetGroupMembership
2024-09-26T22:34:13.808543946Z PRINT Zigbee Switch Mc  group_list >>>>>>        {}
2024-09-26T22:34:13.809381613Z PRINT Zigbee Switch Mc  DeleteAllGroups
2024-09-26T22:34:13.810198279Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug 1)> emitting event: {"attribute_id":"getGroups","capability_id":"legendabsolute60149.getGroups","component_id":"main","state":{"value":"DeleteAllGroups"}}
2024-09-26T22:34:13.827096696Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T22:34:13.828885821Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T22:34:13.958497279Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-26T22:34:13.978273946Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug 1)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xE855, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xBA, rssi: -59, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x41, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
2024-09-26T22:34:14.001220488Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-26T22:34:14.002992321Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug 1)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xE855, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xC2, rssi: -58, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x42, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || ZclStatus: SUCCESS > > >
2024-09-26T22:34:14.158388321Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T22:34:14.159430571Z TRACE Zigbee Switch Mc  Received event with handler device_lifecycle
2024-09-26T22:34:14.277166613Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug 1)> received lifecycle event: infoChanged
2024-09-26T22:34:14.282228655Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T22:34:14.283340280Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-26T22:34:14.284454863Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug 1)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xE855, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Groups >, lqi: 0xC6, rssi: -59, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x43, ZCLCommandId: 0x03 >, < RemoveGroupResponse || status: 0x8B, group_id: 0x0001 > > >
2024-09-26T22:34:14.294460196Z TRACE Zigbee Switch Mc  Found DeviceLifecycleDispatcher handler in Zigbee_Switch_Mc
2024-09-26T22:34:14.295343821Z PRINT Zigbee Switch Mc  << do_Prefrences >>
2024-09-26T22:34:14.296293863Z PRINT Zigbee Switch Mc  Device ID        <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug 1)>
2024-09-26T22:34:14.297193946Z PRINT Zigbee Switch Mc  Manufacturer >>> _TZ3000_kdi2o9m6        Manufacturer_Len >>>    16
2024-09-26T22:34:14.298005946Z PRINT Zigbee Switch Mc  Model >>>        TS011F  Model_len >>>   6
2024-09-26T22:34:14.298793155Z PRINT Zigbee Switch Mc  <<<<< Firmware Version >>>>>     nil
2024-09-26T22:34:14.390592905Z PRINT Zigbee Switch Mc  Memory >>>>>>>   1561.0146484375  Kbytes
2024-09-26T22:34:14.395444030Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T22:34:14.398292446Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-26T22:34:14.399402113Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug 1)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xE855, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Groups >, lqi: 0xBA, rssi: -59, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x44, ZCLCommandId: 0x02 >, < GetGroupMembershipResponse || capacity: 0xFF, group_list_length: 0x00 > > >
2024-09-26T22:34:14.406947738Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T22:34:14.488954613Z TRACE Zigbee Switch Mc  Found ZigbeeMessageDispatcher handler in Zigbee_Switch_Mc
2024-09-26T22:34:14.493580488Z INFO Zigbee Switch Mc  Executing ZclClusterCommandHandler: cluster: Groups, command: GetGroupMembership
2024-09-26T22:34:14.495248071Z PRINT Zigbee Switch Mc  group_list >>>>>>        {}
2024-09-26T22:34:14.496306655Z PRINT Zigbee Switch Mc  DeleteAllGroups
2024-09-26T22:34:14.497330946Z INFO Zigbee Switch Mc  <ZigbeeDevice: 344a52f6-fd87-48a6-a794-e20342adbe31 [0xE855] (Lidl Plug 1)> emitting event: {"attribute_id":"getGroups","capability_id":"legendabsolute60149.getGroups","component_id":"main","state":{"value":"DeleteAllGroups"}}
2024-09-26T22:34:14.509700655Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled

This causes devices that have a different configuration than the default one and are established in the init lifecycle with the functions: device:add_configured_attribute(attribute) and device:add_monitored_attribute(attribute) not to be executed prior to doConfigure and therefore the necessary configuration will not take effect. This does not make any sense.

I have also seen that when you reinstall a device without uninstalling it first, the init lifecycle is not performed, which causes it to be configured with the defaults and not with the ones the device needs and are set in the init lifecycle.

Reinstall device logs 
2024-09-26T23:04:24.554608841Z TRACE Zigbee Switch Mc  Received event with handler device_lifecycle
2024-09-26T23:04:24.556260389Z INFO Zigbee Switch Mc  <ZigbeeDevice: 80cf37a0-0c7d-424e-a03e-53314ca11e1c [0x5FCF] (Lidl Plug 1)> received lifecycle event: infoChanged
2024-09-26T23:04:24.563163020Z TRACE Zigbee Switch Mc  Found DeviceLifecycleDispatcher handler in Zigbee_Switch_Mc
2024-09-26T23:04:24.564172182Z PRINT Zigbee Switch Mc  << do_Prefrences >>
2024-09-26T23:04:24.567066817Z PRINT Zigbee Switch Mc  Device ID        <ZigbeeDevice: 80cf37a0-0c7d-424e-a03e-53314ca11e1c [0x5FCF] (Lidl Plug 1)>
2024-09-26T23:04:24.569193586Z PRINT Zigbee Switch Mc  Manufacturer >>> _TZ3000_kdi2o9m6        Manufacturer_Len >>>    16
2024-09-26T23:04:24.574472237Z PRINT Zigbee Switch Mc  Model >>>        TS011F  Model_len >>>   6
2024-09-26T23:04:24.575523670Z PRINT Zigbee Switch Mc  <<<<< Firmware Version >>>>>     nil
2024-09-26T23:04:24.576406894Z PRINT Zigbee Switch Mc  Memory >>>>>>>   1164.1875        Kbytes
2024-09-26T23:04:24.577221070Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T23:04:24.578031124Z TRACE Zigbee Switch Mc  Received event with handler device_lifecycle
2024-09-26T23:04:24.582813106Z INFO Zigbee Switch Mc  <ZigbeeDevice: 80cf37a0-0c7d-424e-a03e-53314ca11e1c [0x5FCF] (Lidl Plug 1)> received lifecycle event: doConfigure
2024-09-26T23:04:24.600880193Z TRACE Zigbee Switch Mc  Found DeviceLifecycleDispatcher handler in Zigbee_Switch_Mc
2024-09-26T23:04:24.603557063Z INFO Zigbee Switch Mc  <ZigbeeDevice: 80cf37a0-0c7d-424e-a03e-53314ca11e1c [0x5FCF] (Lidl Plug 1)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5FCF, dest_endpoint: 0x0B, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: EC1BBDFFFEA88018, src_endpoint: 0x0B, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 286D97000204B680, dest_endpoint: 0x01 > > >
2024-09-26T23:04:24.628014328Z INFO Zigbee Switch Mc  <ZigbeeDevice: 80cf37a0-0c7d-424e-a03e-53314ca11e1c [0x5FCF] (Lidl Plug 1)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5FCF, dest_endpoint: 0x0B, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 
0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2024-09-26T23:04:24.649273193Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T23:04:24.658839991Z DEBUG Zigbee Switch Mc  <ZigbeeDevice: 80cf37a0-0c7d-424e-a03e-53314ca11e1c [0x5FCF] (Lidl Plug 1)> doConfigure callback did not fail, transitioning device to "PROVISIONED"
2024-09-26T23:04:24.672096692Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T23:04:24.723757391Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-26T23:04:24.724751685Z INFO Zigbee Switch Mc  <ZigbeeDevice: 80cf37a0-0c7d-424e-a03e-53314ca11e1c [0x5FCF] (Lidl Plug 1)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x5FCF, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xC6, rssi: -58, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x51 >, < BindRequestResponse || status: 0x00 > > >
2024-09-26T23:04:24.754437002Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T23:04:24.773035406Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-26T23:04:24.774056187Z INFO Zigbee Switch Mc  <ZigbeeDevice: 80cf37a0-0c7d-424e-a03e-53314ca11e1c [0x5FCF] (Lidl Plug 1)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x5FCF, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xC8, rssi: -58, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x5D, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || ZclStatus: SUCCESS > > >
2024-09-26T23:04:24.971149508Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T23:04:26.045991651Z TRACE Zigbee Switch Mc  Received event with handler device_lifecycle
2024-09-26T23:04:26.066917475Z INFO Zigbee Switch Mc  <ZigbeeDevice: 80cf37a0-0c7d-424e-a03e-53314ca11e1c [0x5FCF] (Lidl Plug 1)> received lifecycle event: infoChanged
2024-09-26T23:04:26.094458697Z TRACE Zigbee Switch Mc  Found DeviceLifecycleDispatcher handler in Zigbee_Switch_Mc
2024-09-26T23:04:26.124240341Z PRINT Zigbee Switch Mc  << do_Prefrences >>
2024-09-26T23:04:26.125448903Z PRINT Zigbee Switch Mc  Device ID        <ZigbeeDevice: 80cf37a0-0c7d-424e-a03e-53314ca11e1c [0x5FCF] (Lidl Plug 1)>
2024-09-26T23:04:26.126307723Z PRINT Zigbee Switch Mc  Manufacturer >>> _TZ3000_kdi2o9m6        Manufacturer_Len >>>    16
2024-09-26T23:04:26.127131103Z PRINT Zigbee Switch Mc  Model >>>        TS011F  Model_len >>>   6
2024-09-26T23:04:26.127946195Z PRINT Zigbee Switch Mc  <<<<< Firmware Version >>>>>     nil
2024-09-26T23:04:26.172062043Z PRINT Zigbee Switch Mc  Memory >>>>>>>   1362.8955078125  Kbytes
2024-09-26T23:04:26.172957762Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-26T23:04:26.700593312Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-26T23:04:26.701674313Z INFO Zigbee Switch Mc  <ZigbeeDevice: 80cf37a0-0c7d-424e-a03e-53314ca11e1c [0x5FCF] (Lidl Plug 1)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x5FCF, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xC0, rssi: -58, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x0E, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >  
2024-09-26T23:04:26.734116334Z TRACE Zigbee Switch Mc  Found ZigbeeMessageDispatcher handler in Zigbee_Switch_Mc
2024-09-26T23:04:26.736231317Z INFO Zigbee Switch Mc  Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2024-09-26T23:04:26.742261551Z INFO Zigbee Switch Mc  <ZigbeeDevice: 80cf37a0-0c7d-424e-a03e-53314ca11e1c [0x5FCF] (Lidl Plug 1)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"2024/09/26 Time: 23:04, LQI: 192 ... rssi: -58"},"visibility":{"displayed":false}}
2024-09-26T23:04:26.762692330Z INFO Zigbee Switch Mc  <ZigbeeDevice: 80cf37a0-0c7d-424e-a03e-53314ca11e1c [0x5FCF] (Lidl Plug 1)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2024-09-26T23:04:26.789231679Z INFO Zigbee Switch Mc  <ZigbeeDevice: 80cf37a0-0c7d-424e-a03e-53314ca11e1c [0x5FCF] (Lidl Plug 1)> emitting event: {"attribute_id":"power","capability_id":"powerMeter","component_id":"main","state":{"unit":"W","value":0}}
2024-09-26T23:04:26.834874304Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled

Could you please check this or am I wrong?

6 Likes
17

Could this be the reason why I can’t re-add my device?

1 Like
18

I don’t know if they have anything to do with the discovery process of this device in a LAN type driver.

1 Like
19

Who knows? Something is different compared to two, three days ago. Despite being well documented, some edge drivers being open source, SmartThings is a blackbox.

The fact is that it’s broken at the moment. And I think it has something to do with the cloud. My hub finds the device, but it can’t add it to the cloud? I don’t know.

Now all of my icons/badges are reset and I can’t change them anymore.

This isn’t related to the hub firmware, but who knows…

2 Likes
20

In my opinion, this could affect ZigBee devices differently depending on whether the devices were already installed before this change or if the devices are installed or reinstalled after this change in the order of execution of the life cycles, which I think must be a mistake, but we will see what they answer.

If the devices were already installed, they should continue to work with the configuration they already had.

If a device is installed or reinstalled and needs a different configuration than the default configuration of the firmware libraries, this will not be done correctly and the device will send periodic reports different from those expected by the driver or the hub and could appear offline from time to time or drain the battery faster than normal, depending on what custom configuration the device needs.

3 Likes