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

@SmartThings

If it helps,
I have tested it with a hub that I have with firmware 53.19 and the life cycles for installing zigbee devices are correct, init, added, doConfigure, infoChanged.

Device Pairing logs with 53.19 firmware
2024-09-27T15:49:45.679715707Z TRACE Zigbee Switch Mc  Setup driver Zigbee_Switch_Mc with lifecycle handlers:
DeviceLifecycleDispatcher: Zigbee_Switch_Mc
  default_handlers:
    init:
    infoChanged:
    driverSwitched:
    doConfigure:
    removed:
  child_dispatchers:
    DeviceLifecycleDispatcher: Zigbee_Switch_Mc -> tuya fingerbot
      default_handlers:
        driverSwitched:
        doConfigure:
        added:
      child_dispatchers:

2024-09-27T15:49:45.687540874Z TRACE Zigbee Switch Mc  Setup driver Zigbee_Switch_Mc with Capability handlers:
CapabilityCommandDispatcher: Zigbee_Switch_Mc
  default_handlers:
    legendabsolute60149.energyReset1:
      setEnergyReset
    refresh:
      refresh
    switch:
      on
      off
    legendabsolute60149.getGroups:
      setGetGroups
    energyMeter:
      resetEnergyMeter
    legendabsolute60149.randomOnOff2:
      setRandomOnOff
  child_dispatchers:
    CapabilityCommandDispatcher: Zigbee_Switch_Mc -> tuya fingerbot
      default_handlers:
        legendabsolute60149.fingerbotMode:
          setFingerBotMode
        legendabsolute60149.fingerbotSustainTime:
          setFingerBotSustainTime
        legendabsolute60149.fingerbotUpMotion:
          setFingerBotUpMotion
        legendabsolute60149.fingerbotDownMotion:
          setFingerBotDownMotion
        legendabsolute60149.fingerbotReverse:
          setFingerBotReverse
      child_dispatchers:

2024-09-27T15:49:45.693448791Z INFO Zigbee Switch Mc  Created dispatcher [SecretDataDispatcher]Zigbee_Switch_Mc that had no handlers
2024-09-27T15:49:45.703678416Z TRACE Zigbee Switch Mc  Setup driver Zigbee_Switch_Mc with Secret Data handlers:
SecretDataDispatcher: Zigbee_Switch_Mc
  default_handlers:
  child_dispatchers:
    SecretDataDispatcher: Zigbee_Switch_Mc -> tuya fingerbot
      default_handlers:
      child_dispatchers:

2024-09-27T15:49:45.717541207Z TRACE Zigbee Switch Mc  Setup driver Zigbee_Switch_Mc with Zigbee handlers:
ZigbeeMessageDispatcher: Zigbee_Switch_Mc
  default_handlers:
    attr:
      ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage
      ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryPercentageRemaining
      ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
    global:
      ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
    cluster:
      ZclClusterCommandHandler: cluster: Groups, command: GetGroupMembership
    zdo:
  child_dispatchers:
    ZigbeeMessageDispatcher: Zigbee_Switch_Mc -> tuya fingerbot
      default_handlers:
        attr:
        global:
        cluster:
          ZclClusterCommandHandler: cluster: 0xEF00, command: 0x06
          ZclClusterCommandHandler: cluster: 0xEF00, command: 0x05
        zdo:
          ZdoHandler
      child_dispatchers:

2024-09-27T15:49:45.732267291Z TRACE Zigbee Switch Mc  Zigbee Device: 62028083-deab-435b-af10-c28ebf0a5874
Manufacturer: _TZ3000_kdi2o9m6 Model: TS011F
        [242]: server | client: 0x0021  [11]: server: Basic, Identify, Groups, Scenes, OnOff | client: OTAUpgrade, Time
