Hello,
I have hassio running inside a container in docker, on a Pi 4. It had been running pretty well, until I added Zigbee2MQTT, and then I used the configurator addon to edit the configuration.yaml to enable MQTT discovery. I think I restarted the system once and it was able to restart, and then did some things (like changed the zigbee device names), and decided to restart again, and I’m unable to see the HomeAssistant web interface.
I see some errors from the portainer logs for the hassio supervisor and home assistant:
2019-08-05 23:02:17 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.2895579408] Connection closed by client,
2019-08-05 23:32:07 INFO (MainThread) [homeassistant.components.stream] Stopped stream workers.,
2019-08-05 23:32:07 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.2896506800] Connection closed by client,
2019-08-05 23:32:07 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.2895748784] Connection closed by client,
Config directory: /config,
2019-08-05 23:33:46 ERROR (MainThread) [homeassistant.config] Invalid config for [homeassistant]: expected a dictionary. Got True. (See ?, line ?). ,
2019-08-05 23:33:46 INFO (MainThread) [homeassistant.core] Starting Home Assistant,
2019-08-05 23:33:46 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved,
Traceback (most recent call last):,
File "/usr/src/homeassistant/homeassistant/core.py", line 1127, in async_call,
raise ServiceNotFound(domain, service) from None,
homeassistant.exceptions.ServiceNotFound: Unable to find service persistent_notification/create,
2019-08-05 23:33:46 INFO (MainThread) [homeassistant.core] Timer:starting,
Config directory: /config,
2019-08-05 23:42:11 ERROR (MainThread) [homeassistant.config] Invalid config for [homeassistant]: expected a dictionary. Got True. (See ?, line ?). ,
2019-08-05 23:42:11 INFO (MainThread) [homeassistant.core] Starting Home Assistant,
2019-08-05 23:42:11 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved,
Traceback (most recent call last):,
File "/usr/src/homeassistant/homeassistant/core.py", line 1127, in async_call,
raise ServiceNotFound(domain, service) from None,
homeassistant.exceptions.ServiceNotFound: Unable to find service persistent_notification/create,
2019-08-05 23:42:11 INFO (MainThread) [homeassistant.core] Timer:starting,
Here’s the superivsor log:
19-08-06 04:40:47 INFO (MainThread) [hassio.core] Hass.io is down,
19-08-06 04:40:47 INFO (MainThread) [__main__] Close Hass.io,
19-08-06 04:40:47 ERROR (MainThread) [asyncio] Task was destroyed but it is pending!,
task: <Task pending coro=<HassIO.start() running at /usr/src/hassio/hassio/core.py:113> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0xb2634550>()]>>,
19-08-06 04:41:18 INFO (MainThread) [__main__] Initialize Hass.io setup,
19-08-06 04:41:19 INFO (MainThread) [__main__] Setup HassIO,
19-08-06 04:41:19 INFO (SyncWorker_0) [hassio.docker.supervisor] Attach to Supervisor homeassistant/armv7-hassio-supervisor with version 170,
19-08-06 04:41:19 INFO (MainThread) [hassio.utils.gdbus] Introspect org.freedesktop.systemd1 on /org/freedesktop/systemd1,
19-08-06 04:41:19 INFO (MainThread) [hassio.utils.gdbus] Connect to dbus: org.freedesktop.systemd1 - /org/freedesktop/systemd1,
19-08-06 04:41:19 INFO (MainThread) [hassio.utils.gdbus] Introspect org.freedesktop.hostname1 on /org/freedesktop/hostname1,
19-08-06 04:41:19 INFO (MainThread) [hassio.utils.gdbus] Connect to dbus: org.freedesktop.hostname1 - /org/freedesktop/hostname1,
19-08-06 04:41:19 INFO (MainThread) [hassio.utils.gdbus] Introspect de.pengutronix.rauc on /,
19-08-06 04:41:19 ERROR (MainThread) [hassio.utils.gdbus] DBus return error: b'Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name de.pengutronix.rauc was not provided by any .service files\n',
19-08-06 04:41:19 WARNING (MainThread) [hassio.dbus.rauc] Can't connect to rauc,
19-08-06 04:41:19 INFO (MainThread) [hassio.host.info] Update local host information,
19-08-06 04:41:19 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1,
19-08-06 04:41:19 INFO (MainThread) [hassio.host.services] Update service information,
19-08-06 04:41:19 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1,
19-08-06 04:41:19 INFO (MainThread) [hassio.host.apparmor] Load AppArmor Profiles: {'hassio-supervisor'},
19-08-06 04:41:19 INFO (MainThread) [hassio.host.services] Reload local service hassio-apparmor.service,
19-08-06 04:41:19 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ReloadOrRestartUnit on /org/freedesktop/systemd1,
19-08-06 04:41:19 INFO (SyncWorker_2) [hassio.docker.interface] Attach to homeassistant/raspberrypi3-homeassistant with version 0.96.5,
19-08-06 04:41:19 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/git/7ad98f9c repository,
19-08-06 04:41:19 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/core repository,
19-08-06 04:41:19 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/git/a0d7b954 repository,
19-08-06 04:41:19 INFO (MainThread) [hassio.store] Load add-ons from store: 61 all - 61 new - 0 remove,
19-08-06 04:41:19 INFO (MainThread) [hassio.addons] Found 3 installed add-ons,
19-08-06 04:41:19 INFO (SyncWorker_8) [hassio.docker.interface] Attach to hassioaddons/log-viewer-armv7 with version v0.6.1,
19-08-06 04:41:19 INFO (SyncWorker_3) [hassio.docker.interface] Attach to homeassistant/armv7-addon-configurator with version 3.4,
19-08-06 04:41:19 INFO (SyncWorker_7) [hassio.docker.interface] Attach to dwelch2101/zigbee2mqtt-armhf with version 1.5.1.1,
19-08-06 04:41:19 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json,
19-08-06 04:41:20 INFO (MainThread) [hassio.snapshots] Found 0 snapshot files,
19-08-06 04:41:20 INFO (MainThread) [hassio.discovery] Load 0 messages,
19-08-06 04:41:20 INFO (MainThread) [hassio.ingress] Load 4 ingress session,
19-08-06 04:41:20 INFO (MainThread) [__main__] Run Hass.io,
19-08-06 04:41:20 INFO (MainThread) [hassio.misc.dns] Start DNS port forwarding for host add-ons,
19-08-06 04:41:20 INFO (MainThread) [hassio.api] Start API on 172.30.32.2,
19-08-06 04:41:20 INFO (MainThread) [hassio.addons] Phase 'initialize' start 0 add-ons,
19-08-06 04:41:20 INFO (MainThread) [hassio.addons] Phase 'system' start 0 add-ons,
19-08-06 04:41:20 INFO (MainThread) [hassio.addons] Phase 'services' start 1 add-ons,
19-08-06 04:41:20 INFO (SyncWorker_2) [hassio.docker.interface] Clean addon_7ad98f9c_zigbee2mqtt application,
19-08-06 04:41:22 INFO (SyncWorker_2) [hassio.docker.addon] Start Docker add-on dwelch2101/zigbee2mqtt-armhf with version 1.5.1.1,
19-08-06 04:41:27 INFO (SyncWorker_7) [hassio.docker.interface] Start homeassistant/raspberrypi3-homeassistant,
It seems like the Zigbee2MQTT addon is still working, because when I look at its log, it seems fine.
2019-08-05T23:41:26: PM2 log: Launching in no daemon mode,
2019-08-05T23:41:26: PM2 log: App [npm:0] starting in -fork mode-,
2019-08-05T23:41:26: PM2 log: App [npm:0] online,
> [email protected] start /zigbee2mqtt-1.5.1,
> node index.js,
zigbee2mqtt:info 8/5/2019, 11:42:07 PM Logging to directory: '/home/pi/docker/zigbee2mq/log/2019-08-05.23-42-06',
zigbee2mqtt:info 8/5/2019, 11:42:07 PM Starting zigbee2mqtt version 1.5.1 (commit #unknown),
zigbee2mqtt:info 8/5/2019, 11:42:07 PM Starting zigbee-shepherd,
zigbee2mqtt:info 8/5/2019, 11:42:09 PM zigbee-shepherd started,
zigbee2mqtt:info 8/5/2019, 11:42:09 PM Coordinator firmware version: '20190619',
zigbee2mqtt:info 8/5/2019, 11:42:09 PM Currently 0 devices are joined:,
zigbee2mqtt:warn 8/5/2019, 11:42:09 PM `permit_join` set to `true` in configuration.yaml.,
zigbee2mqtt:warn 8/5/2019, 11:42:09 PM Allowing new devices to join.,
zigbee2mqtt:warn 8/5/2019, 11:42:09 PM Set `permit_join` to `false` once you joined all devices.,
zigbee2mqtt:info 8/5/2019, 11:42:09 PM Zigbee: allowing new devices to join.,
zigbee2mqtt:info 8/5/2019, 11:42:09 PM Connecting to MQTT server at mqtt://homeassistant,
zigbee2mqtt:info 8/5/2019, 11:42:09 PM zigbee-shepherd ready,
zigbee2mqtt:info 8/5/2019, 11:42:09 PM Connected to MQTT server,
zigbee2mqtt:info 8/5/2019, 11:42:09 PM MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online',
zigbee2mqtt:info 8/5/2019, 11:42:09 PM MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.5.1","commit":"unknown","coordinator":20190619,"log_level":"info","permit_join":true}',
zigbee2mqtt:info 8/5/2019, 11:44:49 PM Successfully reenabled joining,
zigbee2mqtt:info 8/5/2019, 11:47:29 PM Successfully reenabled joining,
zigbee2mqtt:info 8/5/2019, 11:50:09 PM Successfully reenabled joining,
zigbee2mqtt:info 8/5/2019, 11:52:49 PM Successfully reenabled joining,
One thing I did notice is that the hassio supervisor log timestamps are not the correct time zone. Other than that, I’m not sure if the “invalid config” in the HA log is an issue?
This is my current configuration.yaml
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
#added b/c zigbee2MQTT saids so for MQTT device discovery
homeassistant: true
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
# base_url: example.duckdns.org:8123
# Text to speech
tts:
- platform: google_translate
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
mqtt:
discovery: true
broker: localhost # Remove if you want to use builtin-in MQTT broker
birth_message:
topic: 'hass/status'
payload: 'online'
will_message:
topic: 'hass/status'
payload: 'offline'
This was a really small config. The default configuration.yaml I’ve seen from other people seem much much bigger. So maybe there was something odd with my configuration.yaml file? When I first opened it with the web interface to add MQTT discovery, it was my first time seeing it, and it was a more sparse than I remember that file being from previous times I’ve used HA a year ago.