🗑 Custom Home Assistant sensor for scheduling garbage collection (or other regularly re-occurring events - weekly on given days, semi-weekly or monthly)
MIT License
383
stars
90
forks
source link
My configuration broke with recent changes made for 2022.12 #443
[X] I'm running the newest version of Garbage Collection, or the next pre-release.
[X] I have enabled debug logging for my installation.
Describe the bug
my configuration creates a configuration error introduced by the last change for 2022.12.
The error is this. If I remove my garbage configuration ha core check is successfull. With hte garbage collection in ... this comes up.
$ ha core check
Processing... Done.
Error: Testing configuration at /config
INFO:homeassistant.util.package:Attempting install of pysomneo==2.3.1
WARNING:homeassistant.components.ios:The 'push' option is deprecated, please remove it from your configuration
Fatal error while loading config: '<' not supported between instances of 'dict' and 'dict'
Failed config
General Errors:
- '<' not supported between instances of 'dict' and 'dict'
Successful config (partial)
[core-ssh ~]$
Logfiles did not help me.
The sensors show up after reboot but get unavailable after some seconds.
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
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
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started
2022-12-08 23:19:49.498 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration pixelblaze which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-12-08 23:19:49.498 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration browser_mod which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-12-08 23:19:49.499 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration audiconnect which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-12-08 23:19:49.500 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration garbage_collection which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-12-08 23:19:49.500 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration yahoofinance which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-12-08 23:19:49.501 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration xiaomi_cloud_map_extractor which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-12-08 23:19:49.502 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration somneo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-12-08 23:19:49.502 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-12-08 23:19:49.503 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration garmin_connect which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-12-08 23:19:49.504 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration rki_covid which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-12-08 23:19:49.505 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration openwbmqtt which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-12-08 23:19:49.505 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
Before you submit a new bug report, please check that
Describe the bug
my configuration creates a configuration error introduced by the last change for 2022.12.
The error is this. If I remove my garbage configuration
ha core check
is successfull. With hte garbage collection in ... this comes up.Logfiles did not help me.
The sensors show up after reboot but get unavailable after some seconds.
Configuration
Debug logs