Hi all,
my configuration:
version core-2021.2.3
Installation Type Home Assistant Supervised
I’m struggling, because of my little knowledge, to achieve a more or less functioning setting of the doods service on a raspi4 (docker installation). Now I already came to the conclusion that the processing power offered by my hardware is not enough to obtain some useful information (the detected image gets stored after more or less 14-15 sec after the process has been triggered), but during my troubleshooting I think discovered a strange behavior of the Logbook function.
Since I was searching for the doods activation I selected in the search field of the logbook: automation.doods_activation, and this is what came out:
Doods activation camera est has been triggered by state of input_boolean.camera4_motion_detected by Motioneye - Camera4 - Motion started 8:16:56 AM - 3 hours ago
But as I did not find any occurrence in motioneye (triggering element) at that time I had a look in the full log which gave following informations:
2021-02-22 08:15:59 INFO (MainThread) [homeassistant.components.generic_thermostat.climate] Keep-alive - Turning off heater switch.riscaldamento_piano_sopra
2021-02-22 08:15:59 INFO (MainThread) [homeassistant.components.generic_thermostat.climate] Keep-alive - Turning off heater switch.riscaldamento_piano_sotto
2021-02-22 08:17:03 WARNING (MainThread) [homeassistant.config_entries] Config entry ‘RMmini3-1’ for broadlink integration not ready yet. Retrying in 80 seconds
2021-02-22 08:18:28 WARNING (MainThread) [homeassistant.config_entries] Config entry ‘RMmini3-1’ for broadlink integration not ready yet. Retrying in 80 seconds
2021-02-22 08:18:56 INFO (SyncWorker_1) [WazeRouteCalculator.WazeRouteCalculator] From: xxx
.
.
.
2021-02-22 08:36:07 INFO (MainThread) [homeassistant.components.automation.doods_activation] Doods activation camera est: Running automation actions
The activation at 08:36:07 was correctly following the motioneye trigger which I checked on motioneye interface, but there doesn’t seem to be anything related to the event at 8:16:56 AM which was reported by the logbook.
I followed your suggestion and went to see those links but I’m still struggling to make any sense about what happened. Apart from the fact that I had “default_config” in my configuration.yaml (only now thanks to your advice and upon reading the informations in those links I excluded something to alleviate the cpu load), I take that whatever is shown in the Logbook has to be present in the system log (which shows system information among other things) while the other way around is not necessarily true. If that’s the case the question remains: where did the entry at 8:16:56 AM come from.
Set the system log level to DEBUG if you want to capture all events. Be warned though, this will generate a lot of SD card writes and will reduce its life.
In the Logbook you will find wahetever is recorded n database by the Recorder function of Home Assistant : for instance when a light is switched off or an historical data of your living room temperature if you configured the recorder to do so.
Think about this as an operationnal supervision.
In the system logs, you will find… the system logs : all relevant infirmation about your system. For instance when you have an error performing an action, if your CPU usage is getting high, if an addon can not start,…
Think about this as an administration supervision.
Well then, thanks to all of you. So far as I understand I have no chance to find out where that “ghost entry” came from. Anyway, although I did not solve my problem, since the topic I chose was about a possible bug which is not I will flag the first Tom’s post as the solution as his replay demonstrated just this. Thank you