-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Devices gone in z-way smarthome after reboot #156
Comments
First of all please upgrade to v3.1.1 and then if the erro still persists, please provide more info and evidance. |
Ok, but is 3.1.1 ready for Debian 10.6 Buster? This page says 3.0.0 for debian? |
Okey, you are right. Doesn't ubuntu version work btw? |
I updated using Ubuntu 3.1.0, and this problem is gone. 👍 |
That was'nt true after all, i'm still seeing this issue from time to time. |
Please provide logs from Z-Way start to idle state and specify which device is missing. We will check the log for errors |
Where do i find that log? |
If all are missing, Z-Way has failed to connect to the UZB1. Most probable is that the port changes from /dev/ttyACM1 to /dev/ttyACM0 or vice versa |
Log is in /var/log/z-way-server.log Also do dmesg and search for ACM - show those lines and +/- 5 around |
If thisi s the case, you can use udev to set constant tty name to the dongle |
That isn't the case, as the devices are there and working in "expert" GUI. Its just the smarthome GUI that is empty. I found the log, but it hasnt happend in a few days. I'll power cycle it tomorrow to test. |
When the unit is rebooted, the devices disappear from the rooms in the smarthome GUI. They come back when i restart the z-way-server.service manually.
The main devices still shows in the z-wave device list, but the configuration menu only has a "rename device" box, all options on child devices are gone.
I can still actuate devices in expert UI, so the network is running.
System:
Chromebox 1 running Debian Buster
UZB with lisence
Z-Way version 3.0.0
The text was updated successfully, but these errors were encountered: