52.X Hub V2/V3 Customer Beta Release Notes

Hi @posborne

Thanks for the reply,

Lazy loading of subdrivers can be a good improvement.

I think it will need a lot of testing to avoid errors since there are many subdrivers and many peculiarities.

I have been slow to answer because I was fighting with a bug that was suggested to me in a custom subdriver for “fibaro-rgbw-controller”, which uses the 4 channels independently and only fails when the lazy loading function of the subdriver is used, that is always the same error when executing commands from the app and when emit the event
Since I don’t have the 9 libraries, I couldn’t see the code for the line that fails.

And in the end I could see that it may due to the assignment of the 4 endpoints to the four components.

EDIT:
Mysteriously, when I reinstalled the driver it gave the error again continuously and there is no way for it to work again with the lazy loading of the subdriver.

2024-02-05T21:37:33.921546751Z INFO Z-Wave Bulb Mc  <ZwaveDevice: e78f6785-37e1-48bd-a197-ecf8dbc13260 [27] (Fibaro RGBW)> received command: {"args":{},"capability":"switch","command":"on","component":"white","positional_args":{}}
2024-02-05T21:37:33.953046667Z INFO Z-Wave Bulb Mc  <ZwaveDevice: e78f6785-37e1-48bd-a197-ecf8dbc13260 [27] (Fibaro RGBW)> Lazy loaded driver into dispatcher: Fibaro RGBW Controller       
2024-02-05T21:37:33.960921667Z TRACE Z-Wave Bulb Mc  Found CapabilityCommandDispatcher handler in zwave_bulb -> Fibaro RGBW Controller
2024-02-05T21:37:33.967323292Z ERROR Z-Wave Bulb Mc  Fibaro RGBW thread encountered error: [string "st/dispatcher.lua"]:261: Error encountered while processing event for <ZwaveDevice: e78f6785-37e1-48bd-a197-ecf8dbc13260 [27] (Fibaro RGBW)>:
    arg1: table: 0x2a69480
"\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x73\x74\x2F\x64\x69\x73\x70\x61\x74\x63\x68\x65\x72\x2E\x6C\x75\x61\x22\x5D\x3A\x32\x36\x31\x3A\x20\x45\x72\x72\x6F\x72\x20\x65\x6E\x63\x6F\x75\x6E\x74\x65\x72\x65\x64\x20\x77\x68\x69\x6C\x65\x20\x70\x72\x6F\x63\x65\x73\x73\x69\x6E\x67\x20\x65\x76\x65\x6E\x74\x20\x66\x6F\x72\x20\x3C\x5A\x77\x61\x76\x65\x44\x65\x76\x69\x63\x65\x3A\x20\x65\x37\x38\x66\x36\x37\x38\x35\x2D\x33\x37\x65\x31\x2D\x34\x38\x62\x64\x2D\x61\x31\x39\x37\x2D\x65\x63\x66\x38\x64\x62\x63\x31\x33\x32\x36\x30\x20\x5B\x32\x37\x5D\x20\x28\x46\x69\x62\x61\x72\x6F\x20\x52\x47\x42\x57\x29\x3E\x3A\x0A\x20\x20\x20\x20\x61\x72\x67\x31\x3A\x20\x74\x61\x62\x6C\x65\x3A\x20\x30\x78\x32\x61\x36\x39\x34\x38\x30\x0A\x22\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x66\x69\x62\x61\x72\x6F\x2D\x72\x67\x62\x77\x2D\x63\x6F\x6E\x74\x72\x6F\x6C\x6C\x65\x72\x2F\x69\x6E\x69\x74\x2E\x6C\x75\x61\x22\x5D\x3A\x38\x35\x39\x3A\x20\x61\x74\x74\x65\x6D\x70\x74\x20\x74\x6F\x20\x69\x6E\x64\x65\x78\x20\x61\x20\x6E\x69\x6C\x20\x76\x61\x6C\x75\x65\x20\x28\x66\x69\x65\x6C\x64\x20\x27\x3F\x27\x29\x22"
2024-02-05T21:42:59.240993053Z TRACE Z-Wave Bulb Mc  Received event with handler capability
2024-02-05T21:43:00.087143845Z INFO Z-Wave Bulb Mc  <ZwaveDevice: e78f6785-37e1-48bd-a197-ecf8dbc13260 [27] (Fibaro RGBW)> received command: {"args":{},"capability":"switch","command":"on","component":"main","positional_args":{}}
2024-02-05T21:43:00.114087428Z TRACE Z-Wave Bulb Mc  Found CapabilityCommandDispatcher handler in zwave_bulb -> Fibaro RGBW Controller
2024-02-05T21:43:00.120917512Z PRINT Z-Wave Bulb Mc  <<<< set_switch >>>>
2024-02-05T21:43:00.135980553Z PRINT Z-Wave Bulb Mc  <<<< command.component     main
2024-02-05T21:43:00.172384887Z PRINT Z-Wave Bulb Mc  <<<< value 255
2024-02-05T21:43:00.181463137Z ERROR Z-Wave Bulb Mc  Fibaro RGBW thread encountered error: [string "st/dispatcher.lua"]:261: Error encountered while processing event for <ZwaveDevice: e78f6785-37e1-48bd-a197-ecf8dbc13260 [27] (Fibaro RGBW)>:
    arg1: table: 0x2ac0f20
