I think it is based on sunrise/sunset.
@pepeEL && @nickrout It uses the scheme from your client.
If your device/OS is set to dark mode, HA tries to match that.
1 Like
Ok thanks 
I can’t see this behaviour on any of my 3 installs.
reboot has resolved by HACS problem. Thanks.
Concerning the disk space error, please consider voting for Check free disk space before updating
Edit: mostly meant for other people than tom_l you already voted!
great work as always. only issues i have is that fancontrol entity row and button-card (both via hacs) don’t work anymore even after reinstalling the whole hacs and its repositories. no line about that in logs…
update: believe it or not, but reloading the page in chrome did help.
1 Like
I love this Dark Mode! Although I am a bit disappointed - I’ve spent ages fiddling about with my own dark_theme.yaml and now I prefer this one right out-of-the-box!
Great work all, upgraded flawlessly 
1 Like
If you’re a Windows 10 user and frustrated by the lack of automatic light/dark mode switching, check out https://github.com/adrianmteo/Luna. Pretty basic, but does the job, and confirmed working with HA.
1 Like
You can do set times with task scheduler. Also not much good if you live at higher latitudes where you need sunrise/sunset to set the theme.
has this been recognized/solved yet?
All my custom components are still there, but the system reports them missing in the config checker…safe mode and no where to go!
ssh ha core check checks ok:
0.114 appears to have broken my mysql database!! using mariadb add-on also.
Anyway of fixing this? Have so many sensors and data on dashboards. 
Error while rolling back event session: (MySQLdb._exceptions.OperationalError) (2006, ‘MySQL server has gone away’) (Background on this error at: http://sqlalche.me
After upgrading sensors in the filter platform are not loading for me 
Repair or delete the db and restart. There’s a repair topic with some helpful (M)SQL commands but they were from before the great optimisation so not sure if they are still valid.
1 Like
mysql workbench now connected on my pc and data coming back but the sensors still broken. working on it.
Think it might be a permission issue. not sure where though. Something has been revoked or reset.
answering myself for reference here:
after ha core check returned ok, I decided to give it a try… typed ha core restart, hit enter and closed my eyes firmly. 
and what do you know, next up I heard my intercom announce Ha had restarted 
so, don’t despair if you see the same config error, check system and restart once more.
thanks team! Now even my themes survive a restart, one automation down…
1 Like
Had to revert to 113.3. WeMo wasn’t working, Hue Emulations not working.
I’m getting this error under the mariadb logs:
hmm. not sure. mysql workbench will connect. the data is there but my url to the sensors is not connecting.
[11:10:02] INFO: Successfully send service information to Home Assistant.
2020-08-13 11:13:25 25 [Warning] Aborted connection 25 to db: 'homeassistant' user: 'homeassistant' host: '172.30.32.1' (Got an error reading communication packets)
sensors yaml:
- platform: sql
db_url: mysql://homeassistant:password@core-mariadb/homeassistant?charset=utf8
where is it going wrong?
Should I try rebooting the entire linux server?
Data is coming through on the grapsh etc.
Must be the sensor url for the mysql. Can’t figure it out
- platform: sql
db_url: ??
Grafana connects fine with mariadb but all the sensors on sensors yaml are not connecting. Can’t figure it out.
States are being fed into the db
Hi, since updating to .114 (from 112.4) and also os and other update, I suddenly have all my “Custom element doesn’t exist” errors in lovelace … did I miss anything?