finally made the jump to Z-Wave JS and it seems to be working rather well.
I’ve been looking everywhere but cannot seem to be able to find an add-in or something similar that allows me to map out my Z-Wave network.
Any ideas?
For the beginning, I’d even be happy with just to get he info which nodes every node is connected to.
It really isn’t that bad, especially compared to switching to Z-Wave JS from the older stuff. It uses the same add-on integration, just a different integration add-on.
I don’t remember having to go through any major renaming like the big migration to Z-Wave JS; just changing integrations add-on. IIRC, you do have to change the port, and there are a few differences noted here.
Apologies; indeed it does. It’s also changing the add-on, not the integration.
But my previous statement still stands; much easier than the initial migration from z-wave to z-wave js, and the only way to get a network map as far as I know.
Thanks for the hint - saw that I can actually turn off the MQTT part of it
Looks like there’s some functionality missing for the door/window sensor, but for now I can live with that - given that I have the nework map
Follow-up question:
Is there a way to (manually?) force a node to connect to the closest neighbor?
The Door Sensor is only 3 feet away from Receptacle 02 but I can’t seem to get it to connect through anything else but Receptacle 01. No matter how often I remove and add it to the network it keeps connecting through Receptacle 01 that is 20 feet and 2 walls away and it doesn’t work properly that way.
Has anyone found an addon to allow a graphical display of the Z wave network. I recently got Z wave JS running on home assistant and finally was able to add some nodes. I am trying to add a door lock in my outdoor kitchen which is about 40 feet away from the rear door of my house which has a door lock as well. So I added a light switch between the two door locks which is roughly halfway between the two door locks but am trying to figure out what path the farthest door lock is taking. I am having issues with getting the door lock on the outdoor kitchen to connect
As suggested above, I’m using Z-Wave JS to MQTT - works fine for me (MQTT Gateway disabled).
You can see what the network map looks like in my previous post.
Sorry to revive this thread… but are you saying to run Z-wave JS and Z-wave JS to MQTT (MQTT disabled) side by side? I would love to have the mapping feature as well, but I am happy with Z-wave JS. I only have 2 devices so far, but I expect to have more motion sensors and other devices as I migrates some use cases away from zigbee.
No, you can only use one add-on at a time with the same controller. The mapping feature is basically useless, but the health check functionality it also provides is very helpful.
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
Add-on: Z-Wave JS UI
Fully configurable Z-Wave JS gateway and control panel
-----------------------------------------------------------
Add-on version: 1.4.2
You are running the latest version of this add-on.
System: Home Assistant OS 9.4 (amd64 / generic-x86-64)
Home Assistant Core: 2023.1.4
Home Assistant Supervisor: 2022.12.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-zwave-js-ui: starting
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-nginx successfully started
s6-rc: info: service init-zwave-js-ui successfully started
s6-rc: info: service zwave-js-ui: starting
s6-rc: info: service zwave-js-ui successfully started
s6-rc: info: service discovery: starting
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
[12:31:13] INFO: Starting the Z-Wave JS UI...
./run: line 16: ./discovery: No such file or directory
2023-01-14 12:31:14.724 INFO APP: Version: 8.6.2
2023-01-14 12:31:14.727 INFO APP: Application path:/opt
______ __ __ _ _____ _ _ _____
|___ / \ \ / / | |/ ____| | | | |_ _|
/ /____\ \ /\ / /_ ___ _____ | | (___ | | | | | |
/ /______\ \/ \/ / _' \ \ / / _ \ _ | |\___ \ | | | | | |
/ /__ \ /\ / (_| |\ V / __/ | |__| |____) | | |__| |_| |_
/_____| \/ \/ \__,_| \_/ \___| \____/|_____/ \____/|_____|
2023-01-14 12:31:14.738 WARN STORE: scenes.json not found
2023-01-14 12:31:14.739 WARN STORE: nodes.json not found
2023-01-14 12:31:14.739 WARN STORE: users.json not found
2023-01-14 12:31:14.745 INFO APP: Listening on port 44920 host 0.0.0.0 protocol HTTP
2023-01-14 12:31:14.830 INFO MQTT: MQTT is disabled
2023-01-14 12:31:14.833 WARN BACKUP: Store backup is disabled
2023-01-14 12:31:14.833 WARN BACKUP: Nvm backup is disabled
2023-01-14 12:31:14.834 WARN Z-WAVE: Z-Wave driver not inited, no port configured
[12:31:15] INFO: Starting NGinx...