Many of my battery powered zwave sensors are acting up after updating zwavejs

Configuration
1

I updated my zwavejs docker container to the latest version ( 11.19.1/ UI 15.24.2) in anticipation of the force update going to the latest version of HA and now I have 7 battery powered sensor devices with several of the entities showing unknown.

they are a mix of tilt sensors, motion sensors and door/window sensors.

I also have repairs indicated in HA that say, for example:

The binary sensor binary_sensor.garage_door_north_position_sensor is deprecated because it has been replaced with the binary sensor binary_sensor.north_garage_door_position.

The entity was found in the following automations or scripts:
.
.
.
Please update the above automations or scripts to use the binary sensor binary_sensor.north_garage_door_position and disable the binary sensor binary_sensor.garage_door_north_position_sensor and then restart Home Assistant, to fix this issue.

the problem is that in the above example the binary_sensor.north_garage_door_position doesn't exist and the binary_sensor.garage_door_north_position_sensor shows as unknown.

I've restarted HA, I've restarted zwavejs (I run it in docker along with a HA Container install), tried reinterviewing the node (but since they are all battery powered devices I have to wake them and I'm not able to do that right now so not sure if that will do anything).

it seems the battery data is working but none of the other entities are working:

image
image352×398 11.9 KB

I'm not sure what I need to do next.

2

Find the correct entity and rename it to the old name. That's how I solve these things.

3

expand the 7 disabled entities and see what they are. If you got a new entity, the name follows the new convention and you have to wait for the state to update. You could also just run down and open the door/window. Unknown is only there because it's a new entity and hasn't gotten a new state. If you do what @sender said (delete old, rename new to old) and restart, HA will restore the previous state from the old entity_id.

4

Open the door to fix the unknown state.

5

Thanks for the replies.

I'll have to wait till I get home later to give it a try.

In the meantime I've rolled back to an earlier version (but not my original version which was 11.1.0) and everything seems to be working again.

6

Also...

Does anyone know what the required version of zwavejs is for HA 2026.6? I'm sure I saw there was a new minimum version listed somewhere but now I can't find it anywhere.

7

The backwards incompatibility note was not added to the release notes for 2026.6 (yes, devs were notified).

Here's the change: Bump zwave-js-server-python to 0.70.0 by raman325 · Pull Request #169578 · home-assistant/core · GitHub

With this release, you will need to update your zwave-js-server instance. You must use zwave-js-server 3.7.0 or greater (schema 47).

  • If you use the Z-Wave JS add-on, you need at least version 1.3.0.
  • If you use the Z-Wave JS UI Docker container, you need at least version zwave-js/>zwave-js-ui@v11.16.2 (release).
  • If you run your own Docker container or some other installation method, you will need to update your zwave-js-server instance to at least 3.7.0.

Also, 2026.7 release (presumably) will require another update, so might as well make sure you're running that required version. Bump zwave-js-server-python to 0.72.0 by AlCalzone · Pull Request #173309 · home-assistant/core · GitHub

With this release, you will need to update your zwave-js-server instance. You must use zwave-js-server 3.9.0 or greater (schema 49).

  • If you use the Z-Wave JS add-on, you need at least version 1.4.0.
  • If you use the Z-Wave JS UI Docker container, you need at least version zwave-js/[email protected] (release).
  • If you run your own Docker container or some other installation method, you will need to update your zwave-js-server instance to at least 3.9.0.
8

Renaming the old entitity and then renaming the new entity to the old entitiy id causes loss of history,

In order to preserve history. I shutdown HA, copied the entity registry json file, brought it up in vscode, pasted the error messages into Claude and asked Claude to

a) rename the old entity id by appending _old and disable it
b) rename the new entity to the old entity id

It did this task quickly and accurately.

Then copied the entitiy registry back into HA and all works and I still have history.

9

With me it causes no loss of history...

10

Delete the old entity, do not rename it. Then rename the new entity to the same as the old entity and your history will be preserved.

11

Not too concerned about saving my history so just renaming them both worked.

I guess my initial confusion was caused by the entities showing as unknown and the bad luck in picking the first one look at I didn't realize that the entity_id label was a different order between the old and new.

the old one was "garage_door_north_position...". the new one was "north_garage_door_position...". so when I looked for the pattern I didn't find the new one listed in my states list and the abbreviated naming in the device listing it wasn't obvious that they were both there.

Thanks for the help everyone but I should have figured this one out myself tho. :smile: