Does the Solarman driver support the more recent "DeyeCloud" dongle? #323

jrailton · 2024-08-09T14:31:13Z

jrailton
Aug 9, 2024

@kellerza your Sunsynk/Deye components have been a life saver for those who've battled (and lost) with Modbus, a very big thank you for starters!

I am totally new to Deye/Sunsynk and bought two Deye 5kw Single phase LV Hybrid inverters recently (connected in parallel) and setup your standalone option (using a pre-built image for armv7) on a Raspberry Pi 3B+ so that I could consume the data via MQTT

I configured the options.yaml to use the Solarman driver, but had heard that Solarman was the older wifi dongle which had been superceded by a DeyeCloud dongle which was supplied with my two inverters. I presumed that the ModbusTCP interface exposed by the dongle on port 8899 would be the same though, which is possibly inaccurate?

When the docker image is run, I can see MQTT entries being published under homeassistant/sensor/2302064193/# however their values which I presumed would be visible from SUNSYNK/status/2302064193/inverter_current are not listed

So I checked the docker logs which show the following:
logs.txt

2024-08-09 12:12:52,230 INFO    ha_addon_sunsynk_multi.a_inverter Connecting to tcp://192.168.2.121:8899
2024-08-09 12:12:52,253 DEBUG   asyncio <asyncio.TransportSocket fd=10, family=2, type=1, proto=6, laddr=('172.17.0.2', 42718), raddr=('192.168.2.121', 8899)> connected to 192.168.2.121:8899: (<_SelectorSocketTransport fd=10 read=polling write=<idle, bufsize=0>>, <asyncio.streams.StreamReaderProtocol object at 0x75bffcd0>)
2024-08-09 12:12:52,255 INFO    ha_addon_sunsynk_multi.a_inverter Reading startup sensors Prog6 Time, Rated power, Prog2 Time, Prog3 Time, Prog1 Time, Prog5 Time, Battery Low Capacity, Serial, Prog4 Time
2024-08-09 12:12:52,265 DEBUG   pysolarmanv5.pysolarmanv5 SENT: a5 17 00 10 45 8d 00 f6 01 ce a3 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 03 00 03 00 0f f5 fd 6c 15
2024-08-09 12:12:54,283 DEBUG   pysolarmanv5.pysolarmanv5 RECD: a5 10 00 10 15 8d 08 f6 01 ce a3 02 01 c5 5b 03 00 ae 00 00 00 01 ac b2 66 05 00 d0 15
2024-08-09 12:12:54,285 DEBUG   pysolarmanv5.pysolarmanv5 SENT: a5 17 00 10 45 8e 00 f6 01 ce a3 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 03 00 03 00 0f f5 fd 6d 15
2024-08-09 12:12:56,464 DEBUG   pysolarmanv5.pysolarmanv5 RECD: a5 10 00 10 15 8e 09 f6 01 ce a3 02 01 c7 5b 03 00 b0 00 00 00 01 ac b2 66 05 00 d6 15
2024-08-09 12:12:56,464 INFO    sunsynk.solarmansunsynk Frame error retry attempt(0): V5 frame does not contain a valid Modbus RTU frame
2024-08-09 12:12:56,588 DEBUG   pysolarmanv5.pysolarmanv5 [2748187126] COUNTER: a5 01 00 10 47 8e 0a f6 01 ce a3 00 58 15
2024-08-09 12:12:58,469 DEBUG   pysolarmanv5.pysolarmanv5 SENT: a5 17 00 10 45 8f 00 f6 01 ce a3 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 03 00 03 00 0f f5 fd 6e 15
2024-08-09 12:13:00,526 DEBUG   pysolarmanv5.pysolarmanv5 RECD: a5 10 00 10 15 8f 0b f6 01 ce a3 02 01 cb 5b 03 00 b4 00 00 00 01 ac b2 66 05 00 e1 15
2024-08-09 12:13:00,526 INFO    sunsynk.solarmansunsynk Frame error retry attempt(1): V5 frame does not contain a valid Modbus RTU frame
2024-08-09 12:13:02,531 DEBUG   pysolarmanv5.pysolarmanv5 SENT: a5 17 00 10 45 90 00 f6 01 ce a3 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 03 00 03 00 0f f5 fd 6f 15
2024-08-09 12:13:03,274 DEBUG   pysolarmanv5.pysolarmanv5 SENT: a5 17 00 10 45 91 00 f6 01 ce a3 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 03 00 db 00 01 f4 02 3e 15
2024-08-09 12:13:04,546 DEBUG   pysolarmanv5.pysolarmanv5 RECD: a5 10 00 10 15 90 0c f6 01 ce a3 02 01 cf 5b 03 00 b8 00 00 00 01 ac b2 66 05 00 eb 15
2024-08-09 12:13:04,547 DEBUG   pysolarmanv5.pysolarmanv5 SENT: a5 17 00 10 45 92 00 f6 01 ce a3 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 03 00 db 00 01 f4 02 3f 15
2024-08-09 12:13:06,592 DEBUG   pysolarmanv5.pysolarmanv5 RECD: a5 10 00 10 15 91 0d f6 01 ce a3 02 01 d1 5b 03 00 ba 00 00 00 01 ac b2 66 05 00 f1 15
2024-08-09 12:13:06,592 INFO    sunsynk.solarmansunsynk Frame error retry attempt(0): V5 frame contains invalid sequence number
2024-08-09 12:13:08,601 DEBUG   pysolarmanv5.pysolarmanv5 SENT: a5 17 00 10 45 93 00 f6 01 ce a3 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 03 00 db 00 01 f4 02 40 15
2024-08-09 12:13:08,807 DEBUG   pysolarmanv5.pysolarmanv5 RECD: a5 10 00 10 15 92 0e f6 01 ce a3 02 01 d4 5b 03 00 bc 00 00 00 01 ac b2 66 05 00 f8 15
2024-08-09 12:13:08,808 INFO    sunsynk.solarmansunsynk Frame error retry attempt(1): V5 frame contains invalid sequence number
2024-08-09 12:13:10,815 DEBUG   pysolarmanv5.pysolarmanv5 SENT: a5 17 00 10 45 94 00 f6 01 ce a3 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 03 00 db 00 01 f4 02 41 15
2024-08-09 12:13:10,916 DEBUG   pysolarmanv5.pysolarmanv5 RECD: a5 10 00 10 15 93 0f f6 01 ce a3 02 01 d6 5b 03 00 be 00 00 00 01 ac b2 66 05 00 fe 15
2024-08-09 12:13:10,917 INFO    sunsynk.solarmansunsynk Frame error retry attempt(2): V5 frame contains invalid sequence number
2024-08-09 12:13:12,923 DEBUG   pysolarmanv5.pysolarmanv5 SENT: a5 17 00 10 45 95 00 f6 01 ce a3 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 03 00 db 00 01 f4 02 42 15
2024-08-09 12:13:12,930 DEBUG   pysolarmanv5.pysolarmanv5 RECD: a5 10 00 10 15 94 10 f6 01 ce a3 02 01 d8 5b 03 00 c0 00 00 00 01 ac b2 66 05 00 04 15
2024-08-09 12:13:12,931 INFO    sunsynk.solarmansunsynk Frame error retry attempt(3): V5 frame contains invalid sequence number
2024-08-09 12:13:14,281 DEBUG   pysolarmanv5.pysolarmanv5 SENT: a5 17 00 10 45 96 00 f6 01 ce a3 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 03 00 fa 00 06 e5 ca 20 15
2024-08-09 12:13:14,953 DEBUG   pysolarmanv5.pysolarmanv5 RECD: a5 10 00 10 15 95 11 f6 01 ce a3 02 01 da 5b 03 00 c2 00 00 00 01 ac b2 66 05 00 0a 15
2024-08-09 12:13:14,956 DEBUG   pysolarmanv5.pysolarmanv5 SENT: a5 17 00 10 45 97 00 f6 01 ce a3 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 03 00 fa 00 06 e5 ca 21 15
2024-08-09 12:13:16,961 DEBUG   pysolarmanv5.pysolarmanv5 RECD: a5 10 00 10 15 96 12 f6 01 ce a3 02 01 dc 5b 03 00 c4 00 00 00 01 ac b2 66 05 00 10 15
2024-08-09 12:13:16,962 INFO    sunsynk.solarmansunsynk Frame error retry attempt(0): V5 frame contains invalid sequence number
2024-08-09 12:13:18,967 DEBUG   pysolarmanv5.pysolarmanv5 SENT: a5 17 00 10 45 98 00 f6 01 ce a3 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 03 00 fa 00 06 e5 ca 22 15
2024-08-09 12:13:18,980 DEBUG   pysolarmanv5.pysolarmanv5 RECD: a5 10 00 10 15 97 13 f6 01 ce a3 02 01 de 5b 03 00 c6 00 00 00 01 ac b2 66 05 00 16 15
2024-08-09 12:13:18,981 INFO    sunsynk.solarmansunsynk Frame error retry attempt(1): V5 frame contains invalid sequence number
2024-08-09 12:13:20,989 DEBUG   pysolarmanv5.pysolarmanv5 SENT: a5 17 00 10 45 99 00 f6 01 ce a3 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 03 00 fa 00 06 e5 ca 23 15
2024-08-09 12:13:21,051 DEBUG   pysolarmanv5.pysolarmanv5 RECD: a5 10 00 10 15 98 14 f6 01 ce a3 02 01 e0 5b 03 00 c8 00 00 00 01 ac b2 66 05 00 1c 15
2024-08-09 12:13:21,051 INFO    sunsynk.solarmansunsynk Frame error retry attempt(2): V5 frame contains invalid sequence number
2024-08-09 12:13:23,057 DEBUG   pysolarmanv5.pysolarmanv5 SENT: a5 17 00 10 45 9a 00 f6 01 ce a3 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 03 00 fa 00 06 e5 ca 24 15
2024-08-09 12:13:23,063 DEBUG   pysolarmanv5.pysolarmanv5 RECD: a5 10 00 10 15 99 15 f6 01 ce a3 02 01 e2 5b 03 00 ca 00 00 00 01 ac b2 66 05 00 22 15
2024-08-09 12:13:23,063 INFO    sunsynk.solarmansunsynk Frame error retry attempt(3): V5 frame contains invalid sequence number

