@RickKramer thanks indeed that setting solved
Iâm finding that I canât seem to change the mot important settings in the json for the device.
Right now my device is shown in the UI as âswitch_switchâ which I think is based on json âid:â. but I canât change that entry.
I was able to modify some of the other field successfully but not that one.
Is there some limitation on changing that field?
I can see the issue of adding more switches and if all of them are labeled âswitch_switchâ then it will be a bear to discern which one is which.
It looks like that works off MQTT discovery, so the outdoor_outlet_plug is what youâd want to focus on where the ID is most likely something that is auto generated. Just my 2c.
Iâm the one who changed those values to âoutdoor_outlet_plugâ. Before it was something like ânodeID_2_switchâ.
So I could change those vales and once I jumped thru some âdiscovery hoopsâ in HA I finaslly got HA to accept the updated name and entity_id. SO HA is actually good now, I thinkâŚ
Itâs just the representation of the device in the HA discovery UI that is what Iâm trying to fix.
But you know what, now that I think about it some more I really shouldnât care what it says there because the node is already specified in the Node list and itâs name is there already.
Still, Iâm not sure why I can update everything else Iâve tried to specify in that json data except that(those) field(s).
Iâm not sure what you mean by âItâs just the representation of the device in the HA discovery UI that is what Iâm trying to fix.â. With discovery, the âunder the hoodâ keyed name is unique_id. Everything else is mailable. The ID in that JSON doesnât appear to do anything for discovery so I assume its for zwavejs2mqtt.
FYI, for discovery, this bit is the only bit that matters:
If you have the time, read up on the basic MQTT discovery (you might see use cases for it outside zwave2mqtt, I use it for storing states long term that last restarts).
Is it possible to easy migrate from official 1.4 zwave integration and keep entities names?
Sorry, the top part that explains what I mean was cut off in that screen shot.
Once you click on a node in the node list it brings up that part that I posted above with all of the entities that get discovered in HA below the node list.
Here is the screen with the node list at the top showing node 2 (the selected switch device):
The âHA discovery UIâ I was referring to is that whole table at the bottom labeled âHome Assistant - Devicesâ.
I was thinking that a generic âswitch_switchâ designation there would end up being hard to follow which devices were which. But like I said, it wonât be a problem since the node number and name are already listed in the node listing and HA devices table at the bottom is based solely on the node you click on in the node list
1 Like
Just created a new topic specific to installation and configuration: ZWavejs2mqtt installation
Any help would be appreciated!
Only if you manually modify the json info in the âHome Assistant - Devicesâ section I am referring to in the last few posts.
None of the entity information for HA is stored on the zwave controller. And the only thing zwavejs has access to is the info stored on the controller.
This is the missing thing, to go and migrate. With 20+ nodes it is not worth the time
I think that whichever way HA goes when it is time to migrate youâll probably be in the same boat.
Would you mind taking a screen shot of your entire UI settings for some of us to try and work off since you were able to successfully implement it.
Hi thereâs not much more than what is on the github,
Also : you can follow same instructions as zwave2mqtt. very similar config
I dunno, I feel like there were about 40 different config variables, the instructions were like, in the mqtt section, âhost: this is the hostnameâ
Thereâs not exactly a step by step.
Iâll go see if i can find a step by step for zwave2mqtt, as i agree that it has mostly the same settings.
I currently have zwave2mqtt installed and tried to Lock Manager only to find out it doesnât support Set User Code. Does anyone who has tried the JS version know if that command is supported?
1 Like
The underlying library, zwave-js, does support setting user codes. Iâm not sure if the MQTT links are set up to handle it though.
This will 100% be supported with the new z-wave js integration thatâll have a beta release in 2021.2, i was just looking at a PR adding it yesterday or the day before.
1 Like
+1 for the need to add support for remote serial connections (either via socat or rfc2217)
Current lack of support is indeed a major pain.
Trying to decide on a direction. As mentioned I currently have zwave2mqtt installed but itâs missing the user set code feature for locks and I am uncertain if there is a plan to add it. Sounds like zwavejs2mqtt might be getting that feature shorty but as I understand it zwavejs2mqtt is still new so could have stability issues, but OZW has the set code feature now.
-
Do I move to OZW as from what I read that may be the longer term official Home Assistant direction?
-
Do I move to zwavejs2mqtt and complete my cutover and wait for the user code feature? Not in a hurry but really looking to use this so I know who unlocked the door and can build the appropriate automations around it.
As Home Automation is a Hugh investment in time, I am hoping I can take a direction that will be long lived.
Zwave is a mystery for me as there are 4 options (OZW 1.4, OZW 1.6 Beta, zwave2mqtt, zwavejs2mqtt). In fact there are more, Smartthings is supported through an integration.
1 Like
I gave this a try, as I am running the current installation in a docker container I simply stop it and installed this.
Only have a few devices configured so far, I did have to request a node info and provide a name. But after doing that It appears to work fine. In fact a little better than zwave2mqtt. UI is basically the same, but perhaps better in some ways.