Entity customised areas setting is not retained.

Question

Entity customised areas setting is not retained.

sotatech opened this issue a year ago · comments

Pat Rooney commented a year ago

Version of the custom_component

2.0.0

Home Assistant 2023.7.2

Configuration

Add your logs here.

Describe the bug

I have a Cytech alarm system connect to HA via the Node-RED companion. One device is configured for the zones, so it contains binary sensors for every zone. In HA settings for each entity I turn off the option for the entity to use the device area, and set each one according to their location. If I make a change to the flow and deploy it, the area setting for the entity is reset to the default.
I have used this feature with other integrations, and the setting is retained.

Debug log


Logs attached.
[home-assistant_nodered_2023-07-17T08-26-38.078Z.log](https://github.com/zachowj/hass-node-red/files/12067417/home-assistant_nodered_2023-07-17T08-26-38.078Z.log)

Pat Rooney · Answer 1 · Mon Jul 17 2023 16:42:17 GMT+0800 (China Standard Time)

home-assistant_nodered_2023-07-17T08-26-38.078Z.log

Jason · Answer 2 · Tue Jul 18 2023 09:00:53 GMT+0800 (China Standard Time)

2023-07-17 09:26:10.884 INFO (MainThread) [custom_components.nodered] Entity removed: switch.comfort_output_001

At this point in the log, do recall what action is being taken in NR? The entity should only be removed from HA if you deleted the entity config and deployed.

Jason · Answer 3 · Tue Jul 18 2023 09:03:08 GMT+0800 (China Standard Time)

Did you remove the custom component, then re-add it?

Pat Rooney · Answer 4 · Tue Jul 18 2023 15:32:39 GMT+0800 (China Standard Time)

I think I did a deploy in NR and a reload of the integration at that point, after setting the custom area on some of the entities in HA as a test. This was to check if the changed setting would survive.
I didn't remove anything.

Pat Rooney · Answer 5 · Wed Jul 19 2023 17:42:15 GMT+0800 (China Standard Time)

I notice that when I do a reload of the integration, I get a lot of errors about the platform not generating unique IDs:

2023-07-19 10:40:02.585 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform nodered does not generate unique IDs. ID nodered-77e1e680.210de8-041bf28f19b9896a already exists - ignoring binary_sensor.shed_smoke_detector 2023-07-19 10:40:02.586 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform nodered does not generate unique IDs. ID nodered-77e1e680.210de8-041bf28f19b9896a already exists - ignoring binary_sensor.shed_smoke_detector 2023-07-19 10:40:02.587 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform nodered does not generate unique IDs. ID nodered-77e1e680.210de8-041bf28f19b9896a already exists - ignoring binary_sensor.shed_smoke_detector 2023-07-19 10:40:02.587 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform nodered does not generate unique IDs. ID nodered-77e1e680.210de8-4198d5c696950595 already exists - ignoring binary_sensor.utility_room_pir_sensor

Pat Rooney · Answer 6 · Thu Jul 20 2023 15:41:24 GMT+0800 (China Standard Time)

I did some more testing and I found that by clearing the area setting for the device, I could then customise the area for each entity and it would be retained through a reload or restart of HA.
So it would appear that the integration is assuming that all entites associated with a device will have the same area.

github-actions · Answer 7 · Tue Sep 19 2023 09:48:06 GMT+0800 (China Standard Time)

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.