You can take a look at the raw webhook event sent by Netatmo by setting:
homeassistant.components.netatmo.webhook: debug
This should give some insights. The component does not treat vehicle events any different. If you can provide me with some test data I can take a closer look. (feel free to PM me here or on Discord)
Hi @cgtobi ,
This is how I found out about the missing keys in the payload, but I’ve just PMed you a fresh extract from my log. You will see that all the vignette* and snaphsot* related keys (*_id, *_key, *_url) are missing when type is vehicle.
Thanks again for your prompt reply!
Thanks @Friedrieck, I’m pretty sure that the events did contain those in the past. Not sure why they are not included right now. Unfortunately I don’t have an outdoor camera or access to a street facing camera. So, since we’re just passing the even along without removing any of that data this is not in our hands. I’ll pass that on to the Netatmo devs.
Problem solved!
It appears that to have these vignette and snapshot data in the callback, one has to set in the Netatmo parameters at least to record the vehicle events, which I had not (I guess it is the same for the other types). It must be done in the Netatmo app or on the Netatmo website (as pictured below). Having done so, these keys are now in the netatmo_event (for type: vehicle), as expected.
It looks like you don’t have the new template there but the legacy format.
That works different.
Is there a template: part in your config.yaml? If not just copy the code from my example in your config.yaml and it should work.
BTW, copying the actual code and pasting it here is working way better than posting a screen shot. The screen shot is harder to read and it doesn’t show the relevant other parts.
The code I shared is from my template.yaml file. The other stuff in that file is not relevant for you.
Looking at your code from template.yaml you mix up the new and the old (legacy) way of defining templates. You have value_template in your code and that’s legacy stuff. So I doubt if your templates are actually working when you put them in the template.yaml file.
Start with commenting out all code you have in template.yaml and add my code like below:
If that works add your previous stuff, but again I don’t think you have those in the proper place and you should have those as part of binary_sensor:. Your code also starts with binary_sensors which is not correct either.
Please have a good look at the links I shared earlier as there all the stuff regarding the new and legacy template methods is explained. There are plenty examples there which you can use.
And if formatation is wrong that will be related to identation, you can use Visual Studio Code or an online yaml checker for that.
The camera_id and device_id are part of another data indendation, so try the code below.
And you can also use developer tools and then events and monitor netatmo_event to show the data you are looking for.
# Netatmo human
- trigger:
- platform: event
event_type: netatmo_event
event_data:
type: human
data:
camera_id: 70:xx:xx:xx:x:a2
device_id: 70:xx:xx:xx:x:a2
Hi, new HA / Netatmo user.
Just one rookie question as Netatmo app does not sets presence at home quite accurately… is it possible to send to Netatmo app HA presence status?
I am planning to buy the alarm and would not like to have false triggers while home.
THX