Which zwave stick are you using again?
There was a known issue with the 700 series sticks and a firmware update was released.
It’s a Zooz 700. I know there was a problem, I suppose I could get a new firmware from Zooz, but to install it I’d have to move the stick to a PC and use their software. And I’m afraid that if I did that, I’d lose the whole network and have to rebuild from scratch - resetting and re-including every device. I just know it.
make a backup of your stick and a backup of your cache.
Then recall both if you have to after you update the firmware.
EDIT: NVM backup and restore will take a long time if you have a large network.
I completed the firmware upgrade in place without moving my stick to another machine, it’s totally doable in linux.
EDIT: Also didn’t loose my nodes, they’re all intact.
What do you use in Linux?
Can I do it from Home Assistant OS? I thought HAOS was a bit permission-limited.
minicom here’s a nice walkthru to do the deed.
I don’t know if you can do that with HAOS, I’m sure there’s someway to get true SSH access but as I don’t use HAOS I couldn’t tell you.
Yes. I have 22 devices (so not a huge amount) but they are all either mains powered or powered via USB. The network is super stable other than a couple of very old devices which need a reboot every few months. I’m using plain Z-Wave JS.
Plain Zwave JS, 3 power outlets, 15 multisensors, 10 door/window sensors, 1 Z-uno based relay board.
Stable and superfast, never misses a trigger, never any delay. Only had problems in the past with migration / updates on Zwave integration.
I’m very happy with my choice for Zwave.
And this morning, another device is offline. Again, it’s Leviton. And again, re-starting the ZWaveJSMQTT add-on brought it right back.
If my problems do turn out to be with Leviton devices, I guess that would be good news, and bad.
If this problem is in the Leviton firmware, and the device is taking itself offline, why does re-starting the add-on bring it back?
I have the log file, but I must be blind, as I can’t see any way to attach a file to a post here3.
My man, I’ve said this multiple times and it seems you keep ignoring me. Can you PLEASE post logs. Please please please please. This will help us figure out what’s happening. Next time it happens, download the logs from ZwaveJS2MQTT and share them. Use HA to let us know roughly what time they went unavailable.
Click the store.
Click the gear.
Click the download button.
The zip file will contain todays ZwaveJS2MQTT log and ZwaveJS log.
I’m not ignoring you. The devices that tend to go offline don’t get used every day, so I don’t immediately know when I’ve lost one, so I don’t know which log file to use. Today, I noticed one offline this morning, and grabbed the most recent log. But like I just said, I’ve looked all over this post editor and can’t see how to attach a file. Clearly it’s right in front of me and I have a hole in my retina at that point.
Drag and drop
Edit: it might be copy/paste
There are Leviton firmware updates. I don’t know if they’d solve your problems or not. When the driver restarts, it pings all of the nodes. The act of pinging will bring the node back alive if it responds. Instead of restarting, you can just try the Ping button for those devices.
Last time this happened I tried ‘ping’ without success. But next time I’ll try it again.
LOG FILE: Tried drag/drop, and the “upload” icon but they only accept image files. The log is almost a megabyte, that’s a lot of pasting. I tried, but it just crashed the editor and I got “page unresponsive”. Seriously, there has to be a way to attach a file here but I admit I can’t find it. Maybe a link to a file transfer site is the only way.
Yeah, I thought that might happen. We used to be able to drop files here, up to 3 mb. That might have been disabled.
If you store a history for the lights that go unavailable, you should be able to identify a time that it goes unavailable. Then copy/paste an hour or 2 around that time here with the posted time.
e.g.
History shows it went unavailable on May 18 at 8:47PM. It’s Node 15, an outdoor receptacle controlling lights. I think that couple of minutes earlier, a motion detection event triggered an automation which turned that receptacle ‘on’ for a couple of minutes, then ‘off’. And it seems to have gone unavailable at roughly the time it was turned off. However I do not, at first glance, see anything relevant in the log. Here is the surrounding log.
2022-05-18T20:42:28.050Z SERIAL « 0x011500a80001140c7105000000ff07070377060000c664 (23 bytes)
2022-05-18T20:42:28.054Z CNTRLR [Node 020] [~] [Notification] notificationMode: “push” [Endpoint 0] [internal]
=> “push”
2022-05-18T20:42:28.057Z SERIAL » [ACK] (0x06)
2022-05-18T20:42:28.060Z DRIVER « [Node 020] [REQ] [BridgeApplicationCommand]
│ RSSI: -58 dBm
└─[NotificationCCReport]
notification type: Home Security
notification status: 255
notification state: Motion detection (location provided)
event parameters: 0x770600
2022-05-18T20:42:28.064Z CNTRLR [Node 020] [~] [Notification] Home Security[Motion sensor status] [Endpoint 0]
: 0 => 7
2022-05-18T20:42:43.246Z SERIAL « 0x010f00a8000102063105012a036e00b29d (17 bytes)
2022-05-18T20:42:43.249Z CNTRLR [Node 002] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2022-05-18T20:42:43.253Z CNTRLR [Node 002] [~] [Multilevel Sensor] Air temperature: 87.8 => 87.8 [Endpoint 0]
2022-05-18T20:42:43.256Z SERIAL » [ACK] (0x06)
2022-05-18T20:42:43.259Z DRIVER « [Node 002] [REQ] [BridgeApplicationCommand]
│ RSSI: -78 dBm
└─[MultilevelSensorCCReport]
type: Air temperature
scale: Fahrenheit
value: 87.8
2022-05-18T20:43:16.684Z SERIAL « 0x010e00a800011405310503010300c6ba (16 bytes)
2022-05-18T20:43:16.686Z CNTRLR [Node 020] [Multilevel Sensor] Illuminance: metadata updated [Endpoint 0]
2022-05-18T20:43:16.690Z CNTRLR [Node 020] [~] [Multilevel Sensor] Illuminance: 3 => 3 [Endpoint 0]
2022-05-18T20:43:16.694Z SERIAL » [ACK] (0x06)
2022-05-18T20:43:16.696Z DRIVER « [Node 020] [REQ] [BridgeApplicationCommand]
│ RSSI: -58 dBm
└─[MultilevelSensorCCReport]
type: Illuminance
scale: Percentage value
value: 3
2022-05-18T20:43:44.720Z SERIAL « 0x010f00a8000102063105012a036e00b39c (17 bytes)
2022-05-18T20:43:44.723Z CNTRLR [Node 002] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2022-05-18T20:43:44.726Z CNTRLR [Node 002] [~] [Multilevel Sensor] Air temperature: 87.8 => 87.8 [Endpoint 0]
2022-05-18T20:43:44.729Z SERIAL » [ACK] (0x06)
2022-05-18T20:43:44.732Z DRIVER « [Node 002] [REQ] [BridgeApplicationCommand]
│ RSSI: -77 dBm
└─[MultilevelSensorCCReport]
type: Air temperature
scale: Fahrenheit
value: 87.8
2022-05-18T20:44:16.753Z SERIAL « 0x010e00a800011405310503010400c6bd (16 bytes)
2022-05-18T20:44:16.756Z CNTRLR [Node 020] [Multilevel Sensor] Illuminance: metadata updated [Endpoint 0]
2022-05-18T20:44:16.760Z CNTRLR [Node 020] [~] [Multilevel Sensor] Illuminance: 3 => 4 [Endpoint 0]
2022-05-18T20:44:16.763Z SERIAL » [ACK] (0x06)
2022-05-18T20:44:16.766Z DRIVER « [Node 020] [REQ] [BridgeApplicationCommand]
│ RSSI: -58 dBm
└─[MultilevelSensorCCReport]
type: Illuminance
scale: Percentage value
value: 4
2022-05-18T20:44:46.212Z SERIAL « 0x010f00a8000102063105012a036e00b29d (17 bytes)
2022-05-18T20:44:46.215Z CNTRLR [Node 002] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2022-05-18T20:44:46.218Z CNTRLR [Node 002] [~] [Multilevel Sensor] Air temperature: 87.8 => 87.8 [Endpoint 0]
2022-05-18T20:44:46.222Z SERIAL » [ACK] (0x06)
2022-05-18T20:44:46.225Z DRIVER « [Node 002] [REQ] [BridgeApplicationCommand]
│ RSSI: -78 dBm
└─[MultilevelSensorCCReport]
type: Air temperature
scale: Fahrenheit
value: 87.8
2022-05-18T20:45:16.683Z SERIAL « 0x010e00a800011405310503010400c6bd (16 bytes)
2022-05-18T20:45:16.686Z CNTRLR [Node 020] [Multilevel Sensor] Illuminance: metadata updated [Endpoint 0]
2022-05-18T20:45:16.698Z CNTRLR [Node 020] [~] [Multilevel Sensor] Illuminance: 4 => 4 [Endpoint 0]
2022-05-18T20:45:16.702Z SERIAL » [ACK] (0x06)
2022-05-18T20:45:16.703Z DRIVER « [Node 020] [REQ] [BridgeApplicationCommand]
│ RSSI: -58 dBm
└─[MultilevelSensorCCReport]
type: Illuminance
scale: Percentage value
value: 4
2022-05-18T20:45:47.710Z SERIAL « 0x010f00a8000102063105012a036e00b29d (17 bytes)
2022-05-18T20:45:47.712Z CNTRLR [Node 002] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2022-05-18T20:45:47.715Z CNTRLR [Node 002] [~] [Multilevel Sensor] Air temperature: 87.8 => 87.8 [Endpoint 0]
2022-05-18T20:45:47.719Z SERIAL » [ACK] (0x06)
2022-05-18T20:45:47.722Z DRIVER « [Node 002] [REQ] [BridgeApplicationCommand]
│ RSSI: -78 dBm
└─[MultilevelSensorCCReport]
type: Air temperature
scale: Fahrenheit
value: 87.8
2022-05-18T20:46:16.684Z SERIAL « 0x010f00a8000114063105012200ea00c670 (17 bytes)
2022-05-18T20:46:16.687Z CNTRLR [Node 020] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2022-05-18T20:46:16.693Z CNTRLR [Node 020] [~] [Multilevel Sensor] Air temperature: 23.3 => 23.4 [Endpoint 0]
2022-05-18T20:46:16.697Z SERIAL » [ACK] (0x06)
2022-05-18T20:46:16.700Z DRIVER « [Node 020] [REQ] [BridgeApplicationCommand]
│ RSSI: -58 dBm
└─[MultilevelSensorCCReport]
type: Air temperature
scale: Celsius
value: 23.4
2022-05-18T20:46:16.704Z SERIAL « 0x010e00a800011405310503010600c6bf (16 bytes)
2022-05-18T20:46:16.705Z CNTRLR [Node 020] [Multilevel Sensor] Illuminance: metadata updated [Endpoint 0]
2022-05-18T20:46:16.707Z CNTRLR [Node 020] [~] [Multilevel Sensor] Illuminance: 4 => 6 [Endpoint 0]
2022-05-18T20:46:16.710Z SERIAL » [ACK] (0x06)
2022-05-18T20:46:16.711Z DRIVER « [Node 020] [REQ] [BridgeApplicationCommand]
│ RSSI: -58 dBm
└─[MultilevelSensorCCReport]
type: Illuminance
scale: Percentage value
value: 6
2022-05-18T20:46:49.193Z SERIAL « 0x010f00a8000102063105012a038000b574 (17 bytes)
2022-05-18T20:46:49.196Z CNTRLR [Node 002] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2022-05-18T20:46:49.200Z CNTRLR [Node 002] [~] [Multilevel Sensor] Air temperature: 87.8 => 89.6 [Endpoint 0]
2022-05-18T20:46:49.203Z SERIAL » [ACK] (0x06)
2022-05-18T20:46:49.206Z DRIVER « [Node 002] [REQ] [BridgeApplicationCommand]
│ RSSI: -75 dBm
└─[MultilevelSensorCCReport]
type: Air temperature
scale: Fahrenheit
value: 89.6
2022-05-18T20:47:16.682Z SERIAL « 0x010e00a800011405310503010600c6bf (16 bytes)
2022-05-18T20:47:16.685Z CNTRLR [Node 020] [Multilevel Sensor] Illuminance: metadata updated [Endpoint 0]
2022-05-18T20:47:16.689Z CNTRLR [Node 020] [~] [Multilevel Sensor] Illuminance: 6 => 6 [Endpoint 0]
2022-05-18T20:47:16.693Z SERIAL » [ACK] (0x06)
2022-05-18T20:47:16.696Z DRIVER « [Node 020] [REQ] [BridgeApplicationCommand]
│ RSSI: -58 dBm
└─[MultilevelSensorCCReport]
type: Illuminance
scale: Percentage value
value: 6
2022-05-18T20:47:50.681Z SERIAL « 0x010f00a8000102063105012a036e00b29d (17 bytes)
2022-05-18T20:47:50.683Z CNTRLR [Node 002] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2022-05-18T20:47:50.687Z CNTRLR [Node 002] [~] [Multilevel Sensor] Air temperature: 89.6 => 87.8 [Endpoint 0]
2022-05-18T20:47:50.691Z SERIAL » [ACK] (0x06)
2022-05-18T20:47:50.693Z DRIVER « [Node 002] [REQ] [BridgeApplicationCommand]
│ RSSI: -78 dBm
└─[MultilevelSensorCCReport]
type: Air temperature
scale: Fahrenheit
value: 87.8
2022-05-18T20:48:16.682Z SERIAL « 0x010e00a800011405310503010500c7bd (16 bytes)
2022-05-18T20:48:16.685Z CNTRLR [Node 020] [Multilevel Sensor] Illuminance: metadata updated [Endpoint 0]
2022-05-18T20:48:16.688Z CNTRLR [Node 020] [~] [Multilevel Sensor] Illuminance: 6 => 5 [Endpoint 0]
2022-05-18T20:48:16.692Z SERIAL » [ACK] (0x06)
2022-05-18T20:48:16.694Z DRIVER « [Node 020] [REQ] [BridgeApplicationCommand]
│ RSSI: -57 dBm
└─[MultilevelSensorCCReport]
type: Illuminance
scale: Percentage value
value: 5
2022-05-18T20:48:52.180Z SERIAL « 0x010f00a8000102063105012a036e00b19e (17 bytes)
2022-05-18T20:48:52.182Z CNTRLR [Node 002] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2022-05-18T20:48:52.186Z CNTRLR [Node 002] [~] [Multilevel Sensor] Air temperature: 87.8 => 87.8 [Endpoint 0]
2022-05-18T20:48:52.189Z SERIAL » [ACK] (0x06)
2022-05-18T20:48:52.191Z DRIVER « [Node 002] [REQ] [BridgeApplicationCommand]
│ RSSI: -79 dBm
└─[MultilevelSensorCCReport]
type: Air temperature
scale: Fahrenheit
value: 87.8
2022-05-18T20:49:16.682Z SERIAL « 0x010e00a800011405310503010500c5bf (16 bytes)
2022-05-18T20:49:16.684Z CNTRLR [Node 020] [Multilevel Sensor] Illuminance: metadata updated [Endpoint 0]
2022-05-18T20:49:16.687Z CNTRLR [Node 020] [~] [Multilevel Sensor] Illuminance: 5 => 5 [Endpoint 0]
2022-05-18T20:49:16.691Z SERIAL » [ACK] (0x06)
2022-05-18T20:49:16.694Z DRIVER « [Node 020] [REQ] [BridgeApplicationCommand]
│ RSSI: -59 dBm
└─[MultilevelSensorCCReport]
type: Illuminance
scale: Percentage value
value: 5
2022-05-18T20:49:53.663Z SERIAL « 0x010f00a8000102063105012a036e00b19e (17 bytes)
2022-05-18T20:49:53.665Z CNTRLR [Node 002] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2022-05-18T20:49:53.671Z CNTRLR [Node 002] [~] [Multilevel Sensor] Air temperature: 87.8 => 87.8 [Endpoint 0]
2022-05-18T20:49:53.674Z SERIAL » [ACK] (0x06)
2022-05-18T20:49:53.676Z DRIVER « [Node 002] [REQ] [BridgeApplicationCommand]
│ RSSI: -79 dBm
└─[MultilevelSensorCCReport]
type: Air temperature
scale: Fahrenheit
value: 87.8
2022-05-18T20:50:16.681Z SERIAL « 0x010e00a800011405310503010400c6bd (16 bytes)
2022-05-18T20:50:16.683Z CNTRLR [Node 020] [Multilevel Sensor] Illuminance: metadata updated [Endpoint 0]
2022-05-18T20:50:16.686Z CNTRLR [Node 020] [~] [Multilevel Sensor] Illuminance: 5 => 4 [Endpoint 0]
2022-05-18T20:50:16.689Z SERIAL » [ACK] (0x06)
2022-05-18T20:50:16.691Z DRIVER « [Node 020] [REQ] [BridgeApplicationCommand]
│ RSSI: -58 dBm
└─[MultilevelSensorCCReport]
type: Illuminance
scale: Percentage value
Note the time stamps are in GMT/UTC you’ll need to look for the proper time stamps unless you are in GMT/UTC timezone.
You gotta be kiddin’ me. The logs aren’t even in local date//time?
Ok that’s one hoop too many. I give up. I’m not writing a utility to correct the time stamps and make the logs usable.
I wouldn’t learn anything useful, anyway. At best I find out that yes, these devices are flakey. I just checked Levitons’s site and they have no firmware updates for the devices I have. And even if they did I’d need - according to Leviton - a “compatible” Aeotec stick to install them. So if I want a reliable system I’ll have to just pitch them and if I do, I’m replacing them with wifi. ZWave is cool - unfortunately, it hates me.