Obviously, we do care. That is why we released version 2.0 even while we weren’t able to fully test it, as it was complete broken for all Equalizer users without notification to us as developers due to an endpoint being shut down. We rushed the required update that we were preparing in the background, and unfortunately that update seems to break for a, for what we are currently aware of, a small group of users.
Version 2.0 is a complete, modern update of the app, making sure that we can support the app for everyone. Unfortunately, attending the IFA in Berlin has hampered our progress on making progress so far, but it is the first thing that is being looked at for the remainder of this week.
It’s quite hurtful to see these kind of comments of people who do not know what has been done in the background to make this app more robust and better for everyone…
Yes, well thats how I feel, If you’re not able to test the app before you release it, then don’t release it until it’s tested, If you release it either way be sure to fix bugs asap. As of right now it’s not better for anyone. If it’s not working for small group of people, I don’t know but it’s broken for everyone I know.
Same problem here as Jeppe_Ladefoged after update to version 2.0.1 there is no data coming in/out from the charger and the flows for automation are stuck that triggers on that data like: “Charging state” i have re-add the device and repair al my flows after that action, but 24hours later still no data from the charger in my homey app.
drenso When do you expect when the issue resolved? or is it possible to install the old version for the time being?
Thanks in advance if you want to reply and i hope we can realise a workaround for the time being by installing the old version.
In case it helps anyone while we wait: if you have an Equalizer, it still works fine on 2.0.1. Here it’s only the charger device that’s frozen. Mine says Paused while the car pulls 10 kW, but the Equalizer shows total power and current per phase within seconds. Stop from a flow also still works. I stopped a 10.7 kW session from a flow today and it cut within about 15 seconds.
So I simply stopped asking the charger whether it’s charging:
If your car has a Homey app, use the car’s own power and connected status.
Otherwise use the Equalizer’s total power. Above a certain level, a car is charging. Check your own Insights for where your house peaks and where charging sits. My house tops out around 4 kW and charging is about 11 kW, so I use 5000 W.
Check twice in a row before acting on it.
If you run Easy Charge Controller or your own flows, feed the charging/connected input from the car or the Equalizer instead of the charger.
A few things to keep in mind:
Single-phase charging, like many plug-in hybrids at around 3.7 kW, disappears in normal house load. A power threshold won’t catch it.
After a power cut on the Homey I got a few fake 7 to 11 kW readings from the Equalizer for about 15 minutes. Checking twice handles that.
lastUpdated only changes when the value changes, so a steady reading can look hours old even when everything is fine.
I also handle guest cars. If the Equalizer shows charging-level power, and my car isn’t connected and isn’t drawing power, twice in a row, it’s someone else’s car. Then I leave it alone and send one notification per visit. Haven’t had a real guest on it yet though, so see it as an idea rather than proven. Also good to know: after stopping a charge, the next car plugged in starts charging without a new start command, so a leftover stop doesn’t block anyone.
One warning: calling Easee’s cloud API from a HomeyScript means putting your full Easee password in the script. There are no scoped API keys. I wouldn’t…
Sorry to hear that. What does “not working” look like on yours? Frozen values, no power reading at all, or flow cards that don’t trigger? Here the Equalizer updates total power and per-phase current within seconds on 2.0.1, and it’s been paired since before the update. If yours was re-paired after 2.0.1, that could be the difference.
No data at all. So flow cards don´t trigger as well, because of no data at all. It was paired before 2.0.1 and everything was working. After 2.0.1 all data stoped from both charger and Equalizer. I can of cource still send commands localy to the charger - Just don´t get anything back for either of the units.
I just hope that the fix mentioned from drenso is close and working
Same app version here, and I’ve seen a milder version of that. Once both devices went stale at the same time. Restarting the Easee app (Settings, Apps, Easee Home, Restart) brought the Equalizer back within seconds, but not the charger. It doesn’t interrupt charging, so it’s safe to try. If you end up removing and re-adding the devices, give them most of a day. My re-added charger showed nothing for hours and took about 9 hours to fill in all its values.
We just pushed version 2.0.2 which should resolve your issues! If the issue still occurs please make sure to generate a new diagnostics report as close as possible to the moment it stopped working for you (due to limited logging length) and share the code with us (by email only).
I am getting data right now (on 2.0.1) – I also got some for a few hours yesterday. But the flows still don’t react to it, and the data was gone again shortly after. So I expect it to be the same. But the great news from Drenso regarding 2.0.2 might solve it all. Fingers crossed, and good job getting a new version so soon – I did expect it to take longer, to be honest
@drenso Thanks for the quick turnaround. The store says “Resolve reconnection issue”. Does that cover the charger state freezing (charger_status, measure_power and evcharger_charging stuck while the Equalizer keeps updating)? I’m holding off a day because I’m in the middle of a stability test on my Homey, then I’ll update and report back.