My options.yaml is as follows:

---
DRIVER: "solarman"
INVERTERS:
  - SERIAL_NR: "2302064193"
    HA_PREFIX: SS
    MODBUS_ID: 1
    DONGLE_SERIAL_NUMBER: "2748743845"
    PORT: tcp://192.168.2.98:8899
  - SERIAL_NR: "2302064198"
    HA_PREFIX: SS
    MODBUS_ID: 2
    DONGLE_SERIAL_NUMBER: "2748187126"
    PORT: tcp://192.168.2.121:8899
SENSOR_DEFINITIONS: single-phase
SENSORS:
  - inverter_power
  - inverter_voltage
  - inverter_current
  - inverter_frequency
  - grid_frequency
  - grid_power
  - grid_ld_power
  - grid_l2_power
  - grid_voltage
  - grid_current
  - grid_ct_power
  - load_power
  - load_l1_power
  - load_l2_power
  - load_frequency
  - pv1_power
  - pv1_voltage
  - pv1_current
  - pv2_power
  - pv2_voltage
  - pv2_current
  - serial
  - fault
  - overall_state
  - sd_status
  - dc_transformer_temperature
  - environment_temperature
  - radiator_temperature
  - grid_connected
  - date_time
SENSORS_FIRST_INVERTER:
  - battery_temperature
  - battery_voltage
  - battery_soc
  - battery_power
  - battery_current
  - battery_charge_limit_current
  - battery_discharge_limit_current