2024-09-27T15:49:45.774888041Z DEBUG Zigbee Switch Mc  driver device thread event handled
2024-09-27T15:49:45.786232291Z TRACE Zigbee Switch Mc  Received event with handler driver_lifecycle
2024-09-27T15:49:45.795531374Z INFO Zigbee Switch Mc  received driver startupState: {"hub_zigbee_id":"0FKoo2ekAAE=","hub_node_id":1,"hub_ipv4":"192.168.1.55"}
2024-09-27T15:49:45.804917374Z TRACE Zigbee Switch Mc  Found DeviceLifecycleDispatcher handler in Zigbee_Switch_Mc
2024-09-27T15:49:45.815749999Z PRINT Zigbee Switch Mc  <<< Device do_init >>>
2024-09-27T15:49:45.823017624Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> emitting event: {"attribute_id":"energy","capability_id":"energyMeter","component_id":"main","state":{"unit":"kWh","value":0.0}}
2024-09-27T15:49:45.826493999Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> emitting event: {"attribute_id":"energyReset","capability_id":"legendabsolute60149.energyReset1","component_id":"main","state":{"value":"Last: 0.000 kWh (09/27/2024)"}}
2024-09-27T15:49:45.880550666Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> emitting event: {"attribute_id":"randomOnOff","capability_id":"legendabsolute60149.randomOnOff2","component_id":"main","state":{"value":"Inactive"}}
2024-09-27T15:49:45.934278124Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> emitting event: {"attribute_id":"randomNext","capability_id":"legendabsolute60149.randomNextStep2","component_id":"main","state":{"value":"Inactive"}}
2024-09-27T15:49:46.015456499Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-27T15:49:46.056267666Z TRACE Zigbee Switch Mc  Received event with handler environment_info
2024-09-27T15:49:46.095078207Z TRACE Zigbee Switch Mc  Received event with handler environment_info
2024-09-27T15:49:46.141814791Z DEBUG Zigbee Switch Mc  Z-Wave hub node ID environment changed.
2024-09-27T15:49:46.183553541Z TRACE Zigbee Switch Mc  Received event with handler environment_info
2024-09-27T15:49:46.241537832Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> generating doConfigure event for TYPED provisioning 
state
2024-09-27T15:49:46.350838124Z TRACE Zigbee Switch Mc  Found DeviceLifecycleDispatcher handler in Zigbee_Switch_Mc
2024-09-27T15:49:46.659326249Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFB21, 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: D052A8A367A40001, dest_endpoint: 0x01 > > >     
2024-09-27T15:49:46.727581791Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFB21, 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-27T15:49:46.760146874Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-27T15:49:46.794558332Z DEBUG Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> doConfigure callback did not fail, transitioning device to "PROVISIONED"
2024-09-27T15:49:46.798557874Z TRACE Zigbee Switch Mc  Received event with handler device_lifecycle
2024-09-27T15:49:46.819615457Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> received lifecycle event: added
2024-09-27T15:49:46.855450416Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-27T15:49:46.886862999Z TRACE Zigbee Switch Mc  Received event with handler device_lifecycle
2024-09-27T15:49:46.918468416Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> received lifecycle event: doConfigure
2024-09-27T15:49:46.952368541Z TRACE Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> received unhandled lifecycle event: added
2024-09-27T15:49:46.996701374Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-27T15:49:47.072272207Z TRACE Zigbee Switch Mc  Found DeviceLifecycleDispatcher handler in Zigbee_Switch_Mc
2024-09-27T15:49:47.112855374Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFB21, 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: D052A8A367A40001, dest_endpoint: 0x01 > > >     
2024-09-27T15:49:47.118800124Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFB21, 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-27T15:49:47.154462832Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-27T15:49:47.193539166Z DEBUG Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> doConfigure callback did not fail, transitioning device to "PROVISIONED"
2024-09-27T15:49:47.212109541Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-27T15:49:47.236613999Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-27T15:49:47.265396749Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> received Zigbee message: < ZigbeeMessageRx || type: 
0x00, < AddressHeader || src_addr: 0xFB21, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xFF, rssi: -51, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x07 >, < BindRequestResponse || status: 0x00 > > >
2024-09-27T15:49:47.307912249Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-27T15:49:47.355144041Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-27T15:49:47.407493874Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> received Zigbee message: < ZigbeeMessageRx || type: 
0x00, < AddressHeader || src_addr: 0xFB21, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -51, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x01, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || ZclStatus: SUCCESS > > >
2024-09-27T15:49:47.455353416Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-27T15:49:47.521707291Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-27T15:49:47.563744374Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> received Zigbee message: < ZigbeeMessageRx || type: 
0x00, < AddressHeader || src_addr: 0xFB21, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xFF, rssi: -50, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x08 >, < BindRequestResponse || status: 0x00 > > >
2024-09-27T15:49:47.603825957Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-27T15:49:47.663206666Z TRACE Zigbee Switch Mc  Received event with handler device_lifecycle
2024-09-27T15:49:47.751061166Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> received lifecycle event: infoChanged
2024-09-27T15:49:47.781469291Z TRACE Zigbee Switch Mc  Found DeviceLifecycleDispatcher handler in Zigbee_Switch_Mc
2024-09-27T15:49:47.818686791Z PRINT Zigbee Switch Mc  << do_Prefrences >>
2024-09-27T15:49:47.822654083Z PRINT Zigbee Switch Mc  << Preference changed name:      groupAdd        old value:      nil     new value:      0.0
2024-09-27T15:49:47.835982041Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFB21, dest_endpoint: 0x0B, profile: 0x0104, cluster: Groups >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x02 >, < GetGroupMembership || group_list_length: 0x00 > > >
2024-09-27T15:49:47.915683083Z PRINT Zigbee Switch Mc  << Preference changed name:      randomMax       old value:      nil     new value:      10.0
2024-09-27T15:49:47.958989291Z PRINT Zigbee Switch Mc  << Preference changed name:      offTime old value:      nil     new value:      10
2024-09-27T15:49:48.001943208Z PRINT Zigbee Switch Mc  << Preference changed name:      onOffReports    old value:      nil     new value:      300
2024-09-27T15:49:48.051725999Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFB21, 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-27T15:49:48.091525041Z PRINT Zigbee Switch Mc  << Preference changed name:      randomMin       old value:      nil     new value:      1.0
2024-09-27T15:49:48.137878541Z PRINT Zigbee Switch Mc  << Preference changed name:      changeProfile   old value:      nil     new value:      Plug
2024-09-27T15:49:48.176314458Z PRINT Zigbee Switch Mc  << Preference changed name:      version old value:      nil     new value:
2024-09-27T15:49:48.213667041Z PRINT Zigbee Switch Mc  << Preference changed name:      powerTimer      old value:      nil     new value:      5.0
2024-09-27T15:49:48.249693499Z PRINT Zigbee Switch Mc  << Preference changed name:      signalMetricsVisibles   old value:      nil     new value:      No
2024-09-27T15:49:48.289589124Z PRINT Zigbee Switch Mc  << Preference changed name:      groupRemove     old value:      nil     new value:      1.0
2024-09-27T15:49:48.307772583Z PRINT Zigbee Switch Mc  Remove Groups >>>>>>>>>>>>>>>>>
2024-09-27T15:49:48.330062666Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFB21, dest_endpoint: 0x0B, profile: 0x0104, cluster: Groups >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x03 >, < RemoveGroup || group_id: 0x0001 > > >
2024-09-27T15:49:48.333317499Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFB21, dest_endpoint: 0x0B, profile: 0x0104, cluster: Groups >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x02 >, < GetGroupMembership || group_list_length: 0x00 > > >
2024-09-27T15:49:48.336519916Z PRINT Zigbee Switch Mc  << Preference changed name:      restoreState    old value:      nil     new value:      255
2024-09-27T15:49:48.339056041Z PRINT Zigbee Switch Mc  <<< Write restore state >>>
2024-09-27T15:49:48.341584166Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFB21, 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-27T15:49:48.344425374Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFB21, 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-27T15:49:48.347467749Z PRINT Zigbee Switch Mc  << Preference changed name:      onTime  old value:      nil     new value:      10
2024-09-27T15:49:48.349910958Z PRINT Zigbee Switch Mc  << Preference changed name:      localTimeOffset old value:      nil     new value:      0
2024-09-27T15:49:48.352328416Z PRINT Zigbee Switch Mc  << Preference changed name:      loadPower       old value:      nil     new value:      0
2024-09-27T15:49:48.354738083Z PRINT Zigbee Switch Mc  << Preference changed name:      logDebugPrint   old value:      nil     new value:      false
2024-09-27T15:49:48.357332499Z PRINT Zigbee Switch Mc  Device ID        <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)>
2024-09-27T15:49:48.359991333Z PRINT Zigbee Switch Mc  Manufacturer >>> _TZ3000_kdi2o9m6        Manufacturer_Len >>>    16
2024-09-27T15:49:48.362391916Z PRINT Zigbee Switch Mc  Model >>>        TS011F  Model_len >>>   6
2024-09-27T15:49:48.364801208Z PRINT Zigbee Switch Mc  <<<<< Firmware Version >>>>>     nil
2024-09-27T15:49:48.367273124Z PRINT Zigbee Switch Mc  Memory >>>>>>>   929.4091796875   Kbytes
2024-09-27T15:49:48.369726083Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-27T15:49:48.372135833Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-27T15:49:48.374753249Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> received Zigbee message: < ZigbeeMessageRx || type: 
0x00, < AddressHeader || src_addr: 0xFB21, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -51, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x02, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || ZclStatus: SUCCESS > > >
2024-09-27T15:49:48.377915874Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-27T15:49:48.380426166Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-27T15:49:48.382918541Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> received Zigbee message: < ZigbeeMessageRx || type: 
0x00, < AddressHeader || src_addr: 0xFB21, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Groups >, lqi: 0xFF, rssi: -51, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x03, ZCLCommandId: 0x02 >, < GetGroupMembershipResponse || capacity: 0xFF, group_list_length: 0x00 > > >
2024-09-27T15:49:48.385663291Z TRACE Zigbee Switch Mc  Found ZigbeeMessageDispatcher handler in Zigbee_Switch_Mc
2024-09-27T15:49:48.388204333Z INFO Zigbee Switch Mc  Executing ZclClusterCommandHandler: cluster: Groups, command: GetGroupMembership
2024-09-27T15:49:48.391224666Z PRINT Zigbee Switch Mc  group_list >>>>>>        {}
2024-09-27T15:49:48.393625208Z PRINT Zigbee Switch Mc  DeleteAllGroups
2024-09-27T15:49:48.396057708Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> emitting event: {"attribute_id":"getGroups","capability_id":"legendabsolute60149.getGroups","component_id":"main","state":{"value":"DeleteAllGroups"}}
2024-09-27T15:49:48.398931999Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-27T15:49:48.401395374Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-27T15:49:48.403880541Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> received Zigbee message: < ZigbeeMessageRx || type: 
0x00, < AddressHeader || src_addr: 0xFB21, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -50, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x04, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || ZclStatus: SUCCESS > > >
2024-09-27T15:49:48.406813499Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-27T15:49:48.409233374Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-27T15:49:48.411767374Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> received Zigbee message: < ZigbeeMessageRx || type: 
0x00, < AddressHeader || src_addr: 0xFB21, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Groups >, lqi: 0xFF, rssi: -50, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x05, ZCLCommandId: 0x03 >, < RemoveGroupResponse || status: 0x8B, group_id: 0x0001 > > >
2024-09-27T15:49:48.414665374Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-27T15:49:48.417124166Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-27T15:49:48.419626583Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> received Zigbee message: < ZigbeeMessageRx || type: 
0x00, < AddressHeader || src_addr: 0xFB21, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Groups >, lqi: 0xFF, rssi: -50, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x06, ZCLCommandId: 0x02 >, < GetGroupMembershipResponse || capacity: 0xFF, group_list_length: 0x00 > > >
2024-09-27T15:49:48.422428499Z TRACE Zigbee Switch Mc  Found ZigbeeMessageDispatcher handler in Zigbee_Switch_Mc
2024-09-27T15:49:48.425344166Z INFO Zigbee Switch Mc  Executing ZclClusterCommandHandler: cluster: Groups, command: GetGroupMembership
2024-09-27T15:49:48.428203833Z PRINT Zigbee Switch Mc  group_list >>>>>>        {}
2024-09-27T15:49:48.430621666Z PRINT Zigbee Switch Mc  DeleteAllGroups
2024-09-27T15:49:48.433065916Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> emitting event: {"attribute_id":"getGroups","capability_id":"legendabsolute60149.getGroups","component_id":"main","state":{"value":"DeleteAllGroups"}}
2024-09-27T15:49:48.435779666Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-27T15:49:48.438230583Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-27T15:49:48.440896874Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> received Zigbee message: < ZigbeeMessageRx || type: 
0x00, < AddressHeader || src_addr: 0xFB21, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -50, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x07, ZCLCommandId: 0x04 >, < WriteAttributeReponse || < WriteAttributeResponseRecord || ZclStatus: UNSUPPORTED_ATTRIBUTE, AttributeId: 0x4003 > > > >
2024-09-27T15:49:48.443861208Z DEBUG Zigbee Switch Mc  Lidl Plug device thread event handled
2024-09-27T15:49:48.446275333Z TRACE Zigbee Switch Mc  Received event with handler zigbee
2024-09-27T15:49:48.449009916Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> received Zigbee message: < ZigbeeMessageRx || type: 
0x00, < AddressHeader || src_addr: 0xFB21, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -50, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x08, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >

