It’s in hidden files in .storage in your config
No, I hot swapped them. Kept HA running, turned off Zwave js and turned on zwavejs2mqtt
Yeah, found it in core.entity_registry. Just trying to pull the data out now. I’m a little rusty.
1 Like
OK. Hot swap didn’t work for me, I had to restart HA core. Before integration was connected to the ws://core_zwave_js:3000, but zwavejs2mqtt has URL ws://a0d7b954-zwavejs2mqtt:3000
1 Like
OK, this isn’t pretty, and I’m sure someone could have knocked this out in Python in about 3 minutes, but since I don’t know Python that well, I resorted to old skool sed/awk. The following command works in a terminal on Home Assistant OS. Log in, go to the config/.storage directory and copy and paste, and run the command below. It will read the entity store and pull out the following information into a CSV file called entities.csv in the same folder, which you can open in Excel. It includes all enabled as well as disabled entities. This works great for the original zwave 1.4 integration. Don’t know about OZW 1.6. It will include automations, scripts, input booleans, etc., too, not just Nodes. Some of the mobile_app stuff is messy, but it is all there too.
node/unique id
entity_id
name
platform
icon
original_name
enabled/disabled status
sed 1,5d core.entity_registry | awk -v RS=" },\n" -v FS=" \"" '$0 ~ /entity_id/ {print $6 $2 $8 $7 $9 $15 $10}' | sed 's/.*: //;s/[",]//g;s/$/,/;s/[ ]*,//;s/node-//;s/\(^[0-9]\{1,2\}\)-[0-9]\{15,20\}/\1/' | awk -v RS="" -v FS="\n" '{printf "%s,%s,%s,%s,%s,%s,%s\n",$1,$2,$3,$4,$5,$6,$7}' | sed 's/null$/enabled/;s/user$/disabled/' | sort | awk 'BEGIN{print "node/UID,entity_id,name,platform,icon,original_name,enabled"} {print}' > entities.csv
2 Likes
Hello,
This key formating issues gave me the error when installing the add-on:
Aborted
Missing Z-Wave JS add-on discovery info.
removed the leading and trailing " and the 0x seems to fix it.
Is there any way to invert a shutter controller , like in the old integration in the yaml? like ‘cover.roller_shutter_2_current_value:
invert_openclose_buttons: true
invert_percent: true’’
?
Paring my 3 Fibaro FGSD-002 Smoke detectors, one went in without problems with 9 sensors. I still have not been able the get the other two completely in, meaning they end up with only 3 sensors, lacking the rest.
Looks like you have to delete the node, and retry several times, just remember to give it plenty of time when you include. And keep the Fibaro close to the HA-box.
UPDATE: I used secure pairing.
UPDATE: If the integration does not respond. Try restarting the Z-Wave JS addon. And then look at the addon log while you press buttons on the itntegration. Somethimes the integration frezzez but you can see if something is happening in the log.
Did you do secure or unsecure inclusion?
I think I’m having a similar issue with my Flood Sensor (FGFS-101)
I don’t know if it can help, but it looks like it’s correctly working in zwavejs, when triggered/alarming:
INFO ZWAVE: Node 2: value updated: 156-1-state-5 true => false
INFO ZWAVE: Node 2: value updated: 156-1-severity-5 undefined => undefined
INFO ZWAVE: Node 2: value updated: 156-1-duration-5 undefined => undefined
Also, regarding the Zipato Mini Keypad, it’s not working for me yet in HA. Although lock/unlock operations are received by HA as zwave_js_event, I don’t know yet if there is some more tinkering to do (compared to zwave 1.4 or ozw), or if it is not yet fully supported by the new zwavejs integration.
There seems to be a couple related issues open on Github : https://github.com/home-assistant/core/search?q=“keypad+unlock+operation”&state=open&type=issues
I have the Zwave JS rolling now and it is very much faster.
I have a Telldus 102 switch that suddenly started to behave proper, don’t know why but sure is better.
Will there be a Zwave graph or similar showing the device paths?
I enjoyed that tool 
Zwave JS is a completely different zwave driver than OpenZwave.
There are no plans for this yet.
Thanks for all the great work you guys are putting in to this! 
If you use the zwavejs2mqtt add-on/container there is a built-in zwave graph included in there already.
I’m wondering if the nomenclature of the zwave elements we’ve been accustomed to in zwave 1.4 will be different in zwave-js. I assume there will still be entity_ids, and I believe Nodes are tied to the ZWave controller. Is there enough difference that perhaps a mapping between the two would be useful in planning for changes to configs, automations, etc.
BTW, this new page: https://www.home-assistant.io/integrations/zwave_js is fantastic! Very thorough and well-written. Kudos to the team and whomever wrote it.
I did have one question raised by the topic: My device does not automatically update its status in HA if I control it manually. Will certain devices behave DIFFERENTLY in zwave-js than in zwave 1.4? In other words, if all of my devices report physical changes currently under 1.4, can I expect the same behavior under zwave-js, or is there some underlying difference in zwave-js that may make them not respond.
Hello and thanks,
Is there a easy way to activate the zwavejsmqtt?
Is it added on top of the zwave JS add-on that I very recently went to from the deprecated version?
You can add it as an add-on but you have to disable the zwavejs add-on first.
You can’t have them both running at the same time.
Okey - that sounds easy enough - thanks!
So I can switch between the two then without ruining my system?
Same problem here as well. Z-Wave JS Integration doesn’t discover light or fan entities of LZW36