@kellerza Thanks for looking at this. I've just realised I've made a mistake though.

I repeated my steps again, and the inverter screen is also incorrect - just not negative.  When I turn the kettle (essential circuit) on, the inverter defaults to 0 W. When the kettle turns off, the 28W shows up on non-essential again. 

 

Based on your observation regarding the SMA meter vs SS delta - I don't think there is much we can do about it. 

Edited April 1, 20224 yr by _terminal

Would it make sense if we simply report 0 for any negative value?

 

Yes, I believe so. That would at least match the inverter display.

How far is your Grid CT coil from your inverter? 

10 minutes ago, _terminal said:

How far is your Grid CT coil from your inverter?

10, maybe 15m max

The SunSynk is a bidirectional inverter and when zero export selected, tries to not feed to the grid.
When a (large) load is switched on/off it sometimes over compensates and seems to "bounce/over compensate" and feed the grid.
This "bounce" can cause some digital meters to trip (some digital meters designed to prevent feed to grid)
There is a setting on the SunSynk for the amount of "trickle feed" to minimize the tripping.

Also note that the AUX port is also bidirectional and can be configured as Generator IN AUX IN or AUX OUT.

Indeed, but if you look at @_terminal ‘s diagram the inverter is not involved during switching of this large load. Its grid only

The inverter (with the CT clamp) is just not capable of measuring this accurately

 

I'm wondering if it's not electrical interference or the distance. The distance between my CT and inverter is between 15-20m using unshielded CAT5e. 

@kellerzaDo you have a list of sensors or an easy way to include all available? 

EDIT: I've been able to manually grab all sensors from the definitions.py file and underscore them. 

Edited April 3, 20224 yr by _terminal

On 2022/03/23 at 12:33 PM, JGB said:

@_terminal Thanks. I tried to set the Modbus SN as suggested, but it didn't make a difference. 

@kellerza  I'm pretty sure the cabling is good. I crimped a RJ45 on both ends of the cable, tested it (with a network cable tester) and then cut the one end off to connect to the USB (https://www.robotics.org.za/RS485-3P). I used a twisted pair (1 + 2) for B and A and also used the ground (3). I'll give that Waveshare USB a try, although at this point, I think my problem may not be related to the choice of RS485 adaptor.

Just a quick update that might help others with intermittent RS485 communication problems. I discovered that the cable (USB) I was using to power my RPi was rubbish. The RPi was not getting enough power, which was causing the USB interface that the RS485 adaptor was connected on to restart. Replaced the cable ... problems sorted. Picked it up from dmesg in SSH connection to the host OS .

On 2021/04/15 at 10:31 PM, Sc00bs said:

Woohooo, Bloubul7,  I have finally worked out how to access your Dashboards in Node Red, they look frikkin awesome!! 

 

Everything at the moment in my Dashboards is set to 0.

 

Can I read in the current settings from my Inverter and then save them  in one of the Dashboards to be written again at a later stage?

I am assuming that that is what the Read button is for, am just a bit nervous of overwriting my Inverter settings as I have no idea what I am doing 🙂   

Hey @Sc00bs, how do you get access to this dashboard? I am getting tired of going to my inverter every time to change settings

2 hours ago, Saliegh said:

Hey @Sc00bs, how do you get access to this dashboard? I am getting tired of going to my inverter every time to change settings

Hi,

The dashboard should be available at http://noderedip:1880/ui

If you want to safe the settings to a local storage file then you would need to enable context storage in your settings.js 

Edited May 24, 20224 yr by Bloubul7

33 minutes ago, Bloubul7 said:

Hi,

The dashboard should be available at http://noderedip:1880/ui

 

Thanks, reimported those flows, and it's working now

Edited May 24, 20224 yr by Saliegh
fixed

@Bloubul7

Hope you can help me, i bought the USB-to-RS485 adaptor dongle as per this page:

https://github.com/kellerza/sunsynk

Cable crimped and installed as per instructions, 

Please see my configuration port addon

port:
serial:///dev/ttyUSB0

driver:
umodbus

swynsynkid:
2******

****

I get the following error in the log:

s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
2022-05-28 17:11:07,636 INFO    Loading HASS OS configuration
2022-05-28 17:11:07,653 DEBUG   could not patch umodbus: numpy not found
2022-05-28 17:11:07,658 INFO    Filter *last used for battery_soc, total_battery_charge, total_battery_discharge, total_grid_export, total_grid_import, total_pv_power
2022-05-28 17:11:07,659 INFO    Connecting to serial:///dev/ttyUSB0
2022-05-28 17:11:17,689 ERROR   Timeout reading: 
2022-05-28 17:11:17,689 INFO    ############################################################
2022-05-28 17:11:17,690 INFO    No response on the Modbus interface, try checking the wiring to the Inverter, the USB-to-RS485 converter, etc
2022-05-28 17:11:17,690 INFO    ############################################################
2022-05-28 17:11:17,690 CRITICAL This Add-On will terminate in 30 seconds, use the Supervisor Watchdog to restart automatically.
[cmd] ./run.py exited 0
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

 

