Aaron Powell
Aaron Powell
I'd had a bit of a hack myself with the YAML and that's about what I came up with too but lacked the context as to why the original filter...
Mine looks pretty accurate with what I expected for today.
oh damn, nothing like an external API not returning data in the expected structure for the expected windows 😅
I've got it running on my instance (3 phase):  It is confusing because `Mer status` is **Good** but there's a fault and I have no idea what the `Mer...
btw - there's a few other calls still using the v3 API but I didn't dig into those (and I wanted to scope the PR)
Hmm, maybe some of those properties only exist if you're having a fault. I've just had a look at mine again (I'm back online) and I see there's less fields...
If you add the `?event_group=all` query string (as used for `sa_status_log_entry`) you can find those additional properties in the v4 API: ```json { "data": { "event_list": [ { "site_id": 316998,...
Now that my fault is resolved this is the entity in HA:  Since I can't actually find a schema for the REST API I'm mostly using the browser dev...
Ultimately, the more info the better IMO because it means that there's never any potential thought that the integration is "hiding" anything, which was why I added all the parameters...
`fault_exists` was definitely coming back in the JSON payload I had yesterday while my system was offline