No YOU are wrong, I am unable to type in my devive path…I have to use whatever is listed in the drop down…
click the 3 dots… and edit as yaml. You need a chill pill.
No you take a chill pill and take ownership of what you write…
3 Likes
So the UI should still permit usb_path: tcp://192.168.1.101:4000?
Well, usb_path is for the old configuration. I was unsure what that guy was talking about because it seemed like he was here to just complain. The yaml version of the addon should be device. I do not know if it supports TCP. I know the backbones support it.
It sure didn’t for me yesterday @petro , using the latest version. I used the Edit Yaml menu and Z-Wave-JS refused to accept tcp:// as a device. Z-Wave-JS-MQTT .4.1 accepted it just fine, and all is well.
Yah, I’d write up an issue against the Zwave JS Addon then. Because node-zwave-js supports TCP from what I’ve seen from the code (I could be wrong on that too as I haven’t tried it).
Well, 1 question… Did you try putting it in quotes?
device: "tcp://192.168.1.101:4000"
Thanks.
So it appears the UI did change as when I first installed it I could just type my path in the field. I’m not using that now as I changed to MQTT so I cannot look at the current basic UI. That’s what’s confused @ccollinscj. Now you have to go into yaml mode to edit it?
Only if it’s not a usb device that’s detected.
Sure did - tried both single and double. Interestingly, when entering it without quotes, config flow added a single quote automatically, and as you continue to type the rest of the string, would start to overwrite what I had entered. Kinda weird. but anyway, I tried many many times with every variation I could think of to get it to accept it, to no avail.
Ok. The UI should really just let you type what you want and have a three dot option to present a list of local devices, should you not have a clue as to what to enter!
Thanks, will do!
1 Like
I closed my issue as it’s already being looked at in PR https://github.com/home-assistant/addons/pull/1835
I’ve the same resut. Fibaro roller shutter and switch appears and works, but i’ve multiple motion sensor (fibaro) and contact sensor (fibaro - NeoCoolCam) which works fine with OpenZWave plugin that appears as NODE NN with z-wave js without any device/detail inside. I reverted back to OZW with a backup, i’ll try again the new platform in next months… hoping it will be fixed.
HA devs have just nixed supporting tcp:// in the core product. They deem it an advanced use case…
They appear to want to gear the product more towards simple minded users? If we can figure out how to code YAML, Jinja2, JSON, Python we can’t be that simple minded! Just let use use tcp:// in yaml and if we break it, we fix it…
Why not just use zwavejs2mqtt then? It’s basically the same thing and if it supports tcp, then you should be good to go