-
-
Notifications
You must be signed in to change notification settings - Fork 623
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
Go-Control (Linear) NGD00Z-4 Missing attributes #5479
Comments
Unfortunately, I don't see a device interview in the log you posted. Please re-interview the device and post a log of that. |
Updated OP and added todays device interview. In fact there are at least 2 interviews as it seemed sluggish so i pinged it during. So after complete i reinterviewed to ensure it was clean. |
@roblandry you may have to try that again. I'm not sure if it is caused by node 5, but all of the interview attempts are during a phase where the stick refuses to send (probably due to excessive noise).
appears in the log when that happens. Might also be the 7.19 firmware. During one of the interview attempts, I see this flood of incoming reports from the node (which can cause the stick to refuse sending for a while):
followed by the stick restarting several times roughly every 20 seconds:
|
Ok, new logfile. I now see what you mean with all the resets. I moved the dongle to a usb 2.0 hub on a long extension and seems to be much better (less noise), yet still missing the attributes. |
Ok the issue is that the device doesn't report support for the Battery CC. Neither insecurely:
nor securely:
Looking at the OZW file there are probably a few more CCs missing, but I don't trust that file (why does it contain thermostat related CCs?). |
Ok @roblandry please test this file as described here. |
Ok, the new info is populated but providing unknown values. In further reading today, i am not sure it has ever actually provided an actual correct value. I only recall actually seeing 100%, despite the battery being in for years. I think it may be safe to close this issue and remove the PR. |
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
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.
Describe the bug
Seems to be missing battery as reported in #4229.
I have reinterviewed the node multiple times.
Looking back at OG zwave configuration files, i see attributes that are not populated in zwave-js. The specific value for the battery being commandClass 128.
Image from zwave-js
Image from home assistant
Config from zwave-js
Entire config from old zwave config file
Device information
Manufacturer: Nortek Security & Control LLC
Model name: NGD00Z-4
Node ID in your network: 5
How are you using
node-zwave-js
?zwave-js-ui
(formerlyzwavejs2mqtt
) Docker image (latest)zwave-js-ui
(formerlyzwavejs2mqtt
) Docker image (dev)zwave-js-ui
(formerlyzwavejs2mqtt
) Docker manually built (please specify branches)ioBroker.zwave2
adapter (please specify version)HomeAssistant zwave_js
integration (please specify version)pkg
node-red-contrib-zwave-js
(please specify version, double click node to find out)Which branches or versions?
version:
node-zwave-js
branch: 10.10.0zwave-js-ui
branch: 8.8.5Using manually built version to update to latest.
Did you change anything?
yes (please describe)
If yes, what did you change?
No response
Did this work before?
Yes (please describe)
If yes, where did it work?
Open zwave i believe, its been a while.
There are many comments about it not working in a long time.
As example:
https://community.home-assistant.io/t/issues-with-ngd00z-4-garage-door-opener/283517/23
Attach Driver Logfile
S0_LEGACY Key emailed.
2/21/23 Update
2/23/23 Update:
The text was updated successfully, but these errors were encountered: