SOLVED: Power outage: now Zwave2MQTT appears no longer to connect

Configuration Z-Wave
1

I had running zwave2MQTT together with Zigbee2MQTT running fine.

This morning while I was at work I had a power outage.
When I restarted my server (Ubuntu LTS 18.4) everything came up fine with the exception of my *2MQTT integrations.

the zwave2MQTT log shows the following:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 

-----------------------------------------------------------
 Hass.io Add-on: Z-Wave to MQTT
 Fully configurable Z-Wave to MQTT gateway and control panel
-----------------------------------------------------------
 Add-on version: 0.4.2
 You are running the latest version of this add-on.
 System: Ubuntu 18.04.3 LTS  (amd64 / qemux86-64)
 Home Assistant version: 0.105.5
 Supervisor version: 201
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] zwave2mqtt.sh: executing... 
[cont-init.d] zwave2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[21:25:35] INFO: Starting the Z-Wave to MQTT...
2020-02-20T02:25:35.444Z z2m:Store scenes.json not found
2020-02-20T02:25:35.656Z z2m:App Application path:/opt
Initialising OpenZWave 1.4.164 binary addon for Node.JS.
	OpenZWave Security API is ENABLED
	ZWave device db    : /usr/etc/openzwave/
	User settings path : /opt/store
	Option Overrides : --Logging undefined --ConsoleOutput undefined --QueueLogLevel 6 --DriverMaxAttempts 9999 --SaveConfiguration undefined --PollInterval 6000
2020-02-20T02:25:35.696Z z2m:Zwave Connecting to /dev/ttyACM0
2020-02-19 21:25:35.697 Always, OpenZwave Version 1.4.164 Starting Up
2020-02-19 21:25:35.697 Warning, Failed - Network Key Not Set
2020-02-20T02:25:35.744Z z2m:App Listening on port 44920
2020-02-20T02:25:35.757Z z2m:Mqtt MQTT client connected
[21:25:35] INFO: Starting NGinx...
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
2020-02-19 21:25:36.698 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-02-20T02:25:36.699Z z2m:Zwave Notification from node 255: Notification - TimeOut (1)
[19/Feb/2020:21:25:36 -0500] 200 -(192.168.1.198) GET /socket.io/?EIO=3&transport=polling&t=N1WR5_Q HTTP/1.1 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36)
2020-02-20T02:25:36.873Z z2m:App New connection DzveDBBM7Z9mzJCgAAAA
[19/Feb/2020:21:25:36 -0500] 200 -(192.168.1.198) GET /socket.io/?EIO=3&transport=polling&t=N1WR64D&sid=DzveDBBM7Z9mzJCgAAAA HTTP/1.1 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36)
[19/Feb/2020:21:25:37 -0500] 200 -(192.168.1.198) GET /socket.io/?EIO=3&transport=polling&t=N1WR64N&sid=DzveDBBM7Z9mzJCgAAAA HTTP/1.1 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36)
2020-02-19 21:25:37.698 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-02-20T02:25:37.699Z z2m:Zwave Notification from node 255: Notification - TimeOut (1)
2020-02-19 21:25:38.699 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-02-20T02:25:38.699Z z2m:Zwave Notification from node 255: Notification - TimeOut (1)
2020-02-19 21:25:39.699 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-02-20T02:25:39.699Z z2m:Zwave Notification from node 255: Notification - TimeOut (1)
2020-02-19 21:25:40.699 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-02-20T02:25:40.700Z z2m:Zwave Notification from node 255: Notification - TimeOut (1)

I am looking at the log but nothing jumps to my eyes what could be wrong.
I tried restoring my zwave2mqtt configuration from my previous snapshot but that did not change anything.
Any help appreciated.

2

After a lot of testing around…

Somehow the device IDs for my Zwave and Zigbee sticks switched.
Pointed it to /dev/ttyACM1 and suddenly everything works again.

3

I suspect you have come across the problem where the USB stick device name changes from time to time after a system restart…I don’t have a helpful link at the moment, but search around and you’ll find several topics discussing the /dev/tty/ACMx and how to get your system to persist the name over reboots.

4

Thanks, here is the link i used to make the dev sticky.

5

Funny I use /dev/serial/by-id to be always sure it will point to right path.
Today I had remove all usb cables for a dust cleanup. Put everything back.

ZWave Stick was still at same ID but put in different USB port… Zwave2MQTT didn’t work.
Put it back in right USB port and up and running.

So always put the cables back at the same way… even when you use path to BY-ID

1 Like