Switching from Zwave 1.4 (Deprecated) to ZWave JS UI (formerly ZwaveJS2MQTT)

Irek_Malinowski · November 17, 2021, 12:30pm

thanks
but how to delete or remove it?
does it interfere the zwavejz2mqtt?

petro · November 17, 2021, 12:39pm

Remove the integration for ZwaveJS. Then remove the addon for ZwaveJS. Restart.

You do not need to remove ZwaveJS2MQTT addon.

Irek_Malinowski · November 18, 2021, 3:49pm

OK after 2 days most of the nodes started to show up but now i am left with so many entities in the areas on Overview.
Is there a chance to remove it? I do not se where

petro · November 18, 2021, 5:45pm

From the entities list, remove all the unavailable ones. There should be a bulk way to do it. Configuration → entities. Then sort by unavailable.

Irek_Malinowski · November 18, 2021, 8:17pm

Unfortunately i can not remove them

when i see areas lis tit shows that there are entities there

But when i enter the Area it shows no entities

rct · December 8, 2021, 9:14pm

Unless, I’m misunderstanding something, the information on migrating the network key appears out of date as of 0.27.0 - there are now 4 keys:

S2 Unauthenticated
S2 Authenticated
S2 Access Control
S0 Legacy

The docs say to enter both S0 and S2 keys even if not using S2, but doesn’t give any guidance on migrating the network key.

** NOTE: ** If I paste my key in both S0 Legacy and any of the other S2 key fields, there is a driver warning that shows up in the UI which looks somewhat innocuous, but it will NEVER connect to the USB device.

Instead of connecting/starting up, the log just shows:

WARN ZWAVE: Retry connection in 3 seconds...
WARN ZWAVE: Retry connection in 3 seconds...
WARN ZWAVE: Retry connection in 3 seconds...

Now that I’ve got only the S0 legacy key defined, everything finally starts up. However, I’m getting a warning from interviewing my Zwave locks:

Driver: Node 026 supports Security S2, but no S2 network keys were configured. The interview might not include all functionality.

freshcoast · December 8, 2021, 10:11pm

The old “network key” is the S0 Legacy key.

rct · December 9, 2021, 12:41am

Thanks for confirming that. I had pretty much figured that out. The surprise was that adding the same key to the other fields would prevent Zwave2MQTT from connecting to the USB stick without much warning.

@petro - Thanks for the helpful guide. It might be worth updating the guide to mention the S0 Legacy Key as the correct place to copy over the network key.

rct · December 9, 2021, 12:54am

This has probably been discussed elsewhere, but I’m having trouble finding it.

What are the advantages of renaming devices in Home Assistant instead in the Zwave2MQTT UI?

It looks like the advantages of renaming the device in Zwave2MQTT are:

The names will be available in the Zwave2MQTT dashboard and network graph view. The ambiguity if you have a lot of the same devices will be removed.
If one does use the MQTT interface for some reason, the devices will be correctly named.

gwijsman · December 12, 2021, 1:19pm

I encountered the same issue
the old key is S0 legacy
the other 3 I just generated with the generate button
worked fine for me

gwijsman · December 12, 2021, 1:20pm

Thanks for the useful thread! it really helpted me, tnx

Ezekiel · January 25, 2022, 1:20pm

Does anybody know you you can use multiple entities for the zwave_js.refresh_value service.

I need to poll for data every 30 minutes but was thinking I could stop that and just do an automation instead.

The idea is to be able to align the collection at 30 minutes and 0 minutes on the hour rather than polling which I think is just 30 minutes from when the changes were saved so it could be polling at 15 minutes and 45 minutes in the hour.

If I can do this my automation action list is going to be huge but if I can bulk list my entities it would be cleaner.

Thanks again

petro · January 25, 2022, 1:25pm

check out the docs, they explicitly say zwave_js.refresh_value excepts a list of entity_id’s.

Ezekiel · January 25, 2022, 1:38pm

Thanks Petro.
Just a follow up question around the syntax

For this example
service: zwave_js.refresh_value
data:
entity_id: sensor.kitchen_powernode_fridge_energy

Do I put a , and then the next entity after the fridge_energy

or do I list the entity IDs one after the other

service: zwave_js.refresh_value
data:
entity_id: sensor.kitchen_powernode_fridge_energy
entity_id: sensor.kitchen_powernode_dishwasher_energy

or change entity_id for entities?

petro · January 25, 2022, 1:44pm

It’s no different than any other entity_id field. Have you used other services with multiple entities?

Ezekiel · January 25, 2022, 1:47pm

I don’t think so… Or if I have maybe it’s been a group so I haven’t called them out individually.

Happy to play around just if you had an answer on how the list would be that would be great.

Thanks again for the fast replies.

petro · January 25, 2022, 1:48pm

Have you defined a group in yaml before?

petro · January 25, 2022, 1:49pm

Basically, yaml is identical everywhere. Defining listed items does not change from one field to another. It’s all the same. I’m trying to see how much yaml you know.

finity · January 26, 2022, 4:25am

service: zwave_js.refresh_value
data:
  entity_id: 
    - sensor.kitchen_powernode_fridge_energy
    - sensor.kitchen_powernode_dishwasher_energy

or you could separate them with a comma as well

service: zwave_js.refresh_value
data:
  entity_id: sensor.kitchen_powernode_fridge_energy, sensor.kitchen_powernode_dishwasher_energy

But I find the "-’ list easier to read tho.

Ezekiel · January 26, 2022, 10:20am

Hi Petro,

yes I have and you also helped me with creating groups based on key words in the entity name.
Are you suggesting I can use that same technique and create another group of zwave energy entities and call the service against that group?