@JumpMaster Following your guide from above. Does Hass discovery work with the gateway disabled? I see there is a setting there for that. A bit confused why we don’t need the gateway whenever there are Hass-specific settings for it.
Before the new integration was ready, this was used to integrate it via MQTT in Homeassistant (same as zigbe2mqtt for example).
It supports both, but MQTT can be disabled.
well, I was too tempted… I did install the new add-on and integration, and right now have a 100% migrated set of devices and entities, with working Mqtt state_stream to my other instances 
yeah.
about those features to be added, where can we find the thoughts on that from the team? Ive added to the architectural thread on the deprecation just now, but maybe checking the features and contributing to that would be worth the while… I ask because I am not sure this is the correct thread for that, reading the current discussion
You have to use the UI of the Addon (not the one in HA):
In my opinion it’s much better than the old one.
is that the zwavejs2mqtt add-on? https://github.com/hassio-addons/addon-zwavejs2mqtt
seems much more powerful indeed from what I can spot there…
It’s from the official docker image. But as far as I know the add-on you linked comes with the same UI.
I am interested in this as well, I have a node red flow that figures the state of all my devices and lets me know of unresponsive devices. For ZWAVE that was an easy way to find out the state by using the zwave entity. I make a websocket call in node red currently for zigbee node status and I assume something similar could be done for zwavejs but idk yet.
I would image we have some access to the data since it shows up in the frontend under the device:
yes, all data (and maybe more…) is available in the system, you can see it when you ‘download a dump’ of the network
and open the zwave_js_dump.jsonl
hope this will be brought to the Frontend sometime soon.
- alias: livingroom_tv_scene_activation_triple_click
trigger:
- platform: event
event_type: zwave_js_event
event_data:
node_id: 2
scene_id: 0
value: 25
I am trying to get this to work with the zwave_js_event, but its not working. Not quite sure how to format it.
Everything is based on the entityID except for HA based automations. I don’t have many of those but I did have to go back in and pick the correct device again through the UI. My other automations use NodeRED or Appdaemon so those are both solely based on the entityID of the device so once the name is changed to the correct name then life is good.
One thing to note is if you have multisensor devices such as a Motion Sensor the device types don’t map straight across and in my case I monitor the alarm type sensor for motion and in OZW it shows up as a burglar device but in JS it shows up as a status and its usually disabled so I had to go enable it.
EDIT: On a side note this has now happened to me 2 days in a row where at some point over night all of my devices go unavailable in HA. Lucky for me I’ve been the only one who has been forced to take a cold shower these last 2 days due to this as the wife gets the hot water thats in the tank but I get a nice cold shower (sarcasm). Anyways the fix for this is to restart HA then it comes back to life. The other thing I’m noticing is sometimes JS forgets what a device is and I have to go in and tell it to go reinterview a node and then life is good. Anyone else experiencing this?
It took me a bit of screwing around with this but I finally got it. I just had to remove line by line until it worked like it was supposed to.
device_id: cff17fea6505d7a29a334695e96536cf
label: Scene 001
That is all I have in there for mine. If you have a device_id to work with try that. I tried it with just the node_id but couldn’t get the automation to fire.
Hi,
I seem to have cocked this up somehow. I have control of a couple of my items, but, generally speaking, the devices appear to be connected, but the corresponding all important light/switch entities show as unavailable?
Does anyone have any suggestions about why this might be or what I might have done wrong? 
Thank you,
James
My Yale YRD220 locks are working aside from showing their locked/unlocked status. Are other locks reporting this properly before I go too far down the hole on this?
Go into the node in ZwaveJS and tell it to reinterview the node
Then click the little arrow to the right and it will usually fix it.
1 Like
Thank you for this, but I can’t figure out how to do it. I’m using the add on and the integration. Are you suggesting I do this in the add on? (or the intergration!) If you could give me a pointer, I’d much appreciate it.
For the time being, I’ll keep looking for it!
Its in the addon so :8091 does that make sense? BTW I use HA core not HASSIO or Supervisor so my use is going to be a little diff than yours
Thanks - I’ve added a port to the network part of the add-on configuration, and currently restarting to see if I can access the add-on settings to do what you have described.
I think I’m having the same problem as some others. I shut down OZW, configured and fired up Zwave JS and all my wired devices came up instantly and work great. Just about everything Battery Powered shows ProtocolInfo under Interview status and just doesn’t seem to get a Completed there. I do see in the case of motion sensors that they have values of True/False that are working in the Control Panel, but it seems like until the interview process is Complete the integration won’t assign an entity. I’ve had a motion sensor in front of me at my desk for an hour and it never completed even with the constant tripping.