Problem with configuration? - all devices are failed

Discussions about Z-Way software and Z-Wave technology in general
Post Reply
jarek
Posts: 29
Joined: 09 Oct 2017 11:18

Problem with configuration? - all devices are failed

Post by jarek »

For no reason Controller thinks that all devices are failed - the last ok status is equal to the start of service. I tried to restart the system but it does not help :(
I cannot control any device. How to fix it?
In expert inteface there is a lot of failed jobs with message:

Code: Select all

Could not be delivered to Z-Wave stack
Version info:
http://192.168.0.111:8083/expert/#/network/controller :

Code: Select all

Role in Network
Node Id:	1
Home Id:	0xf8a5481c
Primary Role:	Yes
Primary Capability:	Yes
SUC/SIS in network:	1 (SIS)
Hardware
Vendor:	RaZberry by Z-Wave.Me
Vendors Product ID:	1024 / 2
Z-Wave Chip:	ZW0500
Firmware
Library Type:	Static Controller
SDK Version:	6.51.06
Serial API Version:	05.04
Capabillities:
UUID:	00000000000000000000000000000000
Subvendor:	0x0000
Nodes limit:	00
Controller Static API	
Allow max RF power	
Backup/Restore	
Battery save on sleeping	
Advanced network diagnostics	
Z-Wave Long Range	
Fast communications	
Change vendor ID	
Promiscuous mode (Zniffer)	
Full Zniffer	
RF jamming detection	
Capabillities:	slm
Software Information
Version number:	v3.2.2
Compile-ID:	101045968be0f00797fdc4d1a70e2955271fe4e7
Compile-Date:	2021-11-29 15:40:21 +0300
UI
UI version	v1.5.7
Built date	26-11-2021 01:37:55
micky1500
Posts: 298
Joined: 07 Feb 2016 16:29
Location: England

Re: Problem with configuration? - all devices are failed

Post by micky1500 »

Have you taken backups ?
Take some now !
Both types. Backup & Restore and Expert UI Backup.
Do a power cycle. not just a restart !
Good Luck.
Raspi 4 - (Buster - 32 Bit) Zwave Version 4.1.1, Raz 7 Pro, Serial API Version: 07.38
seattleneil
Posts: 172
Joined: 02 Mar 2020 22:41

Re: Problem with configuration? - all devices are failed

Post by seattleneil »

Adding on to the suggestions by @micky1500...

If shutting down and then power-cycling your Pi doesn't fix the problem, the contents of the z-way-server log file (by default, file /var/log/z-way-server.log) should show the cause of the problem.

When I encountered a similar issue, it was caused by a process trying to use the same serial port (/dev/ttyAMA0) that the controller card uses. The following command will show if there are any processes conflicting with Z-Way's use of the serial port: sudo lsof -n | grep AMA0

If the command returns a process that's not a z-way-server process, you have a configuration error on your Pi (most likely in /boot/cmdline.txt or /boot/config.txt due to a conflict related to the console or bluetooth).

Another possibility is a corrupt Z-Way configuration. Hopefully, you've downloaded backups (files ending in .zbk and .zab).
Post Reply