zwave-js / node-zwave-js

Z-Wave driver written entirely in JavaScript/TypeScript
https://zwave-js.github.io/node-zwave-js/
MIT License
749 stars 600 forks source link

When endpoints have a Z-Wave+ lifeline with 0 max. nodes, setup a multi channel association on the root #3099

Closed je-mei closed 3 years ago

je-mei commented 3 years ago

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?

NO, my problem is NOT within ZWaveJS2MQTT

Checklist

Describe the bug

What causes the bug? ./.

What do you observe? ./.

What did you expect to happen? Power-Entity available for FGR223 Fibaro Roller Shutter

Steps to reproduce the behavior:

  1. See result from home assistant / core issue: https://github.com/home-assistant/core/issues/53507

Device information

Add-on with the issue: Z-Wave JS Add-on release with the issue: 0.1.32 Last working add-on release (if known): included in home assistant the first first Operating environment (OS/Supervised): Version core-2021.7.4, supervisor-2021.06.8, Home Assistant OS 6.1

-Roller shutter 2 working correctly, power entity existing -another user uses the legacy zwave implementation, where the power entity also occurs

see https://github.com/home-assistant/core/issues/53507

How are you using node-zwave-js?

Which branches or versions?

Add-on with the issue: Z-Wave JS Add-on release with the issue: 0.1.32 Last working add-on release (if known): included in home assistant the first first Operating environment (OS/Supervised): Version core-2021.7.4, supervisor-2021.06.8, Home Assistant OS 6.1

Did you change anything?

no

If yes, what did you change?

Did this work before?

Yes (please describe)

If yes, where did it work?

Kind regards Jens

Attach Driver Logfile

zwave_config_legacy_integration_by_another_user_where_everything_works_fine_FGRM223_Roller_Shutter_Controller_3.txt zwave_2021-07-26_interview_fgr223.log

kpine commented 3 years ago

See my latest comment in the HA issue. Given the newly provided zwcfg*.xml file, I don't think there's any issue here.

AlCalzone commented 3 years ago

I agree, the device is using the Meter CC to report its consumption and I see it being queried successfully in the log.

je-mei commented 3 years ago

Hi AlCalzone, hi kpine,

first of all thanks for your support! By the way I would like to mention, that some additional points are not clear for me:

  1. Why is there a possibility for configurating "power reports", when they are not available in shutter 3 at all?

image

2. Unfortunately, values for "Roller Shutter 3: Electric Consumed [W]" will not be send, but the kwH do. I opened and closed my shutters, but thats not represented in the graphic/log:

image

image

Kind regards Jens

je-mei commented 3 years ago

update: exclusion of shutter 3 factory reset of shutter 3 inclusion of shutter 3 same phenomenon: no reporting of electric consumed W

image

although mulitple open and close of the shutter, no reporting: image

je-mei commented 3 years ago

image

kpine commented 3 years ago

3600 seconds is one hour for the periodic report. Have you tried reducing it to something like 1 minute to see if anything is reported?

AlCalzone commented 3 years ago
1. Why is there a possibility for configurating "power reports", when they are not available in shutter 3 at all?

I can't speak for how devices behave. Looking at the configuration you posted, the changes should come every 5W or 1%, depending on what is higher: grafik

If they don't appear in the UI, looking at the driver logs could give you a hint whether the reports are received at all. If they aren't, either the messages don't reach the controller (in which case a heal could help) or they never get sent (which you can only figure out with a Zniffer next to the shutters).

je-mei commented 3 years ago

change of energy repots didn't have any effect on reporting therefore I checked system behavior when changing the values via log error message based on "silly" log find attached

image

AlCalzone commented 3 years ago

Hm, looks like that log doesn't actually use the silly loglevel - there should be more. @kpine do you know more about that?

The mention of "Application Status" could mean that the device didn't actually accept the command

kpine commented 3 years ago

Hm, looks like that log doesn't actually use the silly loglevel - there should be more. @kpine do you know more about that?

No, but it sounds like you got some attention in Discord. The funny thing is, we gathered the interview logs using the same procedure. That seemed to be successful. 🤷🏻‍♂️

je-mei commented 3 years ago

