Sorry what I meant to ask is if the recorder is still working in 0.114.
If it is deprecated then how do we specify the default database to record to?
When I upgraded to 0.114 all my sensors stopped working but the database could still be accessed from grafana and mysqlworkbench. I rolled back to 0.113 and all my sensors came back. In the sensor yaml I have a ton of sql queries pulling from mariadb.
Sorry may have misunderstood previous posts. Some people had issues with their database, removed the recorder and recreated their database files.
I may try upgrading again since the first release as we’re on 0.114.3 now.
Not sure if the sql issues has been fixed or if it’s just related with my specific queries.
I have a lot of sensors with these types of queries (from views and procs) which all stopped working on 0.114:
- name: heating_downstairs_on_time
query: 'SELECT sum(Duration) as Duration FROM homeassistant.Heating_Downstairs'
column: 'Duration'
unit_of_measurement: 'minutes'
Hello again, is there any progress on the question (it’s asked 3 times but I cannot read an answer in this topic) about the dark map in the dark theme? I cannot see anything sensible on the dark map…
This may not help, but you could try to go into the map card config and put: dark_mode: false.
I use a dark theme for AMOLED devices and had to turn it on by doing the opposite.
It is tough to read, but I’m not looking too closely at my map so it works for me.
So this shows the entities I’m tracking and the tag dark_mode: allows me to have it match the rest of my theme. Otherwise I have a white card when the rest of the page is dark. This is what you will have as well, but it will be more readable for you. I just tried it and it works.
Again rolling back to 0.113 as so many parts are broken. I tried with 0.114 last week. rolled back.
Then I tried 0.114.4 today hoping the sensors had been fixed. Nope.
Importantly the sensors platform for mysql queries from mariadb. Thought this would be at the top of the list for NIT testing.
Also the simple weather cards and shutters cards. The dark themes can be implemented without the need for 0.114. Have plenty of customs themes that simulate a dark theme.
Having said that, not many people I think are using sql sensors. They are not needed for what you are doing I think. You seem to be using them to determine the length of time something has been in a certain state. You could look at this to do the same thing: https://www.home-assistant.io/integrations/history_stats/
You will see that your issue is waiting for an upstream change.
Can the history stats be used with a mysql database such as mariadb? I went down the mariadb route as I understood history stats is only for the default database.
I need 6-12 months of data to work with.
Think because I’m a Database developer I naturally go to create my stats with views/tables and procs.
I produce lots of stats for appliance consumption etc.
I also have lots of fixed coding in views for the cost of electricity per kwh etc to produce daily/monthly costs of different zones in the house based on on/off datetimes.
If it is deprecated then I’ll have to start working with rendering stats from grafana I guess. I just found these too slow
You are obviously right, at least for apps that break all the time, like HA. But normally i don’t have such problems with other apps.
The lastest HA App Update fixed all my problems, therefor i want to stay on this app version, as i don’t need unnecessary drama in my life.
Is there a way to just flag one app, to not update itself?
Why is it that when adding comments to a script when using HA UI in YAML mode, the comment line disappears when I switch back to UI mode? Even if I again switch into YAML mode, the comment line is still lost.
Not being able to add comments to a script makes it very hard to read.
If you use the GUI editor (Any GUI editor, script editor, automation editor, lovelace, etc) all comments are lost when the system parses the code back and forth into/out of YAML. This is “expected behaviour” and if you want to retain comments you must use YAML mode only, and not edit anything via the GUI.
Maybe a good “What The Heck” topic if you think this is annoying.
The Automation Editor does not support comments. If you add comments using a text editor and then later use the Automation Editor, the moment you click its Save icon, all existing comments are lost.
It’s mentioned at the very bottom of this page in the documentation.
Any comments in the YAML file will be lost and templates will be reformatted when you update an automation via the editor.
There is a way to keep ‘manually created’ automations separate from the automations created via the Automation Editor. Created a sub-directory for your automations (mine is simply called ‘automations’) and then add a automation manual option as shown here.
Now you can keep your automations, created with a text editor, in the automations sub-directory, separate from the automations.yaml that is used by the Automation Editor. You can choose to keep all your automations in a single file in that sub-directory or spread out over several files (handy way to separate and organize the automations).
Hi Viktak, I had the same problem. Looking in the log, there was an error message about the mysql3 db being malformed. From what I can tell, the db is only used to store history, which I don’t find terribly important, so I shut down Home Assistant, deleted the home-assistant_v2.db file in the config directory and restarted home assistant. It created a new db file. There are ways to migrate data to a new db file, ut for me it seemed like too much effort for the non-critical data I have in the db.
Indeed - annoying. But I know better than to criticise open source contributors - especially since I am unable to contribute myself (with anything but criticisms).
So, how to I turn this into a “WTH” case?