Guys why would my Esp32 and rs485 be showing incorrect data. Example my solar showing 6700w and it Night time.

My grid power is a negative -1,217

Could be my wiring in the boards etc

Thanks 

Edited November 4, 20232 yr by Vaughanza

I doubt very much that it is wiring @Vaughanza 

The inverter has a series of modbus addresses that, when queried, respond with the values for those specific sensors. 

If you go to the entity history you will be able to see when it was last updated 

You could  have a wifi comms issue or maybe a comms issue with the RS485 board. 

Check out your ESPhome logs as well

On 2023/11/04 at 7:32 PM, Vaughanza said:

Guys why would my Esp32 and rs485 be showing incorrect data. Example my solar showing 6700w and it Night time.

My grid power is a negative -1,217

Could be my wiring in the boards etc

Thanks 

Guys solved my problem. I forgot to remove R7 resister on the RS485 board and now all my Data looks good. No night solar power etc. I thought I had bought really good solar panels with nighttime solar power. 

So you must remove the R7 Resistor for Sunsynk 8k Invertor.

@slipx @Sc00bs

Edited November 5, 20232 yr by Vaughanza

On 2023/08/16 at 5:49 PM, caswell1000 said:

I am struggling with these same error logs as well, I even changed the esp32 thinking it was a hardware error, the error logs persist. 

Caswell, what is your inverter?, mine is the 5.5kW Ecco and I am based in the UK but I am sure that this inverter doesn't have pin 1 and 2 going anywhere on the CAN \ BMS port only the CAN pins are connected. 
 

On 2023/11/04 at 7:32 PM, Vaughanza said:

Guys why would my Esp32 and rs485 be showing incorrect data. Example my solar showing 6700w and it Night time.

My grid power is a negative -1,217

Could be my wiring in the boards etc

Thanks 

Just noticed something... I think something is up with your solar entities... 3080.6A? and 819.2A.

Not sure if you've seen this....

On 2023/10/17 at 9:35 AM, chessmaster said:

Small update, looks like MQTT is looking healthier after installing this https://github.com/SharkyRawr/hass-mqtt-fix

I doubt you have an issue with MQTT

On 2023/10/17 at 9:35 AM, chessmaster said:

However I'm still getting these errors in the sunsynk multi logs:

This clearly states the modbus interface is not responding, so no connection to the inverter. The addon will only connect to MQTT once it connected to the inverter and verified your serial number.

As others also pointed out, this URL usually points to a Modbus gateway/mbusd add-on on your local homeassistant node. If this is not what you intended, you should rather connect to a USB port

