-
-
Notifications
You must be signed in to change notification settings - Fork 597
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
IBT4ZWAVE used to work with Gen5 and not working with ZooZ stick #7130
Comments
This is not an issue with the stick - it is "just" a radio for the most part. Issues with that device have been reported before, but AFAIK there has never been a solution or an answer what's going on. After trying to control the device, it sends back an Application Status CC, with the Application Rejected Request command. This CC is not understood by Z-Wave JS, but typically means "can't do that". In this case the device actively responded that it won't execute the request. Maybe the motor is jammed? Maybe it needs to be calibrated? |
Hi @AlCalzone What I don't understand is why he used to work with the same installation and Gen5 stick. If I understood you the good news is that if he used to work, he should still be working. I did a manual calibration, and try to push for a level change to 40 Here is the log: Should I look to make a level calibration directly from the Zwave/stick? Thanks PS: https://www.niceforyou.com/sites/default/files/upload/manuals/idv01mm_en.pdf |
Can you share a log of you controlling the device with the Gen5 stick then? |
Sorry I don't have it anymore. I could find a backup of the Gen5 stick if that works (before I did upgrade it and brick it). Then I was so piece off that I bought a new stick as after the upgrade I couldn't get it working again (and I don't have a windows machine that is not virtualized to make proper stick upgrades). What if I re-interview the device in silly mode with the ZooZ, could the interview process help understanding is the items were correctly 'created'? |
I see, that sounds like a hurdle. You could also contact the manufacturer and ask why the device responds with a Application Status CC, with the Application Rejected Request command. Re-interviewing doesn't make sense in this case. |
Do we know if the module is supposed to work? What I mean is the issue specific to me (could I have break/brick the device?) or all folks are having issues with this device? It seems that it's working for some people, so I will search if this is linked to a device fw issue and yes will try to open a case with them then? it's supposed to be supported: |
It's working for some people. I can't tell you why yours isn't working, other than it refuses to react to controlling commands. Your best bet is to ask the manufacturer, they should be able to tell you. |
Hello All,
The inclusion was done OK and the device is correctly added (and ping works and the interview too). But action like open or close don't work.
Is the device supported with the ZooZ stick, is it a pb of a firmware?
I see messages like:
Here is the log:
Zwave.log
Zwave-silly.log
Thanks
XabiX
Version:
zwave-js-ui: 9.17.0zwave-js: 13.1.0home id: 3886169917home hex: 0xe7a23f3d
The text was updated successfully, but these errors were encountered: