UZB7 issues after upgrading to 7.19.3+

[kpine]

A small test network stops working after upgrading the UZB7 firmware (as mentioned on Discord).

Symptoms:

• Node is dead on startup
• Fails to respond to Ping and other commands

Scenario:

• UZB7 controller
• Last working firmware 7.18.6
• Broken firmware 7.19.3 and 7.20.1
• One node, a FLiRS thermostat

In 7.18.6, this test network worked fine. The node responds to pings and is responsive for all other commands.

Upon upgrading to 7.19.3 (and others, like 7.20.1), the node is unresponsive on startup, and fails to respond to pings.

When I use a Zniffer, the 7.19.3 case is extremely noisy with CRC_ERROR and WakeUp Beam Start/Stop, while the 7.18.6 is very clean.

I don't have any other nodes to use with this network. Another user has reported problems only with Door locks, which are also FLiRS, which makes me wonder if that's the issue.

Here are log files and Zniffer captures. In each case, I startup Z-Wave JS. Then ping the node. For the good case, I refreshed the thermostat mode. In the bad case, the command classes aren't shown in ZUI, so I can't try that.

• Driver logs for 7.18.6 zwavejs_2023-08-14_7.18.6_good.log
• Driver logs for 7.19.3 zwavejs_2023-08-14_7.19.3_bad.log
• Zniffer capture files for both cases zniffer_captures.zip

Some diagnostics I have tried, that were unsuccessful

• Downgrade Z-Wave JS to 11.6.0, prior to using 16-bit node types
• Disable soft-reset (on 11.6.0), re-plug USB stick
• Change TX power levels (default is 0 / 3.3)
  • 0 / 0
  • 9.9 / -6.5 (Aeotec Z-Stick 7 setting)
  • 6 / 0 (Zooz ZST10 700 setting)
• Change region to US LR

[kpine]

Here's a second capture without much CRC errors. It is possible those are coming from my production network, although I only see the messages when ZJS is starting up, so I find that suspect. Either way, the result is the same.

bad_2_7.19.3.zip

[kpine]

I guess this is just the same problem that was previously discussed. That mostly centered on problems with EU region, while I am in US. Particularly #2544 (comment).

Circular reference to https://community.silabs.com/s/question/0D58Y0000ATI2q8SQD/upgraded-firmware-completely-lost-all-range?language=en_US.

[kpine]

In other words, just broken firmware.