forum

Back in business now. Complete reinstall and a not to old backup restore gave me a slow start. Had to reinvent all automations including mqtt subscriber setup. Works great after some days.
Created a new backup.

from log file [2024-12-14 11:42:18.432] [core] Executing script: /*** Z-Way Home Automation Engine main executable ***************************** ... [2024-12-14 11:42:18.541] [core] Executing script: // Comon utilities and functions ... [2024-12-14 11:42:18.607] [core] Executing script: // This scri...

managed to blank the whole json file

what do i do then?

how do I reinstall z wave with minimum hazle?

Managed to delete the very long password. But cannot access anyway.
Should I insert the password in the file instead of leaving it blank ?

Hello Due to some electrical work my raspi were cycled uncontrolled a few times. Now I cant access the zwave trough zboxweb or local ipadress due to "Remote access not possible or wrong password" I can access the pi trough putty and have restarted zwave. any command trough putty that can s...

Well Here is more serious problem. Changed router today with new ip addresses. The PI persisted to the old ip address and I tried an IP release before booting up again (lan). Now I cant find the PI trough the old or the new network. therefore cannot ssh either. is it possible to connect a pc with rj...

pi@raspberrypi:~ $ ip a ; ip l 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred...

I have the same issue; however upgrade to 4.1.4 worked through the error messages.
ref: https://forum.z-wave.me/viewtopic.php?f=3417&t=36013

Upgrade to 4.1.4 trough the interface worked, but the same error message occured during the process, I.e. no upgrade in process window active.
After upgrade, the select z-way restart in the system/advanced menu brings up the same error message as before..
Not fixed then ?

Best regards

this problem still persists.
had to do a sudo update and upgrade to get to 4.1.3 today

any clues how to make the menu work as intended yet?