MANUFACTURER: Deye
READ_ALLOW_GAP: 2
READ_SENSORS_BATCH_SIZE: 20
SCHEDULES:
SCHEDULES:
  - KEY: W
    READ_EVERY: 15
    REPORT_EVERY: 60
    CHANGE_BY: 80
  - KEY: RW
    READ_EVERY: 15
    REPORT_EVERY: 60
    CHANGE_ANY: true
  - KEY: any_unit
    READ_EVERY: 30
    REPORT_EVERY: 60
    CHANGE_BY: 80
NUMBER_ENTITY_MODE: "auto"
MQTT_HOST: 10.0.0.70
MQTT_PORT: 1883
MQTT_USERNAME: 
MQTT_PASSWORD: 
DEBUG: 2
DEBUG_DEVICE: /dev/ttyUSB0

Are the errors im seeing because of a config issue that you can see or is it a Solarman compatability issue?

kellerza · 2025-01-06T20:24:30Z

kellerza
Jan 6, 2025
Maintainer

The newer DeyeCloud dongle you refer to is not supported - see the pysolarmanv5 docs

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Does the Solarman driver support the more recent "DeyeCloud" dongle? #323

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Does the Solarman driver support the more recent "DeyeCloud" dongle? #323

Uh oh!

Uh oh!

jrailton Aug 9, 2024

Replies: 1 comment

Uh oh!

kellerza Jan 6, 2025 Maintainer

jrailton
Aug 9, 2024

kellerza
Jan 6, 2025
Maintainer