However, when a reinstallation of the device is performed without uninstalling it with firmware 53.19, the init life cycle was no longer performed and doConfigure was performed, which also makes no sense, but I could be wrong!

4 Likes

@SmartThings, this kind of changes in the API/platform must be communicated properly to the 3rd party developers. This is unacceptable.

1 Like

2 posts were split to a new topic: Icon/Badges reset and cannot be modified

I see the icon issue in the app regardless of the firmware so I suspect that is a coincidence. It might be that a new version of the app is rolling out and they had to preempt that.

The code and documentation always implied that the added lifecycle was meant to trigger an init lifecycle and they certainly used to have code to suppress a double init. I never understood why the way the lifecycles actually worked (with an init appearing early) was different to the way they seemed to be intending them to work long term. I have a comment in my driver that init runs after an added or a reboot and it seems that could finally be true.

That’s NOT to say that it makes sense to me that init comes before doConfigure when the documentation explicitly suggests that add_configured_attribute() and add_monitored_attribute() should typically be in the init handler and that is where they appear in stock handlers. That said my understanding of Edge drivers is limited and init has always seemed the wrong place for them to me.

As you say, the documentation talks about lifecycles, but it leaves a lot of doubts about the order in which they are called and when each of them is called, at least for me.

The init lifecycle, as its name seems to indicate, should be the first to be executed and in fact when the driver is initialized by a hub reboot or a driver update, it is the only life cycle that is executed.
In this init lifecycle, should put the code that is needed to initialize non-permanent set_field() type variables, functions to assign the enpoints to the components and vice versa, and also the add_monitored_attribute() function, to initialize the table with the customized values ​​of the maximum intervals of the attributes, if the device was configured with values ​​different from the defaults and the healt_check function can be executed if necessary.

