addons: Z-wave JS 0.1.11 Crashes at startup
The problem
I updated the Z-wave JS addon to version 0.1.11 and now the addon won start. I rebooted the system, but that did not help.
Environment
- Add-on with the issue: Z-wave JS
- Add-on release with the issue: 0.1.11
- Last working add-on release (if known): 0.1.10
- Operating environment (OS/Supervised): OS
Problem-relevant configuration
Traceback/Error logs
The System log (repeats constantly) 21-03-15 21:24:28 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with core_zwave_js! 21-03-15 21:24:28 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning addon_core_zwave_js application 21-03-15 21:24:28 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-zwave_js with version 0.1.11
This is the Z-Wave log
[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] config.sh: executing…
[cont-init.d] config.sh: exited 0.
[cont-init.d] structure.sh: executing…
[cont-init.d] structure.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[22:22:58] INFO: Successfully send discovery information to Home Assistant.
22:23:00.381 DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗
███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
22:23:00.390 DRIVER version 6.5.0
22:23:00.391 DRIVER
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
ZWaveError: The config has not been loaded yet!
at ConfigManager.lookupMeter (/usr/lib/node_modules/zwave-js/node_modules/@zwave-js/config/src/ConfigManager.ts:326:10)
at ConfigManager.lookupMeterScale (/usr/lib/node_modules/zwave-js/node_modules/@zwave-js/config/src/ConfigManager.ts:342:22)
at new MeterCCReport (/usr/lib/node_modules/zwave-js/src/lib/commandclass/MeterCC.ts:559:43)
at new CommandClass (/usr/lib/node_modules/zwave-js/src/lib/commandclass/CommandClass.ts:108:13)
at new MeterCC (/usr/lib/node_modules/zwave-js/src/lib/commandclass/MeterCC.ts:340:1)
at Function.from (/usr/lib/node_modules/zwave-js/src/lib/commandclass/CommandClass.ts:331:15)
at new ApplicationCommandRequest (/usr/lib/node_modules/zwave-js/src/lib/controller/ApplicationCommandRequest.ts:88:32)
at Function.from (/usr/lib/node_modules/zwave-js/src/lib/message/Message.ts:222:15)
at Driver.serialport_onData (/usr/lib/node_modules/zwave-js/src/lib/driver/Driver.ts:1395:18)
at SerialAPIParser.emit (events.js:315:20)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
ZWaveError: The config has not been loaded yet!
at ConfigManager.lookupMeter (/usr/lib/node_modules/zwave-js/node_modules/@zwave-js/config/src/ConfigManager.ts:326:10)
at ConfigManager.lookupMeterScale (/usr/lib/node_modules/zwave-js/node_modules/@zwave-js/config/src/ConfigManager.ts:342:22)
at new MeterCCReport (/usr/lib/node_modules/zwave-js/src/lib/commandclass/MeterCC.ts:559:43)
at new CommandClass (/usr/lib/node_modules/zwave-js/src/lib/commandclass/CommandClass.ts:108:13)
at new MeterCC (/usr/lib/node_modules/zwave-js/src/lib/commandclass/MeterCC.ts:340:1)
at Function.from (/usr/lib/node_modules/zwave-js/src/lib/commandclass/CommandClass.ts:331:15)
at new ApplicationCommandRequest (/usr/lib/node_modules/zwave-js/src/lib/controller/ApplicationCommandRequest.ts:88:32)
at Function.from (/usr/lib/node_modules/zwave-js/src/lib/message/Message.ts:222:15)
at Driver.serialport_onData (/usr/lib/node_modules/zwave-js/src/lib/driver/Driver.ts:1395:18)
at SerialAPIParser.emit (events.js:315:20)
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
Additional information
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 5
- Comments: 37 (12 by maintainers)
We’re working on resolving this with an update.
We’ve reported it upstream. We’ll update here when there is news.
thanks for the quick action, can confirm this to be working just fine again!
I’m having the same issue and had to restore back to 0.1.10 I tried everything uninstalling, rebooting etc. I spent a good 2 hours on this last night trying to help figure it out. My error is the exact same as what is posted above and it just keeps crashing and looping.
@MartinHjelmare do you feel this is still incidental? I ask because the update still pops up, and people might update without knowing this is bugged, and run into severe issues… Maybe better pull the add-on update?
Please stop commenting on this issue with off topic remarks.
Really surprised, a better clever reaction would be to REMOVE 1.10 from available releases, it would be better than deleting my messages…
Oh I’m so sorry…