In the Terminal i can see

/dev/ttyUSB0

Hope you can assit

 

 

 

 

@Marius Schonken

You want to check that your USB adapter is being recognised and that you have the correct address for i.

In Home assistant go to settings > system > hardware and then click on the three dot hamburger menu on the top RHS. Click on all hardware and go down to USB for the info, should look something like this: 

 

Morning  @Sc00bs

I do get reply, attached,i also atached screenshot of addon log

 

Some things you can try:

1. Ensure your MODBUS_SERVER_ID matches what is configured on your inverter
2. Ensure only a single connection is made to the serial port at any time (which seem to be /dev/ttyUSB0 from your screenshot)
3. Check the cabling again (use a shorter cable/different cable while testing)

For setting the inverter Modbus ID see:
https://powerforum.co.za/topic/8451-sunsynk-inverter-monitoring/?do=findComment&comment=118621
https://powerforum.co.za/topic/8451-sunsynk-inverter-monitoring/?do=findComment&comment=118862

 

Edited May 31, 20224 yr by system32

39 minutes ago, rob1 said:

Hi all, I'm joining this conversation a bit late, apologies. I didn't want to go through 20 pages of posts lol.

I'm thinking of pulling the trigger on SolarAssistant. I have a 5Kw Sunsynk and Freedomwon 10/8 on CAN bus. Will I be able to get real-time monitoring and be able to update my settings from this SolarAssistant? Do I need to buy special cables? Is it relatively easy to set up?

I don't need anything too fancy - I just want to mainly update my battery grid charge thresholds on weekends and during the week without having to press those flimsy "buttons" on the front of the Inverter.

Thanks!

You can use the SolarMan App/Dongle or SunSynk App/Dongle to manually set the SunSynk battery grid charge thresholds remotely.
AFAIK, nether supports triggers/schedules.

Roll your own setup with HomeAssistant + USB/RS485 cable + https://github.com/kellerza/sunsynk
HA can do triggers/schedules - changing settings is at your own risk.

Not familiar with Node-Red - but seems capable.

SolarAssistant + USB/RS485 cable https://solar-assistant.io/shop/products/sunsynk_rs485
SA can feed HA via mqtt (but not accept commands from HA - Support to change inverter mode via MQTT and HA is planned)
You can remotely manually change SunSynk settings from SA (similar to SolarMan/SunSynk App)
AFAIK, there is no trigger/schedule function in SA yet.

Edited May 31, 20224 yr by system32

18 minutes ago, rob1 said:

Thanks for the feedback! Where do I change those settings in SolarMan? That would solve my need but for the life of me I can't see any way to make any changes within the app. I've tried Solarman business and Solarman smart.

*EDIT* I found a 'Device control' icon in Solarman business web UI but I get this when I click it:

 

AFAIK, You need to ask SolarMan support to give you remote access rights to change your own settings.
Send them an email.
https://powerforum.co.za/topic/8256-new-remote-control-feature-on-solarman-smart/
https://powerforum.co.za/topic/12107-sunsynk-updating-settings-from-phone-possible/?do=findComment&comment=121239

The SunSynk app includes the remote setting by default.

 

Edited May 31, 20224 yr by system32

12 minutes ago, rob1 said:

I see there's also a mobile app update that's not on the play store.
The only reason I know to distribute APKs outside of the play store is if you don't intend to abide by Google's policies. Could be spyware. It's always Chinese companies doing this - "security" cameras especially. Makes me mad.

AFAIK, you can do it with the normal/business SolarMan from the app store.
You just need to ask via email for the correct rights [email protected]

6 hours ago, rob1 said:

I see there's also a mobile app update that's not on the play store.
The only reason I know to distribute APKs outside of the play store is if you don't intend to abide by Google's policies. Could be spyware. It's always Chinese companies doing this - "security" cameras especially. Makes me mad.

Not disputing this app or the current update.

However due to US Sanctions on Chinese companies, they have been blocked from updating their apps on the Google Play store.
This does not mean their apps immediately contain spyware, but mostly just that the American Government has too much control over large companies like google.

Same thing happened to DJI where they have been unable to update the version hosted on the Play Store due to US Sanctions.

21 hours ago, system32 said:

AFAIK, you can do it with the normal/business SolarMan from the app store.
You just need to ask via email for the correct rights [email protected]

Tried this yesterday and got the below:

 

Hi there, I'm about to start with Home Assistant, primarily using Sonoff/Ewelink LAN, but super-keen to integrate with Sunsynk using @Bloubul7template. Can the Sunsynk integration work on Home Assistant OS, or does one need to use the complete PiOS and run HA in a container. Excuse terminology, I'm just getting into this.

