Page 1 of 2
support: 26 03
Posted: 27 Sep 2022 16:45
by fez
I have been ignoring this issue for some time:
Code: Select all
[W] [zway] Unhandled command in policy - contact Z-Wave.Me support: 26 03
[W] [zway] Got unsecure packet from device 22, but Command Class 0x26 SwitchMultilevel is marked as secure and not present in unsecure NIF. Ignoring packet.
[E] [zway] Error returned from _zway_cc_call_handler(zway, command, controller->id, 0, data[4], &data[5]): Function class not supported by the hardware (-4)
Device 22 is a Roller Shutter FGRM-222.
Some advice how to handle this would be welcome.
Re: support: 26 03
Posted: 28 Sep 2022 06:19
by PoltoS
We need more [D] lines just before it. But I suppose the device reported its state insecurely, while it was added with security.
In v4.0.0 we will dramatically improve the security policy and many such errors might go away.
Re: support: 26 03
Posted: 29 Sep 2022 19:21
by fez
Thanks.
I guess I'll just wait it out than.
Re: support: 26 03
Posted: 29 Sep 2022 22:13
by fez
I actually have a second issue, which falls in this category after looking into the logs. Some of my Fibaro devices (button, swipe) send Central Scene Notifications. I see these in the Zniffer, but these don't show in the Zway events and rules activated by these don't work.
I found this in the logs:
Code: Select all
[...869] [D] [zway] RECEIVED: ( 01 12 00 04 00 4A 09 60 0D 00 00 5B 03 32 00 02 C3 00 00 6C )
[...870] [D] [zway] SENT ACK
[...870] [D] [zway] SETDATA devices.74.data.lastReceived = 0 (0x00000000)
[...870] [W] [zway] Ignoring packet recieved on lower security scheme Plain text than device highest S0
[...870] [E] [zway] Error returned from (returnStatus = _zway_cc_call_handler(zway, cmd, node_id, data[3], length - 4, &data[4])): Function class not supported by the hardware (-4)
These use to work just fine. I have not been using these devices for a while, so I don't know when this got broken.
Any suggestions how to fix this would be great.
Re: support: 26 03
Posted: 30 Sep 2022 03:57
by PoltoS
Both mean the device is sending unsecure commands, while it is included securely. This happens with buggy devices.
You can set devices[74].data.acceptSetSecurityLevel=0 to allow insecure commands.
Re: support: 26 03
Posted: 30 Sep 2022 12:31
by fez
You can set devices[74].data.acceptSetSecurityLevel=0 to allow insecure commands.
Where could I do (add) this?
Re: support: 26 03
Posted: 30 Sep 2022 20:57
by fez
I have tried this via the "Load custom JavaScript code" module:
Code: Select all
zway.devices[74].data.acceptSetSecurityLevel=0;
... but with no effect
Re: support: 26 03
Posted: 01 Oct 2022 10:30
by piet66
try this:
Code: Select all
http://IP:8083/ZWaveAPI/Run/zway.devices[74].data.acceptSetSecurityLevel.value=0
You can check with .../ZWaveAPI/Data/0 whether it's stored.
You should check too whether the type is changed from "empty" to "int" or "string".
Re: support: 26 03
Posted: 03 Oct 2022 11:20
by fez
Thanks for the hint piet66.
The type is int. The value has been stored.
... still no effect
Re: support: 26 03
Posted: 10 Oct 2022 03:25
by PoltoS
Sorry, it is a report.
This is a device bug - include it insecurely or wait for 4.0.0 to allow to fix it using acceptReportSecurityLevel