Sc00bs

Wouldn't touch it with a barge pole, they don't even have a phone number under their contacts. They may as well just have a sign, "EFT your money" to this account number and never see it again!

Still looking at my battery options, they seem to get cheaper every time I look

What boards are you using , esp32 & RS485? If those are your logs then I would guess that you are probably not loading the firmware onto the board correctly cause it doesn't look like ESPHome is seeing the board I would start by onboarding the ESP32 and check the logs before you update the firmware with the SLIPX06 code. From Grok: The ESPHome log you provided shows a boot sequence for a device, likely an ESP32 or ESP8266, with timestamps from July 29, 2019. The log indicates a power-on reset and a successful boot via SPI fast flash boot. However, the repeating [18:22:11][mode: DIO, clock div: 2] and subsequent load messages followed by an entry point suggest the device is attempting to load firmware or configurations but may be encountering issues. Here are potential problems and explanations: Corrupted Firmware or Configuration: The load entries (e.g., 0x3fff0030, 0x40078000, 0x40080400) indicate the bootloader is trying to load segments of the firmware into memory. If the firmware or configuration file (e.g., YAML file in ESPHome) is corrupted or incompatible with the device, it might fail to proceed beyond this point. Solution: Recompile and reflash the firmware using ESPHome. Ensure the YAML configuration matches your device's specifications (e.g., correct board type, memory layout). Incorrect Flash Mode or Clock Settings: The log shows mode: DIO, clock div: 2, which refers to the flash mode (Dual I/O) and clock divider. If the flash mode or clock settings are incorrect for your specific hardware, the device might fail to read the firmware properly. Solution: In your ESPHome YAML, explicitly set the flash mode to match your hardware (e.g., flash_mode: dio or flash_mode: dout). Also, check the clock frequency—clock div: 2 implies a slower clock, which might not be optimal for your setup. Hardware Issue (Flash Memory or Power Supply): If the flash memory chip is faulty or there’s a power supply issue (e.g., insufficient voltage or current), the device might struggle to read the firmware, leading to a boot loop or failure. Solution: Verify the power supply (e.g., use a stable 3.3V source with enough current). Check the flash chip connections and consider replacing the chip if it’s damaged. Bootloader or Partition Table Issue: The entry 0x400805e4 indicates the bootloader is trying to jump to the firmware entry point. If the partition table is misconfigured or the bootloader is outdated, it might fail to execute the firmware. Solution: Ensure the partition table in your ESPHome configuration is correct. You might need to update the bootloader by flashing a fresh ESPHome firmware. ESPHome Version or Compatibility: Since the log is from 2019, you might be using an older version of ESPHome that has compatibility issues with your device or firmware. Solution: Update to the latest version of ESPHome and reflash the device. Check the ESPHome documentation for any breaking changes since 2019. Next Steps:Recompile and reflash the firmware with a minimal ESPHome configuration to rule out YAML errors. Double-check your hardware setup (power, flash chip, etc.). If the issue persists, enable more verbose logging in ESPHome (e.g., logger: level: DEBUG) to get more details on the failure.

Having both connected does not affect communication to the dongle on the DEYE/Sunsynk inverters. What board are you using to communicate with your Solis Inverter (thinking 5V RS485 could be causing an issue if the dongle is V3.3)? Or maybe you may be interfering with the comms, maybe try using a different modbus address for the ESP32 board maybe.

I made a video some time ago on setting it up.

No need to go twice the size generator of your inverter @Neil.inSA , I have a 5.5KVA Petrol generator connected up to my 16Kw DEYE for emergencies. It only gets used a few times a year and would rather spend money on more batteries than a big generator. I have set the generator shaving set to 2.5kw and it ticks away quite happily. Going to a larger generator does not increase the efficiency significantly although switching to Diesel does use less fuel. There is a Gentec 8.5kva petrol generator that does have an ATS built in so it can be started by the inverter if you want. Cost is around R20k or you can find Diesels with an ATS as well if you want it to turn on automatically.

There is also an option on the DEYE menu (not sure about Sunsynk) now that allows you to select for a Generator on the Grid input. I assume that this allows for a larger range of frequency, voltage & probably a slower ramp up off the load on the generator, will ask for confirmation from DEYE and see what they say.

Is anyone else going through to the show? Free to get in if you book tickets online Thought it might be cool to have a meet up there on the 26th if anyone is keen. :-) Solar & Storage Live Africa 2025Solar & Storage Live Africa 2025 | JohannesburgAfrica's leading exhibition, showcasing solutions in solar innovation.

Will just take a bit longer to heat up Omni CalculatorWater Heating CalculatorUse the water heating calculator to determine how much time and energy you'll need to increase the temperature of the water.

Would just put a 3kw element in.

From Deepseek :-) If the voltage supplying your 4kW geyser increases from 230V to 250V, the geyser will indeed use more power. Here's a concise explanation: Power Calculation: The geyser's power rating of 4kW (4000 watts) is at 230V. Using the formula P=V2RP=RV2, where RR is resistance, we calculate the resistance at 230V as R=23024000≈13.225R=40002302≈13.225 ohms. Increased Voltage Impact: At 250V, the current becomes I=25013.225≈18.9I=13.225250≈18.9 amps. The new power consumption is P=250×18.9≈4725P=250×18.9≈4725 watts or 4.725kW, an increase of approximately 0.725kW. Considerations: Energy Use: The geyser may heat water faster, but total energy over time might remain similar if controlled by a thermostat. Safety: Operating at a higher voltage than rated can cause overheating, reducing the geyser's lifespan. Voltage Fluctuations: Consistently high voltage may require a voltage stabilizer to prevent damage. In conclusion, the increased voltage will make the geyser use more power, potentially leading to faster heating but also safety risks. It's advisable to ensure the geyser is rated for the higher voltage or use protective measures.