Im using the Sunsynk card with my Luxpower, i still need to get Solar though ;(

On 2023/08/05 at 10:43 AM, ArthurB said:

I have attached two images for context. I will need to jumper out of the box to get the lid on when using USB power. It solves the problem, but should not be necessary. The connector to the RS485 board has been moved to the main board because of lid clearance. (I had the issue before moving the connector) Using high stand-offs to fit DC-DC LM2596 under board with big gap between boards. (Had problem before adding DC reg under board.)

I bought a few more of these ESP32 CP2102 boards for geyser temperature, etc... I hope that not all projects will need to be powered via the USB to eliminate comms errors.

 

9 minutes ago, ArthurB said:

Hi, Just an update in case someone else has the same issue. I had lots of bad data when using the 5V in power pin and not powering via USB connector. Using the 38pin ESP32-DEV-CP2102-C Wroom Type-C version. I found that the 3 ground pins are not connected internally and one of the other ground pins (Pin 38) had an effect on my WiFi quality.

 

Edited December 13, 20232 yr by ArthurB

I've also had weird issues with comms using various bargain basement USB power supplies for my ESP32 board.  Mileage varied when using bundled cellphone chargers of various makes - some allowed intermittent comms, others just a bunch of errors, and some killed the wifi reception.  I settled on quite an oversized (2A) after-market charger which appears to introduce very little noise and is also large enough to drive my fans.

I guess power filtering isn't exactly high on the design criteria for these supplies, or the ESP boards are just particularly sensitive...

1 hour ago, sgs said:

or the ESP boards are just particularly sensitive...

ESP32 Boards are not all the same, the WROOM might be an original Espressiv or it might be an Clone from some electronics factory in China. I prefer to buy the ESP with geniune Espressiv boards, rather pay a little more and get one of the brands that deliver good quality than gamble with a no-name board. Seen too many complaints about cheap boards with rubbish wifi. You get what you pay for.

The PSU 5V also gets converted down to 3.3V and the filter capacitors on the cheap boards might also be the cheapest option available. So stick to the brands even though they cost 2USD more

I managed to successfully set up ESPhome and HA Dashboards using @slipx configs and dashboards following @Sc00bs video tutorials. Thank you gents, it looks like a lot of effort went into this, thank you for sharing your hard work with the community. I hit one snag which took a while to figure out so I thought I would post it here incase anyone had the same issue. Maybe this has been documented and in my haste I missed it.

I set everything up but was not getting any sensor readings on my ESPHome provisioned ESP32. I was getting "[W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=150 count=1" errors. The ESPHome yaml configuration I was using had the modbus_controller address as "0x01".


It turns out that my SunSynk 8kW Inverter had the "Modbus SN" setting in Advance menu set to "00"
 

 

When I changed it to 01, the ESPHome started reading the correct sensor readings. Changing this setting requires switching the inverter off and back on again to clear a Grid Mode Change alarm that is generated. What is interesting is you can't even change the Modbus SN back to 00 so not sure why it was set to that value in the first place.

Edited December 15, 20232 yr by Gambit

7 hours ago, Gambit said:

I managed to successfully set up ESPhome and HA Dashboards using @slipx configs and dashboards following @Sc00bs video tutorials. Thank you gents, it looks like a lot of effort went into this, thank you for sharing your hard work with the community. I hit one snag which took a while to figure out so I thought I would post it here incase anyone had the same issue. Maybe this has been documented and in my haste I missed it.

I am glad the video's helped, have been having lots of fun making them. 

Am looking for new topics to do video's on so if you have any ideas let me know 🙂 

15 hours ago, Sc00bs said:

I am glad the video's helped, have been having lots of fun making them. 

Am looking for new topics to do video's on so if you have any ideas let me know 🙂 

Still early in my HA journey, was going to look at automating the Sunsynk mode settings next, based on load shedding level. Checking your channel now, I see you have already covered this in one of your videos, going to check that out and give it a go next. Ideally like to vary battery SOC and grid charging based on weather/solar forecast and load shedding level. I have installed the solcast and load-shedding plugins. After that, I want to try to dump excess solar into my Geyser. Still thinking of other use cases for these tools.

Pretty much have those topics covered I think, let me know if you get stuck 🙂 

Hi All,

Well I have found the issue with my inverter and finally have it working with Home Assistant.
If turns out there are 2 * 5.5kW Ecco inverters in the UK.

One has the conbined BMS \ CAN port and my 5.5kW inverter has the CAN and RS485 port which are seperate (Ports.jpg)

Now on the RS485 port you can not use pins 1 + 2 for RX / TX, you have to use ping 1 and 7. You can see why on this photo when I got a flashlight behind the connection board. (Track.jpg)

Once I wired up Orange\White to B- and Brown\White to A+ (rj45.png) and altered the ModBus SN from 0 to 1 (Inverter will require a reboot to get rid of the error) I was able to pull data from it.

 

Edited December 29, 20232 yr by Ivan Endicott

Has anyone tried to collect sensor metrics directly from the battery BMS eg Synsynk BYD RS232 port? I am not sure if this rabbit hole is worth the effort, what useful data can you collect other than individual battery cycles, cell voltages and temperatures?

17 minutes ago, Gambit said:

Has anyone tried to collect sensor metrics directly from the battery BMS eg Synsynk BYD RS232 port? I am not sure if this rabbit hole is worth the effort, what useful data can you collect other than individual battery cycles, cell voltages and temperatures?

JKBMS over bluetooth, with comms to the Sunsynk/Deye via CAN port to derate the charge current discussed over here 

 

 

 

Edited January 4, 20242 yr by iiznh

Guys,

If I turn off my timer at night the Grid starts charging my batteries. I don't want the grid to charge my batteries, only want my solar to charge my batteries. I don't have GRID or Gen ticked.

 

Pls assist

Thanks

9 hours ago, Vaughanza said:

If I turn off my timer at night the Grid starts charging my batteries.

The timer is purely for when you do not have solar and need to run in UPS mode where the grid charges your battery. You should not turn it off if you have solar. Set the required SOC to keep in reserve for that time, if it goes below the soc the inverter will switch to grid power.

You should also be posting this question in a new thread or a related thread as it has nothing to do with the 8kW dat collection setup, basic forum etiquette

Good day all you clever people...

I've had my Deye 8kw hooked up to an esp32 and RS485-TTL (R7 removed) this has been running smoothly for the last couple of months.

Now over the Holiday season when I was away, I checked in on my goodies on Home Assistant and found that the logging of data went all weird... I could not do anything as I wasn't home and thought I'd just do an update on esphome as I figured a restart of the esp would have done the trick... (it didn't)

Got home and investigated a bit more and checked the ESPHome logs and found the following

[14:13:32][D][modbus_controller:043]: Modbus command to device=1 register=0xBE countdown=0 no response received - removed from send queue
[14:13:33][D][sensor:094]: 'Deye Total PV Power': Sending state nan W with 0 decimals of accuracy
[14:13:34][D][modbus_controller:043]: Modbus command to device=1 register=0x51 countdown=0 no response received - removed from send queue
[14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=70 count=10
[14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=84 count=3
[14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=90 count=2
[14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=96 count=2
[14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=108 count=5
[14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=154 count=1
[14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=164 count=6
[14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=172 count=4
[14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=178 count=1
[14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=182 count=3
[14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=186 count=2
[14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=194 count=1
[14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=217 count=1
[14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=237 count=1
[14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=239 count=1
[14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=243 count=1
[14:13:34][W][modbus_controller:136]: Duplicate modbus command found: type=0x3 address=247 count=2
[14:13:34][W][component:214]: Component modbus_controller took a long time for an operation (0.15 s).
[14:13:34][W][component:215]: Components should block for at most 20-30ms.

 

Could it be that the magic blue smoke escaped my RS485-TTL module out of thin air?

Any input would be greatly appreciated

2 hours ago, fStof said:

Could it be that the magic blue smoke escaped my RS485-TTL module out of thin air?

Any input would be greatly appreciated

The that specific comms board that everyone butchers and remove R7 was designed for use in an arduino with 5V signalling

The ESP32 was only designed for 3.3V so the io pin might be dead. Try another GPIO for RX

It could also be a lightning strike nearby that induced a spike 

22 minutes ago, iiznh said:

The that specific comms board that everyone butchers and remove R7 was designed for use in an arduino with 5V signalling

The ESP32 was only designed for 3.3V so the io pin might be dead. Try another GPIO for RX

It could also be a lightning strike nearby that induced a spike 

I actually swapped out the rx, tx and flow control pins on the esp... made no difference.

I'm no expert... But if it was a lightning strike, would it not have done much worse damage?

3 minutes ago, fStof said:

But if it was a lightning strike, would it not have done much worse damage?

There is a big difference between a direct lightning strike and an induced spike. Induced spikes will kill circuits connected to a long wire (that acts as a signal amplifier). 

You Esp32 is still working and sending wifi packets which is a good sign. Maybe just the MAX485 chip that was harmed in the process. Do like mechanics do. Start replacing parts till it starts working again...

Have any of you been interested in register 146 for 3 phase inverters? Currently we only use on and off time of use, but I got interested in the days of the week yet. Does anyone know how to do this?