Too bad you guys aren’t sending any diagnostic reports, and login after a year and start with
“Too bad the app hasn’t been updated in 2 years”.
Nothing is stopping you from making a pull request to fix a problem, right?
I’m sorry if I offended you. That was not my intention.
I just got on here to see if anyone else experienced the same thing.
Maybe they already brought it under your attention.
The thing is that with community based apps the development sometimes stops once the developer doesn’t want to put in the effort anymore.. And I assumed this was the case because it says that the app wasn’t updated for 2 year.
My mistake for assuming and I apologise again.
Can you tell me what information you need to look at the problem? (And maybe instruct me on how to do this in GitHub.. I don’t know the platform)
I’m happy to help!
Thanks!
You could send me your login details so I can take a look. If you don’t want to, then you have to wait until someone does, because unfortunately I do not own a Smappee device myself. I initially build it together with someone else who provided his login credentials.
Also mention what setup you have, so which devices you have in Smappee.
You can do this via a PM, or via email which I can provide via a PM.
Can you send me your e-mail? I can share the location with you as read only.
Yeah, that is also a problem. I forgot to mention this. When locations are shared with other people, those people don’t have access to the API, so I do need your “master” account, unfortunately.
Since 30 July (±17:25) the measure_power of my Smappee EV1 has been frozen at 0 W in Homey, while charging and cable_connected still update live and charging control from Homey keeps working. The Smappee cloud/dashboard shows correct live values.
Restarting the app and a full Homey Pro reboot did not help — verified during an active charging session (~4.6 kW confirmed by my P1 meter, charging=true, EV1 stayed at 0 W, lastUpdated unchanged since 30/7).
Maybe useful for debugging: power reporting worked fine for me until 30 July, then froze mid-day. App v1.3.4, Homey Pro (early 2023).
Diagnostic report: 81b85850-83b3-4c73-98a9-cd755a6ad863
Happy to provide more info if needed.
Small follow-up on my report above, with some extra findings from today that might help narrow things down:
- The freeze is clearly on the integration side, not on the charger itself: the Smappee app shows my EV Wall charging at 1,514 W live, while the measure_power (and measure_power.alwayson) capability in Homey has been frozen at exactly 0 W since July 30. Meanwhile the event-type capabilities (charging, cable_connected) keep updating within seconds, so the connection itself is alive.
- Possibly related: charging_mode in Homey only knows normal / smart / paused. I switched the charger to Solar mode in the Smappee app this morning, but Homey still reports “smart” (last updated hours before the switch). So Solar does not seem to be modelled in the capability - same request as Toon_Tijtgat made earlier in this thread, +1 from me.
Happy to test a new (test) release or send another diagnostic report if that helps. Thanks for all the work on this app!
Thank you for your detailed findings. If the app worked correctly before, the cause of it suddenly not working anymore is probably due to changes on the side of Smappee. As I do not have a Smappee integration at home, I would like ask you to provide your login information as stated here to investigate the problem further.
As far as I can see, that mode isn’t supported by the API (docs), or it isn’t documented…
@Toon_Tijtgat Or I need your login details to check how this mode is set in the Smappee portal.
retired my Smappee today. It is obsolete for me since the smart meter.
Thank you evdpol for your good work. You’ve done a brilliant job, despite the unreliable Smappee API 
Thanks @evdpol. I’d rather not share my Smappee login, but I can give you something more useful: I’ve been running my own workaround against the Smappee cloud API for six weeks now, so here is what I found.
1. Solar mode can be set through the API — not via the documented setChargingMode endpoint you linked, but via the smart-devices action route:
POST https://app1pub.smappee.net/dev/v3/servicelocation/{serviceLocationId}/smartdevices/{connectorUuid}/actions/setChargingMode
body: [{"spec":{"name":"mode","species":"String"},"value":"SOLAR"}]
Returns 200 and the charger switches within seconds; the same call accepts SMART, NORMAL and PAUSED. I call this daily from HomeyScript (Bearer token from the normal OAuth flow). So a charging_mode value “solar” would be feasible in the app. One quirk: when the connector is paused, SOLAR/SMART only take effect after an un-pause first (I send the smart-mode card, wait 5 s, then set SOLAR).
2. measure_power is still frozen at 0 W since 30 July (app 1.3.4, Homey Pro 2023); charging and cable_connected keep updating live. I’ve switched to my P1 meter for the charging power, so it’s not urgent for me, but it’s still broken.
Happy to install a test build and report back, or to send diagnostic reports / raw API responses (with ids redacted) if that helps.
Hello,
I had a look at the Smappee API and this is technically possible — and I can confirm that controlling the EV Wall this way already works in practice.
Charging current can be controlled through the official API:
PUT /dev/v3/chargingstations/{serial}/connectors/{position}/mode
using for example:
{
"mode": "NORMAL",
"limit": {
"unit": "AMPERE",
"value": 12
}
}
I currently control the EV Wall this way and can dynamically change the charging current, while taking the documented limit of 20 API calls per hour into account.
So maybe you could que that card to send with the next api call.
So it should be possible to add a Homey Flow action such as “Set charging current (A)”.
The actual charging current can also be read through the consumption API. Smappee provides the individual phase currents (L1, L2, L3). For a three-phase charger, the useful EV charging current should be the average of the active phases, not their sum. For example, 16 A on each phase means 16 A charging current, not 48 A.
So in principle the Homey app could expose both:
=> Actual charging current in amperes
=> Set charging current in amperes
This would make the Smappee EV Wall much more useful for external EMS integrations, dynamic PV charging and Peak Guard control.
I am diving into this app again after a long time. I see more people are participating and providing very useful and practical information and solutions even, thanks!
As I do not own a Smappee device, and me having limited electrical knowledge on this level, bear with me on this one.
I’ll catch up with the replies, and maybe we can sort things out, as I see some of you are also know their way around the technical API stuff which is always very helpful.
Hi Edwin, since Homey firmware 13.5.2 (rolled out 16/10 ~06:00) my EV Wall device keeps measure_power at 0 W while the car is charging (Smappee cloud shows 3.8 kW). REST data (charging state, cable) still updates; the MQTT realtime channel seems to be gone: UniFi shows no connections from Homey to mqtt.smappee.net since the update, nothing blocked. App restart didn’t help, no repair option. Diagnostics report: e1696b6d-ae28-46c2-b34e-60051867896b. App v1.3.4. Thanks! Wim
