Blank zwave device IDs

UPDATE As I was writing this I upgradded to the latest version, and the problem has gone away. I think it was the full reset of Hass.io rather than 0.67 fixing some bug. I’m going to post this anyway as the solution seemed to be a full restart of Hass.io, rather then just restarting Home Assistant. If it happens with my next one, I’ll capture relevant info from OZW and open a bug.

I’m trying to add a new Philio PAN11-4 switch to my zwave network, I already have one up and running so I know the devices work on my network.

When you first switch it on it goes into auto-setup mode, and you’re supposed to start the inclusion process on your controller, which I did through the ZWave config page in Home Assistant, it’s found the device, but it hasn’t given it an identifier for the switch or one of the sensors. It’s also not saved the device to zwcfg either.

I left the device overnight to see if it would correct itself but it’s still the same this morning (day 2).

Yesterday (day 2) I tried to remove/exclude the node from the network, and I thought I had so I went to include it again, and now (day 3) I have 2 devices, with id’s 14 & 15, 14 being the original. Overnight one has been marked as failed, so I went to remove it via the config interface and while the OZW log suggests it tried, nothing in the UI seems to have changed.

The network itself is healthy, looking in the OZW logs the other devices see ID:15 as a neighbor, and don’t list ID:14 as one.

As a follow up to this, the device’s switch has still kept the blank ID it had yesterday and show sup in the list of entities as switch.switch_2 rather than following the other parts which are named after the full device, sensor.philio_technology_corporation_pan114_smart_energy_plug_in_switch_current_2 for example.

You are not alone … I just added a new aeon nano switch and can’t find the entities… Just noticed that they are there but without the zwave device name… my switch is now called switch.switch instead of switch.hallway_0_light_switch.
This seems like a bug after the changes in the zwave naming

When were those changes?

There were changes between 63 and 65 in the entities naming. Last I added a new zwave device was under 62 and that worked ok