room-assistant: Update killed my setup
Describe the bug A clear and concise description of what the bug is. Loading integrations: none To reproduce Steps required to reproduce the issue.
Restart
Relevant logs
Log output that correlates to the bug. You can get debug output with room-assistant -v.
[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] done.
[services.d] starting services
[services.d] done.
[19:38:36] INFO: Setting up Home Assistant configuration
[19:38:36] INFO: Starting room-assistant
*** WARNING *** The program ‘node’ uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/blog/projects/avahi-compat.html
*** WARNING *** The program ‘node’ called ‘DNSServiceRegister()’ which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/blog/projects/avahi-compat.html
2/5/2021, 7:38:37 PM - info - IntegrationsModule: Loading integrations: none
2/5/2021, 7:38:37 PM - info - NestFactory: Starting Nest application…
2/5/2021, 7:38:37 PM - info - InstanceLoader: AppModule dependencies initialized
2/5/2021, 7:38:37 PM - info - InstanceLoader: ConfigModule dependencies initialized
2/5/2021, 7:38:37 PM - info - InstanceLoader: NestEmitterModule dependencies initialized
2/5/2021, 7:38:37 PM - info - InstanceLoader: IntegrationsModule dependencies initialized
2/5/2021, 7:38:37 PM - info - InstanceLoader: HttpModule dependencies initialized
2/5/2021, 7:38:37 PM - info - InstanceLoader: DiscoveryModule dependencies initialized
2/5/2021, 7:38:37 PM - info - InstanceLoader: PrometheusModule dependencies initialized
2/5/2021, 7:38:37 PM - info - InstanceLoader: ClusterModule dependencies initialized
2/5/2021, 7:38:37 PM - info - InstanceLoader: TerminusModule dependencies initialized
2/5/2021, 7:38:37 PM - info - InstanceLoader: ScheduleModule dependencies initialized
2/5/2021, 7:38:37 PM - info - InstanceLoader: EntitiesModule dependencies initialized
2/5/2021, 7:38:37 PM - info - InstanceLoader: StatusModule dependencies initialized
2/5/2021, 7:38:37 PM - info - RoutesResolver: EntitiesController {/entities}:
2/5/2021, 7:38:37 PM - info - RouterExplorer: Mapped {/entities, GET} route
2/5/2021, 7:38:37 PM - info - RoutesResolver: StatusController {/status}:
2/5/2021, 7:38:37 PM - info - RouterExplorer: Mapped {/status, GET} route
2/5/2021, 7:38:37 PM - info - RoutesResolver: PrometheusController {/metrics}:
2/5/2021, 7:38:37 PM - info - RouterExplorer: Mapped {/metrics, GET} route
2/5/2021, 7:38:37 PM - info - ConfigService: Loading configuration from /usr/lib/node_modules/room-assistant/dist/config/definitions/default.js, config/default.json, config/local.json
2/5/2021, 7:38:37 PM - info - ClusterService: Starting mDNS advertisements and discovery
2/5/2021, 7:38:37 PM - info - NestApplication: Nest application successfully started
2/5/2021, 7:38:39 PM - info - ClusterService: 6e66619d-room-assistant has been elected as leader
2/5/2021, 7:38:39 PM - info - EntitiesService: Refreshing entity states
Relevant configuration Paste the relevant parts of your configuration below.
default + global: instanceName: Den Room-Ass integrations: - bluetoothLowEnergy - bluetoothClassic - homeAssistant weight: 10 bluetoothClassic: whitelist: - bc-a5-8b-fc-fa-26 tagOverrides: bc-a5-8b-fc-fa-26: name: Note-BT bluetoothLowEnergy: whitelist: - 10f86430134611e491912caa8e003811-111-111 - 46692fd7ddfe - 10521c65367e - 2caa8e00a766 - 2caa8e40953a - 2caa8e003811 - null tagOverrides: 10521c65367e: name: T Watch homeAssistant: mqttUrl: ‘mqtt://192.168.1.191:1883’ mqttOptions: username: ########### password: ########### cluster: port: 6425 peerAddresses: - ‘192.168.1.77:6425’
Expected behavior A clear and concise description of what you expected to happen. After update it wont load any integrations and nothing is discovered
Environment
- room-assistant version: [e.g. 2.13]
- hardware: Raspi-hassio-bin and ubuntu with docker both do the same
Additional context Add any other context about the problem here.
Right after update the config file was gone on both setups --blank unistalled both the repo and everything on hassio. config disappears after i set it up and restart it. was working great before update. tried using default config but same thing happens
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 33 (12 by maintainers)
The latest version of the add-on (2.13.1) fixed this issue - the config was now moved into the Home Assistant config folder. You can use your complete config as you used it before (no limitations) by creating it as e.g.
/config/room_assistant/local.ymlon the file system. If no configuration exists a default file will be created there on first add-on start. You can create/edit the file using the SSH, Samba or File Editor add-ons.This was the best option that I found for fixing this stuff in a timely manner, even though it makes things a bit more complicated. Everything else won’t work until some changes are implemented in the supervisor unfortunately.
@outofsight Yeah, or an inline YAML like:
Since my issues on the supervisor repo haven’t received any real reaction I think that we likely won’t see any quick fixes there… so I’ll consider an alternative option that would allow complete configuration again.
@hippydave Yep, that’s a supervisor issue that I reported here: home-assistant/supervisor#2559.
Alright, I added a basic schema that should at least allow you to get basic functionality restored again. This is as far as I could go with the current state of the supervisor - any options that are deeper than two levels or have an array on the second level are unsupported. You also have to have all root objects defined, even if they are empty… otherwise the schema validation fails.
To get the partially working version: uninstall the add-on, reload the add-ons (Add-on Store tab -> three dot menu top right -> Reload), install the add-on again.
I will open issues for everything that is unsupported in the supervisor repo.
Turns out that this is related to a change in the supervisor: home-assistant/supervisor#2540. The change came without warning for me and is something that I instinctively disagree with (but I also don’t know the reasons for why they took this feature away).
Only workaround for now is downgrading your supervisor version.