I tried it already and it doesn’t. What capabilities do you have defined for lifetime energy?
I had similar issues for my Homevolt app in the past and then it was down to how I’d defined those.
That would be meter_power
Hm, alright … Could it be an issue with the energy capabilities needing to be defined more explicitly? E.g. this from homey docs. It sounds a bit weird, but it doesn’t seem to show up today and it does for most other devices 
{
“name”: { “en”: “My Driver” },
“energy”: {
“meterPowerImportedCapability”: “meter_power.imported”
}
}
Appreciate you thinking about what can be off 
meterPowerImportedCapability is set here, homey-no.easee/drivers/charger/driver.compose.json at d14260688cb08a692d3f338184c365cf9b5f7426 · ricott/homey-no.easee · GitHub
Should’ve just looked at the source directly 
Then I’m out of ideas. Only thing I can think of is the the driver capabilities has been changed for new devices but not updated dynamically for old ones.
I’ll try to delete and re add my device to test the theory 
1 Like
I am also missing Easee in the top consumers. I also have an issue where I can not see any Effect data (W) in insights. It says it does not find any data and then Homey crashes every time I try to look. I can see kWh and other data from Easee, and when the it’s charging I can see that the effect shows (W) correct.
The issue with top consumers was fixed by Athom in Homey firmware 12.6.0
- Allows EV chargers as possible Top Consumers.
3 Likes
You should ask Athom, as the only information the Easee app reports is 36kWh.
1 Like
I understand but maybe someone seen the same behavour?
The total usage was 48,5 kWh
Easee usage was 36 kWh (Shown as 286%)
Heating usage was 0,9 kWh (Shown as 7,1%)
So what I figured out:
Easee usage is calculated: 36 / (48,5-36) = approx. 286%
Heating usage is calculated: 0,9 / (48,5-36) = approx. 7,1%
Conclusion: Easee usage is subtracted from total usage before calculating percentage for both Easee, Heating and all other consumers.
Hello,
Can someone please share their screenshots (in English or Dutch) how they managed to get the car charging in the cheapest 4 hours during the night between 0-6hr (through PBTH)? When I connect my car and authorize it immediately starts charging. I want it to charge during the 4 cheapest hours.
Thanks in advance.
I have been using the “Turn off” flow card to stop charging in a flow for years now, but recently that is no longer working. It seems the flow card no longer exists (despite being shown on the app page Easee Home | Homey), so I changed it to use “Stop charging” instead. However, that also doesn’t work for me. I usually set a schedule in the app, and then from a flow I stop the charging based on some other parameters. This used to work fine (with the “Turn off” flow card), but as I said, it no longer works.
It seems the only way (for me) to stop charging from a flow is to use the “Pause charging” flow card instead (or possibly set the dynamic current low enough). Since the app hasn’t changed for a month, I suspect that perhaps Easee has done something in their system.
Not the end of the world, just annoying when things that used to work stops functioning.
Turning smart charging off and on. Whats considered frequent? I mean flash should be able to write atleast 100k+ times. Right?
I was thinking as i can use both homey and Tibber at the same time I would just make a flow to turn off smart charging when the car is at 90% charge to stop tibber from charging and re-enable it every time car is plugged back in as our Zoe has no way of controlling this.
It’s been reported on github - a user found that the api has been changed - but no response from the developer yet.
I hadn’t checked Github, so thanks for letting me know. Using pause seems to work OK for me, but it is a bit annoying when they change the API like that.
You’re welcome. I might give the pause card a shot - currently Ive simply set the easee app not to charge during the evening where it’s most expensive here.
Sorry, been busy with … life, I guess 
I don’t believe I have received any diagnostic reports for the problem mentioned.
I checked the Easee developer Slack channel, and there are no mentions of a changed API. If there are breaking changes, they usually email me since they are aware that the Homey app has lots of users.
Hi, I have been extremely satisfied with the Easee app, and it has worked flawlessly for as long as I have been using it. Nine days ago, Homey lost contact. It seems like I can’t log back in, I get a timeout error message. I haven’t made any changes to my network or charging settings. Has anyone else experienced similar problems? Or does anyone have any ideas on how I can troubleshoot this? I can connect to the charger if I use the Easee native app.
Given that the last release of the Homey Easee app was in October, it is not a code change that is the reason for these problems.
I wrote this on a GitHub issue yesterday regarding the problems with the turn on/off actions.
I have done some testing and chatted with an Easee developer on Slack. There seem to be multiple changes in their internal logic and possibly a bug as well regarding the commands endpoint where we check if the command was accepted by the charger. This endpoint now hangs for 12-13 seconds on each invocation - previously the reply was instant.
I pushed a test version where I attempt to address all changes.
2 Likes
Does the app also works with the “easee charge up “ wall changer?
