As far as I know the original doesn’t work with hyphens either based on earlier discussion in this thread.
Did you try my beta? I tried to resolve it in that one.
The original did seem to work for me with Hyphens.
I have now updated to the Beta one and will see if it works, thanks!
Oh yes because you have to type the name of the camera in that rather than select the entity. I remember now.
In any case. I can fix the blueprint for you, just let me know how it goes with beta
1 Like
@SgtBatten Good day. I was able to install your revised blueprint and it worked wonderfully. Thanks for taking time to support this!
2 Likes
Got it working thanks for the assistance @SgtBatten
Now trying to get the disable_times working, I set them from 5 - 19 - Thus I only want notifications outside of these time.
Yet the condition seems to be True all the time:
conditions/3
Executed: January 6, 2023 at 14:07:07
Result:
result: true
entities: []
When I enter the values into the Developer Tools, then I get the expected result of False:
When I replace this condition
"{{ not disable_times|length or not now().hour in disable_times }}"
with this
"{{'false' if now().hour in [5,6,7,8,9,10,11,12,13,14,15,16,17,18,19] else 'true'}}"
Interesting… What was your automation yaml during the traces where it went true
Edit: just tested myself and same issue.
I think I see the problem. Current user facing selection menu creates a list of strings not integers. Will look into it later today.
Edit 2:
I think I have resolved it with beta 8j
2 Likes
After updating on Frigate 12 Beta the blueprint stopped working for me.
Can anyone confirm this?
Which blueprint? If the original one by hunterjm there is an issue with frigate since 0.11. it doesn’t seem to affect everybody but I have fixed it in my fork if that is indeed your problem.
If not then we need to understand what’s not working and if there are any errors in the log or in the blueprint trace. Also we need to understand what changes with frigate 12.
Now that I have my notifications working well (thanks @SgtBatten), I want to add a little more. I would like to trigger some other events based on this outside of HASS. Is it possible to setup a virtual device and turn it on when motion is detected? I can then use this device to make some JSON calls and other things needed to alert people in the house via Sharptools touchscreens connected to my Hubitats.
I think the Frigate integration does what you need already. There are plenty of sensors exposed by it.
Yes the frigate integration can already give you a motion Boolean among other things. If you want it filtered in the same way as the notifications though you would likely need to modify the blueprint to also do action x
I dont get any notifications anymore either since going to beta 12
Someone else reported this too. I have not updated to beta 12. Can you share the content of the mqtt message when a new event is triggered?
Is this it:
{“before”: {“id”: “1674046429.669159-w0do3k”, “camera”: “Gavl”, “frame_time”: 1674046797.507163, “snapshot_time”: 1674046795.980295, “label”: “car”, “sub_label”: null, “top_score”: 0.84375, “false_positive”: false, “start_time”: 1674046429.669159, “end_time”: null, “score”: 0.68359375, “box”: [1424, 157, 1942, 699], “area”: 280756, “ratio”: 0.955719557195572, “region”: [0, 0, 2488, 2488], “stationary”: true, “motionless_count”: 257, “position_changes”: 3, “current_zones”: [], “entered_zones”: [], “has_clip”: false, “has_snapshot”: false}, “after”: {“id”: “1674046429.669159-w0do3k”, “camera”: “Gavl”, “frame_time”: 1674046802.552679, “snapshot_time”: 1674046801.974467, “label”: “car”, “sub_label”: null, “top_score”: 0.84375, “false_positive”: false, “start_time”: 1674046429.669159, “end_time”: null, “score”: 0.84375, “box”: [1405, 166, 1935, 720], “area”: 293620, “ratio”: 0.9566787003610109, “region”: [835, 0, 2127, 1292], “stationary”: true, “motionless_count”: 286, “position_changes”: …
Does anyone know if it’s possible to download clips or snapshots on the iOS companion app? I’m having problems doing this.
EDIT: I raised an issue on github as it’s a limitation of the app, Safari works fine.
I looked at some of the changes in the beta docs and i dont think theres been a change to the mqtt topic or message format, so are you getting traces at all? From what I can see you should be and if you are, perhaps the issue is with the frigate integration. Did you update that to the beta also? And could you advise if the camera name or fps sensor entity is different?
Integration is updated aswell.
sensor.detection_fps
camera.gavl
Same question as above. I think it’s purely because sensor.[name]_camera_fps no longer exists.
Can you show me what sensor.detection_fps looks like in dev tools and I can get a fix out right away.
I was not right, this is not the issue
Hmm unfortunately that’s not going to be the issue I originally thought, is there a sensor for the camera fps still? I assume this is unchanged so i’ve been focusing on the wrong thing.
I need to know what’s different, perhaps I just need to upgrade myself.