I have a Z-Wave window sensor ( Ecolink Z-Wave Plus Door Window Contact Sensor (DWZWAVE2.5-ECO)) that is only allowing Ping. I’ve tried going to configure, but there is nothing there. How can I configure this so I get the open/closed events?
Thanks.
Re interview the device.
Nothing happens when I click the re-interview start button. I made sure the device was on, and the last seen timestamp is updated in the log. Is there a way to manually configure this in configuration.yaml?
If it is a battery powered device, you need to wake it up for a reinterview. It will not react to reinterview, while it is sleeping.
Wake up is done by pressing a button, manual will tell you, which one.
1 Like
I did that, and could see in the HA log that it was connected. Again, is there a way to manually configure a device?
What does “connected” mean? According to the device manual I found online, the device will wake up when removing the cover, not by pressing a button. The interview must also be started before you wake it up, otherwise Z-Wave JS will put it to sleep if there’s nothing to do.
That doesn’t mean the interview was started or completed, the timestamp could be from any kind of communication. On the Device page, under Device Info → Z-Wave info there is a “Ready” field, that must be “yes”. If not “yes”, the interview is not complete and the device will not be usable in HA.
There’s no way to “manually configure” a Z-Wave device in configuration.yaml.
1 Like
Yeah! I had to mess around a bit to get HA to recognize it as active, but once I did that, and did the re-interview, it now shows up correctly with open/close statuses. Thanks so much for this.
Since you seem to know more than anyone else I’ve dealt with on the forum, I wonder if you could help me with my last remaining issue? I have a Trane XL624 thermostat (Z-Wave) that sort of works with HA (works fine with Homeseer). The issue is that when getting the setpoint and current temperature from it, the information is stale (this is true on the thermostat card as well). I haven’t figured out what causes the information to finally update. Without that, I can’t control it the way that I want (increasing/decreasing the current set point by a degree). Do you have any thoughts as to why this could be. I don’t think it’s a config issue, since it does work correctly in Homeseer. If there was a way I could force a poll of the device, that would work for me.
Anyway, thanks for fixing one of my last two problems!
1 Like
If the device does not support Assocations with a Lifeline group, then it won’t send status updates. Older pre-Z-Wave-Plus devices are an example of this. The Trane XL624 seems to be quite old so it might fit in this category. If it’s working in Homeseer, then maybe it is configured to poll, or HS does it automatically. Might be worth it to confirm that.
In you need to poll in HA you write an automation to do so: https://www.home-assistant.io/integrations/zwave_js/#my-device-doesnt-automatically-update-its-status-in-ha-if-i-control-it-manually
When polling a climate entity, I would enable refresh_all_values in the refresh action to also refresh all of the watched values (setpoints, operating state, etc.), as the primary value will be the thermostat mode.
3 Likes
This Github issue talks about setting the lifeline group on a Trane XL624. Sounds a lot like your problem, so it’s a simple fix in that case.
1 Like
And following the links you get to Trane XL624 Thermostat Missing Lifeline Association · Issue #5218 · zwave-js/node-zwave-js · GitHub. The issue became stale as the reporter never followed up. Fixing the associations is a much better solution then implementing polling, so I would follow up there.
How can I change the bug from closed to open? I’ve tried adding a comment, but that didn’t seem to do it. This appears to be exactly my problem, so getting it fixed would be my last hurdle.
I’m trying to do this manually by following the github issue referenced by mterry63, but it looks like the answer is to modify the source for zwave-js and rebuild it. Is this correct? Is there any other way I can fix the associations for this device?
The maintainer will re-open it. You also provided the wrong log file, the instructions are posted in the issue.
No, you don’t rebuild anything. You just create a custom device config file and drop it into ZUI’s Store “config” directory. Instructions are at https://zwave-js.github.io/zwave-js-ui/#/device-support/custom-device-files. Unfortunately the OP of the GH issues did not contribute anything, so you will need to create the file yourself. You can modify the upstream one and add the groups to it. Search the repo for examples, or provide the requested driver debug log to the node-zwave-js and wait for the maintainer to sort it out.
1 Like
The first thing I would check is to make sure the associations exist. He stated his stat started reporting once he added the association to the controller in Group 1. That is a simple 2-minute exercise in the UI.
1 Like
When you say I downloaded the wrong log file, I went to system->Logs and selected the Z-Wave JS UI log. I tried finding it via samba and couldn’t. Is the one from system logs not correct?
I added a reply on the bug report, but it still shows as closed. Does this just take some time to happen, or will I need to reach out to someone?
Sounds like adding the association is the way to go, can you point me in the right direction for adding that in the UI?
I really appreciate all the help.
No, for driver problems you generally need to provide driver logs. The ones you added are application (ZUI) logs. See https://zwave-js.github.io/zwave-js-ui/#/troubleshooting/generating-logs?id=driver-logs.
Got it, didn’t look far enough down on the page.
