search

zwave-js / node-zwave-js

Z-Wave driver written entirely in JavaScript/TypeScript
https://zwave-js.github.io/node-zwave-js/
MIT License
750 stars 599 forks source link

Ring 4AK1SZ #6164

Closed candrea77 closed 1 year ago

candrea77 commented 1 year ago

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?

NO, my problem is NOT within Home Assistant or the ZWave JS integration

Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?

NO, my problem is NOT within Z-Wave JS UI

Checklist

Describe the bug

What causes the bug? I can't get any event in zwave / Home assistant I've noticed that I have no assciation .... any GROUPS is missing

What do you observe? In the zwavejs ui , under GROUPS there is "no data avilable". If I try to add an association, nothing happen, still "No data available" message.

What did you expect to happen? Add an association with NodeID_1

Device is configured with "S2 Access Control"

I've tryed the "Re-interview Node" function but still no success

Device information

Manufacturer: Ring Model name: 4AK1SZ Node ID in your network:

How are you using node-zwave-js?

Which branches or versions?

version: zwave-js-ui: 8.22.3.8607bd8 zwave-js: 11.9.2

Did you change anything?

no

If yes, what did you change?

No response

Did this work before?

Don't know, this is a new device

If yes, where did it work?

No response

Attach Driver Logfile

2023-08-14 23:15:55.722 DEBUG SOCKET: Event ZWAVE_API emitted to j7fvQDdDBm9594VfAAAq 2023-08-14 23:15:55.723 INFO Z-WAVE: Calling api addAssociations with args: [ { nodeId: 157, endpoint: 0 }, 1, [ { nodeId: 1, endpoint: 0 }, length: 1 ],

] 2023-08-14 23:15:55.724 INFO Z-WAVE: [Node 157] Adding Node 1 to Group 1 of Node 157 2023-08-14 23:15:59.284 INFO Z-WAVE: Success zwave api call addAssociations true 2023-08-14 23:15:59.313 DEBUG SOCKET: Event ZWAVE_API emitted to j7fvQDdDBm9594VfAAAq

zwave-js-bot commented 1 year ago

👋 Hey @candrea77!

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 is required to diagnose most issues.

Please consider uploading a logfile that captures your problem.

AlCalzone commented 1 year ago

What the bot said

candrea77 commented 1 year ago

Yep,.I'll send the log as soon as i came back to home.

Do you need log when I'll try to made the group association ? Or something different ?

Mail inviata da dispositivo Mobile

Il Mar 15 Ago 2023, 11:06 AlCalzone @.***> ha scritto:

What the bot said

— Reply to this email directly, view it on GitHub https://github.com/zwave-js/node-zwave-js/issues/6164#issuecomment-1678628851, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGGSROI2ERGLS6IXRJHCH43XVM32DANCNFSM6AAAAAA3QHVN2M . You are receiving this because you were mentioned.Message ID: @.***>

AlCalzone commented 1 year ago

Ideally include a re-interview and the failed attempt at creating association in the log.

candrea77 commented 1 year ago

Hi there, I've also take time to git pull the latest release (zwavejs/zwavejs2mqtt:master)

Now I'm on : zwave-js-ui: 8.22.3.62ecc4b zwave-js: 11.11.0

Below you can find the log (start zwavejs + Re-interview Node)

Let me know in case I've to do something else.

zwavejs_2023-08-16.zip

candrea77 commented 1 year ago

And sorry .... I forgot the reassociation. Here you are the related log zwavejs_2023-08-16.zip

AlCalzone commented 1 year ago

It looks like you are having connectivity issues. Lots of timeouts during the interview. Sending commands takes a long time and there's a ton of permanent traffic from sensors.

I have a few links I suggest working through, then try again:

  1. https://zwave-js.github.io/node-zwave-js/#/troubleshooting/connectivity-issues?id=general-troubleshooting
  2. https://zwave-js.github.io/node-zwave-js/#/troubleshooting/network-health?id=optimizing-the-reporting-configuration
  3. https://zwave-js.github.io/node-zwave-js/#/troubleshooting/network-health?id=testing-the-connection-strength

