I'm trying to use this to track EnOcean button state, which has a list as the identifying value. The obvious choices for event filter "id: 254, 237, 171, 245" and "id: [254, 237, 171, 245]" both get truncated at the first comma when saving the configuration. I'm probably just missing the right syntax to use, but maybe it could be added to the documentation?
Hi @rvk, that kind of event filter is not possible with the current implementation, as it is expecting simple filters without that kind of nested data (a list of integers in your case). Sorry :(
I'm trying to use this to track EnOcean button state, which has a list as the identifying value. The obvious choices for event filter "id: 254, 237, 171, 245" and "id: [254, 237, 171, 245]" both get truncated at the first comma when saving the configuration. I'm probably just missing the right syntax to use, but maybe it could be added to the documentation?
Here is an example of the event:
{ "event_type": "button_pressed", "data": { "id": [ 254, 237, 171, 245 ], "pushed": 0, "which": 0, "onoff": 0 }, "origin": "LOCAL", "time_fired": "2021-04-22T04:02:27.549129+00:00", "context": { "id": "0a49bae0cf4c4281b6fa10be9b7e48b9", "parent_id": null, "user_id": null } }