hypfer / deye-microinverter-cloud-free Goto Github PK

Hello again :)

After my other issue (decreasing grid power today) I went through the logs and found a lot of warnings regarding this unknown packet.

Is this something to worry about?
I'm using the Deye SUN600G3-EU-230 with firmware "MW3_16U_5406_2.32".

My inverters don't want to connect to the dummycloud.
Both are configured to use the IP Address of the docker server:

The container is up and running with that docker-compose config:

The container connects to the mqtt broker:

But still both inverters state they aren't connected:

Is there anything i can do to investigate that further?

Hi Hypfer,
thanks for this awesome project. I'm running the dummy cloud and for some reason the "grid energy today" value seems to be decreasing? This also happens for the "Grid energy total" (see screenshots)

Hi,

I forked vordenken's fork of your excellent Deye dummycloud (thank you!) in order to make it accessible for HomeAssistant as an add-on repository.

I created "repository.yaml", "dummycloud/build.yaml", "dummycloud/config.yaml" and edited "dummycloud/Dockerfile" in order to be able to add your dummycloud as a HomeAssistant Supervisor add-on.
Please find all mentioned files here.

As I am not able to program anything myself or to maintain this repository further, I wanted to ask if you're interested in adding those files to your "original" dummycloud repository.

Thanks for your and vordenken's great work and best regards,
David

I was comparing the reported data using this great dummycloud software with the data I get via deye-inverter-mqtt. At least with the firmware 1.57 it seems that the faster reporting configured via AT command is not providing more measurements but just re-sending the same measurement more often.

If anyone else can confirm my observation, it might be worth to mention it in the README. I really like the dummycloudsolution anyway, just wanted to set right expectations.

$ deye-logger-at-cmd -t <deye-ip>:48899 -xat AT+TIME
2023/10/15 07:18:59 * Connecting :0 -> <deye-ip>:48899...
2023/10/15 07:19:02 +ok=1,60,120
2023/10/15 07:19:03

In the below diagram you can see the two in comparison, showing that the data from dummycloud is also only changing about every 5 minutes.

I've been using the dummycloud for a few days now, and it's impressively stable and reliable. Thanks for your excellent work on this!

However, I've come across an issue. When my inverter goes offline (typically when it gets dark), the values vanish from my dashboard due to their expiration after 300 seconds. Of course, this is as designed.

But, for my use-case, I'd like to see some of the last recorded values. One straightforward fix would be to either prevent their expiration or extend the expiration time. By doing so, however, there's another problem: the values displayed would be the last the inverter could operate with, which is slightly above 0, rather than the actual value when the inverter is offline, which is 0. This approach would be super helpful, especially when I want to check the day's total production in the evening.

However, the flip side is that we wouldn't be alerted if the inverter stops sending data due to some malfunction.

Another option could be to save the last value (like the last temperature or any other relevant data) to a helper entity through automation.

Honestly, I'm a bit torn on what's the best solution and don't have a strong preference. I'd love to hear your thoughts on this. What do you think?

@Hypfer Thanks for your great documentation on this!

The one thing I'm a bit unclear on is how to get Yield today working:

Note that with internet access blocked, the inverter never receives any time information. This breaks the Yield today counter as it will never properly reset unless you manually set the time on each boot using modbus register 22, 23 and 24

Is this something homeassistant can do by setting the registers via modbus if the device comes online? Do you have the config for this and can you publish it?

Hi,

I got dummycloud running - thanks a lot for your work!

Now I wanted to increase the data logging rate, but my 2000W microinverter refuses connections on port 48899. Only ports 8899 and 80 are open.

Do you happen to know an alternative solution?

Thanks!

Hi, I'm running the Dummycloud with a Deye SUN-M80G3-EU-Q0 with Firmware MW3_16U_5406_2.32-D1 and I receive a lot of data packets that contain bullshit after being parsed. Most of the time, I receive multiple packets in row and often the first one contains reasonable data and the latter bullshit. But this is not always the case.

Here are some example logs:

 [2024-04-08T17:14:03.092Z] [TRACE] 2024-04-08T17:14:03.092Z Data received from client: �JB,��Tgi��e�2305107146Z�        ��
▒�▒�▒�▒�V0.2.0.1V0.1.1.7V1.2.1.8@'q2305107146-1    2305107146-2    2305107146-3    2305107146-4    �,
�&�<▒   ▒��,I
�&�=

