I know there is a History view available in the Rules section, but this is not helpful if you are trying to troubleshoot a device that is not linked to any rules, such as the floodlights, which are a nightmare to trouble shoot, ( esp. since they are usually mounted in such a way that a ladder is required to reset them, but thats another issue )
If the floodlights are turning on and off in a way that is not desired or intended, it would be great to see WHAT was causing this to happen
It would be so much easier to see what was triggering them to turn on / off / record events, and then adjust the various settings to work for your personal set up if we could see this information
When not linked to rules, I think Motion Tagging serves the same purpose. Even PIR triggered cams should include the motion tagged trigger via preroll that starts the event capture. Perhaps a bug precludes motion tagging for floodlights?
This would be great for the Floodlight Pro. Due to the Onboard AI, if the sensitivity is set to anything beyond mediocre, it will activate the lights on “AI Recognition” at a very low confidence threshold which will then completely fail to upload any event at all because the upload confidence threshold is so much higher. No upload, no tag.
I used Alexa as a workaround to detect any time the light was turned on to send me a push notification. I then had MacroDroid writing to separate logs, one for Alexa Light Activation Routine Notifications and one for FLP AI Detection tag notifications. Comparing the two allowed me to see how many AI Light activations were happening without any uploads and tags.
This is a great idea. I’d like to see a history section on each device or even an overall history section that lets you see when all things turned on or off, sensors were opened or closed, etc.