forum

Here's what I understand about Z-Way backups. Hopefully, @PoltoS will consider filling in the blanks. Z-Way has 2 different backups. The first backup uses the smarthome UI and downloads a .zab file. The second backup uses the expert UI and downloads a .zbk file. The 2 backup files serve different pu...

You done good. Hopefully @PoltoS has time to respond and provide an answer. This is why the z-way-server died: Thread 7 "zway/core" received signal SIGSEGV, Segmentation fault. If I was in your shoes, I would simply install a clean version of Z-Way. Perhaps a file on your old SD card got c...

Hmm, I would have expected the default pi password (raspberry) to work. Here's a link to the generic procedure for resetting the pi password: https: //howtoraspberrypi.com/recover-password-raspberry-pi/ Note that you will need a PC to modify a file on the SD card and you'll need to plug in a USB key...

It looks like new SD card is working fine and you've followed the commands per the suggestion by @PoltoS. I think the instructions by @PoltoS could have been written more clearly. I'll try to add some clarity: 1. As user pi, at the linux command line run: sudo su - You should now have a linux root p...

The mystery continues... At this point, you've confirmed the z-way-server process died (evidenced by the log file stopping at 3:00, port 8083 being closed and your python traceback reporting the connection to Z-Way fails which is logical since port 8083 is closed), but the cause remains unknown. The...

The output from the commands all look normal. As best as I can tell, you confirmed the problem is not software related. Instead of cloning your old SD card onto your new SD card, you might want to backup your Z-Way using the smarthome and expert UI, do a virgin install of Z-Way onto your new SD card...

Jessie is not supported by newer versions of Z-Way software. As a result, you'll need to upgrade your Raspberry Pi from Jessie (based on Debian 8) to either Buster (Debian 10) or possibly Bullseye (Debian 11). Upgrading the OS is going to take some effort, especially if you follow the apt dist-upgra...

A guess... The z-way log file shows: [2022-01-10 02:59:00.258] {I} [zway] Saving configuration data to config/zddx/cf22bda8-DevicesData.xml [2022-01-10 03:00:00.875] [E] [zway] Dropping packet to myself (node 1) The file cf22bda8-DevicesData.xml is likely quite large (check: ls -l /opt/z-way-server/...

In addition to checking linux cron jobs that run at 3:00, here's a couple of ideas: 1. Check Z-Way's internal cron jobs: curl -s -u admin:[ADMIN PASSWORD] 127.0.0.1:8083/ZAutomation/api/v1/instances/Cron The json output is virtually impossible to interpret, so I use an online json pretty printer to ...

This doesn't solve the problem, but it's a quick and easy way to help recover from "surprises". Add a daily cron job that takes creates a tar file of Z-Way's config data: 59 23 * * * /bin/tar cf /opt/z-way-server_`/bin/date +%a`.tar /opt/z-way-server/config/zddx /opt/z-way-server/automatio...