Major change / improvement

[myny-git]

All,
I did not plan to do any major improvements, however, I discovered mqtt.smappee.net. This is an online mqtt service with nearly realtime data.

It works nicely for me on my setup, however, please let me know what does not work - or what need improvements.

Moreover, if you don't see the power/current/energy values, then, I would like you to do a curl with information shown below:
https://smappee.atlassian.net/wiki/spaces/DEVAPI/pages/916422661/Get+metering+configuration
I use this information in the integration to specify what is what.

Anyway, this would make MODBUS obsolete.

[myny-git]

I see now that for 1 phase, Smappee does not make a nice list in the meteringconfiguration. grid and pv are nicely mapped, but the carcharger not.

For the ones who want to test the mqtt and what you see, before you try:

install a software package MQTT Explorer
then:

1: just pick a name, I just use my serial number, but I do not think this matters
2 and 3 are equal, and are you servicelocationUUID. You can take this from getmeteringconfiguration

Then: click on advanced and add a topic:
servicelocation/SERVICELOCATIONUUID/#

Afterwards, it should start running.

[scruysberghs]

I've sent you some feedback on MQTT tests in Discord

[ballydoon]

I have a single phase EV wall with Smappee Connect. The MQTT appears to be working even though it's not supposed to with a connect device. I tried MQTT explorer and got the following.