On the other hand, the init lifecycle is the only one that is not shown in the CLI logs with a log.INFO that clarifies when it is called in the debug logs, as is the case with added, doConfigure and the rest.

2024-09-27T15:49:46.819615457Z INFO Zigbee Switch Mc  <ZigbeeDevice: 62028083-deab-435b-af10-c28ebf0a5874 [0xFB21] (Lidl Plug)> received lifecycle event: added

That is why in the drivers where I need to execute specific code in this lifecycle, I put a log.PRINT to know that the call to the init lifecycle has been received.

2024-09-27T15:49:45.815749999Z PRINT Zigbee Switch Mc  <<< Device do_init >>>

As you say, the stock drivers have the add_configured_attribute() and add_monitored_attribute() functions in the init lifecycle so that the related devices ​​in the configurations.lua module can be configured with custom values, when the doConfigure lifecycle will be executed.
Therefore this change seems to me that is an unintentional error since it leaves many of the stock drivers with the custom devices configuration unusable.

add_configured_attribute() and add_monitored_attribute() could be put directly in the doConfigure lifecycle function code, but add_monitored_attribute() needs to be run also when initializing the driver to restore the values ​​in the monitored attribute table if the hub reboots or the driver is updated or initialized since the doConfigure lifecycle will not be rerun in these cases.

