Core: Z-Wave disabled entities triggered for updates

[bieniu]

Home Assistant release with the issue:
0.98.1

Last working Home Assistant release (if known):
None

Operating environment (Hass.io/Docker/Windows/etc.):
RPi3B/Raspbian/Python 3.7.2/venv

Component/platform:
Z-Wave/sensor

Description of problem:
I have those errors in log at Home Assistant start when I disabled some entities via Entity Registry:

2019-08-30 09:47:16 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.fibaro_fgs223_exporting_1 is incorrectly being triggered for updates while it is disabled. This is a bug in the zwave integration.
2019-08-30 09:47:16 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.fibaro_fgs223_energy_1 is incorrectly being triggered for updates while it is disabled. This is a bug in the zwave integration.
2019-08-30 09:47:16 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.fibaro_fgs223_alarm_type is incorrectly being triggered for updates while it is disabled. This is a bug in the zwave integration.
2019-08-30 09:47:16 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.fibaro_fgs223_alarm_level is incorrectly being triggered for updates while it is disabled. This is a bug in the zwave integration.
2019-08-30 09:47:16 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.fibaro_fgs223_sourcenodeid is incorrectly being triggered for updates while it is disabled. This is a bug in the zwave integration.
2019-08-30 09:47:16 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.fibaro_fgs223_heat is incorrectly being triggered for updates while it is disabled. This is a bug in the zwave integration.
2019-08-30 09:47:16 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.fibaro_fgs223_power_management is incorrectly being triggered for updates while it is disabled. This is a bug in the zwave integration.
2019-08-30 09:47:16 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.fibaro_fgs223_exporting_2 is incorrectly being triggered for updates while it is disabled. This is a bug in the zwave integration.
2019-08-30 09:47:16 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.fibaro_fgs223_energy_2 is incorrectly being triggered for updates while it is disabled. This is a bug in the zwave integration.
2019-08-30 09:47:16 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.fibaro_fgs223_previous_reading_1 is incorrectly being triggered for updates while it is disabled. This is a bug in the zwave integration.
2019-08-30 09:47:16 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.fibaro_fgs223_interval_1 is incorrectly being triggered for updates while it is disabled. This is a bug in the zwave integration.
2019-08-30 09:47:16 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.fibaro_fgs223_previous_reading_2 is incorrectly being triggered for updates while it is disabled. This is a bug in the zwave integration.
2019-08-30 09:47:16 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.fibaro_fgs223_interval_2 is incorrectly being triggered for updates while it is disabled. This is a bug in the zwave integration.

[probot-home-assistant[bot]]

Hey there @home-assistant/z-wave, mind taking a look at this issue as its been labeled with a integration (zwave) you are listed as a codeowner for? Thanks!

[cgarwood]

For a temporary workaround, instead of disabling them via the entity_registry, disable them from the Z-Wave config panel

[Linwood-F]

Thanks for looking into this, just ran across it. Disabling them from z-wave seems to have no impact, they still show up in unused entities for example, and developer tools/states. So at least for me the workaround isn't usable. Do the errors actually cause trouble or can they just be ignored?

[cgarwood]

@Linwood-F for the workaround via the z-wave panel to take effect, you'll have to add the following to configuration.yaml and restart:

zwave:
  device_config: !include zwave_device_config.yaml

Then after excluding the devices from the Z-Wave panel they'll still stick around until another HA restart.

[Linwood-F]

Ah.. sorry for the tangent. I had no idea. Just tried it and it worked fine. Seems odd that the feature exists but is disconnected, thanks for the info.

[cgarwood]

Yeah there’s a lot of legacy code floating around in the zwave component from the days before stuff like the entity registry existed in the core

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Phontana]

This is still an issue in the latest version of Home Assistant (0.102.3).

[SeraphimSerapis]

+1 -- it would be great if we could at least filter those messages so the Log doesn't get cluttered too much.

[MoHf7f4]

still an issue with Home Assistant 0.103.6

[cdk222]

Still an issue. All my old sensors have come back since last Hass.io update and are now impacting the stability of my other zwave device states (Flickering - which I had previously fixed).

[MoHf7f4]

Update took care of it for me too.

On Thu, Jan 23, 2020, 12:00 PM cdk222 [e-mail] wrote:

Still an issue. All my old sensors have come back since last Hass.io
update and are now impacting the stability of my other zwave device states
(Flickering - which I had previously fixed). Very annoying that this
remains unsolved.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/26288?email_source=notifications&email_token=AEIA5XQBB6YBC7AYVBDCVALQ7HLMXA5CNFSM4ISLLJTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJYH54A#issuecomment-577797872,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEIA5XXROIK6JJYDP57DITTQ7HLMXANCNFSM4ISLLJTA
.

[Twanislas]

Still happening in 0.105 at every HA restart.
Cheers ! :)

[fortepc]

Just found this in my dev-tools logs. Wanted to report I'm also having this issue.

[kpine]

Use the zwave device configuration to ignore entities as @cgarwood has explained above, not the entity registry.

I would not expect a fix for this bug as all effort is being directed to the new integration.

[skynet01]

Also 106.. Any word on when the new integration is released?

[kpine]

You can follow these if you'd like to keep tabs on status:
https://community.home-assistant.io/t/the-future-of-z-wave-in-ha-qt-openzwave/148541
https://github.com/cgarwood/homeassistant-zwave_mqtt

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[ZetaPhoenix]

Still an issue with 0.110.4.

[ludipq]

Still the same issue in 0.111.4

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.