SES302 Temperature Sensors Issue [bug]

[jasonwragg]

node_11.txt
Before submitting a bug please read: https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/bug_report

Version

Build/Run method

• [ X] Docker
• PKG
• Manually built (git clone - npm install - npm run build )

zwavejs2mqtt version: 1.2.2
zwavejs version: 6.4.0

On Secure Meters (UK) Temperature sensor the external tank sensors all report the same value as the main sensor

A clear and concise description of what the bug is.

Added the device

Expected behavior

Each end point should receive its own temperature

Additional context

Add any other context about the problem here.

[robertsLando]

@jasonwragg logs please

[jasonwragg]

zwavejs_1.log
I found this which might help.
OpenZWave/open-zwave#1249

[robertsLando]

Could you better explain what you mean here: Temperature sensor the external tank sensors all report the same value as the main sensor ?

[jasonwragg]

Sure, when the main unit reports it temperature it is assigned to all the endpoint rather than just the main unit.

15:42:13.460 DRIVER « [Node 007] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Air temperature
scale: Celsius
value: 19.75
15:42:13.472 CNTRLR [Node 007] Mapping unsolicited report from root device to first supporting end
point zwave-js/zwave-js-ui#1
15:42:13.479 CNTRLR [Node 007] Mapping unsolicited report from root device to first supporting end
point zwave-js/zwave-js-ui#2
15:42:13.484 CNTRLR [Node 007] Mapping unsolicited report from root device to first supporting end
point zwave-js/zwave-js-ui#3
15:42:13.489 CNTRLR [Node 007] Mapping unsolicited report from root device to first supporting end
point zwave-js/zwave-js-ui#4
15:42:13.495 CNTRLR [Node 007] Mapping unsolicited report from root device to first supporting end
point zwave-js/zwave-js-ui#5

The first time the unit connects and sends the values for all the value to the correct endpoint but after that only the main unit is being updated.

[jasonwragg]

This is from the manual, not sure if it help.

Association
Group Info
(V1)
Group Name Get
Group Name Report
Group Info get
Group Info Report
Group Command List Get
Group Command List Report
Only one association group is supported on each end
point and its name is “Lifeline”.
20
Profile MSB -
ASSOCIATION_GROUP_INFO_REPORT_PROFILE_G
ENERAL
Profile LSB -
ASSOCIATION_GROUP_INFO_REPORT_PROFILE_G
ENERAL_NA
Supported Command class and command :

1. COMMAND_CLASS_SENSOR_MULTILEVEL,
   SENSOR_MULTILEVEL_REPORT_V6
2. COMMAND_CLASS_BATTERY,
   BATTERY_REPORT

[robertsLando]

@AlCalzone I think this is something on your side

[AlCalzone]

Okay, the fact that the values are mapped to all endpoints is a bug. I've already fixed it in master.

To figure out why only one report for the root endpoint comes in, please re-interview the device, wake it up and post a log of that. The current log is pretty empty because it only contains the update after restart from cache.

[jasonwragg]

Okay, the fact that the values are mapped to all endpoints is a bug. I've already fixed it in master.

To figure out why only one report for the root endpoint comes in, please re-interview the device, wake it up and post a log of that. The current log is pretty empty because it only contains the update after restart from cache.

zwavejs_1.log

[AlCalzone]

You didn't have to exclude it, just repeat the interview :)

[AlCalzone]

Okay what I can see from the log:
The device supports 5 endpoints, but does not support Multi Channel Association. In this case, zwave-js sets up a node association from the root device to the controller and calls it a day.

It seems however that this device expects each single endpoint to be associated with a target. At least I think that, because the manual is not exactly very specific:

Product supports one group for each end point that have a maximum of 2 nodes.
Only one association group is supported on each end point and its name is “Lifeline”

This is currently not possible, as we need to add support to configure associations an an endpoint.
==> #1861