But all this could be clarified in a very easy way and I hope that one day someone will answer. :partying_face:

3 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.

I have reopened this topic, because in the case of a staggered rollout like this one which is not even completed yet, I believe the Announcement thread should remain open until three days after the end of the staggered rollout, not three days after the original announcement.

10 Likes

As noted in this Firmware Release Notice on September 23, 2024, the Firmware for the above-mentioned Hubs is in the process of being updated to v54.10 from September 24th through October 11th.

As of today, we have four hubs which are still on v53.19. Typically we’ll see one or two updated early on.

I understand that the rollout is staggered and is projected through October 11th, but I’m curious if others have seen it come their way, any problems, has it been suspended, etc. ?

I know @cljara80 mentioned it broke the Shelly Edge Drivers. Anyone else seeing problems with Shelly Edge Drivers or anything else on the new v54.10 ?

1 Like

just a complaint - IMO you really should not use the same exact post title (almost) that was used as the announcement for firmware updates because it will be very confusing for some users. Everyone should use the STAFF posted thread (and staff monitored) to post issues:

my comment is only directed at the title.

4 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.

Nonetheless the title of this topic should be edited.

2 Likes

@jkp your suggestion is noted, thank you!

Unfortunately, that staff post was auto-locked so users can’t post any further. I referenced the Fireware Release Notice by link for continuity and wanted to keep the title on topic as best as I could (focused on the Aeotec/SmartThings Hub Models rather than other HUB Manuf/Models :slightly_smiling_face:

1 Like

I have reopened the original topic and moved all the discussion posts to that one, because I feel that in the case of a staggered rollout, like this one, the announcement thread should stay open until three days after the rollout completes.

Keeping all the comments together will be helpful to both the community and support staff.

Carry on. :sunglasses:

9 Likes

Thanks @JDRoberts !

… and back to the question posed…

Anyone else seeing problems with Shelly Edge Drivers or anything else on the new v54.10 ? I’m hoping to get some sense before my hubs get updated and implode :face_with_head_bandage:

2 Likes

9 posts were split to a new topic: Multiple Hub disconnected notifications

I tired to find any info regarding smartthings station and hub built in tv , when they will get updated to v54 ?

3 Likes
1 Like

Hello, I’m new to this forum so bear with me. I have a lock and a thermostat using Zwave connected to Aeotec and both were working perfectly. Recently, my lock (Schlage FE599) is connect and reconnect very frequently. Is there a relationship between the firmware update and my lock issue? Unfortunately, I’m away and have no access to the lock to completely disconnect and reconned it. Any advice? Thanks

3 Likes

smartthings station and built in hub tv are already update to v53 matter 1.2 , my question was about latest v54

1 Like

@alissa.dornbos With this fix coming, any chance SmartThings has suspended the rollout of v54.12?

We still have four hubs on v53.19 and I’m not looking forward to the issues v54.12 has created for other users, such this post.