[2024-04-08T17:14:03.092Z] [TRACE] 2024-04-08T17:14:03.092Z Data a54a01104215162c9ad6ea0108540516670069030000d60fad6501008e0500003233303531303731343604005a000000ef06000000000000100900000000000000000000921304000000d20a18fc18fc18fc18fc0000000000000000000000000f01000016010000000000000000000056302e322e302e3156302e312e312e3756312e322e312e38000000001f4002010004000400040000000000000327000003710000000000000000323330353130373134362d3120202020323330353130373134362d3220202020323330353130373134362d3320202020323330353130373134362d3420202020139c002c00010000000000000abe0726141e128e003c1804081109010001000102011712180000000000000000000000000000000000ff000000000000139c002c00000000000000000049000000000001000000000abe0726141e128e7f3d0000000000000000000000020c15
[2024-04-08T17:14:03.092Z] [DEBUG] Received packet of type "DATA"
[2024-04-08T17:14:03.092Z] [DEBUG] DATA packet data from ::ffff:192.168.179.10 {
  pv: {
    '1': { v: 27.1, i: 0, w: 0, kWh_today: 0.4, kWh_total: 80.7 },
    '2': { v: 27.8, i: 0, w: 0, kWh_today: 0.4, kWh_total: 88.1 },
    '3': { v: 0, i: 0, w: 0, kWh_today: 0, kWh_total: 0 },
    '4': { v: 0, i: 0, w: 0, kWh_today: 0, kWh_total: 0 }
  },
  grid: {
    active_power_w: 4,
    kWh_today: 0.9,
    kWh_total: 177.5,
    v: 232,
    i: 0,
    hz: 50.1
  },
  inverter: { radiator_temp_celsius: 27.7 },
  inverter_meta: {
    rated_power_w: 800,
    mppt_count: 2,
    startup_self_check_time: 60,
    current_time: 2024-04-08T17:09:01.000Z,
    grid_freq_hz_overfreq_load_reduction_starting_point: 50.2,
    grid_overfreq_load_reduction_percent: 44,
    grid_v_limit_upper: 275,
    grid_v_limit_lower: 183,
    grid_freq_hz_limit_upper: 51.5,
    grid_freq_hz_limit_lower: 47.5,
    protocol_ver: 'V0.2.0.1',
    dc_master_fw_ver: 'V0.1.1.7',
    ac_fw_ver: 'V1.2.1.8'
  }
}
[2024-04-08T17:14:03.093Z] [DEBUG] Data event emitted.
[2024-04-08T17:14:03.093Z] [TRACE] Response a50a00101216162c9ad6ea0101db251466000000005a15
[2024-04-08T17:14:03.297Z] [TRACE] 2024-04-08T17:14:03.297Z Data received from client: �*B,���Tgi��e�3806571563-01230510714�"o��
                                                                                                                                ;
                                                                                                                                 ;&

                                                                                                                                   ��

,



        ����A   �#x@�,�.�0�
                           ���`���@��LSW5BLE_MW17_5406_RELAY_270_1.00-SH#
[2024-04-08T17:14:03.298Z] [DEBUG] Received packet of type "DATA"
[2024-04-08T17:14:03.298Z] [DEBUG] DATA packet data from ::ffff:192.168.179.10 {
  pv: {
    '1': { v: 0, i: 0, w: 0, kWh_today: 1, kWh_total: 195.5 },
    '2': { v: 0, i: 3339.1, w: 0, kWh_today: 1, kWh_total: 475 },
    '3': { v: 474.3, i: 25.6, w: 12142.08, kWh_today: 1, kWh_total: 253 },
    '4': { v: 0, i: 0, w: 0, kWh_today: 231.4, kWh_total: 2 }
  },
  grid: {
    active_power_w: 0,
    kWh_today: 0.49,
    kWh_total: 89235128.2,
    v: 1387.6,
    i: 0.8,
    hz: 0
  },
  inverter: { radiator_temp_celsius: 0 },
  inverter_meta: {
    rated_power_w: 30,
    mppt_count: 0,
    startup_self_check_time: 0,
    current_time: Invalid Date,
    grid_freq_hz_overfreq_load_reduction_starting_point: 0,
    grid_overfreq_load_reduction_percent: 256,
    grid_v_limit_upper: 0,
    grid_v_limit_lower: 0,
    grid_freq_hz_limit_upper: 0,
    grid_freq_hz_limit_lower: 0,
    protocol_ver: '\x00\x02\x00\x00\x00\x02\x0B;',
    dc_master_fw_ver: '\x0B;\x07&\x04\x0B\x04\x0B',
    ac_fw_ver: '\x14\x1E\x14\x1E\x12\x0E\x12\x0E'
  }
}
[2024-04-08T17:14:03.299Z] [DEBUG] Data event emitted.
[2024-04-08T17:14:03.299Z] [TRACE] Response a50a00101217172c9ad6ea0101db251466000000005c15

Can you make any sense of it?

Hi, thanks for publishing the dummy cloud! I also worked on deciphering the protocol over the past weeks and we basically found the same things. I might have some additions, I'd need to check in detail.

Until now, I only had access to packets from the SUN300G3 and I see you are using the 600 model. There should be a value specifying the number of usable/used MPPT paths, but I see several bytes with the value 0x01.

The relevant payload bytes are: 15, 131, 132, 228, 252
Is one of them constantly 0x02 for you?