Thank you for the advise above

 

i am now connected, but get incorrect readings form my battery, please see log file

 

2022-06-05 19:32:21,376 INFO    Loading HASS OS configuration
2022-06-05 19:32:21,393 DEBUG   could not patch umodbus: numpy not found
2022-06-05 19:32:21,398 INFO    Filter *last used for battery_soc, total_battery_charge, total_battery_discharge, total_grid_export, total_grid_import, total_pv_power
2022-06-05 19:32:21,399 INFO    Connecting to serial:///dev/ttyUSB0
2022-06-05 19:32:21,482 INFO    ###########################################################
2022-06-05 19:32:21,482 INFO                Inverter serial number 'xx'
2022-06-05 19:32:21,483 INFO    ############################################################
2022-06-05 19:32:21,484 INFO    MQTT: Connecting to mqtt_user@core-mosquitto:1883
2022-06-05 19:32:21,500 INFO    MQTT: Connection successful
2022-06-05 19:32:22,613 ERROR   Read Error: (1,78,1) CRC validation failed.
2022-06-05 19:32:22,615 INFO    Retrying individual sensors: ['Total PV Power:last', 'Total Battery Charge:last', 'Total Battery Discharge:last', 'Total Grid Export:last', 'Total Grid Import:last', 'Battery SOC:last']
2022-06-05 19:32:22,755 ERROR   Read ErrorTotal Battery Charge: (1,72,2) CRC validation failed.
2022-06-05 19:32:22,825 ERROR   Read ErrorTotal Battery Discharge: (1,74,2) CRC validation failed.
2022-06-05 19:32:22,963 ERROR   Read ErrorTotal Grid Import: (1,78,1) CRC validation failed.
2022-06-05 19:32:23,099 ERROR   Read Error: (1,72,4) CRC validation failed.
2022-06-05 19:33:23,208 ERROR   Read Error: (1,72,4) CRC validation failed.
2022-06-05 19:34:23,315 ERROR   Read Error: (1,72,4) CRC validation failed.
2022-06-05 19:35:23,411 ERROR   Read Error: (1,72,4) CRC validation failed.
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/sunsynk/sunsynk.py", line 52, in read_sensors
    r_r = await self.read_holding_registers(grp[0], glen)
  File "/usr/local/lib/python3.9/site-packages/sunsynk/usunsynk.py", line 43, in read_holding_registers
    return await self.client.read_holding_registers(self.server_id, start, length)
  File "/usr/local/lib/python3.9/site-packages/async_modbus/core.py", line 181, in read_holding_registers
    return await self._send_message(request)
  File "/usr/local/lib/python3.9/site-packages/async_modbus/core.py", line 142, in _send_message
    return await self.protocol._async_send_message(
  File "/usr/local/lib/python3.9/site-packages/async_modbus/core.py", line 78, in send_message_rtu
    return rtu.parse_response_adu(response_error_adu + response_remainder, adu)
  File "/usr/local/lib/python3.9/site-packages/umodbus/client/serial/rtu.py", line 183, in parse_response_adu
    validate_crc(resp_adu)
  File "/usr/local/lib/python3.9/site-packages/umodbus/client/serial/redundancy_check.py", line 76, in validate_crc
    raise CRCError('CRC validation failed.')
umodbus.client.serial.redundancy_check.CRCError: CRC validation failed.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/src/app/./run.py", line 180, in read_sensors
    await asyncio.wait_for(SUNSYNK.read_sensors(sensors), OPT.timeout)
  File "/usr/local/lib/python3.9/asyncio/tasks.py", line 478, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.9/site-packages/sunsynk/sunsynk.py", line 54, in read_sensors
    raise Exception(  # pylint: disable=raise-missing-from
Exception: (1,72,4) CRC validation failed.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/usr/src/app/./run.py", line 274, in <module>
    LOOP.run_until_complete(main(LOOP))
  File "/usr/local/lib/python3.9/asyncio/base_events.py", line 642, in run_until_complete
    return future.result()
  File "/usr/src/app/./run.py", line 260, in main
    await polltask
  File "/usr/src/app/./run.py", line 252, in poll_sensors
    if await read_sensors([f.sensor for f in fsensors]):
  File "/usr/src/app/./run.py", line 191, in read_sensors
    raise Exception(f"Multiple Modbus read errors: {err}") from err
Exception: Multiple Modbus read errors: (1,72,4) CRC validation failed.
[cmd] ./run.py exited 1
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

Edited June 5, 20224 yr by Marius Schonken

12 hours ago, Marius Schonken said:

Thank you for the advise above

 

i am now connected, but get incorrect readings form my battery, please see log file

 

Did you change the serial number to your inverters serial number in the setup? 

If yes and all are your readings are wrong, I would check the cable. 

Edited June 6, 20224 yr by Sc00bs
spelling