[APP] Amina - Power up your smart home with Amina S

The sun is (slowly) out so I have been using my “solar charging” flow again for a few days now.

It is working very good now.
My return energy is below 200W.
I wont get any better because the resolution of controlling the Amina is (1Ampere x220V=) 220Watt resolution)

In the middle the readout of my energy meter. You can see the peak loads (my quooker) does not affect the charging.
You can also see it nicely stays around zero.

The top is rhe mean value (1min) of that same readout. I use that as input for my flow

At the bottom is the current usage of the Amina, that is nicely following the mean (with a resolution of 1A)

The setup is also robust for sudden changes. Below you see the response of sudden high usage (my induction cooking switching on for a boiled egg during lunch :grinning:)

2 Likes

Tried the import @FKey that works. Unfortunately it only imports one flow.
I have sent you a DM!

1 Like

Amazing update :star_struck: Thanks for sharing these insights.

I have published my flow for “Surpluys Solar Charging” as a TEF file for importing.

I have added it to the sections where I explained the “surplus solar charging” above

2 Likes

no readings phase B&C after homey was off for >5min

I ran into an issue after homey had been off for a longer period (>5min).
After restarting homey the Amina app restarts fine, but reporting on phase A & B (current and voltage) has stopped. This made my surplus solar flow behave very instable.

A restart of the App fixes the problem. So I now have a flow that restarts the Amina app, 1 minute after a homey restart.

Rootcause:
The problem reproduces very well,so I was able to provide the app developer with good diagnotics.
They found the issue, but it need sto be solved by Athom.
When homey is down for a longer time the zigbee network needs to be rebuild. Homey does not report when that is done.
If an app starts before the network is up the handlers in the app are configured wrong. It is also not possible to detect this by the app.
So untill Athom provided a solution, restarting the app after 1min is the best way to go…