Trane XL624 Thermostat Missing Lifeline Association

[1activegeek]

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

What causes the bug? Inclusion of Trane XL624 thermostat into my ZWave network.

What do you observe? The thermostat does not register it's lifeline association properly, and thus will not send updates to the controller.

What did you expect to happen? Updates from the controller should always go through, not just when the controller reaches out to the node.

Steps to reproduce the behavior:

1. Include Trane XL624 thermostat into the ZWave network

I reported this previously here: #4132
Since then, I reported this here: home-assistant/core#82228

A kind soul found my issue with the missing lifeline association. They suggested I come here to suggest that the device config can be fixed in the core libraries. Specifically this post of his, calls out the fix that was needed: home-assistant/core#82228 (comment). I simply chose to manually add the lifeline config in the ZWaveJS UI console for now. But a long term fix would be best.

Device information

Manufacturer: Trane
Model name: XL624
Node ID in your network: 10 and 38

How are you using node-zwave-js?

• zwave-js-ui (formerly zwavejs2mqtt) Docker image (latest)
• zwave-js-ui (formerly zwavejs2mqtt) Docker image (dev)
• zwave-js-ui (formerly 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)
• Manually built from GitHub (please specify branch)
• Other (please describe)

Which branches or versions?

version: 1.3.0
node-zwave-js branch:
zwave-js-ui branch:

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?

It had worked in the previous legacy ZWave integration. I noticed the issue once migrating over to the ZWaveJS integration.

Attach Driver Logfile

Not applicable as my instance has now been fixed.

[zwave-js-bot]

👋 Hey @1activegeek!

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]

The re-interview log would still be needed to know what needs to be done to fix this. Even if it works now.

[1activegeek]

Ok, so to generate that log - would I be following these directions linked above and then doing a re-interview action to make sure it catches this, then uploading that log here?

[AlCalzone]

Correct. Please make sure to put it on loglevel "debug"

[zwave-js-assistant]

This issue has not seen any recent activity and was marked as "stale 💤".
Closing for housekeeping purposes... 🧹

Feel free to reopen if the issue persists.

[danhi]

I am having this issue as well, I've attached the log I think you need. Let me know if you need any additional info>

a0d7b954_zwavejs2mqtt_2024-11-20T21-05-37.074Z.log

[danhi]

Not sure if the log above had all the debug values set. Here it is again.
a0d7b954_zwavejs2mqtt_2024-11-22T17-33-53.139Z.log

[danhi]

OK, I think I have the right files now. Let me know if this isn't what you are looking for.
z-ui_2024-11-22.log
zwavejs_2024-11-22.log

[AlCalzone]

Looks simple enough: Z-Wave JS does not know which one is the lifeline:

2024-11-22T17:20:53.348Z CNTRLR   [Node 002] No information about Lifeline associations, cannot assign ourselves

@danhi do you have a device manual?

[AlCalzone]

Hmm, according to this comment, group 1 should be the lifeline and I can see that the controller is already part of that group.

Maybe node 6 coming before node 1 is the problem?

2024-11-22T17:20:53.191Z CNTRLR « [Node 002] received information for association group #1:
                                  maximum # of nodes: 5
                                  currently assigned nodes: 6, 1

You could try removing that one and see if things start working.

[AlCalzone]

The original issue should be fixed by #7547

[1activegeek]

Just so I validate my understanding - my changes I made to solve this issue, should get overwritten I would assume with this update? Or will it not affect mine since they're already configured/learned?
The good thing is I think anyone else who happens to have these should not run into the issue I did originally anymore correct?

[AlCalzone]

All correct! You can delete your custom configuration file once the update is released and you have updated.