Jasco Motion Dimmer 26932 / ZW3008 not updating Motion detection #7440
Replies: 2 comments
-
|
👋 Hey @christensonautohome! Thanks for opening an issue! It doesn't look like you provided a logfile though. While not strictly necessary for every issue, having a driver log on loglevel debug is required to diagnose most issues. Please consider uploading a logfile that captures your problem. As a reminder, here's how to create one: |
Beta Was this translation helpful? Give feedback.
-
|
I ran a debug log and this is all that pulled for the node when I walked in and walked out activating the switch. 2024-11-25T21:42:49.985Z CNTRLR [Node 082] The node is alive. |
Beta Was this translation helpful? Give feedback.
-
Checklist
I have read and followed the above instructions
I have checked the troubleshooting section and my problem is not described there.
I have read the changelog and my problem was not mentioned there or the fix did not work.
Describe the issue
What is happening? installed Jasco motion dimmer 26932 / ZW3008 exposes a motion sensor but the motion sensor does not update when the motion on the switch is triggered. The light (which is exposed) does update almost immediately when motion is triggered and the light turns on, however the exposed motion sensor does not record any activity.
What did you expect to happen instead? I would expect the exposed motion sensor to report motion
Steps to reproduce the behavior:
no steps needed, exposed motion sensor is not updating values
Anything else we should know?
Software versions
Driver (node-zwave-js): ID 82
Z-Wave JS UI:
Home Assistant Z-Wave Integration: Z-Wave JS
Home Assistant Z-Wave JS Addon: ...
ioBroker.zwave2 Adapter: ...
If you are using something non-standard, tell us here: ...
Z-Wave Controller (Stick/Dongle/...)
Manufacturer: ...
Model name: ...
Firmware version: ...
Device information
Manufacturer: JASCO
Model name: 26932 / ZW3008
Node ID: 82
Checklist
I made sure to provide a driver log on level debug.
The log includes a re-interview of the problematic device (if applicable).
The log includes the problematic interaction with the device (if applicable).
I provided the node ID of the problematic device (if applicable).
Upload Logfile
2024-11-25 16:36:26.149 INFO STORE: [Node 082] Value updated: 38-0-targetValue 69 => 0
2024-11-25 16:36:26.151 INFO STORE: [Node 082] Value updated: 38-0-currentValue 34 => 0
2024-11-25 16:36:31.519 INFO STORE: [Node 082] Value updated: 38-0-currentValue 0 => 0
2024-11-25 16:36:44.560 INFO STORE: GET /health/zwave 301 0.607 ms - 162
2024-11-25 16:36:45.548 INFO STORE: [Node 082] Value updated: 38-0-currentValue 0 => 34
2024-11-25 16:36:47.199 INFO STORE: [Node 033] Metadata updated: 50-1-value-66049
2024-11-25 16:36:47.201 INFO STORE: [Node 033] Value updated: 50-1-value-66049 0 => 0
2024-11-25 16:36:47.297 INFO STORE: [Node 033] Metadata updated: 50-2-value-66049
2024-11-25 16:36:47.298 INFO STORE: [Node 033] Value updated: 50-2-value-66049 7.2 => 7.1
2024-11-25 16:36:47.396 INFO STORE: [Node 033] Metadata updated: 50-0-value-66049
2024-11-25 16:36:47.398 INFO STORE: [Node 033] Value updated: 50-0-value-66049 7.2 => 7.1
Beta Was this translation helpful? Give feedback.
All reactions