"\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x73\x74\x2F\x64\x69\x73\x70\x61\x74\x63\x68\x65\x72\x2E\x6C\x75\x61\x22\x5D\x3A\x32\x36\x31\x3A\x20\x45\x72\x72\x6F\x72\x20\x65\x6E\x63\x6F\x75\x6E\x74\x65\x72\x65\x64\x20\x77\x68\x69\x6C\x65\x20\x70\x72\x6F\x63\x65\x73\x73\x69\x6E\x67\x20\x65\x76\x65\x6E\x74\x20\x66\x6F\x72\x20\x3C\x5A\x77\x61\x76\x65\x44\x65\x76\x69\x63\x65\x3A\x20\x65\x37\x38\x66\x36\x37\x38\x35\x2D\x33\x37\x65\x31\x2D\x34\x38\x62\x64\x2D\x61\x31\x39\x37\x2D\x65\x63\x66\x38\x64\x62\x63\x31\x33\x32\x36\x30\x20\x5B\x32\x37\x5D\x20\x28\x46\x69\x62\x61\x72\x6F\x20\x52\x47\x42\x57\x29\x3E\x3A\x0A\x20\x20\x20\x20\x61\x72\x67\x31\x3A\x20\x74\x61\x62\x6C\x65\x3A\x20\x30\x78\x32\x61\x63\x30\x66\x32\x30\x0A\x22\x5B\x73\x74\x72\x69\x6E\x67\x20\x22\x66\x69\x62\x61\x72\x6F\x2D\x72\x67\x62\x77\x2D\x63\x6F\x6E\x74\x72\x6F\x6C\x6C\x65\x72\x2F\x69\x6E\x69\x74\x2E\x6C\x75\x61\x22\x5D\x3A\x38\x30\x37\x3A\x20\x61\x74\x74\x65\x6D\x70\x74\x20\x74\x6F\x20\x69\x6E\x64\x65\x78\x20\x61\x20\x6E\x69\x6C\x20\x76\x61\x6C\x75\x65\x20\x28\x66\x69\x65\x6C\x64\x20\x27\x3F\x27\x29\x22"

NEW EDIT:

After several tests, in a driver reinstallation it worked again without changing anything.
And in the same way, without changing anything, it stopped working with the same error on another reinstallation.

It seems to have to do with a problem with lazy loading of the subdriver and its handlers, some times do not load fine.

Normally work fine the subdriver zwave handlers and works bad the capability handlers

May be the is a big subdriver??

What I have seen is that the lazy loading function can be used very flexibly and you can not use lazy loading for a specific subdriver or subdrivers and it works perfectly.

Everything else works fine on the 6 drivers I’m testing works fine, but I only use one or two subdrivers per driver.

2 Likes

Hello Everyone,

Today we have released 52.7 to the Customer Beta population for V2/V3 Hubs. Please let us know if you see any changes that are concerning.

Thank you.

1 Like

Hey, so ive been having issues with my zigbee rgbw controllers disconnecting and ive done the survey last week but i havent gotten the new firmware yet… any way i can get this beta to see if it solves my zigbee issues?

