As a result of an issue with ZWaveJS whereby it has stopped and the UI Start is not starting the addon, I have 2 questions.
- Given the logs below, any ideas why it has stopped and cannot restart?
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/config.sh
[20:37:26] INFO: Both 'network_key' and 's0_legacy_key' are set and match. All ok.
[20:37:28] INFO: Virtual Machine not detected, enabling soft-reset
cont-init: info: /etc/cont-init.d/config.sh exited 0
cont-init: info: running /etc/cont-init.d/structure.sh
cont-init: info: /etc/cont-init.d/structure.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun zwave_js (no readiness notification)
s6-rc: info: service legacy-services successfully started
[20:37:30] INFO: Successfully send discovery information to Home Assistant.
2022-10-05T19:37:33.453Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗
███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2022-10-05T19:37:33.462Z DRIVER version 10.3.0
2022-10-05T19:37:33.463Z DRIVER
2022-10-05T19:39:22.025Z DRIVER Failed to open the serial port: Error Resource temporarily unavailable Cannot
lock port
Unable to start driver ZWaveError: Failed to open the serial port: Error Resource temporarily unavailable Cannot lock port (ZW0100)
at Driver.openSerialport (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1070:9)
at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:947:5) {
code: 100,
context: undefined,
transactionSource: undefined
}
[19:39:22] WARNING: Halt add-on
s6-rc: info: service legacy-services: stopping
[19:39:22] INFO: Service restart after closing
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Logger: homeassistant.components.http.ban
Source: components/http/ban.py:84
Integration: HTTP (documentation, issues)
First occurred: 20:41:28 (3 occurrences)
Last logged: 20:41:34
Login attempt or request with invalid authentication from fe99::ec99:c699:ee99:db99 (fe99::ec99:c699:ee99:db99). Requested URL: '/api/config'. (None)
Login attempt or request with invalid authentication from 192.168.1.xxx (192.168.1.xxx). Requested URL: '/api/services/mqtt/publish'. (python-requests/2.3.0 CPython/2.6.5 Windows/post2008Server)
- This is my original reason for posting. I am trying to create automations that check addons and restart if stopped. I have seen many examples using the addon REST info page but this is my first foray into REST. All of these seem to have an authorisation key under header, seemingly starting with the text BEARER. What is this key and how do I access or create it for addons in home assistant?