Portal Notification in HA

4 comments started 2023-08-14 last 2023-08-14
Cloud PortalHome Automation
P
#1 Phil_H

Yesterday afternoon after my battery hit 100% something went wrong and I ended up with a number of BMS over voltage and Battery voltage high errors in the portal notifications, the system also took my battery offline and so wasn't discharging to the house in the evening. I've managed to resolve the problem and it is currently running fine, but I only noticed by chance that the battery wasn't supplying the house when I happened to walk past my always on display.

I have Home Assistant installed and while I could try to set an automation to detect the scenario based on battery voltages and charge/discharge powers and grid usage etc, I was wondering if there is a simple way to get the portal notifications back to HA so that I can notify my phone for any issues?

C
#2 cluelesscris

Phil_H I have made a suggestion to GE that they add email notifications option to the portal. I have managed to cobble together a solution which uses screen scraping and node red to detect notifications and generate an MQTT message which HA listens for and blasts an SMS message to my phone and an email to my inbox. I used node red because I already had similar logic for monitoring my horses through cctv (long story!) but you could do it all in HA without node red.

P
#3 Phil_H

cluelesscris Screen scraping for it feels a little crude given the tech we're dealing with (not saying your choice to do that is crude, but we should have better methods)!

I've got as far as https://beta.givenergy.cloud/docs/api/v1#inverter-data-GETinverter--inverter_serial_number--events which looks like it will give me the sort of event details I'm expecting for a given timeframe but getting HA to run the script and then get the results back to trigger a notification is currently beyond my knowledge.

C
#4 cluelesscris

Phil_H Yes, it's very crude but as I said I already had the logic and a few tweaks and I was done. The API is a much better path but at the time the API was very unreliable. You are right in that it should be preferred. I'm a don't fix what isn't broken sort so never bothered to go back to the API.

I do use API logic in other automations but again I use node red for the actual API exchanges as I am yet to get to enjoy working with YAML. Node red being very visual suits my development style. It also has very good API handling nodes.