zwave_js.refresh_value error | Home Assistant | Page 1

atomic reef Sep 29, 2024, 2:10 AM

#

I use this action to refresh the value of sensor.dishwasher_internal_temperature It has worked well for a while. Recently it has started to generate an error in Home Assistant.

Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:761
integration: Sensor (documentation, issues)
First occurred: 9:44:26 PM (16 occurrences)
Last logged: 9:57:07 PM

Platform zwave_js does not generate unique IDs. ID 3479161084.182-112-0-32 already exists - ignoring sensor.dishwasher_internal_temperature

severe field Sep 29, 2024, 2:14 AM

#

Look in .storage/core.entity_registry and see what's already registered with that unique id

#

If you have jq you could try

atomic reef Sep 29, 2024, 9:51 AM

#

I already removed it. @severe field did something change with zwave_js.refresh_value?

#

It is trying to add the entity as well as refresh its value

severe field Sep 29, 2024, 4:09 PM

#

I tried it w/o any issue

atomic reef Sep 29, 2024, 4:45 PM

#

What did you try?

#

To use that service on an entity?

#

Are you running beta?

severe field Sep 29, 2024, 5:17 PM

#

Yes. Have you tried other entities?

#

The service code itself has not changed. And the entity has to actually exist to get anywhere. Using a non-existent entity gives me:

Failed to perform the action zwave_js.refresh_value. No zwave_js entities found in service call. Got {'type': 'execute_script', 'sequence': [{'action': 'zwave_js.refresh_value', 'data': {'entity_id': ['light.dining_room_light_switch22']}}], 'id': 50}

atomic reef Sep 29, 2024, 7:46 PM

#

Yes, I have tried other entities without error. Not sure what is going on. Just excluded, reset and included. Still doing it. Maybe specific to inovelli? No clue what to try next

#

Was working perfect until yesterday.

severe field Sep 29, 2024, 7:59 PM

#

is there not another entity with the same unique id? that's what the error is complaining about.

atomic reef Sep 29, 2024, 8:01 PM

#

No, not that I can find. I searched core.entity_registry and that sensor.dishwasher_internal_temperature is the only one that comes up

#

My setup is pretty solid these days, I don’t make many changes.

#

That’s what I am saying. It looks like zwave_js.refresh_value on that entity is trying to create duplicate entity with the exact same unique id

#

And same name

#

Same everything

#

When it can’t. It errors and ignores

#

I even tried changing the unique id. It changed it back

severe field Sep 29, 2024, 8:05 PM

#

are there any other logs surrounding it?

atomic reef Sep 29, 2024, 8:05 PM

#

Let me look

severe field Sep 29, 2024, 8:06 PM

#

is the refresh actually working, and that comes after?

#

you might try enabling the integration debug logging to see what the sequencing is like

#

that's a config parameter?

#

Ah that's the ticket. I reproduced by enabling a config-parameter entity and refreshed

#

I guess I should check if it's any other kind of disabled entity.

atomic reef Sep 29, 2024, 8:13 PM

#

ha...you figured it out?

#

and the refresh actually works

severe field Sep 29, 2024, 8:14 PM

#

well, not sure what the root cause is. either 1) limited to config parameter entities or 2) entities that were disabled and then enabled

atomic reef Sep 29, 2024, 8:15 PM

#

it was disabled when first added but it worked for like months

#

this just recently started happening

severe field Sep 29, 2024, 8:15 PM

#

could simply be that

atomic reef Sep 29, 2024, 8:15 PM

#