FWIW, associations work fine if there is no connectivity problem: grafik

candrea77 commented 1 year ago

Hi there, I moved the Ring KeyPad very close to the controller and restart interview just to exclude any possibile zwave network problem (same room , 1 meter distance)

After reinterview finished, no group association is present.

I've tried again manual group association, but nothing changed. Here it is the new logs ....

zwavejs_2023-08-17.log

BTW : Another strange thing ..... I've got no battery indicator ('null%' , in your screenshoot , it seems ok on your device) image

Wich version of Firwmware is yours (mine 1.18.0 sdk 7.12.4) ?

May I've to try to delete the device and reiinclude it in order to solve my problems ?

AlCalzone commented 1 year ago 
2023-08-17T13:22:16.274Z CNTRLR » [Node 157] querying battery status...
...
2023-08-17T13:22:17.344Z CNTRLR   [Node 157] Timed out while waiting for a response from the node (ZW0201)

For some reason your keypad is not responding to that query. It doesn't seem to be a communication issue, as it does confirm that it gets the commands.

Mine has the same firmware as yours. Have you tried putting it on the USB cable for the interview yet? Maybe the load of queries is a bit too much for it on battery power.

candrea77 commented 1 year ago

Have you tried putting it on the USB cable for the interview yet? Maybe the load of queries is a bit too much for it on battery power.

Thanks for quick reply. Unfortunately It's already on USB power.

AlCalzone commented 1 year ago

Do you have a different Z-Wave stick you could use for a test? Otherwise I'm out of ideas. I don't have any issues, neither on USB or battery power.

candrea77 commented 1 year ago

Unfortunately no.

Just a quick question .... if I get a different stick can i backup and restore the whole zwave db (all devices) from old to new one ? I'm planning to switch to a 700chipset, and that's can be a valid reason to speed-up the change.

Meanwhile, I'll try exclude and re-include and let you know.

AlCalzone commented 1 year ago

With your stick and firmware version, yes. Just do an NVM backup in Z-Wave JS UI, and restore that on the new stick.

If you're located in EU, you should know though that the Z-Stick 7 has severe RF range issues for an unknown reason. I've had the best performance with 500 series controllers and those 700 series controllers that you put on the GPIO of a Raspberry Pi (or similar).

candrea77 commented 1 year ago

With your stick and firmware version, yes. Just do an NVM backup in Z-Wave JS UI, and restore that on the new stick.

Do you mean replacing old stick with a new one same model ? Or do I change brand/model and do backup and restore ?

If you're located in EU, you should know though that the Z-Stick 7 has severe RF range issues for an unknown reason.

Never hear that ... good to know.

I've had the best performance with 500 series controllers and those 700 series controllers that you put on the GPIO of a

Raspberry Pi (or similar). I'm running docker image on a QNAP , and planning to use an Aeotec ZStick7. So I think that is that a model that I need to be worried about.

Meanwhile, exclude and re-include does the trick ..... don't know why. image

Here it is the log, in case can be helpfull zwavejs_2023-08-17.zip

AlCalzone commented 1 year ago

Do you mean replacing old stick with a new one same model ? Or do I change brand/model and do backup and restore ?

Z-Wave JS supports migrating the NVM between entirely different sticks. The only requirement is that the SDK of both the target and the source is new enough (>= 6.61). And 800 series is not supported yet.

Meanwhile, exclude and re-include does the trick ..... don't know why.

And now the timeouts are gone... Maybe the keypad was in a weird state.

I'm running docker image on a QNAP , and planning to use an Aeotec ZStick7. So I think that is that a model that I need to be worried about.

Honestly, if there's nothing broken (keypad works now it seems), I'd stick with the Gen5 for now. I know a couple of users who went back to this one after having weeks of problems with newer sticks.