EVSE BS20 Current State "out of sync"

[kl310]

Hi,

As I reported a few months ago, I wasn't able to use this application. Turned out that my version of Pi OS was to old. So since a month having a PI5 and everything is working now. But I notice a small issue. if the Message field is "EV is connected, please press start" then the Current State is "Charging". And if I really start charging, then the message is changing to "Charging", but the Current State is changing to "Completed". And if I finish the charging again, it is back to EV is connected, please press start and Charging. Looks like the field is just 1 cycle out of sync.

I also notice that if the PI is starting or if I start the program manually) it is telling "Device not initialized yet" and keeps doing that. Until I start the app on my phone. It instantly

2025-07-28 15:28:05,459 - evseMQTT - INFO - Connected to MQTT broker
2025-07-28 15:28:05,459 - evseMQTT - INFO - Scanning for evse BLE devices...
2025-07-28 15:28:10,488 - evseMQTT - INFO - Found device: ACPxxxxxxxx (aa:bb:cc:dd:ee:ff)
2025-07-28 15:28:10,489 - evseMQTT - INFO - Connecting...
2025-07-28 15:28:10,489 - evseMQTT - INFO - Connecting to aa:bb:cc:dd:ee:ff, attempt 1
2025-07-28 15:28:15,015 - evseMQTT - INFO - Connected to aa:bb:cc:dd:ee:ff
2025-07-28 15:28:15,242 - evseMQTT - INFO - Connected.
2025-07-28 15:28:15,242 - evseMQTT - INFO - Waiting for device initialization...
2025-07-28 15:28:15,242 - evseMQTT - INFO - Device not initialized yet, waiting...
2025-07-28 15:28:16,244 - evseMQTT - INFO - Device not initialized yet, waiting...
2025-07-28 15:28:17,245 - evseMQTT - INFO - Device not initialized yet, waiting...
2025-07-28 15:28:18,246 - evseMQTT - INFO - Device not initialized yet, waiting...
2025-07-28 15:28:19,248 - evseMQTT - INFO - Device not initialized yet, waiting...
2025-07-28 15:28:19,310 - evseMQTT - INFO - Device sent a single charge ac status
2025-07-28 15:28:20,250 - evseMQTT - INFO - Device not initialized yet, waiting...
2025-07-28 15:28:21,252 - evseMQTT - INFO - Device not initialized yet, waiting...
2025-07-28 15:28:22,253 - evseMQTT - INFO - Device not initialized yet, waiting...
2025-07-28 15:28:23,254 - evseMQTT - INFO - Device not initialized yet, waiting...
2025-07-28 15:28:24,255 - evseMQTT - INFO - Device not initialized yet, waiting...
2025-07-28 15:28:25,257 - evseMQTT - INFO - Device not initialized yet, waiting...
2025-07-28 15:28:26,259 - evseMQTT - INFO - Device not initialized yet, waiting...
2025-07-28 15:28:27,260 - evseMQTT - INFO - Device not initialized yet, waiting...
2025-07-28 15:28:27,621 - evseMQTT - INFO - Device sent charging status
2025-07-28 15:28:28,261 - evseMQTT - INFO - Device not initialized yet, waiting...
2025-07-28 15:28:29,262 - evseMQTT - INFO - Device not initialized yet, waiting...
2025-07-28 15:28:29,285 - evseMQTT - INFO - Device sent a single charge ac status
2025-07-28 15:28:30,264 - evseMQTT - INFO - Device not initialized yet, waiting...
2025-07-28 15:28:31,265 - evseMQTT - INFO - Device not initialized yet, waiting...
2025-07-28 15:28:32,267 - evseMQTT - INFO - Device not initialized yet, waiting...
2025-07-28 15:28:33,268 - evseMQTT - INFO - Device not initialized yet, waiting...
2025-07-28 15:28:33,880 - evseMQTT - INFO - Device accepted login request
2025-07-28 15:28:33,880 - evseMQTT - INFO - Device sent response to login request - confirming login
2025-07-28 15:28:33,880 - evseMQTT - ERROR - Exception occurred: int() argument must be a string, a bytes-like object or a real number, not 'NoneType'
2025-07-28 15:28:33,882 - evseMQTT - INFO - Device sent login banner - requesting login
2025-07-28 15:28:34,225 - evseMQTT - INFO - Device sent a single charge ac status
2025-07-28 15:28:34,225 - evseMQTT - INFO - Device sent charging status
2025-07-28 15:28:34,269 - evseMQTT - INFO - Device initialized with serial: 12345678901234. Proceeding with login request.
2025-07-28 15:28:34,269 - evseMQTT - INFO - Waiting for software version...
2025-07-28 15:28:34,368 - evseMQTT - INFO - Device sent charging status
2025-07-28 15:28:35,205 - evseMQTT - INFO - Device sent a single charge ac status
2025-07-28 15:28:35,274 - evseMQTT - INFO - Subscribed with QoS: (0,)
2025-07-28 15:28:35,455 - evseMQTT - INFO - Device sent charging status
2025-07-28 15:28:35,754 - evseMQTT - INFO - Device sent heartbeat - replying
2025-07-28 15:28:35,906 - evseMQTT - INFO - Device accepted login request
2025-07-28 15:28:36,056 - evseMQTT - INFO - Device sent login banner - requesting login
2025-07-28 15:28:37,353 - evseMQTT - INFO - Device accepted login request
2025-07-28 15:28:37,537 - evseMQTT - INFO - Device sent login banner - requesting login
2025-07-28 15:28:38,043 - evseMQTT - INFO - Device accepted login request
2025-07-28 15:28:38,137 - evseMQTT - INFO - Device sent login banner - requesting login
2025-07-28 15:28:38,531 - evseMQTT - INFO - Device accepted login request
2025-07-28 15:28:38,681 - evseMQTT - INFO - Device sent login banner - requesting login
2025-07-28 15:28:39,224 - evseMQTT - INFO - Device accepted login request
2025-07-28 15:28:39,227 - evseMQTT - INFO - Device sent login banner - requesting login
2025-07-28 15:28:39,618 - evseMQTT - INFO - Device accepted login request

So after the short start of the app on the phone, it is triggering a good connection. And from that moment on it is OK. I'm really happy with the fact that it is on the fly handling the change of charge Amps. So I already created in HA a nice load balancing.

There is 1 small thing that I'm missing: In the phone app i tis telling how much power has been added in the current session. I've tried to create it myself in HA with the use of the "Total Energy" and the difference versus the session. And that is how I found out that the Current State is out of sync.