:disappointed_relieved: any way i can get this fw pushed to my hub? not sure how the process works to get my hub selected. i already signed up on the portal but nothings happened.

1 Like

I think that they normally update the hub list at the start of the beta cycle. So in your case you’d be eligible for the 53.x releases. That is how it worked when I signed up while a release cycle was in process, and also once when I had changed my owner account and it was incorrect at the start of a cycle.

Doesn’t mean they won’t make an exception though.

1 Like

Lame… this zigbee issue is tempting me to try home assistant :frowning:

Hi @alissa.dornbos ,

Over the last few days I’ve have many Zigbee sensors (motion, contact, ad leak) go offline and then com back online a while later. A few of them even have new batteries, so all I’ve been doing is just watching and not removing/replacing batteries to see if they come back, and then usually do.

ST has access to anything as you’ve requested above. I’ll PM you my email shortly.

Currently this device is offline and I expect it to come back:
Garage Motion Sensor

These have gone offline and came back:
Garage Window Double Right
Garage Window Double Left
Upstairs Bath Toilet Leak Sensor

1 Like

I have been seeing similar symptoms with both Zigbee and Thread devices. Usually pulling the batteries for a few seconds brings them back online.

Try Z-Wave!

Sorry, couldn’t resist :grin:.

2 Likes

I have been seeing similar symptoms too.

1 Like

Z-wave devices are actually doing really well at the minute for me.

Lol, no worries!

2 Likes

@alissa.dornbos ,

Add Garage Window Single

Edit:

@alissa.dornbos , any word on what’s going on? This particular device came back online, then off again, and then I replaced the battery to get it back online, and now it’s offline again.

Hello All,

We are still working on Release 52 and will be releasing a new version of 52.8 to external beta participants as soon as today.

Release notes for this release include:

  • Changes were made to the Zigbee and Thread stacks. Please call out potential issues you may experience with Zigbee or Matter-Thread devices.

I know some of you have requested to be added to the Beta with V2/V3 hubs, I will make that request known to the release team.

Thank you.

5 Likes

Hi @alissa.dornbos , I tagged you in this post from @Mariano_Colmenarejo :metal:

2 Likes

Hello!

We will be rolling out an updated version of 52.9 to customer beta hubs as soon as today! Please stay tuned. Thank you!

6 Likes

Hi @alissa.dornbos ,

With 52.9 I’ve experienced more Zigbee devices going offline than any of the more recent firmware updates.

While some battery powered devices going offline could have been related to an actual low battery condition, I’m continuing to experience extreme battery drain, or at least rapid drain; but, now I’m getting mains powered Zigbee devices going offline. Those have all been mostly switches, and after a period of time they will come back online, now I have a siren offline, and it’s never gone offline before.

Here’s what’s offline this morning as of 8am EST:
Kitchen Siren (mains powered)
Nook Center Window (battery powered, 100% battery but I don’t believe it)
Garage Electrical Panel (battery powered, 100% battery which I replaced last night when it hit 11%)

Over the past week I’ve seen at least three switches go offline and eventually go back online without any intervention on my end, and I had three other battery powered contact sensors go offline, but they only came back online after I removed the battery and put the same one back.

ST has access as requested above with no end date.

EDIT : Those same devices are still offline as of 2:30pm. When I get home from work I’ll get them going again.

5 Likes

I know this potential improper use of the forum may frustrate some people but please forgive me as I’m relatively new and don’t know how to use the forum properly. I’m trying my best here and acting in good faith but my disabilities make me find it hard & struggle. (Instead of reporting and deleting perhaps a dev or mod could split this off into a thread that has the right category? I saw that done once, was much appreciated)

With that said, I do have a feature/update request that many users might benefit from. Seeing as matter over thread (1.3) has started to gain traction, could TREL (for Thread over infrastructure) support be implemented for devices that have WiFi and/or ethernet alongside their thread border router? It would be useful to the smartthings network for many reasons and Apple has already begun to roll it out on their Hub Networks with Google starting to work on it for theirs. I currently have both in my Home Assistant Network (alongside my 3 Samsung Hub’s) which is a mix of Matter Over WiFi & Matter Over Thread devices

Hello Everyone,

I am writing to inform you that today we have rolled out 52.11 to the Customer Beta population for V2/V3 Hubs.

