-
A small test network stops working after upgrading the UZB7 firmware (as mentioned on Discord). Symptoms:
Scenario:
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.
Some diagnostics I have tried, that were unsuccessful
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
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. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
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.