lifeline reports

[juntiedt2]

My z-wave thermostat sends 8 different reports to lifeline. One of it is Battery report. I can configure the report to be send once a day. If I do this through the UI it immedeately sends a "get value response". If I do battery report config through the command factory I don't get a "get value response". Why?

And I don't get a report once a day as well..

If I want to get the lifeline reports do I have to associate the thermostat with Group 1? Could this be my prblem?

Z-Wave Config DB:
https://devices.zwave-js.io/?jumpTo=0x0148:0x0003:0x0001:0.0

[marcus-j-davies]

Hey! @juntiedt2.

The UI does calls to getValue
And the calling entity (in this case the UI) will get the result (via a GET_VALUE_RESPONSE),
but at the same time, this event is passed to any listening device node.

if you open UI Monitor - you can see all the getValue(s) that are being called, it does this to fill the values, so you can see them in the UI.

The response being passed back to the UI.

node-red-contrib-zwave-js/zwave-js/zwave-js.js

Line 1347 in b14fef6

if (send) {

The response also being distributed to any potential device node(s)

node-red-contrib-zwave-js/zwave-js/zwave-js.js

Line 1385 in b14fef6

RED.events.emit('zwjs:node:event:' + Node.id, { payload: PL });

It's probably something I can improve at some point, but currently low priority.

---

The life line group in zwave spec is designed to receive everything (and its should only be the controller that is associated to it)

devices will have at least 1 group that is designated Lifeline - i.e the destination controller for all reports.
a device can have many many groups - all having some different use.

Associations/Groups are different on every device.
ideally, the the Lifeline should receive them all, but again, it depends on what the user manual states.

if a certain report, is not delivered via its lifeline (but does have a group for it)
you may be able to also associate the controller to it.

Associations / Endpoints are always a mess in zwave - Manufacturer A does one thing, Manufacturer B does something completely opposite.

If you fancy some reading
https://zwave-js.github.io/node-zwave-js/#/getting-started/migrating-to-v8?id=reworked-handling-of-endpoints-and-lifeline-associations

[marcus-j-davies]

And I don't get a report once a day as well..

If you are not getting reports, then they are not being transmitted over the lifeline association.
or the device is using a different endpoint for them.

Our configs (per device) can work around these oddities, so if you are not getting any reports, we will need to see an interview log of that device, so the config file for it, can be adjusted.

Edit:
There might actually be a fix for this already.
Let me know what is happening, and I'll know more.

[juntiedt2]

Ok, part one is solved.
Reports are still open.
How can I get the interview log. Do you mean UI Monitor?
next question: are the devices automaticaly associated with the controller (lifeline)?
what is for example the command class for Battery report - 64?

[marcus-j-davies]

Hi @juntiedt2,

How can I get the interview log

Turn on logging in the controller config (don't forget to deploy after) , and then hit 'Interview Node', for the selected node.

are the devices automatically associated with the controller (lifeline)

Yes - this is trivial, devices advertise what is the life line group, and the controller will be assigned to it.
All reports are sent to the life line group (well the device should), you can see all associations in the Manage Associations UI for the selected node - Group 1 should be allocated to at least the controller (1)

what is for example the command class for Battery report - 64?

No, 64 (0x40) is the ID for Thermostat Mode CC
The battery command class ID is 128 (0x80).

Before anything however...

I am trying to find out why you don't get the timed battery report (or any other timed reports?)
can you be certain of that - how did you come to the conclusion, are you capturing everything coming in from that device, and storing it somewhere - and don't see anything over a 24 hour period?

If you really are not getting any reports, then:

1 - The lifeline is not correct on the device, and the device has advertised the wrong one. OR
2 - A recent update to the driver, has implemented fixes for this device.

It's worth noting, this device has known firmware bugs, that may extend to your issue.
see this: #140

if you are not getting any timed reports, we first try an update of the driver.
if still nothing, we need a log of the interview - to see what the device is telling us about its endpoints.

[juntiedt2]

ok, I will log command class 128 for 25 hours and see what happens.
btw, I am logging my wake ups to my mobile phone via Telegram. Don' t need the computer to check :-)

[juntiedt2]

yes, all reports are missing. You will find the list of reports under Association in the Docu.

[AlCalzone]

I do see one unsolicited report:

2021-11-22T11:39:17.791Z DRIVER « [Node 013] [REQ] [BridgeApplicationCommand]
                                  └─[MultilevelSensorCCReport]
                                      type:  Air temperature
                                      scale: Celsius
                                      value: 19.1

There were a couple of commands that could not be sent during the interview, probably interference issues. Maybe the device itself is experiencing the same problems when it tries to report.

[juntiedt2]

I have 3 thermostats. All 3 do not send unsolicited reports once every 24 hours.
Air temp reports depending on temp differences of 0.1 degree are working ok. (VALUE_UPDATED)
As I do not receive the unslicited reports I send a get value to the Battery Stats every 12 hours and at start up. This works ok as well.

[marcus-j-davies]

Hi @juntiedt2

Air temp reports depending on temp differences of 0.1 degree are working ok.

i.e an unsolicited report 😄
I thought you were not getting any?

The fact you get updates when you are not asking for them (aka unsolicited) suggests that life line is working on this device.

therefore, if its simply the battery reports you are net getting, can you confirm you have enabled them todo so?
if you have, maybe pull the battery out and re-insert them.

I have motion sensors, that don't report battery on their intervals after an interview - and I need to pull the battery and re-insert it before the device behaves correctly.

if this still does nothing, this one maybe for the manufacture to answer 🤷‍♂️

[juntiedt2]

mea culpa! mea maxima culpa!
I thought that all reports are unsolicited once a day. Did not read good enough :-(
The thermostas are working. So far so good.
But I was not able to get all listed life line reports yet.
I implemented a few logging routines and I will check the results over the next few days.
Many thanks for your support.
I will keep you updated.

[marcus-j-davies]

No worries,

The unsolicited reports (where we have not asked for the info) I believe you will get are (at least according to the devices manual - they are not always accurate):

• Battery Reports (If enabled)
• Thermo Mode (if changed on the device)
• Set point (if changed on device)
• Multi Level Sensor (Air Temp Changes)
• Multi Level Switch (manual Valve position changes)

All these will be delivered to the lifeline on that device (i.e. the controller - its configured during interview).

if you have enabled battery reports, pull the battery then re-insert it, some of my motions sensors, stop reporting after the lifeline has been configured, only working again when the battery is re-inserted (I think its just a characteristic of certain devices).

also check some of this
they might not be enabled 👍

[juntiedt2]

hi Marcus,
after testing for a while I have the folowing status:
Measured temp report is working ok
Valve Opening report is working ok
Battery report is not working. I now do a "value get" once a day at 1:00 and I am getting data back. They did not change until now. Will see what happens after a month or longer..
I have send an email to EUROTRONIC TECHNOLOGY GMBH. No response.
in the internet I found some posts which had the same problems with this thermostat.
If you are interested I would send you the n-r flow.

[marcus-j-davies]

Hi @juntiedt2

• Measured temp report is working ok
• Valve Opening report is working ok

These will be delivered via the same lifeline as the battery reports (or at least the battery reports should be).

it's very possible the battery reports are broken on this device, and use an endpoint that is not advertised from the device during its interview, or the device simply is not sending battery reports what so ever - Have you done a battery pull and reinsert - I have devices that don't send battery reports unless I pull and re-insert after an interview.

Given your have found other reports of this nature (and we have had Firmware Bugs on this device with other users), I'm lead to believe, it is indeed some buggy firmware that it is running.

further - you can query the battery maually (or in your case at a schedule), and it returns with no problem - so Battery reports should be sent automatically without issue.

My stance on this is, the device is simply not sending scheduled battery reports by its self, have they fixed this with a FW update?, did they get the manual wrong?

🤷‍♂️

Given you can still schedule a report your self, I suppose is a silver lining - but I agree, in that a message to EUROTRONIC, may not hurt.

[marcus-j-davies]

If you are interested I would send you the n-r flow.

Sure, if I see something odd - I'll let you know.

[juntiedt2]

my flow:
eurotronic SPIRIT Z-WAVE PLUS.txt
w

[marcus-j-davies]

Nice,

Quick question.
how are you concluding you don't get battery?
if its becuase you don't see it changing on your dashboard - it may not have had a capacity drop?

Are you capturing/storing everything from the controller side?

The only storing I see in your flow is here out to a file.

But your all Notifications filter - does not include VALUE_UPDATED which I think the battery will fall under.
its good you don't have any VIDs in there (hence it will allow it all through), but if this is used to check if battery reports are coming in, you may need VALUE_UPDATED.

just a thought, but if you have other means - then carry on 😄

[juntiedt2]

Here is my loggin
z-wave logging.txt
g:
12 13 and 14 are my thermostats

[juntiedt2]

if it is a unsolicited report once a day a capacity drop should not be relevant for the report

[marcus-j-davies]

Yup,

it was more if you were monitoring the dashboard for changes, but since you log everything, it should show up.
still, if its not there - I guess still waiting to see what EUROTRONIC says.

I also found forum discussions mentioning this device and its lack of battery reports.