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.

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

[zwave JS] Fibaro rollershutter 3 stops working with version 0.1.77 #2939

Closed
ljsquare opened this issue Mar 27, 2023 · 5 comments
Closed

[zwave JS] Fibaro rollershutter 3 stops working with version 0.1.77 #2939

ljsquare opened this issue Mar 27, 2023 · 5 comments

Comments

@ljsquare
Copy link

Describe the issue you are experiencing

After updating the add-on to version 0.1.77 the Fibaro Rollershutter 3 won't respond to any commands. According to the status it is recognised and alive.
I revert back to 0.1.76 and I don't have any issues.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

Z-Wave JS

What is the version of the add-on?

0.1.77

Steps to reproduce the issue

  1. update to 0.1.77
  2. control cover with up/down
  3. no reaction
    ...

System Health information

none

Anything in the Supervisor logs that might be useful for us?

No response

Anything in the add-on logs that might be useful for us?

2023-03-27T09:16:44.016Z CNTRLR   [Node 043] Timed out while waiting for a response from the node (ZW0201)
Z-Wave error ZWaveError: Cannot check for firmware updates for node 43: Failed to query fingerprint from the node! (ZW0260)
    at ZWaveController.getAvailableFirmwareUpdates (/usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:5742:10)
    at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/controller/message_handler.js:205:30)
    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:106:62) {
  code: 260,
  context: undefined,
  transactionSource: undefined
}

Additional information

No response

@MartinHjelmare
Copy link
Member

@raman325 any idea?

@raman325
Copy link
Collaborator

not sure - one thing to try would be to switch to the Z-Wave JS UI addon and to try controlling the device from the UI panel. If it works, it's an HA problem, if it doesn't, then it's a zwave-js problem

@raman325
Copy link
Collaborator

@AlCalzone is this something you have heard or seen in any reports?

@AlCalzone
Copy link
Contributor

No. I'd start by re-interviewing the device.

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Apr 27, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants