Behaviour upon receiving empty eventData #7525
Replies: 2 comments 1 reply
-
👋 Hey @01ste02! It looks like you attached a logfile, but its filename doesn't look like it a driver log that came from Z-Wave JS. Please double-check that you uploaded the correct logfile. If you did, disregard this comment. As a reminder, here's how to create one: |
Beta Was this translation helpful? Give feedback.
-
To clarify (as I suggested submitting the issue), there is not an empty payload, as that is what one would actually expect with the |
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?
When receiving the following event:
We get an empty payload, even though the dataType is set to 0. Is this allowed? This is then interpreted as 0x00 when stringifying the JSON data, resulting in the following parsing:
Is this expected behavior on your part, or is it undefined/unexpected?
Anything else we should know?
This is also discussed here:
home-assistant/core#134172
With more in-depth analysis in home-assistant/core#134172 (comment)
Software versions
Driver (node-zwave-js): 14.3.7
Z-Wave JS UI: 9.27.8
Home Assistant Z-Wave Integration: 1.40.2
Z-Wave Controller (Stick/Dongle/...)
AEON Labs Z stick Gen5 USB Controller v1.1
Device information
Manufacturer: Philio Tech
Model name: PSK01
Node ID: 3
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
home-assistant_zwave_js_2024-12-28T19-33-19.766Z.log
Beta Was this translation helpful? Give feedback.
All reactions