OpenZWave / Zwave2Mqtt

Fully configurable Zwave to MQTT gateway and Control Panel using NodeJS and Vue
MIT License
355 stars 93 forks source link

[question] z2m: Zwave Driver Failed with Aotec USB stick #684

Closed dbrandesky closed 4 years ago

dbrandesky commented 4 years ago

Hi all, I'm totally new to this project. Got the Docker container for 3.4.1 running on my Raspberry Pi Zero W using an ARMv6 build by @samsonnguyen, made sure I had the correct serial device, etc., but I see the following on startup:

docker-compose up Starting dan_zwave2mqtt_1 ... done Attaching to dan_zwave2mqtt_1 zwave2mqtt_1 | z2m:Store scenes.json not found +0ms zwave2mqtt_1 | z2m:Store nodes.json not found +85ms zwave2mqtt_1 | z2m:Gateway No customDevices file found +0ms zwave2mqtt_1 | z2m:App Zwave2Mqtt version: 3.4.1 +0ms zwave2mqtt_1 | z2m:App Application path:/usr/src/app +7ms zwave2mqtt_1 | Initialising OpenZWave 1.6.0 binary addon for Node.JS. zwave2mqtt_1 | OpenZWave Security API is ENABLED zwave2mqtt_1 | ZWave device db : /usr/local/etc/openzwave zwave2mqtt_1 | User settings path : /usr/src/app/store zwave2mqtt_1 | Option Overrides : --Logging undefined --ConsoleOutput undefined --QueueLogLevel 6 --DriverMaxAttempts 9999 --SaveConfiguration false --PollInterval 1000 --AutoUpdateConfigFile true zwave2mqtt_1 | z2m:Zwave Connecting to /dev/ttyAMA0 +0ms zwave2mqtt_1 | 2020-08-23 21:41:30.917 Always, OpenZwave Version 1.6.-1 Starting Up zwave2mqtt_1 | 2020-08-23 21:41:31.077 Always, Using Language Localization zwave2mqtt_1 | 2020-08-23 21:41:31.136 Warning, Failed - Network Key Not Set zwave2mqtt_1 | z2m:Zwave Zwave connected, Openzwave version: 1.6.0 +6s zwave2mqtt_1 | z2m:App Listening on port 8091 +0ms zwave2mqtt_1 | z2m:Mqtt MQTT client connected +0ms zwave2mqtt_1 | z2m:App New connection nYTGx3OHCg8WTJBTAAAA +12s zwave2mqtt_1 | 2020-08-23 21:41:45.223 Warning, Download of http://download.db.openzwave.com/images/leviton/vrpa1.png Failed (Node: 0) zwave2mqtt_1 | 2020-08-23 21:41:45.234 Warning, Download of http://download.db.openzwave.com/images/inovelli/lzw36.png Failed (Node: 0) zwave2mqtt_1 | z2m:Zwave Driver failed { version: '1.6.0' } +8s The last helpful message I see is the "z2m:Zwave Driver Failed { version: '1.6.0' }" message, so that's basically what I have to go on right now. The web UI shows the Controller status as "unknown" as well. I do not yet have any Z-Wave devices to test with yet, those come later this week.

What are my next steps here?

dbrandesky commented 4 years ago

Also wanted to note, MinOZW doesn't return any errors:

MinOZW /dev/ttyAMA0 Starting MinOZW with OpenZWave Version 1.4.79 2020-08-23 17:59:40.047 Error, Cannot find a path to the configuration files at ../../../config/, Using config/ instead... 2020-08-23 17:59:40.051 Warning, Failed to Parse config/options.xml: Failed to open file 2020-08-23 17:59:40.053 Warning, Failed to Parse options.xml: Failed to open file 2020-08-23 17:59:40.064 Always, OpenZwave Version 1.4.79 Starting Up 2020-08-23 17:59:40.067 Info, Setting Up Provided Network Key for Secure Communications 2020-08-23 17:59:40.070 Warning, Failed - Network Key Not Set 2020-08-23 17:59:40.073 Info, mgr, Added driver for controller /dev/ttyAMA0 2020-08-23 17:59:40.078 Info, Opening controller /dev/ttyAMA0 2020-08-23 17:59:40.080 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1) 2020-08-23 17:59:40.084 Info, Serial port /dev/ttyAMA0 opened (attempt 1) 2020-08-23 17:59:40.088 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9 2020-08-23 17:59:40.091 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc 2020-08-23 17:59:40.094 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9 2020-08-23 17:59:40.097 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb 2020-08-23 17:59:40.106 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa 2020-08-23 17:59:40.110 Detail, 2020-08-23 17:59:40.117 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9 2020-08-23 17:59:40.119 Detail, contrlr, Notification: DriverFailed 2020-08-23 17:59:40.124 Detail, Notification: DriverRemoved 2020-08-23 17:59:40.125 Always, *************************************************************************** 2020-08-23 17:59:40.126 Always, ********************* Cumulative Network Statistics ********************* 2020-08-23 17:59:40.126 Always, *** General 2020-08-23 17:59:40.127 Always, Driver run time: . . . 0 days, 0 hours, 0 minutes 2020-08-23 17:59:40.127 Always, Frames processed: . . . . . . . . . . . . . . . . . . . . 0 2020-08-23 17:59:40.127 Always, Total messages successfully received: . . . . . . . . . . 0 2020-08-23 17:59:40.128 Always, Total Messages successfully sent: . . . . . . . . . . . . 0 2020-08-23 17:59:40.128 Always, ACKs received from controller: . . . . . . . . . . . . . 0 2020-08-23 17:59:40.129 Always, *** Errors 2020-08-23 17:59:40.130 Always, Unsolicited messages received while waiting for ACK: . . 0 2020-08-23 17:59:40.131 Always, Reads aborted due to timeouts: . . . . . . . . . . . . . 0 2020-08-23 17:59:40.133 Always, Bad checksum errors: . . . . . . . . . . . . . . . . . . 0 2020-08-23 17:59:40.135 Always, CANs received from controller: . . . . . . . . . . . . . 0 2020-08-23 17:59:40.137 Always, NAKs received from controller: . . . . . . . . . . . . . 0 2020-08-23 17:59:40.139 Always, Out of frame data flow errors: . . . . . . . . . . . . . 0 2020-08-23 17:59:40.140 Always, Messages retransmitted: . . . . . . . . . . . . . . . . . 0 2020-08-23 17:59:40.143 Always, Messages dropped and not delivered: . . . . . . . . . . . 0 2020-08-23 17:59:40.145 Always, *************************************************************************** 2020-08-23 17:59:40.146 Warning, WARNING: Tried to write driver config with no home ID set 2020-08-23 17:59:44.131 Detail, contrlr, Removing current message 2020-08-23 17:59:44.134 Info, mgr, Driver for controller /dev/ttyAMA0 removed

dbrandesky commented 4 years ago

Fixed! I had to use /dev/serial/by-id/ rather than /dev/ttyAMA0 as the device. Weird but hey, it works!

robertsLando commented 4 years ago

@dbrandesky Sorry for the late reply @dbrandesky , glad you fixed it, sincerly never heard about this bug but good to know hope this can help other users :)