mqtt.smappee.net
servicelocation
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
etc
carcharger
acchargingcontroller
v1
devices
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
property
chargingstate = {"available":true,"percentageLimit":0,"chargingState":"STARTED","chargingMode":"NORMAL","optimizationStrategy":"EXCESS_ONLY","iecStatus":{"current":"F"},"status":{"current":"UNAVAILABLE","stoppedByCloud":false,"errors":[]}}
power = {"serviceLocationId":xxxxxx,"utcEndtime":1755768530000,"consumptionPower":2548,"solarPower":-1,"alwaysOn":172,"froggySensorDailyDeltas":[],"infinityInputSensorDailyDeltas":[],"channelData":[2307,5,0,0,0,2548,-220,-1,10,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"currentData":[9,11160,48,11,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"a…
tracking = {"value": "ON", "clientId": "ha-xxxxxxxxxxxxxxxxxxxxxxxxxx", "serialNumber": "xxxxxxxxxx", "type": "RT_VALUES"}
homeassistant
heartbeat = {"serviceLocationId": xxxxxx}

/
/

servicelocation/xxxxxxxxxxxxxxxxxxxxxxxx/homeassistant

[myny-git]

Hi, yes, that was the discovery ;-) It is working and you get about 5sec data...
Now, with your meteringconfiguration, the current implementation does not work, as your meteringconfiguration is pretty 'empty'.

But from your mqtt, everything is there. Let's see, whenever I have time, I look into it.

[ballydoon]

Here are the entity values I get. The currents L2 and L3 don't appear as expected.
I disabled MQQT Last Seen as it writes a logbook entry every 5 seconds.

It appears if MQTT disconnects it changes settings as it reconnects ie. Charge Mode, Stop, Start, Pause, and Connector Available (without actually making the connector available).

Log as follows-
Smappee EV Wallbox Charging Mode 1 changed to SOLAR
8:46:12 PM - 5 minutes ago
Smappee EV Wallbox MQTT Connected was connected
8:46:10 PM - 6 minutes ago
Charging state 1 changed to STARTED
8:46:09 PM - 6 minutes ago
Smappee EV Wallbox MQTT Connected was disconnected
8:46:08 PM - 6 minutes ago
Smappee EV Wallbox Connector 1 available turned on
8:46:08 PM - 6 minutes ago
Smappee EV Wallbox EVCC Charging Control 1 turned off
8:46:08 PM - 6 minutes ago
Smappee EV Wallbox Set charging mode 1 changed to August 19, 2025 at 4:34 PM
8:46:08 PM - 6 minutes ago
Smappee EV Wallbox Pause charging 1 changed to August 19, 2025 at 4:32 PM
8:46:08 PM - 6 minutes ago
Smappee EV Wallbox Stop charging 1 changed to August 19, 2025 at 5:35 PM
8:46:08 PM - 6 minutes ago
Smappee EV Wallbox Start charging 1 changed to August 21, 2025 at 3:51 PM
8:46:08 PM - 6 minutes ago
Smappee EV Wallbox Charging Mode 1 changed to NORMAL
8:46:08 PM - 6 minutes ago
EVSE status 1 changed to UNAVAILABLE
8:46:08 PM - 6 minutes ago
EVCC state 1 changed to F
8:46:08 PM - 6 minutes ago
Smappee EV Wallbox MQTT Connected became unavailable

[myny-git]

I have now seen a similar bug. When Home Assistant restarts, and so MQTT disconnects and reconnects, my values are gone and became unknown. Other values became weird. So I need to see how to remain the last known states for these MQTT sensors.

[dirkpiano]

Version 2025.8.12 working perfectly here, fantastic addition, I can finally create an entity "1 phase / 3 phase charging" that doesn't need to guess just based on the P1 meter's phases

[dirkpiano]

update: after I disconnected the cable the status changed immediately to STOPPED, and the EVSE status changed to AVAILABLE

[myny-git]

All, I updated the code - I also got a bit inspired with the approach of https://github.com/edwinvdpol/homey-smappee

I don't want to release it completely yet, however, for those who want to experiment:
Version 2025.8.12b4

I am curious how single phase installations go, 2 cable installations and multi-servicelocation installations.
Also, I want to do some debugging before I release this in general as a release. So all inputs welcome with respect to sensor names, ...

[ballydoon]

Hi

Happy to try it on my single phase system. Tried to download the new version via HACS but got a migration error. Went back to the previous version. I am a bit of a novice, should I install the test version in a different manner?

[myny-git]

Just remove your old installation and reinstall.

[myny-git]

For everyone who is helping to test, take 2025.8.12b6 --> I found a small bug in a translation of grid power data
consumption power --> house consumption power
grid power = grid power

Looking forward to your tests. Please post here a screenshot of the integration in HA. This is how mine look:
3 phase EV Wall Home.

So far, everything seems to work nicely

[gvnuland]

I'm back from holiday. A major step forward in the new version. I like it.

[myny-git]

Thanks, which version did you install? I am still looking to make a new release from 2025.8.12b6, after a few users did some pre-testing. I can only test my own situation ;-)

[myny-git]

Could you maybe try this version?
2025.8.12b6

[gvnuland]

2025.8.12

…

-------- Original Message -------- SUBJECT: Re: [myny-git/smappee_ev] Major change / improvement (Discussion #17) DATE: 2025-08-25 14:21 FROM: myny-git ***@***.***> TO: myny-git/smappee_ev ***@***.***> Thanks, which version did you install? I am still looking to make a new release from 2025.8.12b6, after a few users did some pre-testing. I can only test my own situation ;-)

-- Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. You are receiving this because you commented.Message ID: ***@***.***> Links: ------ [1] #17 (reply in thread) [2] https://github.com/notifications/unsubscribe-auth/ATUFOZGKVFTUAOGPSY3NQLD3PL5WBAVCNFSM6AAAAACEMC22OCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMRRGAYDMNA

[gvnuland]

After install all entities were disabled. Also a reset of the configuration doesn't work. I don't like always to delete all sensors and install it again. All automation rules are corrupt and the energy configuration lose all historical data... Can you have a look that the sensors still work after upgrade?

…

-------- Original Message -------- SUBJECT: Re: [myny-git/smappee_ev] Major change / improvement (Discussion #17) DATE: 2025-08-25 15:27 FROM: myny-git ***@***.***> TO: myny-git/smappee_ev ***@***.***> Could you maybe try this version? 2025.8.12b6

-- Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. You are receiving this because you commented.Message ID: ***@***.***> Links: ------ [1] #17 (reply in thread) [2] https://github.com/notifications/unsubscribe-auth/ATUFOZGLHXDTXTJMYYAYV3T3PMFLPAVCNFSM6AAAAACEMC22OCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMRRGA3TEMY

[myny-git]

I understand that this has happened in the past. Apologies for this, but it is my first time making a github repo. I hope that after this 2025.8.12b6, which I want to turn into a real release 2025.8.14 (after some users confirm this), no major refactoring is needed.
Is there no way to test your situation, without reinstalling it? Perhaps on a second home assistant?

Well, I tested it by first deleting my current integration, then restarting home assistant and re-installing the newest version (b6). And indeed, I have manual disabling foreseen.

[myny-git]

you can look at the post above, there I posted a picture for my entities.

[scruysberghs]

Testing 2025.8.12b6

Second charging station (currently in evcc pv mode)

Need to confirm but it looks like the energy import sensor is overreporting. Yesterday it went up by over 10kwh per hour while only charging 4kw.

Also, one small thing with 2 charging stations, controls like the max charing speeds numver (slider) have a unique senor id like number.smappee_ev_5130051969_max_charging_speed_1 and number.smappee_ev_5130053002_max_charging_speed_1 while the sensors do not (for example sensor.connector_1_current and sensor.connector_1_current_3 )

[myny-git]

The newest version 2025.8.12b8 has solved the sensor names, making it uniform and unique.
One item I am considering; removing the MQTT last seen, as it is flooding the logs and slowing down home assistant.

energy overreporting is something we have to look into. It seems like an error in the mqtt stream.

[scruysberghs]

as discussed on discord, the energy over reporting is on some charging stations where mqtt reports the total energy usage for the station for every phase, 3 time the same value (and thus calculated energy consumption in the integration is 3 times too high). Something to do with the type of metering Smappee does but still unclear.

[myny-git]

The energy issue has been solved I believe, next in line: real multi charger setup

[peterdedecker83]

Just a question: is there a reason to prefer the internet-required mqtt approach over the 100% local Modbus approach?

[myny-git]

For me personally: yes, because the MQTT does also update the charging status and gives a better user experience with rapid feedback.

[scruysberghs]

my 2 cents:

• availalbe by default, no need to have Smappee support open up the modbus interface
• available for every charger, no matter the extra Smappee hardware
• no extra dependency on internet connection as you need it for the controls anyway (cloud api)

A full local modbus implementation (sensors and controls) would of course be better, but not possible. (yet?)