Closed AlfaBravoX closed 2 years ago
Also Z-wave+ is reported as NO, however the controller is PLUS capable and Wake interval remains on 1800 instead of 300s, so it looks it is not negotiated and devices dont wake up. But this is on all of them so it must be z-wave js related and not devices itself
I'll look at the logs later, thanks!
however the controller is PLUS capable
That has nothing to do with the devices. AFAIK the LC-13 are not Z-Wave+ certified. We're not showing most of that information for the controller because it cannot be queried.
Adding more logs
I'll look at the logs later, thanks!
however the controller is PLUS capable
That has nothing to do with the devices. AFAIK the LC-13 are not Z-Wave+ certified. We're not showing most of that information for the controller because it cannot be queried.
Thanks for clarification. And additional logs attached. I did set factory reset to all devices and paired them again, but problem is the same. After succesfull pairing they show E5 after while again and wake period remains on 1800
I am seeing the same problem with my Devolo TRVs (which I think are Danfoss TRVs with different firmware). These have worked on ZWaveJS for several months up until early this week maybe around 28th/29th Nov.
I am seeing the same problem with my Devolo TRVs (which I think are Danfoss TRVs with different firmware). These have worked on ZWaveJS for several months up until early this week maybe around 28th/29th Nov.
Yes, I did migration a week about and it was working few days, so something had to happen with the code on 28th/29th Nov.
I'm suspecting https://github.com/zwave-js/node-zwave-js/pull/3691 has an unintended interaction. I'm going to revert it later for the 8.x branch.
However I'd like to understand what exactly breaks the communication so I can fix it properly. @jordanrkirby if you could also contribute some driver logs of the thermostats waking up, it might help.
Of course. Debug logs attached. TRVs are device IDs 7, 8, 10, 11, 12, 15, 16, 17, 18
Thanks
Hello,
i have quite the same issue with TRV Danfoss Living Connect (Popp & Devolo brand) displaying E5 error a few minutes after zwave communication.
i have reset my controller without success. Same issue appears.
I use zwavejs2mqtt as Hassio add-on. I have roll back from v0.31.0 to v0.29.0 and everything is working great again.
No more E5 error and I can control my TRV now.
@jordanrkirby The logs look okay - there are two instances where the queries couldn't be sent, but for the remaining wakeups, the TRVs get queried as expected.
I guess I need a log which captures the moment the error appears. @Minims maybe?
I reverted even to v0.30.0 and it started to work again. no E5 anymore
Any chance you could provide a log which captures the moment the error appears?
Any chance you could provide a log which captures the moment the error appears?
i attached 2 logs. the one with zip format, should have errors captured
Oh right 👍🏻
Edit: I've remembered I have one of these lying around in a box. Managed to get it included after 20 attempts and can reproduce.
Trying to get logs this morning.
I have restart v0.31.0 and on first zwave connection with a device, it is stuck in awake
instead of falling back to Asleep.
So I think that in few minutes my TRV will display E5 error. Can it be bad close connection to the device ?
Trying to get logs this morning. I have restart v0.31.0 and on first zwave connection with a device, it is stuck in
awake
instead of falling back to Asleep.So I think that in few minutes my TRV will display E5 error. Can it be bad close connection to the device ?
Please just read this thread carefully, then you will find response to your question. Problem is not at your side.
it is stuck in
awake
instead of falling back to Asleep.
That sounds like the "go sleep" message doesn't get sent (like I'm seeing above). The device still goes to sleep but doesn't get the expected message and starts whining about it.
Was this also fixed with the reverts in 8.8.3 (for those who can't install a beta)?
It should, since the bug was caused by the send queue changes
Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
YES, BUT a Home Assistant developer has told me to come here
Is your problem within ZWaveJS2MQTT?
YES, BUT a ZWaveJS2MQTT developer has told me to come here
Checklist
[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog and my problem was not mentioned there.
Describe the bug
What causes the bug? This happened after migration to z-wave JS, so just pair nodes and let them be for a while (30 mins)
What do you observe? E5 error at node show according to docs error in comunication - TRV is out of range from Smart home HUB. Please more HUB closer or add repeater into a system. All TRVs are 2meters distance from controller.
What did you expect to happen? TRV should not show E5 code and remain connected
Steps to reproduce the behavior:
Device information
Manufacturer: Danfoss Model name: Living Connect Z Thermostat Node ID in your network: 5,7,9
How are you using
node-zwave-js
?zwavejs2mqtt
Docker image (latest)zwavejs2mqtt
Docker image (dev)zwavejs2mqtt
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: 6.0.2zwavejs2mqtt
branch: 8.8.2Driver Version: 8.8.2 Server Version: 1.12.0
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Yes (please describe)
If yes, where did it work?
Yes deprecated HA z-wave integration worked well
Attach Driver Logfile