WazzaCPT

So, been observing some strange behaviour before and after midnight the last few days. Anyone else seeing strange data?

Hello @Gary Waterworth, I am trying to understand the following error. 13/03/2024, 15:59:42node: Export Data Export To Entity function : (error) "Logger In Warning Mode, continuing" How can I diagnose this? I am not sure if it because I am missing a entity in the templates or something else I have done wrong. This is on both sites I have assisted with.

Thank you. Will have a look at customising the export node. Might even be able to look at implementing mqtt from there.

Thanks for the response. So if a plant is not on the ignore list then all the data pulls through. Does your system sum all sites together or would there be identification between sites in the consolidated data?

Hello @Gary Waterworth, With you the ignore plant list, I assume that your new system can poll data from multiple sites. How does it handle this and will there be information for each site identifiable in the consolidated data sensors? Also, in theory would it be possible to programmatically generate all the appropriate sensors via Node-Red and have them published through MQTT with auto-discovery instead of using the templates, sensors and inputs?

You update manually but re-importing the flows. Don't forget to update the template entities as well for the filtering.

To be honest, not sure if you would need to ESP32 or one. But you can have a look at the following GitHub repo ESPHome Stream Server, it is possible that this might work with KellerZa integration. Alternatively, the following is some ESPHome things for Sunsynk Sunsynk ESPHome. There may be more up to date code somewhere.

You will need two RS485 converters. There is ESPHome Yaml floating around for that method. Otherwise there is the option of running a TCP Modbus gateway device and use tyhe KellerZA integration. Alternatively you can direct connect to the HA machine with the WaveShare RS485 USB adaptors using the KellerZA integration. I believe there may be some limitations on the RS485 cable length. Another option is to use the KellerZA integration with the Solarman dongles. Not sure if this would work with parallel inverters though. A third option is using the Sunsynk API and the Node-Red flows from this guide if you are using the Sunsynk connect app: E-Linter Logger API access and the forum post: Sunsynk Logger Integration

Do your systems display 300s for the gateway module on the website or do they still show 60s? Both sites I have sorted out are still listed as 60s on the gateway settings.

Hello @kellerza, I see there is reference in the definitions for device type. 0x0601: "High voltage three phase hybrid 20-50kw" Does this help define the sensor definitions and register positions? I see that battery 1 is reporting a temperature that is out of range. It is reporting 129 and should be 29. I will go through the dev branch and add sensors one by one until I workout which ones do not align. It looks like the settings registers do not align on the 50kW HV sunsynk unit. 3:14:21 INFO Schedules: +-----------+-----+------+--------+-----------+----------+------------+ | Key | src | Read | Report | Change by | Change % | Change any | +-----------+-----+------+--------+-----------+----------+------------+ | date_time | | 60 | 60 | | | True | | rw | | 5 | 300 | | | True | | enum | | 5 | 300 | | | True | | w | * | 5 | 30 | 80 | | | | kwh | | 300 | 300 | | | | | any_unit | | 15 | 300 | | | | | no_unit | | 15 | 300 | | | True | +-----------+-----+------+--------+-----------+----------+------------+ +-----+------------------------------------------------------------------------------+ | s | Sensors | +-----+------------------------------------------------------------------------------+ | 5 | pv2_power, pv1_power, pv_power, pv3_power, battery_1_power, pv4_power | | 15 | battery_1_voltage, pv4_current, pv1_current, pv2_current, pv3_voltage, | | | pv2_voltage, battery_1_soc, pv4_voltage, pv1_voltage, battery_1_current, | | | pv3_current, battery_1_temperature | | 300 | total_pv_energy, total_grid_export, total_battery_charge, total_grid_import, | | | total_battery_discharge | +-----+------------------------------------------------------------------------------+ 13:14:22 INFO Report every (inverter 1) +-----+----------------------------------------------------------------------------------+ | s | Sensors | +-----+----------------------------------------------------------------------------------+ | 30 | pv2_power, pv1_power, pv_power, pv3_power, battery_1_power, pv4_power | | 300 | total_pv_energy, battery_1_voltage, total_grid_export, pv4_current, pv1_current, | | | total_battery_charge, pv2_current, total_grid_import, pv3_voltage, pv2_voltage, | | | battery_1_soc, pv4_voltage, pv1_voltage, battery_1_current, pv3_current, | | | total_battery_discharge, battery_1_temperature | +-----+----------------------------------------------------------------------------------+ 13:15:41 ERROR OSError in read_sunsynkmb: timeout reading 12 registers from 672 poll_need_to_read 13:16:04 ERROR OSError in read_sunsynkmb: timeout reading 1 registers from 590; timeout reading 4 registers from 672 poll_need_to_read 13:16:11 WARNING Did not complete read, only read 12/6 13:16:45 ERROR OSError in read_sunsynkmb: timeout reading 6 registers from 586; timeout reading 12 registers from 672 poll_need_to_read 13:20:00 ERROR (8 in 5 min) OSError in read_sunsynkmb: timeout reading 6 registers from 586; timeout reading 12 registers from 672 poll_need_to_read 13:20:00 ERROR (1 in 5 min) OSError in read_sunsynkmb: timeout reading 12 registers from 672 poll_need_to_read 13:21:08 ERROR OSError in read_sunsynkmb: timeout reading 4 registers from 516; timeout reading 4 registers from 522; timeout reading 2 registers from 534; timeout reading 6 registers from 586; timeout reading 12 registers from 672 poll_need_to_read Are there any settings I should try change with the polling rates and reporting rates?

