#ZWA-2 - Now What?

1 messages · Page 1 of 1 (latest)

swift pebble
#

Now that I've migrated to ZWA-2, what is the best way to exploit its capabilities in an existing network? Should I rebuild all its routes (ZUI -ZWA-2 > Advanced > Rebuild Routes) to enjoy the new longer/better mesh range? I presume it should eliminate at least some 2 and 3 hop connections if it is told to try. Yes? Anything else? Re-interview all 66 nodes perhaps?

true patio
#

There would be no reason to re-interview nodes solely from a controller migration.

swift pebble
#

The go.nabucasa link in the ZWA-2 device mailer missed that. Maybe its in the missing Step 3 on the link

#

I modified my docker config to point at the new /dev/serial/by-id device which is how I got the ZWA-2 assigned Node-ID 1, and from which I could do an NVM restore.. That's another post 🙂

#

After manually rebuilding routes, I don't see any material differences from my ZOOZ controller. Its odd though, that the network graph in HA > Devices > Zwave ... show a number of unconnected devices. The ZUI network graph, not so, but much obtuse

#

And its odd that the HA integration shows battery devices as forwarding nodes below (Garage 4-in-1 for example

true patio
#

Pretty sure the HA integration Visualization is a work in progress. It's not accurate at all.

#

(at least I hope it's a WIP)

swift pebble
#

Fair enough. Are there any before / after ZWA-2 network configuration topology improvement examples? I can't show any, so far.

true patio
#

I've heard of several, though I don't have the conversations at hand.

swift pebble
#

No worries. I'll play with the controller. The ZOOZ form factor has a much higher WAF than the candlestick. Absent a performance leap, I can only hide it behind the couch for so long

signal otter
true patio