home_assistant_solarman: Querying registers fails for Deye SUN600G3-EU-230

Hello,

I own a Deye SUN600G3-EU-230, that is currently connected to a single panel with 420W for testing purposes.

Here’s my current configuration:

HA version: Home Assistant 2023.1.7
Inverter firmware: MW3_16U_5406_1.53
Device S/N: 416*******
Port: 8899
Slave ID: 1
Parameters: deye_4mppt.yaml

I am unsure if I’m setting things up wrong or whether there’s a problem with the inverter, but no matter what parameters I try, I always get the following in my HA logs:

2023-01-31 13:02:33.076 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.deye_pv1_voltage is taking over 10 seconds
2023-01-31 13:01:25.062 WARNING (SyncWorker_7) [custom_components.solarman.solarman] Querying registers [3 - 128] failed, aborting.
2023-01-31 13:00:25.332 WARNING (SyncWorker_9) [custom_components.solarman.solarman] Querying registers [3 - 128] failed, aborting.
2023-01-31 13:02:39.275 WARNING (SyncWorker_9) [custom_components.solarman.solarman] Querying registers [3 - 128] failed, aborting.
2023-01-31 13:03:30.467 WARNING (SyncWorker_5) [custom_components.solarman.solarman] Querying registers [3 - 128] failed, aborting.

At this point I’ve run out of ideas and even thought about getting API access to the solarmanpv site, however I’d prefer to be able to collect data without relying on a cloud. Once I set up local data collection I’ll even turn off the cloud access with my firewall. Not a big fan of devices phoning home.

This might be related to #130 but I’m not sure, so I’m opening a new issue. I’m sorry if that’s wrong.

If there’s any tests you need me to perform, I would be happy to run those.

Thanks for taking the time to look at this!

EDIT: Unsure if helpful, but I’ve found a few posts on various sites all recommending pysolarmanv5. Is this already in use by this project?

About this issue

  • Original URL
  • State: open
  • Created 4 years ago
  • Comments: 15 (4 by maintainers)

Commits related to this issue

Most upvoted comments

Just for the convenience of future readers:

  1. take deye_4mppt.yaml and copy it to custom_parameters.yaml
  2. search for validation and comment out the whole part to look like this:
#      validation:
#        min: 0.1
#        invalidate_all:
  1. Set up the integration as described in the readme, but now choose custom_parameters.yaml

This made it work for me. 😃

Same problem here, same fix worked (removing the validation lines)

btw using the deye_4mppt.yaml for DEYE 600 G3 here

I had the same issue and found what was wrong for me. I have aSUN-M80G3-EU-Q0 and was using the wrong serial number. Do NOT use the inverter serial number, but the device serial number, to query your inverter. I looked at the modbus messages directly and this is what the error code reported (wrong serial). Unfortunately, this library does not handle this error code.

Edit: Also, I used the latest version from this repository instead of the latest from HACS store so I could use deye_2mppt.yaml

Deye SUN600G3-EU-230 no(empty) data issue

Maybe totally wrong though about this issue… I played around with some stuff in the hidden config(config_hide.html) of the microinverter to deactivate the access point: If the Working mode is set to TRANSPARENCY(instead of DATA Collection) there will be only EMPTY Values either if you access the normal status page or using console command:

curl -u username:passwort ip-address/status.html | grep "$dat ="

So IF no data is shown(while inverter is connected) have a look at the secret page.

Perhaps wrong config file used(for deye600 the deye_2mppt.yaml file should be used as other definitions may contain additional sensors which are NOT present in your device)

That’s the one that was installed when it arrived. I upgraded manually using https://github.com/dasrecht/deye-firmware/blob/main/0_D0002_18/MW3_16U_5406_1.53.bin

@CybDis May I ask which firmware is installed on your inverter?

sure: Firmware version MW3_15U_5406_1.471

Thanks for your detailed guide… For me it is still not working. Nevertheless, the error message chagend to:

2023-02-01 14:53:29.585 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Starting to query for [1] ranges… 2023-02-01 14:53:29.592 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Querying [3 - 112]… 2023-02-01 14:53:29.593 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] a5170010450000c33bbe8302000000000000000000000000000001030003006e34267c15 2023-02-01 14:53:29.600 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] a510001015007a346ac9f8020170210100a5040000684dd96306004315 2023-02-01 14:53:29.600 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] invalid modbus crc 2023-02-01 14:53:29.601 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Querying [3 - 112] failed, invalid response packet. 2023-02-01 14:53:29.601 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Querying [3 - 112] failed, [5] retry attempts left 2023-02-01 14:53:29.601 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] a5170010450000c33bbe8302000000000000000000000000000001030003006e34267c15 2023-02-01 14:53:29.614 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] a510001015007b346ac9f8020170210100a5040000684dd96306004415 2023-02-01 14:53:29.614 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] invalid modbus crc 2023-02-01 14:53:29.614 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Querying [3 - 112] failed, invalid response packet. 2023-02-01 14:53:29.614 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Querying [3 - 112] failed, [4] retry attempts left 2023-02-01 14:53:29.614 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] a5170010450000c33bbe8302000000000000000000000000000001030003006e34267c15 2023-02-01 14:53:29.625 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] a510001015007c346ac9f8020170210100a5040000684dd96306004515 2023-02-01 14:53:29.625 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] invalid modbus crc 2023-02-01 14:53:29.625 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Querying [3 - 112] failed, invalid response packet. 2023-02-01 14:53:29.625 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Querying [3 - 112] failed, [3] retry attempts left 2023-02-01 14:53:29.625 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] a5170010450000c33bbe8302000000000000000000000000000001030003006e34267c15 2023-02-01 14:53:29.637 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] a510001015007d346ac9f8020170210100a5040000684dd96306004615 2023-02-01 14:53:29.637 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] invalid modbus crc 2023-02-01 14:53:29.637 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Querying [3 - 112] failed, invalid response packet. 2023-02-01 14:53:29.637 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Querying [3 - 112] failed, [2] retry attempts left 2023-02-01 14:53:29.637 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] a5170010450000c33bbe8302000000000000000000000000000001030003006e34267c15 2023-02-01 14:53:29.649 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] a510001015007e346ac9f8020170210100a5040000684dd96306004715 2023-02-01 14:53:29.649 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] invalid modbus crc 2023-02-01 14:53:29.649 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Querying [3 - 112] failed, invalid response packet. 2023-02-01 14:53:29.649 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Querying [3 - 112] failed, [1] retry attempts left 2023-02-01 14:53:29.650 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] a5170010450000c33bbe8302000000000000000000000000000001030003006e34267c15 2023-02-01 14:53:29.661 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] a510001015007f346ac9f8020170210100a5040000684dd96306004815 2023-02-01 14:53:29.661 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] invalid modbus crc 2023-02-01 14:53:29.661 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Querying [3 - 112] failed, invalid response packet. 2023-02-01 14:53:29.661 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Querying [3 - 112] failed, [0] retry attempts left

Can anyone help?