Adding Motion Sensors and Entity ID Changed Overnight?

Configuration Z-Wave
1

I have the Gen 5 stick and used the AIO installer. I added the motion sensors last night and this morning the sensor entity ID names changed. It used to be binary_sensor._sensor_2 or 3

binary_sensor.ecolink_doorwindow_sensor_sensor_2
binary_sensor.ecolink_doorwindow_sensor_sensor_3

Also noticed a bunch of ones added. I don’t have any of these sensor alarms.

sensor.ecolink_doorwindow_sensor_alarm_level_2
sensor.ecolink_doorwindow_sensor_alarm_level_3
sensor.ecolink_doorwindow_sensor_alarm_type_2
sensor.ecolink_doorwindow_sensor_alarm_type_3
sensor.ecolink_doorwindow_sensor_burglar_2
sensor.ecolink_doorwindow_sensor_burglar_3
sensor.ecolink_doorwindow_sensor_sourcenodeid_2
sensor.ecolink_doorwindow_sensor_sourcenodeid_3

Any ideas?

2

They are the same sensor, just different attributes you can access. You’ll need to read up on the sensor to find out what these attribute represent but they are just additional states you can monitor. Go to your states panel and click on the entity and that should show you the current state of that attribute.

3

Do you know why the entity_ID would change? I set it up last night and they were a different name. Now my automation don’t work as they don’t reference the correct entity_ID.

4

Well the state of the window/door being open or closed would be a binary state; open or closed, on or off - so those would be binary_sensors. One sensor delivering one of two states. The other attributes would hold variable values, so they would be regular sensors.

Not sure why the binary sensors changed names though. Remember, I don’t use a Zwave stick. Are your originally named binary sensors still there or did the new ones replace them?

5

ZWave names are a little squirrely - did you restart your HA? They seem to settle down after a couple of HA restarts.

6

That is so odd that the entity_ID would reset in itself. Once I renamed my automations, it worked again. Did this happen to you too @aimc?

7

Maybe first polling, it just saw the motion sensor attribute and it took awhile longer for the other attributes to register?

8

Hopefully I wake up to a working version!

9

Hopefully, you aren’t using it as your alarm clock!

10

Part of it is that when the discover component sees the device for the first time it has trouble pulling all of the information (this may be a limitation of ZWave as I see OZWCP takes a minute or two sometimes). After a restart, HA has had time to gather all the info and fills it in and the device name changes, but after that it should remain stable. I have had no issues of device names changing after the first couple of restarts except one time when some actual code changes were made that explained the name changes.

11

Kinda like I said above. So best practices would be to add the devices and wait a few cycles before adding then to any automations or groups.

12

I’d just reboot once or twice - mine hasn’t changed anymore!

Things are back on track.