2024-09-29 16:07:32.016 INFO (MainThread) [homeassistant.helpers.script.websocket_api_script] websocket_api script: Running websocket_api script
2024-09-29 16:07:32.016 INFO (MainThread) [homeassistant.helpers.script.websocket_api_script] websocket_api script: Executing step call service
2024-09-29 16:07:32.065 ERROR (MainThread) [homeassistant.components.sensor] Platform zwave_js does not generate unique IDs. ID 3479161084.184-112-0-32 already exists - ignoring sensor.dishwasher_internal_temperature
2024-09-29 16:07:32.066 ERROR (MainThread) [homeassistant.components.sensor] Platform zwave_js does not generate unique IDs. ID 3479161084.184-112-0-32 already exists - ignoring sensor.dishwasher_internal_temperature
2024-09-29 16:07:32.067 INFO (MainThread) [homeassistant.components.zwave_js] Refreshing primary value ConfigurationValue(value_id='184-112-0-32') for sensor.dishwasher_internal_temperature, state update may be delayed for devices on battery
2024-09-29 16:07:34.494 INFO (MainThread) [pyalarmdotcomajax] Getting system data for 4306849.
2024-09-29 16:07:34.520 INFO (MainThread) [pyalarmdotcomajax] Getting all devices in 4306849.

severe field Sep 29, 2024, 8:15 PM

#

debug logs show more

#

but basically just confirms it's trying to add the entityt

#

2024-09-29T20:09:47.984Z CNTRLR   [Node 064] [~] [Configuration] 9: 2 => 2                          [Endpoint 0]
2024-09-29 20:09:47.991 DEBUG (MainThread) [zwave_js_server] Received message:
WSMessage(type=<WSMsgType.TEXT: 1>, data='{"type":"event","event":{"source":"node","event":"value updated","nodeId":64,"args":{"commandClassName":"Configuration","commandClass":112,"property":9,"endpoint":0,"newValue":2,"prevValue":2,"propertyName":"LED Indicator Brightness"}}}', extra='')

2024-09-29 20:09:47.992 DEBUG (MainThread) [homeassistant.components.zwave_js] [select.master_bedroom_lamp_switch_led_indicator_brightness] Value 9/None changed to: 2
2024-09-29 20:09:47.994 DEBUG (MainThread) [homeassistant.components.zwave_js] Processing node Node(node_id=64) added value ConfigurationValue(value_id='64-112-0-9')
2024-09-29 20:09:48.000 DEBUG (MainThread) [homeassistant.components.zwave_js] Discovered entity: ZwaveDiscoveryInfo(node=Node(node_id=64), primary_value=ConfigurationValue(value_id='64-112-0-9'), assumed_state=False, platform=<Platform.SELECT: 'select'>, platform_data=None, additional_value_ids_to_watch=set(), platform_hint='config_parameter', platform_data_template=None, entity_registry_enabled_default=False, entity_category=None)
2024-09-29 20:09:48.002 ERROR (MainThread) [homeassistant.components.select] Platform zwave_js does not generate unique IDs. ID 3611217407.64-112-0-9 already exists - ignoring select.master_bedroom_lamp_switch_led_indicator_brightness

atomic reef Sep 29, 2024, 8:17 PM

#

so its prob a beta issue?

severe field Sep 29, 2024, 8:17 PM

#

I haven't gone back to check

atomic reef Sep 29, 2024, 8:19 PM

#

now that you reproduced it and it is not something with my setup, i can roll back to stable and see. i rolled back to 0b3 and no change

#

not happening on 2024.9.3 so definately a beta issue. thanks. so it is only happening on config zwave entities?

severe field Sep 29, 2024, 8:31 PM

#

I haven't found an entity I could test yet

atomic reef Sep 29, 2024, 8:34 PM

#

ok, well i did a refresh 3 times without any errors on 2024.9.3

severe field Sep 29, 2024, 8:36 PM

#

Betting it's related to https://github.com/home-assistant/core/pull/125326/

GitHub

Enable Zwave notification sensors by default by joostlek · Pull Req...

Breaking change
Previously some sensors got duplicated as both a binary sensor and a (disabled) normal sensor.
The disabled sensors that already have a binary sensor will no longer be discovered.
A...

atomic reef Sep 29, 2024, 8:45 PM

#

so if i have a binary_sensor.dishwasher_internal_temperature sensor?

severe field Sep 29, 2024, 8:46 PM

#

Yep, reverting the PR fixes it

steady coyote Sep 29, 2024, 8:50 PM

