core: Z-Wave JS: Can no longer enter tcp://192.168.1.101:4000 as my device...
Checklist
- I have updated to the latest available Home Assistant version.
- I have cleared the cache of my browser.
- I have tried a different browser to see if it is related to my browser.
Describe the issue you are experiencing
When this integration was first released I could enter tcp://192.168.1.101:4000 as my device. Now I cannot and the UI only presents a list of local devices to choose from. I’ve been informed that the backend code still supports tcp:// Please fix the UI.
Describe the behavior you expected
Ideally, if you want to stick with a list selection, add Network as an option and let the user enter the IP and the port (that’s how HomeSeer does it).
2nd option: Remove the mandatory local devices list and let the user type what they want in the field. There could be a three dot option to present a list of local devices to choose from should the user not have any idea what to put in the field.
Steps to reproduce the issue
- Device entry only permits selecting from a list of local HA devices.
What version of Home Assistant Core has the issue?
core-2021.2.3
What was the last working version of Home Assistant Core?
core-2021.2.0 ?
In which browser are you experiencing the issue with?
No response
Which operating system are you using to run this browser?
Windows 10 20H2
State of relevant entities
N/A
Problem-relevant frontend configuration
N/A
Javascript errors shown in your browser console/inspector
N/A
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 26 (16 by maintainers)
We could add the option to expose the port to the core add-on, I don’t see the harm in that (actually helpful to expose a production instance for development purposes as well).
The Z-WaveJS2MQTT add-on, currently does provide the option to expose the port.
The built-in core Z-Wave JS add-on doesn’t currently expose the server outside the host where the add-on is running so it’s not possible at the moment, as far as I know and have tried, to connect to the add-on server from a different host (I’m not an add-on expert).
If the server is exposed to other hosts there’s nothing stopping us from connecting to the server from another host in the integration.
You can realise this by running a docker image with the server and setting the docker network settings appropriatly. There are many ways of course.
Hmmm, just a basic HA with Z-Wave-JS addon… Overcomes the inconvenience of keeping just a Z-WaveJS server up to date by utilizing HA to do it. Did not think of doing it that way! I’ll format a new SD card for the Pi with HA and give it a whirl…