yeap the manual trigger is i think what i started with but then that one is a trigger added to the notification where u click on manually correct? then i did the custom action auto trigger, but it did not work… i removed the actions from that one and put them on custom action auto trigger in loop and that seems to work fine, but it is a bit delayed…so you are saying i should have the same actions in auto trigger in loop like i have now in custom action auto trigger as well? and that should fix the delay??
so it looks like it worked with both of them…its interesting tho… as mentioned earlier i will get the notification on the group of phones, but it doesnt alwyas follow the actions.
so there was motion in front and i got the notifcation and the actions played.
got another notification saying motion but actions didnt go through? shouldnt it be that if i get a notification the actions should also go through?
edit 1 : is this from cooldown or Silence New Object Notifications (Optional)
?
Hello everyone. I use this puppy for some rime already and just recently i noticed that its not sending me anythung anymore.
Now that i am checking it says “Automation is unavailable” and i have this droid head with the question mark.
I can edit it and when i try to safe it it says "meassage malformed: device unknown ‘false’
My system is version 2023.11.2
Interestingly, while poking around just now i found that i have 2 frigate notification blueprints??!!, one without a version number and one with 0.12.0.1. Something seems to be odd
I’ve found one issue preventing the initial action from working which is probably why you are seeing variations. Will try to fix it tonight.
If you want to do it though edit the blueprint and on line 938 there are 3 places it uses the key entered_zones. this needs to change to enteredzones with no underscore
here is the complete section with the fix
- alias: "Custom Action Auto"
choose:
- conditions:
- "{{ custom_action_auto |length > 0 }}"
- "{{ not zone_only or (not zone_multi and zones|select('in', enteredzones)|list|length > 0) or (zone_multi and enteredzones|length > 0 and zones |reject('in', enteredzones) |list |length == 0) }}"
- "{{ not initial_home }}"
- "{{ not state_only or states(input_entity) in states_filter }}"
Hello, i tried that one on the beta but did not change a thing.
It lets me save as soon i put a device name in but was using group name before. Hope that leads u in samo direction.
Is there actually a practical way to debug and single stepping like in regular sdk’s?
Correct, use a device and a group. it will behave as if you only use a group as per the group description.
The traces usually offer answers as you can see where things are failing, but only if the automation starts, until you add a device it wont be working.
HA 2023.11 enforces a new validation on the device input that they did not previously, hence it now being mandatory.