Where Does Z-Wave JS UI Store the Network Store?
Z-Wave JS UI network security keys and device cache paths for Docker and addon installs on home servers.
Last updated
Z-Wave JS UI keeps network state in a store folder. Docker installs default to /data/store with settings.json and node files inside. That folder holds security keys and device caches.
Network keys are the critical contents. They pair every device on the mesh. Back up the store folder with settings.json together. Losing keys means excluding and readding each device by hand. Heal operations rebuild mesh routes nightly. Debug logs trace inclusion failures clearly. Backups before firmware updates save pain. MQTT gateway bridges to other stacks.
Where Z-Wave JS UI stores this, by platform
/data/store (Z-Wave JS UI)
Network keys, node cache, and settings.json for container installs. Mount a volume here to survive updates. Keep keys private and off version control.
/data/store/settings.json
Settings file with store path and gateway options. Back up with the store folder. Addon installs keep parallel paths under Hass data.
Frequently asked questions
what do i back up for a Z-Wave move
Copy the store folder with settings.json for full moves. It holds network keys and node cache. The keys pair every device, so keep them private. Without keys the network must be rebuilt.
where is the Z-Wave JS UI store folder
Open the UI settings to read the store path. Docker defaults to /data/store with a volume. Addon installs keep equivalents under Home Assistant data. The settings file records the path.
Notice an outdated path? Let us know.