Thank you,

Alissa

2 Likes

Hello,

I don’t know if it has anything to do with the new Beta 52.11 version, but I have observed the following on several devices with different drivers.

  • I have stopped receiving the 2 ZDO messages from the Basic cluster with each AttributeReport message on several devices with different drivers:

with 52.09:

2024-03-07T17:54:00.424525730Z INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 075f38a5-5928-444b-ac8a-4563446777f4 [0xDD38] (Sensor Mov-1)> received Zigbee message: < ZigbeeMessageRx || type: 0x02, < AddressHeader || src_addr: 0xDD38, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: Basic >, lqi: 0xD0, rssi: -82, body_length: 0x000B, < ZDOMessageBody || < ZDOHeader || seqno: 0x89 >, GenericBody:  00 00 00 00 00 00 00 00 00 00 > >
2024-03-07T17:54:01.390896771Z DEBUG Zigbee Motion Sensor Mc  Sensor Mov-1 device thread event handled
2024-03-07T17:54:01.401375355Z TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2024-03-07T17:54:01.414923980Z INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 075f38a5-5928-444b-ac8a-4563446777f4 [0xDD38] (Sensor Mov-1)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xDD38, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xBA, rssi: -61, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x75, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0002, DataType: Bitmap16, ZoneStatus: 0x0020 > > > >
2024-03-07T17:54:01.420222230Z TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2024-03-07T17:54:01.424796771Z INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus
2024-03-07T17:54:01.434003896Z INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 075f38a5-5928-444b-ac8a-4563446777f4 [0xDD38] (Sensor Mov-1)> emitting event: {"attribute_id":"motion","capability_id":"motionSensor","component_id":"main","state":{"value":"inactive"}}
2024-03-07T17:54:01.444903605Z DEBUG Zigbee Motion Sensor Mc  Sensor Mov-1 device thread event handled
2024-03-07T17:54:02.633368043Z TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2024-03-07T17:54:02.674138752Z INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 075f38a5-5928-444b-ac8a-4563446777f4 [0xDD38] (Sensor Mov-1)> received Zigbee message: < ZigbeeMessageRx || type: 0x02, < AddressHeader || src_addr: 0xDD38, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: Basic >, lqi: 0xD0, rssi: -82, body_length: 0x000B, < ZDOMessageBody || < ZDOHeader || seqno: 0x8A >, GenericBody:  00 00 00 00 00 00 00 00 00 00 > >

with 52.11

2024-03-07T21:48:29.341479337Z INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 9b6380e3-7155-4d74-85f6-0878a92e0a85 [0xB389] (Sensor Mov-2)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xB389, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xBC, rssi: -60, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x11, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0002, DataType: Bitmap16, ZoneStatus: 0x0020 > > > >
2024-03-07T21:48:29.411513503Z TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2024-03-07T21:48:29.417151378Z INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus
2024-03-07T21:48:29.423116128Z INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 9b6380e3-7155-4d74-85f6-0878a92e0a85 [0xB389] (Sensor Mov-2)> emitting event: {"attribute_id":"motion","capability_id":"motionSensor","component_id":"main","state":{"value":"inactive"}}
  • Smoke detector Mc: The 3 paired devices only send AttributReport message.

  • Contact Sensor Mc: Some devices continue to send ZDO messages. I have re-paired one of them, resetting the device, WITH HUB SECURE MODE DISABLED, and it has been re-paired, configured correctly, they have a new network ID (DNI), it has not lost any routines and it has stopped sending messages ZDO of the Basic cluster.

  • Motion Sensor Mc: Identical to the Motion Sensor Mc. I also re-paired a device with the same result.

  • It is possible that since they are sleeping devices, they have not been reconfigured with the Hub reboot. Tomorrow I will re-pair all the devices with these drivers with this quick and easy method. Now it’s too late here.

  • Switch Mc: all but one of the controller devices have stopped sending ZDO cluster basic messages

  • Multi Switch Mc: one of two the driver devices have stopped sending ZDO cluster basic messages

  • Temperature humidity Mc: The two driver devices have stopped sending ZDO cluster basic messages.

If they have nothing to do with it, it doesn’t matter, it is good news for the zigbee network and for the batteries.

2 Likes