It’s not really a dilemma, and yes I know it is a simple sensor, but I would like to understand why this showed up after the transfer. I’m naturally curious and this was not expected. Assuming it was not by error, and instead as you say likely and entity that changes a property, I would like to know how to use/exploit it. I don’t spend a lot of time on Home Assistant but I do like to understand how things work however, there is not a lot of relevant current documentation since HA is constantly evolving. So we are left with asking questions on the forums in hope that someone in the know can explain it. That’s all.
I had to work through several issues in transferring the few devices I have and since the provided conversion script didn’t clean up everything, I also wanted to make sure I didn’t miss anything.
You’re way off the mark with your assumptions. That particular number sensor provides the ability to Set and Get the Basic Command Class value. If you don’t know what the Basic CC is, then you probably don’t need that entity. There’s a reason it’s disabled by default.
The new zwave platform exposes everything it can about your z-wave device. If you’re unfamiliar with the terminology that comes across, you should be googling the name after the colon with the keyword zwave. You’ll get all the information you need about the command classes that come through. You may not understand them, but you how have access to them.
OK, thanks, that’s all I needed. What through me off was entity id started with number, and the previous entity id had “any” tagged on so immediately thought this was something new that allowed me to group several sensors and respond if any went off. Been so long since I did anything with zwave, I never thought it had something to do with command class. I don’t need that functionality at the moment so I’m pretty set.
I have about 50 zwave devices in my home, but these constitute over 230 separate entities. Some of my zwave devices have 10+ entities associated with them.
I’d like to switch from Zwave 1.4 to Zwave JS, and can stomach renaming 50 devices, but would really like to avoid renaming every single entity. The way I used zwave 1.4 was to add devices, then stop homassistant, then rename the devices in zwcfg_*.xml, then delete the entities in .storage/core.{device,entity}_registry, then restart homeassistant. I know this isn’t really what you are supposed to do, but the only way to make my scripts and automations at all human readable is to have the devices themselves have vaguely human-readable names. I also like to cut and paste automations between different instances of a particular device, so it’s super useful just to be able to search and replace back_door for front_door, for example.
Is there any way, when moving to the zwave JS integration, to rename devices and have the names of the entities all be adjusted? I don’t mind doing ugly things like stopping homeassistant and editing files in .storage/*.
when you rename the device (any device not just zwavejs) the UI asks if you want to rename all of the entities as well. if you say yes the new entity id’s will be based on the new device name.
If you have your entity ids based on some standard then you might be able to find a method of renaming the device to end up with the desired entity id’s.
But I kind of doubt. zwavejs gives some non-intuitive entity ids as default. I think you will be forced to accept that you will just have a lot of manual renaming to look forward to.
Actually, I hadn’t realized this happens. Even though the rename is for the human-readable name, I think I can chose a human-readable name that ends up producing the exact same entity-ids I had before, which means I might be able to keep all my automations and scripts after editing 50 device names through the UI.
This is still nowhere near as convenient as doing it with a text editor in the .homeassistant directory, but I think it might be tolerable.
I suggest an update to this guide: at step 6, the network_key has to be filled in the s0_legacy_key, and the s2_*_key has to be left empty to that they are autogenerated at first start of the add-on
Just a quick question about network key. I never used one, since i had no use for encryption when i started with homeassistant.
Will migration work when no network key exist?
Search around in the Config/.storage directory for the network key. It was likely autogenerated when you first enabled zwave in HA. Without that key, you will not be able to connect to your zwave network. Write it down and store it somewhere safe.
I have successfully migrated to ZwaveJS from Zwave after having to factory reset my kwickset 888 locks and then re-adding them they all now work. The problem that I currently have is, in the old Zwave integration the lock status was reported as locked or unlocked, and how it was last locked in an attribute field. The attribute case that I was using was “Locked with Keypad by user 0” , which I would use as a trigger from any of the three locks to trigger a script that would lock all of the doors. So when leaving the house if you pushed the lock button on the outside of the door the automation would be triggered to lock all of the doors.
The problem that is now the lock doesn’t carry any “attributes” and the “status” is only locked or unlocked. I suppose I could use the status to trigger the script, but I am afraid it may error as the script executes and re-triggers the automation.
Is there a way that I can get the status of how the lock was “locked”, in the same manner as the old integration? I see there are more things that can be done in the background with the yaml but I am not quite up to that without some guidance.
Thanks
OK, I found out how to get the data that I needed to be able to all the doors, when the external lock button is pressed on one of the three locks. There is a Youtube video that shows how to get event data which is much more detailed than the status that is on the entity. I hope it is ok that I have linked the video here, if not then please delete and let me know.
Hello everyone. I’m trying to figure out what I am doing wrong with my migration. None of my devices will migrate. I entered my network_key that was in my configuration.yaml except I removed all of the commas and “0x” as the s0_legacy_key, left all other fields blank except for the usb path. I also tried with entering nothing, same result.
Just tried to do this after updating to the latest core today and I’m still stuck. Error is utterly useless. I finally found the “key” deep in the files and pasted it in the legacy key box, acted like it was starting then just didn’t work.
I have this same issue. Went through the migration wizard today after waiting months thinking everything would be stable and easy by now. But mine is also saying that none of the devices could be migrated and I’m now left with 60+ nodes that have to be renamed along with their entities. Not a great user experience and very frustrating considering the first post with the guide was over a year ago. I would have expected an automatic migration method by now.
I was not able to migrate Zwave on my HASS.IO during many months. Now I have the time.
I have 35 devices and 235 entities. The ZWave dongle is an Aeotec ZW090 Z-Stick GEN5.
I started to use the migration wizard, but I block on this. I woke up some device but the list remain like that, no any line disappear. (For the best result, wake the device up if it is battery powered and wait for this device to become ready.)
@seandavidson I also do not have a network key. When you left it blank, did you stumble on any issues while migrating? I’m dragging my feet with 79 zwave devices and 419 entities and this already seems the first hurdle.
@Tyfoon I did not have the network key and did not have issues. I did have to redo 1 that did not pick up but I followed the migration path and went very smooth.
