Vision ZP3102 Motion Sensor packet ignored

Discussions about existing Z-Wave device and their usage with Z-Way/Z-Cloud/Z-Box
Post Reply
kfxo
Posts: 5
Joined: 28 Feb 2022 19:44

Vision ZP3102 Motion Sensor packet ignored

Post by kfxo »

I have a few old motion sensors, Vision ZP3102, that stopped working after recent updates, I am on 4.0.2. The status never updates. I have tried excluding and reincluding (unsecure and secure), setting acceptSetSecurityLevel = 0, setting AcceptReportSecurityLevel =0, and mapBasicSetToSpecificReport = True, but nothing works.

An error is reported in the log when motion is activated at the sensor:

Code: Select all

[2023-02-17 14:17:11.398] [D] [zway] SETDATA devices.17.data.lastReceived = 0 (0x00000000)
[2023-02-17 14:17:11.399] [W] [zway] Ignoring packet recieved on lower security scheme Plain text than our highest S0
[2023-02-17 14:17:11.399] [E] [zway] Error returned from _zway_cc_call_handler(zway, device->default_instance, controller->id, 0, data[4 + L], &data[5 + L]): Function class not supported by the hardware (-4)
The full section of the log when motion is activated at the sensor:

Code: Select all

[2023-02-17 14:17:11.398] [D] [zway] RECEIVED: ( 01 0C 00 04 00 11 03 20 01 FF B8 00 00 83 )
[2023-02-17 14:17:11.398] [D] [zway] SENT ACK
[2023-02-17 14:17:11.398] [D] [zway] SETDATA devices.17.data.lastReceived = 0 (0x00000000)
[2023-02-17 14:17:11.399] [W] [zway] Ignoring packet recieved on lower security scheme Plain text than our highest S0
[2023-02-17 14:17:11.399] [E] [zway] Error returned from _zway_cc_call_handler(zway, device->default_instance, controller->id, 0, data[4 + L], &data[5 + L]): Function class not supported by the hardware (-4)
[2023-02-17 14:17:11.419] [D] [zway] RECEIVED: ( 01 13 00 04 00 11 0A 71 05 07 FF 00 FF 07 02 00 00 B8 00 00 3D )
[2023-02-17 14:17:11.419] [D] [zway] SENT ACK
[2023-02-17 14:17:11.419] [D] [zway] SETDATA devices.17.data.lastReceived = 0 (0x00000000)
[2023-02-17 14:17:11.419] [D] [zway] SETDATA devices.17.instances.0.commandClasses.113.data.V1event.alarmType = 7 (0x00000007)
[2023-02-17 14:17:11.419] [D] [zway] SETDATA devices.17.instances.0.commandClasses.113.data.V1event.level = 255 (0x000000ff)
[2023-02-17 14:17:11.419] [D] [zway] SETDATA devices.17.instances.0.commandClasses.113.data.V1event = Empty
[2023-02-17 14:17:11.419] [D] [zway] SETDATA devices.17.instances.0.commandClasses.113.data.7.2.status = True
[2023-02-17 14:17:11.419] [D] [zway] SETDATA devices.17.instances.0.commandClasses.113.data.7.2.parameters = byte[0]
[2023-02-17 14:17:11.419] [D] [zway]   ( zero-length buffer )
[2023-02-17 14:17:11.419] [D] [zway] SETDATA devices.17.instances.0.commandClasses.113.data.7.2 = Empty
[2023-02-17 14:17:11.419] [D] [zway] SETDATA devices.17.instances.0.commandClasses.113.data.7.status = True
[2023-02-17 14:17:11.419] [D] [zway] SETDATA devices.17.instances.0.commandClasses.113.data.7 = Empty
[2023-02-17 14:17:18.101] [D] [zway] Job 0x3b: deleted from queue
Any way to get it to work again?
Top
Post Reply

Return to “Device specific”