Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Razberry Pro 7 and Vision ZD2102 sensor #6298

Closed
vaxjool opened this issue Sep 21, 2023 · 6 comments
Closed

Razberry Pro 7 and Vision ZD2102 sensor #6298

vaxjool opened this issue Sep 21, 2023 · 6 comments
Labels
cannot fix ❌ This is something out of our control - like invalid device behavior

Comments

@vaxjool
Copy link

vaxjool commented Sep 21, 2023

Hi,

My Vision ZD2102-EU (documentation), Razberry 7 Pro, doens't work with zwave-js-ui/zwavejs2mqtt after version 8.21.

After migration/re-creating the container using the :latest -version, all my battery operated door sensors stop working, with any version of zwavejsui, greater than version 8.21. It doesn't register open/closed state. I can ping it if I keep it "alive". If re-interviewing the configuration is corrupt/non existing.

Version 8.21 works perfectly with the exact same hardware and devices.

Any suggestions as to why this is the case?

br
@robertsLando
Copy link
Member

robertsLando commented Sep 21, 2023 •
edited by AlCalzone
Loading

Please make a driver log of a re-interview, loglevel debug and attach it here as a file (drag & drop into the text field).

@robertsLando robertsLando transferred this issue from zwave-js/zwave-js-ui Sep 21, 2023
@zwave-js-assistant zwave-js-assistant bot added the stale 💤 This issue seems to have gone stale. Interact with it to keep it open label Sep 29, 2023
@zwave-js-assistant
Copy link

This issue has not seen any recent activity and was marked as "stale 💤".
Closing for housekeeping purposes... 🧹

Feel free to reopen if the issue persists.

@vaxjool
Copy link
Author

vaxjool commented Oct 2, 2023 •
edited
Loading

Hi, sorry for the delay, it's just a crazy time atm. Could you please re-open this issue, thanks.

I've attached both files and I re-interviewed device 23.

As you can see, after the re-interview the device id is wrong, using the old 8.21.2.c version it is: 265-258-8193 (0x0109-0x2001-0x0102) and it doesn't register state changes in newer versions.

zwavejs_2023-10-02.log
z-ui_2023-10-02.log

@AlCalzone AlCalzone reopened this Oct 3, 2023
@AlCalzone
Copy link
Member

This looks like a bug in the controller firmware. Z-Wave JS enables 16-bit node IDs, which the controller claims to support, but once enabled it sets the node ID of all incoming commands to 1. Therefore, the responses from the node are not detected.

I don't specifically see this issue mentioned on the changelog, but there are a few firmware upgrades available: https://z-wave.me/support/uzbrazberry-firmwares/
Currently I'd recommend not going above 7.28 / 07.17.02.01 SDK 7.17.02 though. The newer Z-Wave SDKs have a few glaring bugs.

@AlCalzone AlCalzone added cannot fix ❌ This is something out of our control - like invalid device behavior and removed waiting for info ⏳ stale 💤 This issue seems to have gone stale. Interact with it to keep it open labels Oct 6, 2023
@vaxjool
Copy link
Author

vaxjool commented Oct 8, 2023

Ok, thanks, I'll report back as soon as I've tested with newer firmware. I'll try to test this during the week.

@zwave-js-assistant
Copy link

This issue has not seen any recent activity and was marked as "cannot fix ❌".
Closing for housekeeping purposes... 🧹

Feel free to reopen if the issue persists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cannot fix ❌ This is something out of our control - like invalid device behavior
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@vaxjool @robertsLando @AlCalzone