Not sure, they did work just fine from the 12th of Feb till the 6h of March.

Hi Everyone, I have been trying to help one of my neighbors with a problem he is having with his system. Sunsynk 8kw 4 x Hubble AM2 batteries (1 recently installed) The new battery was installed on the 12 Feb system however ran fine until the 5th of March when the SOC's started jumping between 0% & 100% SOC. The system refuses to push/pull any power to/from the batteries. When the grid is disconnected it switches off. The battery is however recognised in the BMS menu and show the correct battery info i.e. 200Ah Voltage @ 52V or thereabouts I spoke yesterday to Hubble and had them check the batteries and update all the firmware to the latest version for me (was already up to date as far as I could see). Everything checked out 100% according to them. I also had the Inverter updated yesterday to the latest Firmware, is currently on Protocol Version：V0.2.0.1MAIN：6027-0717HMI：0000-E43D Subsequent to the updates the SOC now jumps between 0% & 39% and still refuses to either charge or discharge the battery at all. If I switch the Battery from Lithium to Voltage, the voltage reading on the front screen of the inverter seems to chase whatever I set the desired voltage for in the work mode settings. So, if I set the Voltage in the Work mode setting to 53.6V, the SOC on the inverter might reflect as 48V but starts increasing until it gets to 53.6V, no power going in/out the battery. If I drop it to 46V the voltage on the display drops down to 46V. I unfortunately didn't have a multimeter with me so couldn't check the actual voltage. The guys from Hubble were saying that they have had a few problems in the last few weeks from Sunsynk inverters with similar issues. Does anyone have any suggestions as to where the problem could be and steps for how to resolve this problem ? I think I am going to go back with my multimeter to check his battery connections for voltage and perhaps disconnect all; but one battery and see if it works like that.

He had the 8kw version, not the 6kw version though, as it has the ATS built in. I am not sure if the 6kw has an ATS, I think that it may only have a remote start

Hi @LidaH I was actually speaking to someone a few weeks ago about the Gentec generator, he was telling me all about it as I had not heard of any small petrol generators with an autostart feature. He said that he had managed to get it working with his Sunynk, so apparently it does work (2nd hand I know but)

Will Prowse does a pretty good video covering this topic.

8 Cells is a 24V battery, not a good idea to connect a 24V battery in parallel with a 48v battery. Some "48V" batteries have 15 cells and some have 16 cells, you can't mix them due to the different operating voltages. A 16-cell LiFePO4 battery typically has a nominal voltage of 51.2 volts. This is because each individual LiFePO4 cell has a nominal voltage of around 3.2 volts, and 16 cells multiplied by 3.2 volts equals 51.2 volts. Key points about 16-cell LiFePO4 batteries: Nominal Voltage: 51.2 volts Full Charge Voltage: Around 57.6 volts (depending on the specific battery) Discharge Cut-off Voltage: Around 48 volts A 15-cell LiFePO4 battery typically has a nominal voltage of 48 volts as each cell in a LiFePO4 battery is considered to have a nominal voltage of 3.2 volts, so 15 cells in series would equal 48 volts (15 x 3.2 = 48). Key points about a 15-cell LiFePO4 battery: Nominal voltage: 48 volts Per cell voltage: 3.2 volts Application: Often used in systems requiring a 48 volt power supply I disagree with @I84RiS on the max charging amperage of the batteries. The power absorption of the batteries will be higher when they are in parallel than each of them individually so you can set to the max charge amperage of the larger battery quite safely as the current will be spread across the batteries proportionally to their capacity. i.e. If you have a 200Ah and 100Ah in parallel and give it 30A, 20A will be absorbed by the 200Ah and 10A by the 100Ah.

KellerZA has a great Github page with the info on how to add an extra sensor there. https://kellerza.github.io/sunsynk/reference/mysensors

Unfortunately I don't us @kellerza's integration myself anymore but it sounds like you could add it as a custom sensor

I have Grid Shaving working on my 16kw using @slipx's ESPHome integration.

As far as I am aware, it should be the same registry entry on the 8kw & 16kw.

I wouldn't get rid of your pump if you don't have to. 3 phase is actually preferable for speed control over single phase and you can run your 3 phase borehole pump of a single phase supply using a VSD, will also help reduce the large inrush of current required. https://cfptechnologies.co.za/product-category/variable-frequency-drives/

I can change the value with my using the ESP32 ESPHome integration so it must be somethin in your node red setup. Not many people, that I know of, that are still using the NodeRed method for inverter queries so you may struggle to find someone able to assist. Easiest would probably be tro just switch to the Kellerza integration if you can.

Which integration are you using to speak to the inverter? Go to the integration and you will see a list of the sensors it is getting from the device. Will probably be along the lines of number.inverter_grid_peak_shaving_power but it varies depending on which integration you are using. You battery SOC should be something along the lines of sensor.inverter_battery_soc You can also find the sensor names by going to Developer Tools/States and looking for the sensors names there.

Easiest is to just ask ChatGPT to write the automation for you, give it the name of the entities you want to do the automation on and then what you want it to do and it will write the YAML code for you.