#

Which Z-Wave value ID does this correspond to?

severe field Sep 29, 2024, 8:50 PM

#

It's a config parameter

steady coyote Sep 29, 2024, 8:50 PM

#

huh?

severe field Sep 29, 2024, 8:50 PM

#

I'm trying to find another default-disabled entity to test

#

Configuration CC

steady coyote Sep 29, 2024, 8:51 PM

#

That's odd

severe field Sep 29, 2024, 8:51 PM

#

that PR made changes to how discovered values are tracked

#

        if (
            not value.node.ready
            or not (device := self.dev_reg.async_get_device(identifiers={device_id}))
            or value.value_id in self.controller_events.discovered_value_ids[device.id]
        ):
            return

#

usually on a "value updated" event the 3rd line will exit

#

with new code the value ID is not present

steady coyote Sep 29, 2024, 8:54 PM

#

@silver star @dry crow FYI

#

the nightmare PR continues 😄

severe field Sep 29, 2024, 8:55 PM

#

Not seeing an issue with a default-disabled binary_sensor (Binary Sensor CC)

steady coyote Sep 29, 2024, 8:57 PM

#

I guess the discovery schema for the config parameter needs an allow_multi now to also create a binary sensor.

#

IIRC that flag wasn't working correctly before

severe field Sep 29, 2024, 8:58 PM

#

But it's already a select entity?

steady coyote Sep 29, 2024, 8:59 PM

#

Hm I might be missing some of the context above

severe field Sep 29, 2024, 8:59 PM

#

I was testing two different values to see if it was anything to do with being default disabled

#

at least so far, just related to config cc values

#

The binary sensor one is working as expected

steady coyote Sep 29, 2024, 9:00 PM

#

Ok that's what I misunderstood

severe field Sep 29, 2024, 9:00 PM

#

at least in relation to the value update

steady coyote Sep 29, 2024, 9:01 PM

#

I thought somehow the config parameter was also discovered as a binary sensor, and that wasn't working

atomic reef Sep 29, 2024, 9:04 PM

#

https://github.com/home-assistant/core/issues/127059

GitHub

zwave_js.refresh_value tries to recreate an already existing entity...

The problem Logger: homeassistant.components.sensor Source: helpers/entity_platform.py:761 integration: Sensor (documentation, issues) First occurred: 7:51:15 PM (38 occurrences) Last logged: 8:09:...

severe field Sep 29, 2024, 9:04 PM

#

Ah but you were on the right track

#

allow_multi defaults to False

atomic reef Sep 29, 2024, 9:05 PM

#

in my cass i have a binary_sensor.dishwasher_internal_temperature already if that matters

severe field Sep 29, 2024, 9:06 PM

#

If it has a different unique id, shouldn't be relevant

dry crow Sep 29, 2024, 9:07 PM

#

steady coyote <@461603794090852353> <@80252278073724928> FYI

Oh didn't see this ping

steady coyote Sep 29, 2024, 9:08 PM

#

Just happened 3 minutes ago

dry crow Sep 29, 2024, 9:08 PM

#

steady coyote the nightmare PR continues 😄

https://tenor.com/view/happy-tears-gif-9394121133314611352

Tenor

dry crow Sep 29, 2024, 9:08 PM

#

steady coyote Just happened 3 minutes ago

yea but I already send it to you via other channels not knowing you were already up to date 😂

#

Euh I have to look into this tomorrow, but I can't garuantee that I am able to know how to fix it

severe field Sep 29, 2024, 9:11 PM

#

I think it might be because config parameters are outside of the normal schema list

#

        # prevent re-discovery of the (primary) value if not allowed
        if not schema.allow_multi:
            discovered_value_ids[device.id].add(value.value_id)

    if value.command_class == CommandClass.CONFIGURATION:
        yield from async_discover_single_configuration_value(
            cast(ConfigurationValue, value)
        )

#

async_discover_single_configuration_value probably needs to add to discovered_value_ids

#

or something

#zwave_js.refresh_value error