Netatmo adapter does not show all received event data (subevents) from netatmo outdoor cameras

[The2Earthlings]

Describe the bug
When checking the logs of the event handler you can see that Netatmo delivers subevent data. Here the logs in iobroker from the iobroker.netatmo adapter:

Handle Event: {"id":"63c1481xxxx","type":"outdoor","time":1673611290,"module_id":"70:ee:50:xx:xx:xx","subevents":[{"id":"f497f0e9-1cb2-4194-97a4-1b84af591ca2","type":"human","time":1673611290,"verified":true,"offset":0,"snapshot":{"url":"https://netatmocameraimage.blob.core.windows.net/production/63c1481cb7642afdea02axxxx"},"vignette":{"url":"https://netatmocameraimage.blob.core.windows.net/production/63c1481cb7642afdea02a7fe9a0902a5494e42700xxxx"},"message":"Person erfasst"},{"id":"fa4cae9c-xxxx","type":"human","time":1673611305,"verified":true,"offset":23,"snapshot":{"filename":"vod/29aebfc9-009d-43ac-xxxx/events/fa4cae9c-6bcd-xxxx.jpg"},"vignette":{"filename":"vod/29aebfc9-xxxx/events/fa4cae9c-6bcd-xxxx/vignette_fa4cae9c-xxxx.jpg"},"message":"Person erfasst"}],"video_id":"29aebfc9-xxxx","video_status":"available"}

But the object structure in iobroker for the netatmo adapter does not show up these information. At least this information is in my eyes relevant for events:

• module_id -> to get the right camera
• type -> to identify the event type
• snapshot.url -> image url
• snapshot.filename -> image filename
• vignette.url -> vignette url
• message -> message which describes the event
• vignette.filename -> vignette filename

Versions:

• Adapter version: 3.1.0

[Apollon77]

In fact the "historic events" are not containing all data, this is correct. Is it really needed there? because of the dynamic naming they are more for reference than for a real automated usage ...

The data are listed in the Device specific event states then when they happen ... Please check the .LastEventData. states ...

[The2Earthlings]

I am not using the LastEventData (even not configured).

It would be very helpful also for historic information.

• module_id: At the moment you cannot assign an event to a cam if you have multiple... then you have to check with all cameras :-( => this is not dynamic so this is already very helpful

For the subevents I think you can just iterate through and create sub objects (id's) in ioBroker. Then everybody can use or not use the information.

Why I need the following data:

• snapshot.url: when showing my historc event I always display a mini image to identify faster where it was; without image this would not be possible
• message: currently with the implementation you do not know what happened at the event... just "outdoor" is not useful I think... the message shows more details