There are no zwave entities for zwave_js. Everything has been broken out into services or separate entities.
I had a similar issue with my power boards.
Check the hidden entities for a disable element named âŚnode status and enable that. See the post from @firstof9 above for more details.
I have a flood sensor that had a lot of entities. See below:
When I updated (see below) even with the three at the bottom that were/are hidden, it still doesnât sync up with what I had before
Youâll have completely different entities. I donât know how else to tell you. There will not be a 1 to 1 scenario.
Stand back for a second. Are you actually missing things you need? Chances are, no. You most likely can get all your information from the 3 items that are not hidden.
So if you click on the sensor.flood_sensor_node_status line is the entity disabled and can you slide it to enabled and press update. A messaging saying the entity will update in 30 seconds should appear. Then you can see the sensor.flood_sensor_node_status. which will be the replacement for your zwave.flood_sensor from zwave 1.4
Sorry I may be misunderstanding what youâre after. I took it you were looking to see if the flood sensor was ready/alive on your mesh network
heâs questioning why heâs not getting the same number of entities that he had in zwave 1.4 vrs zwave js.
Switched over and everything is working well. Did have less entities and different entities but all good now. Some of my sensors were changed to multiple binary_sensors which effected my automations and had to redo those but up and kickin. Thanks for the help.
1 Like
By the way, everything is working but recently noticed Add-Ons that the Z-Wave JS one is stopped. So
Never saw this screen during the setup:
So here shows the Z-Wavs JS Integration piece running with Z-Wave JS to MQTT. That basically normal?
Many thanks for great guide, as such it is simple to follow. I have finally made a switch from OZW integration but unfortunately it is not as smooth as I would expect. The Zwave2Mqtt was not able to interview all my devices, I needed to bring them close to the Aeotec stick, still have 2 qubino 2 channel switch modules which are installed in switch boxes outdoors and they are not able to get interviewed. Is bringing them home the only way to interview them? Additionally I have a radiator thermostat which looks good in Zwave2mqtt but no entities are visible in HA:
I donât have a radiator close to the server/stick so how can I force the interview/update?
I switched over as well, doing the migration by hand as described above. Everything worked exactly as planned.
As I never had sensible entity names I kept the changed ones / tweaked them. I then opened all my YAML files in Notepad++ and did a âReplace in all open filesâ of old entity to new entity. Worked great.
For ~60 nodes (almost all mains powered) it took 3-4 hours. All stable since.
Short update: The last two modules were qubino flush 2 relays but they required factory reset and inclusion from scratch. Now the network seems to work. A bit strange is that all devices, except one, are connect to the coordinator directly - so I donât understand why most of them were not getting re-interviewed until I have brought them close to the coordinator. Hope this was the last problem with my zwave network 
Hi
I am trying updating from Zwave 1.4 (Deprecated) to ZwaveJS2MQTT as updating just to ZwaveJS gets me in trouble. I am loosing all names but this is not the issue i have only around 7 5modes so I can rename them but than in automations it does not show actions to choose.
I uninstalled all Zwave integrations and addons restarted the VM and also the pc it is on.
Installed ZwaveJS2MQTT added port and keys but have an issue as it still can not connect to port?
What shall i put there in port
/dev/serial/by-id/usb-0658_0200-if00
or
ttyACM0
the error is
Driver: Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200) at Driver.sendMessage (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:3274:23) at ZWaveController.identify (/opt/node_modules/zwave-js/src/lib/controller/Controller.ts:668:33) at Driver.initializeControllerAndNodes (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:947:26) at Immediate.<anonymous> (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:817:16) (ZW0100)
Not sure if itâs exactly the same error but I had a similar issues last week and found a post on GitHub to disable soft reset in the setting menu of the zwave js to Mqtt page. Once disabled you need to check if the zwave stick/hub is still mounted to the vm and restart zwave js to Mqtt.
Again not sure itâs 100% the same but it helped fox a similar issue.
1 Like
Thanks it helped but now i am in the situation that i have this all 64 nodes and they are waiting for product info?
Ok in your original post you has 7 5nodes. So is that 75 nodes? If so I know my 18 nodes took a while to clear up. 75 would take a while (based on my experience). Itâs been about 6 hours now have any of them gone live?
OrâŚ
Was it 7 nodes and you have 57 phantom nodes just sitting there?
By now I would hope that some have failed and you can delete them.
Thanks for the answer
I do have 62 nodes but it did not changed anything still the same progress
In devices they showing done unknown some alive but you can not control them.
and still the same
nut on the info bar on the top it shows healing process compleated healed 61 devices
and after restart still the same but in integration one more zwave showed
some nodes have more green
and one shows orange nodeinfo instead of protocolinfo
Youâll need to comment out (use #) your zwave details in your configuration.yaml file and restart HA. I donât think you can run both. You moving off zwave deprecated.
yes I deleted all zwave before i started to move but after restart it showed up again?
Which lines do i need to remove from Yaml
The only line about zwave there i have got this 
If ZwaveJS keeps installing itself, then you need to adjust your Zwave JS integration installation or remove it to move forward. The integration on restart will install the Zwave JS addon if it doesnât exist on your system if you set it up to run with Zwave JS Addon and not ZwaveJS2MQTT.
Thatâs the old integration, remove that too. You should have no references to zwave in your configuration.
1 Like