sofar2mqtt doesnt start

[AlexPascou]

I have a Sofar ME3000 SP, starting sofar2mqtt with docker compose :

services:
  sofar2mqtt:
    container_name: sofar2mqtt
    image: rpearce/sofar2mqtt-python
    restart: unless-stopped
    environment:
      - MQTT_HOST=192.168.1.202
      - MQTT_PORT=1883
      - MQTT_USERNAME=XXXXXXXXXXX
      - MQTT_PASSWORD= XXXXXXXXXXX
      - CONFIG_FILE=SOFAR-HYD-ES-AND-ME3000-SP.json
      - TTY_DEVICE=/dev/ttyUSB0
    devices:
      - /dev/ttyUSB0:/dev/ttyUSB0

And I have this error :

sofar2mqtt  | 2026-03-19 23:04:57,509 - INFO - Starting sofar2mqtt-python 4.0.1
sofar2mqtt  | Traceback (most recent call last):
sofar2mqtt  |   File "/opt/sofar2mqtt/sofar2mqtt-v2.py", line 1214, in <module>
sofar2mqtt  |     main()
sofar2mqtt  |     ~~~~^^
sofar2mqtt  |   File "/usr/local/lib/python3.14/site-packages/click/core.py", line 1130, in __call__
sofar2mqtt  |     return self.main(*args, **kwargs)
sofar2mqtt  |            ~~~~~~~~~^^^^^^^^^^^^^^^^^
sofar2mqtt  |   File "/usr/local/lib/python3.14/site-packages/click/core.py", line 1055, in main
sofar2mqtt  |     rv = self.invoke(ctx)
sofar2mqtt  |   File "/usr/local/lib/python3.14/site-packages/click/core.py", line 1404, in invoke
sofar2mqtt  |     return ctx.invoke(self.callback, **ctx.params)
sofar2mqtt  |            ~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
sofar2mqtt  |   File "/usr/local/lib/python3.14/site-packages/click/core.py", line 760, in invoke
sofar2mqtt  |     return __callback(*args, **kwargs)
sofar2mqtt  |   File "/opt/sofar2mqtt/sofar2mqtt-v2.py", line 1207, in main
sofar2mqtt  |     sofar = Sofar(daemon, retry, retry_delay, write_retry, write_retry_delay, refresh_interval, broker,
sofar2mqtt  |                   port, username, password, ca_certs, topic, write_topic, log_level, device, legacy_publish)
sofar2mqtt  |   File "/opt/sofar2mqtt/sofar2mqtt-v2.py", line 72, in __init__
sofar2mqtt  |     self.raw_data['serial_number'] = self.determine_serial_number()
sofar2mqtt  |                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
sofar2mqtt  |   File "/opt/sofar2mqtt/sofar2mqtt-v2.py", line 747, in determine_serial_number
sofar2mqtt  |     serial = part1 + part2
sofar2mqtt  |              ~~~~~~^~~~~~~
sofar2mqtt  | TypeError: unsupported operand type(s) for +: 'NoneType' and 'NoneType'
sofar2mqtt exited with code 0

Any idea why this might be?

Thanks !

[rjpearce]

Let me investigate,

Can you switch back to image: rpearce/sofar2mqtt-python:3.1.1 ?

[AlexPascou]

I tried using rpearce/sofar2mqtt-python:3.1.1, but it doesn't start and returns a different error

sofar2mqtt  | 2026-03-20 09:01:33,625 - INFO - Starting sofar2mqtt-python 3.1.0
sofar2mqtt  | 2026-03-20 09:01:33,734 - INFO - Failed to validate serial number from first location: Slave reported illegal data address
sofar2mqtt  | 2026-03-20 09:01:36,560 - INFO - Failed to validate serial number from second location: sequence item 0: expected str instance, NoneType found
sofar2mqtt  | 2026-03-20 09:01:39,393 - INFO - Failed to validate serial number from third location: sequence item 0: expected str instance, NoneType found
sofar2mqtt  | 2026-03-20 09:01:39,394 - ERROR - Failed to determine serial number
sofar2mqtt  | 2026-03-20 09:01:39,395 - ERROR - Failed to determine serial number. Exiting
sofar2mqtt  | 2026-03-20 09:01:39,396 - INFO - Terminating
sofar2mqtt  | 2026-03-20 09:01:39,397 - INFO - Publishing offline to sofar2mqtt_python/bridge
sofar2mqtt exited with code 0

I also tried adding this to SOFAR-HYD-ES-AND-ME3000-SP.json

{
    "name": "serial_number",
    "read_type": "static",
    "value": "ME3000SP",
    "refresh": 86400
},

and

{
	"name": "serial_number",
	"register": "0x2001",
	"read_type": "string",
	"registers": 7,
    "refresh": 86400
},

same error ...

I have an older version that works (possibly from before the 3.x.x releases). The image is still tagged as "latest", but I don't know which version it is...

I wanted to update in order to take advantage of autodiscovery with Home Assistant and support for ME3000 charge/discharge.

[zulufoxtrot]

@rjpearce I think we never got around the serial number issue for the ME3000SP.
@AlexPascou if you don't mind editing the code, you can try to remove the part that builds the serial number. It's not much use anyway, if I remember correctly.

I am working on a refactor and a couple of bug fixes, I'll try to address this :)