@poltos,
For the last 4-5 days, almost everyday I have a couple of devices with this issue!
Razberry Z-Way 3.0.0--CRC16 and Security classes showing up
Re: Razberry Z-Way 3.0.0--CRC16 and Security classes showing up
I can confirm that everyday for the last 3 days, I'm having at least 3-4 nodes that are no more working 'cause of the "CRC16" or "Security" class that show up!
Re: Razberry Z-Way 3.0.0--CRC16 and Security classes showing up
I just had one device do this. I literally have had one device with this problem in 2-3 months. It is still annoying and I learned how to recover it using a JS API command. @PoltoS, I know you are waiting to reproduce it and figure out what the exact mechanism is but in the meantime, could you not implement my suggestion of not allowing new command classes to be added to the device configuration without the a user manual interview? I am very convinced that it is from a false packet coming from a noisy zwave environment passing the CRC check.
Re: Razberry Z-Way 3.0.0--CRC16 and Security classes showing up
I agree with @rafale77 too, for the moment, at least our environment will work perfectly for more than a couple of days!
Re: Razberry Z-Way 3.0.0--CRC16 and Security classes showing up
I also think it has something to do with the z-wave traffic. A few months ago I reduced the traffic in my network considerably and since then this problem has not reappeared.
Raspberry Pi 3 Model B Rev 1.2
Raspbian GNU/Linux 10 (buster, 32bit)
RaZberry by Z-Wave.Me ZW0700 7.20.00 07.38/1766938484 1025/257
Z-Way version v4.1.2 from 2023-10-18 03:34:26 +0300
Raspbian GNU/Linux 10 (buster, 32bit)
RaZberry by Z-Wave.Me ZW0700 7.20.00 07.38/1766938484 1025/257
Z-Way version v4.1.2 from 2023-10-18 03:34:26 +0300
Re: Razberry Z-Way 3.0.0--CRC16 and Security classes showing up
Please send me the log so I can check the reson of it and we fix it in upcoming release.
The problem is due to corrupted packets from 3rd gen devices that passes CRC8 check still being corrupted. We need to see those packets to fix it. Please help us with providing the log.
The problem is due to corrupted packets from 3rd gen devices that passes CRC8 check still being corrupted. We need to see those packets to fix it. Please help us with providing the log.
Re: Razberry Z-Way 3.0.0--CRC16 and Security classes showing up
I'm unable to provide logs as I can see it couple days later when a device stop responding!
Re: Razberry Z-Way 3.0.0--CRC16 and Security classes showing up
You can provide me many logs, we will find it out
Re: Razberry Z-Way 3.0.0--CRC16 and Security classes showing up
Thanks @PoltoS but I am just wondering if you could just prevent any new command classes from showing up on the configuration from anything but during the user configuration. Understanding the mechanism is great but you won't be able to prevent corrupt packets from coming in, nor will we be able to guarantee that there aren't other types of corrupt packets. Apparently this is a problem only after version 3.0.0 so I can't see how much logs will help you fix the problem. Apparently we are seeing security and CRC16 classes along with a couple of more rare ones showing up across all kinds of different devices so it isn't a single type of packet causing the creation of a single type of command class.
I wish I could help you with logs but it is impossible for me to figure out exactly when the command class occurred and even less to be able to find the corresponding log since we don't even get any message when this happens. I would highly recommend to go to a routine of forbidding/blocking command class creation/addition outside of interview time.
I wish I could help you with logs but it is impossible for me to figure out exactly when the command class occurred and even less to be able to find the corresponding log since we don't even get any message when this happens. I would highly recommend to go to a routine of forbidding/blocking command class creation/addition outside of interview time.
Re: Razberry Z-Way 3.0.0--CRC16 and Security classes showing up
This is what we want to do. We just want to understand what is coming corrupted. It is definitely easier to fix a bug if you can reproduce it
Search for "instantiating it as not supported". Looks we know how to catch it
Search for "instantiating it as not supported". Looks we know how to catch it