#Error "Cannot change status. Disabled by Config entry." after migrating to Z-Wave JS UI

1 messages · Page 1 of 1 (latest)

knotty hemlock
#

Hi,
I migrated to Z-W JS UI following this guide (https://community.home-assistant.io/t/switching-z-wave-js-addons-with-minimal-downtime-z-wave-js-official-to-z-wave-js-ui-community/409904), and it went mostly as planed.
Every device is migrated, identified and communicates with the controller/HA. There is no errors in the log as far as I can see.

But the majority of entities is disabled. The "main" entity is enabled and working, but entities like "temperature", "power", etc. is disabled.
It's not possible to enable them, and there is a message "Cannot change status. Disabled by Config entry.".

When looking in the log I see that that the devices is reporting as expected:

2025-02-19T10:45:29.794Z SERIAL « 0x01180004001412600d01003202215400000022000000000000ee (26 bytes) 2025-02-19T10:45:29.798Z SERIAL » [ACK] (0x06) 2025-02-19T10:45:29.801Z CNTRLR [Node 020] [Meter] value[66049]: metadata updated [Endpoint 1] 2025-02-19T10:45:29.803Z CNTRLR [Node 020] [~] [Meter] value[66049]: 933.42 => 0.34 [Endpoint 1] 2025-02-19T10:45:29.808Z DRIVER « [Node 020] [REQ] [ApplicationCommand] └─[MultiChannelCCCommandEncapsulation] │ source: 1 │ destination: 0 └─[MeterCCReport] meter type: Electric scale: W rate type: Consumed value: 0.34 time delta: 0 seconds

Any suggestions?

(Has done full restart of HA and Z-Wave JS UI-addon multiple times..)

z-wave-fail.png
unborn torrent
#

What does your integration page for zwave_js look like? Sounds like the integration is still disabled. Maybe you forgot the step to re-enable it?

knotty hemlock
#

Hmm.. I think I did everything as described, but I was a unfocused at the end. (Because of happyness - I tried to migrate a year ago, and messed up.)

unborn torrent
#

Hmm well it looks enabled. I don't know then.

real light
#

@stark drum any ideas?

stark drum
#

What's a "main" entity?

stark drum
#

Can you run these commands from one of the Terminal add-ons and paste the output.

jq '.data.entries[] | select(.domain == "zwave_js") | .data |= with_entries(select(.key | endswith("_key") | not))' /config/.storage/core.config_entries

jq '.data.entities[] | select(.entity_id == "sensor.m_bathroom_wall_light_power") | pick(.config_entry_id, .disabled_by, .unique_id)' /config/.storage/core.entity_registry
knotty hemlock
#

{
"created_at": "1970-01-01T00:00:00+00:00",
"data": {
"integration_created_addon": false,
"url": "ws://a0d7b954-zwavejs2mqtt:3000",
"usb_path": "/dev/serial/by-id/usb-0658_0200-if00",
"use_addon": false
},
"disabled_by": null,
"discovery_keys": {
"hassio": [
{
"domain": "hassio",
"key": "557683ab87c2431db61b835430cb8671",
"version": 1
}
],
"zeroconf": [
{
"domain": "zeroconf",
"key": [
"_zwave-js-server._tcp.local.",
"4204850534._zwave-js-server._tcp.local."
],
"version": 1
}
]
},
"domain": "zwave_js",
"entry_id": "e502f8a0d30fa612ef51872ceb413eea",
"minor_version": 1,
"modified_at": "2025-02-19T09:03:39.811797+00:00",
"options": {},
"pref_disable_new_entities": false,
"pref_disable_polling": false,
"source": "hassio",
"title": "Z-Wave JS",
"unique_id": "4204850534",
"version": 1
}

#

"config_entry_id": "e502f8a0d30fa612ef51872ceb413eea",
"disabled_by": "config_entry",
"unique_id": "4204850534.21-49-1-Power"
}

#

Sorry ‘bout the formatting. Is on phone.
With «main entity» I mean for example «climate.thermostat», and «sensor.air_temperature» as «sub entities». (Think I saw it visualized like that in an old Fibaro z-wave-gateway.)

stark drum
#

Looks ok to me, the config entry is correct and enabled. You could try disabling the integration and re-enabling it. Not sure what updates the entities, it seems whatever that is missed them.

knotty hemlock
#

I hate you!
(In a good way.. ❤️)

I’ve tried disable/enable multiple times as well, but no luck.. This time?

Well, well..
Being a IT-consultant I know all about things suddenly working..

Thanks a lot. 🙂

real light
#

That's just their good aura 🤣