its really strange :-( :-(

I was using shutter 2+3 in fhem first. next to the known bug "send no update for position" it worked really fine. I used the power/electric reports to trigger a zwave-update for the whole sensor. similar like the blueprint. and it worked.

so i directly switched from fhem (excluding) to ha (reset, incluing) within 1 day, so hardware couldn't be the root cause. :-(

just made another update of the configuration for you: change report "on change" and "periodic". Here is the result:

image

Network heal already done a few days ago and many times ... . But finally it is sending no update:

image

Although open and close a minimum of twice a day.

By the way: Shutter 2 is also sending no energy, but power ;-)

image

shutter 2 sends only power, but no energy watt: image (screenshot during close progress)

image

image

If I could do anything to help give me some information what to do.

Kind regards Jens

je-mei commented 3 years ago

did a configuration change for shutter 2

image

zwave_js-log (2).txt

je-mei commented 3 years ago

thats all shutter 2: image

je-mei commented 3 years ago

shutter 2: image

AlCalzone commented 3 years ago

change report "on change" and "periodic". Here is the result:

Looks like the device doesn't like you changing the parameters. I think that is because you're setting an unsupported value for the periodic report. Only 0 and 30-32400 are allowed. grafik

I can confirm that my Roller Shutter 2 reports power via a Multilevel Sensor (Power) and Electric Consumed [kWh] with the configured frequency, but the Electric Consumed [W] never changes in the time it is moving. Maybe FHEM was polling? zwave-js doesn't do that automatically.

next to the known bug "send no update for position" it worked really fine. I used the power/electric reports to trigger a zwave-update for the whole sensor

You do know that this isn't necessary in zwave-js, right? It uses the Supervision CC to get informed about the position changes of the Roller Shutter 3. Can you make a log where you move the Shutter 3?

je-mei commented 3 years ago
  1. log during change of config for shutter 3
    1. log during many open and closes incusive a screenshot of the graphic / cover

during_change_parameter_shutter3-log.txt cover_after_open_closes_many_times graphic_after_open_closes_many_times after_many_open_and_closes-log.txt

je-mei commented 3 years ago

i will send you another log, where shutter is triggered by local shutter switch to open and close tomorrow if needed

je-mei commented 3 years ago

arghh :-/ not many information stored in the log, thats different to the information displayed.

i will do it again tomorrow and copy data from screen into text file

kpine commented 3 years ago

@je-mei Are you using the log download button in HA, or copying and pasting from the window? The download button does not work properly, so you should copy and paste.

je-mei commented 3 years ago

@kpine yes, forgotten :-(. used copy and paste from the window instead.

please find attached "silly" logs and corresponding screenshots (same number link 01_* means same progress)

00_change-device-configuration.txt 00_change_device_configuratoin 01_position_change_via_ha- 01_postition_change.txt 02_no_change_in_electric_consumed 02_no_change_in_electric_consumed_developertools 02_no_change_in_electric_consumed2 02_no_change_in_electric_consumed3 03_one_time_down_one_time_up_by_local_swith_shutter3.txt 03_one_time_down_one_time_up_by_local_swith_shutter3 03_one_time_down_one_time_up_by_local_swith_shutter3_developertools

kpine commented 3 years ago

In your original HA dump file, the meter value is associated with endpoint one. In your zwave-js debug logs, endpoint 0 is reporting the meter values. This would mean HA wouldn't see the updates.

              {
                "endpoint": 1,
                "commandClass": 50,
                "commandClassName": "Meter",
                "property": "value",
                "propertyKey": 66049,
                "propertyName": "value",
                "propertyKeyName": "Electric_W_Consumed",
                "ccVersion": 3,
                "metadata": {
                  "type": "number",
                  "readable": true,
                  "writeable": false,
                  "label": "Electric Consumed [W]",
                  "ccSpecific": {
                    "meterType": 1,
                    "rateType": 1,
                    "scale": 2
                  },
                  "unit": "W"
                },
                "value": 0.6
              },
2021-07-30T15:45:13.338Z SERIAL « 0x0112000400200a32022132058a00000000b600d9                          (20 bytes)
2021-07-30T15:45:13.341Z CNTRLR   [Node 032] [~] [Meter] value[66049]: 0.6 => 141.8                 [Endpoint 0]
2021-07-30T15:45:13.343Z SERIAL » [ACK]                                                                   (0x06)
2021-07-30T15:45:13.345Z DRIVER « [Node 032] [REQ] [ApplicationCommand]
                                  └─[MeterCCReport]
                                      type:       Electric
                                      scale:      W
                                      rate type:  Consumed
                                      value:      141.8
                                      time delta: 0 seconds

Also, your original dump had the Shutter 3 as node 31, did you remove and add it? Could you provide a new dump file to confirm it's in the same situation?

je-mei commented 3 years ago

did you remove and add it --> yes, I did. I did everything to get the shutter run ;-).

here my new reports

  1. reinterview
  2. down and up via local switch
  3. down and up via HA

00_reinterview 00_reinterview.txt

01_down_and_up_via_local_switch- 01_down_and_up_via_local_switch-.txt

02_down_and_up_via_HA 02_down_and_up_via_HA.txt

kpine commented 3 years ago

Could you please provide the network dump. I just wanted to confirm that HA still sees only values for endpoints 1 and 2.

je-mei commented 3 years ago

zwave_js_dump-json.txt

kpine commented 3 years ago

@AlCalzone looks like another case of values for endpoints 1, etc, but reports on endpoint 0?

AlCalzone commented 3 years ago

Yeah, that looks like another edge case for the association setup. The endpoints 1/2 share their lifeline with the root endpoint (max. no of nodes is 0), so it looks like they have a node association when they actually don't.

je-mei commented 3 years ago

hi, fyi - behaviour of my shutter 2 in addition. I have only two shutters. one shutter 3 and one shutter 2. shutter 2 runs better, but maybe there is the same issue occuring, but the power entity is running great ;-) reinterview_shutter2.txt up_down_manually_via_local_shutter.txt up_down_manually_via_local_shutter.txt reinterview_shutter2.txt Screenshots_before_and_during_progress.pdf

je-mei commented 3 years ago

Roller Shutter 3 runs great now, thanks for your work!

Kind regards Jens