Hello @kellerza and @Sc00bs, With the amount of struggle @Gary Waterworth is experiencing with the Sunsynk API. Has anyone ever tried to use a CANbus interface to communicate with the Sunsynk inverters. I ask this because of the installation I have at my parents is using the RS-485 comms for the BMS. Secondly, how do I go about doing testing and providing feedback on the Sunsynk 50kW HV unit with the KellerZA Sunsynk integration. When I last testing the integration with the inverter it kept bombing out. Kind Regards,

Hello There JTJ, I believe you may be a little confused. This thread is purely for the E-Linter (SUNSYNK) dongle. The dongle with the external antenna is the Solarman dongle and works with KellerZA integration and supports local polling. Gary has done some amazing work here for the people that do not have the ability to connect to their RS-485 port and still need their dongles to be connected to retain warranty/SLA support. If you are using the Sunsynk Application or connect to the sunsynk.net website and using region 2 for the login, then you are in the correct place to get your data into Home Assistant via the Node-Red flows and HA templates. Regards, Wazza

Not sure if this has been asked or addressed, but I am getting some strange behaviour on the card. I have a 3 phase setup and using a combination of ATESS and SolarEdge inverters. The issue I am picking up is that the output voltage values for the inverter display on the grid input section of the card. Not sure if this is me being pedantic, but it is just a little strange. There is also no option to include more than just a single grid voltage value. There is also setion to include the grid frequency. Thank you for that awesome work.

@Gary Waterworth, what is possibly causing the random large spikes in the energy dashboard? Slipx dash is fine, but the energy dashboard has too big spikes.

What about BLE proxy on ESP32?

Thank you for the headsup.

@kellerza, do you know if anyone has tried your integration with the 50kW three phase?

@kellerza, so I adjusted the polling rates according to the link provided. It then still crash. I then increased to 20 seconds and it still crashed. here is some of my config. Maybe there is something wrong with the sensors. SENSOR_DEFINITIONS: single-phase SENSORS: - energy_management - power_flow_card - pv2_voltage - pv2_power - pv2_current - battery_temperature - dc_transformer_temperature - radiator_temperature - total_load_energy - settings - load_limit SENSORS_FIRST_INVERTER: - settings MANUFACTURER: Sunsynk READ_ALLOW_GAP: 2 READ_SENSORS_BATCH_SIZE: 20 SCHEDULES: - KEY: W READ_EVERY: 20 REPORT_EVERY: 60 CHANGE_BY: 80 - KEY: RW READ_EVERY: 20 REPORT_EVERY: 60 CHANGE_ANY: true - KEY: any_unit READ_EVERY: 30 REPORT_EVERY: 60 CHANGE_BY: 80

Thank you.

@kellerza Is there something in the configuration that could be causing my SolarMan dongle to freeze and become inaccessible?

My contact ordered one of the Ethernet based E-Linter loggers yesterday. He should receive it tomorrow or Friday. I did also tell him about the supposed update, we will confirm details on the update.

I will ask my installer contact. He has been quite frustrated with it as well on his personal setup. He was also going to give me a dongle to play with if I wanted.

Has anyone successly found a way to create a new firmware for the E-linter dongle and still retain the connection to the Sunsynk API? Or was this avenue abandoned thanks to the work from @Gary Waterworth? Currently the way the dongle currently handles wifi and channel hopping and the AP is causing some troubles on the networks at a few sites I know. This would be solved with the Ethernet edition.

Bump... Anyone here get a solve for this issue. Having the same issue now.

Hello Steve, glad you made some headway. - sensor: - name: "Sunsynk Inverter 1 PV" unit_of_measurement: W state: > {{state_attr('sensor.sunsynk_input', 'pv')|float}} - sensor: - name: "Sunsynk Inverter 2 PV" unit_of_measurement: W state: > {{state_attr('sensor.sunsynk_input_2', 'pv')|float}} - sensor: - name: "Sunsynk Combined PV Power" unique_id: "sensor.sunsynk_combined_pv_power" unit_of_measurement: W state: > {{state_attr('sensor.sunsynk_input', 'pv')|float + state_attr('sensor.sunsynk_input_2', 'pv')|float}} Here is an example of of what I have done. pv1 and pv2 refer to the MPPT controllers per inverter. pv without a number is the combined PV of the inverter. sunsynk_input is inverter 1 and sunsyn_input_2 is inverter 2. A similar approach should be done for the total energy, battery in an out energy and your grid energy in an out. Be careful what you edit. So of the data will be missing unless you modify the Node-Red flows to expand the final message payload that generates the attibute data of each entity.