Probably fixed, you can wait for update or change the files in the commit manually.
2 Likes
well, I was warned and made an extra guard now, so could check quicker: it’s the Ping device tracker. How this can happen is beyond me, because these devices are nowhere near the network!?!
I’ll take them out of the tracked groups now, to see what gives.
1 Like
There are some automations that show this screen. No debug screen on the left.
Is this a wrong automation, or something that’s wrong in the new feature?
But as it turns out, only works for automations.yaml - so none at all in my case, I have all my automations loaded from separate files in a folder (!include_dir_merge_list automations/)
Well, if there are no traces, then you of course get that output.
Did the automation run since the last HA restart? If no, then there will not be a trace (they are not persisted across instance restarts).
2 Likes
do your automations have a id listed for each one?
eg
- id: 'nodredwatchdog'
alias: NodeRed WatchDog
trigger:
Do you use IDs as it was mentioned above?
Read from this point and below again…
1 Like
Looks awesome. I was just troubleshooting an automation last night and this will be really helpful. Thanks to everyone for the great project!
Indeed, thanks!
This message is a bit misleading, that’s why I thought it works only for automations.yaml
1 Like
Hmm…does anyone have issues with MySQL ??
My database was 16Gb…and after 12 hrs I decided to dump the database and start over.
However, whatever I do, HA won’t rebuild the tables and gives an error notification:
Invalid config
The following integrations and platforms could not be set up:
recorder
logbook
history
default_config
Please check your config and logs.
But no trace of this in any log…
It is also weird, as I only dumped the tables, I did not change any config…
So then, how do you like it?
Keep in mind this as well!
To those posting about the DB upgrade.
It would be useful to others if you state the size of your DB, what kind of DB it is (e.g. sqlite) and your hardware. This can help set the expectations for others.
Also keep in mind that sqlite isn’t a fancy kind of DB and is accessed with a single processing thread and connection. It’s essentially some files on disk and was built for convenience over speed.
5 Likes
It’s 5 hours and still migration not completed. I am using default DB…
What will happen if i do a HA Core stop ed then restart? How to know if the migration process is still running?
EDIT: Strange is the Db has the hour of when the process begun…
Anyone else notice that this release has broken the ability to change LIFX light colors via lifx.set_state and/or light.turn_on services? I am still however able to change colors via the UI color wheel
2 Likes
By dumped, do you mean you truncated them or did you drop them? I would drop the DB and then recreate it.
1 Like
Started by dropping the tables only, that didn’t work, so I dropped the whole DB and created a new one.
Samesame result
Just wanted to make sure that nobody else has this problem before raising a ticket 
Sounds like a sqlalchemy cache issue. Try changing your recorder to this:
recorder:
db_url: 'sqlite:///:memory:'
Let HA boot up then shut it down gracefully. Then change your recorder back to your original and see if that fixes it.
1 Like
Or just keep it like that, that’s what I do 
2 Likes
Thanks. When the automation has been started for first time after a reboot I get a trace. 