[BUG]

[jebeke65]

I am using the integration to dynamically drive my Smappee, meaning that I ‘continuously’ adapt the power to my car depending on the power I allow. Because if the monthly peak and the solar power and the house consumption, this might change very frequently.

It happens a lot that I ask e.g. 20A but the car is not receiving the 20A. The Smappee app is showing 20A though. If I then pause the Smappee and send again the 20A, then it’s fine again.

[myny-git]

Does this occur with the new integration, as API-calls have been changed.

Some questions/remarks to get this right:

• I guess you use standard charging mode
• how often do you change the current limits? Every second, every few seconds, every minute ...
• Does home assistant show you the correct current, or the smappee APP, or the dashboard?

[iwanvandaele]

Possibly the same issue here :

Symptom: the requested charging current isn't delivered to the car. HA and the Smappee app both show the correct value (10 A / 9.9 A), but the car only draws ~6 A (minimum).

Reproduction:

Session started via the HA button (start_charging) correctly at ~9.4 A/phase (my 10 A setting) for the first ~4–5 minutes, then dropped to ~5.8 A/phase (6 A) and stayed there the whole session.
Throughout, the HA number._current_2 limit stayed at 9.9 A and the HA select._charging_mode_2 reported standard — so from HA's side nothing changed.
support_grid for that connector went to 6 during the session.

A new charging session on Connector 2 seems to clear the mode selection, after which the requested current is ignored and the connector defaults to minimum (6 A). The HA integration still reports standard, so there's a desync between the reported mode and the actual cloud state.

The charging mode selection being lost in the Smappee cloud, per connector. On my station, Connector 1 kept "Standard charging". (no new session started) Connector 2 had no charging mode selected in the Smappee web dashboard (none of Standard/Smart/Solar highlighted), the selection Standard was lost after starting a new session.

[jebeke65]

Indeed. Sorry for the late response. (Holidays)

[myny-git]

A few things: indeed, I don't know why the Smappee cloud forgets the charging mode. Sometimes I believe their cloud may be 'buggy'. It would be interesting to see what the mqtt stream publishes about the charging mode. Because the integration updates the state based on the MQTT.

Session started via the HA button (start_charging) correctly at ~9.4 A/phase (my 10 A setting) for the first ~4–5 minutes, then dropped to ~5.8 A/phase (6 A) and stayed there the whole session.
Throughout, the HA number._current_2 limit stayed at 9.9 A and the HA select._charging_mode_2 reported standard — so from HA's side nothing changed.
support_grid for that connector went to 6 during the session.

This one is a bit strange. I assume you use standard charging. At least the HA integration is in par with the dashboard/smappee app, which is good.

I believe indeed there is nowhere feedback on 'real current delivery' and its setpoint today. You could try to make an automation which detects a difference in setpoint and actual current, (with some built-in hysteresis or threshold), and asks the integration to resend the setpoint.

[jebeke65]

As far as I remember, there is no endpoint that returns the current status

…

On 31 Jul 2026 at 07:48 +0200, myny-git ***@***.***>, wrote: myny-git left a comment (myny-git/smappee_ev#246) A few things: indeed, I don't know why the Smappee cloud forgets the charging mode. Sometimes I believe their cloud may be 'buggy'. It would be interesting to see what the mqtt stream publishes about the charging mode. Because the integration updates the state based on the MQTT. > Session started via the HA button (start_charging) correctly at ~9.4 A/phase (my 10 A setting) for the first ~4–5 minutes, then dropped to ~5.8 A/phase (6 A) and stayed there the whole session. > Throughout, the HA number._current_2 limit stayed at 9.9 A and the HA select._charging_mode_2 reported standard — so from HA's side nothing changed. > support_grid for that connector went to 6 during the session. This one is a bit strange. I assume you use standard charging. At least the HA integration is in par with the dashboard/smappee app, which is good. I believe indeed there is nowhere feedback on 'real current delivery' and its setpoint today. You could try to make an automation which detects a difference in setpoint and actual current, (with some built-in hysteresis or threshold), and asks the integration to resend the setpoint. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>