Support for Sunsynk inverter via Solarsynk2 add-on for Home Assistant about pv_opt HOT 91 OPEN

OK - apologies for the delay. Please can you try pre-release 4.0.0-sunsynk-alpha-7 which should address the issues above and also includes various patches made to the production release.

from pv_opt.

I'm away for a couple of days. Will try to look when I'm back

from pv_opt.

Forgot to add HA entities to read:

Battery minimum SOC: sensor.solarsynk_{inverter sn}_battery_shutdown_cap (%)
Battery SOC:         sensor.solarsynk_{inverter sn}_battery_soc (%)
Either:
  Load power:        sensor.solarsynk_{inverter sn}_load_power (kW), or
  Load today:        sensor.solarsynk_{inverter sn}_day_load_energy (i.e kWh)
Either:
  Grid import power: sensor.solarsynk_{inverter sn}_grid_power (this is probably total import and export)
  Grid export power: 
Or:
  Grid import today: sensor.solarsynk_{inverter sn}_day_grid_import (kWh) and
  Grid export today: sensor.solarsynk_{inverter sn}_day_grid_export (kWh)

from pv_opt.

I can certainly try to get something working for you. It may take a while - need to solve a few other bugs 1st.

from pv_opt.

That's great, thankyou. The installation's only been in for a week and we're not certified to export yet. Then I'll need to familiarise myself with programming it manually. What do you think about the update settings method provided by the Solarsynk add-on? It takes up to 5 min to send to the cloud, then maybe another 5 min until the results are readable from HA sensors. Is that fast enough?

regards
Mark

from pv_opt.

OK - I've had a very preliminary start at this. It will is v4.0.0-alpha-1 pre-release so you will need to enable Beta versions in HACS and manually select it. You will also need the config_sunsynk.yaml file from the GitHub release or the branch associated with this Issue (rename it to config.yaml

If you are very lucky it might work in Read Only mode! Either way please send me the logs. In the meantime I will try to have a look at the documentation for the integration.

from pv_opt.

Thanks I'll give it a go! I'll try to clarify the working modes for the inverter tomorrow - they control whether the inverter gives priority to essential load / non-essential load / battery / grid export. I've also discovered another check we should do - the inverter will support battery types which use voltage instead of SOC to control charge / discharge so we should check that the battery is compatible with SOC. Also, I think my documentation is wrong about ticking 'Grid' for a discharge, it looks like it should be unticked. I'll update the documentation

from pv_opt.

Sorry my mistake - {inverter sn} should be {sunsynk_serial} as defined in solarsynk addon. Also - cosmetic change - could you change the spelling of solarsync2 to solarsynk2 please. I don't know how far I can get with testing because we're not certified for export yet so we haven't changed tariff from the fixed rate Flexible Octopus to some thing smart such as Agile or Flux. Unless there's a way to bypass it for testing purposes?

from pv_opt.

I think there are 2 typos in sunsynk.py:

from pv_opt.

Is there any way of extracting {sunsynk_serial} from the addon? If not I might prefer to keep {inverter_sn} as a generic parameter across brands. Will fix the typos now and re-release as alpha-2

from pv_opt.

alpha-2 available. You will need to manually copy config-sunsynk.yaml

from pv_opt.

[sunsynk_serial} is in the config for the Solarsynk add-on but I can't see a sensor for it

from pv_opt.

from pv_opt.

Sorry but I think there's another typo:

from pv_opt.

Also I think the underline character is missing in {inverter_sn} on all of the sensors above

from pv_opt.

Updated my documentation for the inverter. There are a couple of problems, such as

• No method in Solarsynk integration to check max power of inverter
• No method in Solarsynk integration to check whether an Auxiliary power source (e.g. generator / wind turbine) is connected which I imagine would invalidate a pv_opt plan
• The Solarsynk update method is based on a batch process and takes 5 - 10 minutes to return, plus the return codes are only visible in the Solarsynk log

Apart from that I think it should work!
sunsynk inverter class for pv_opt v2.odt

from pv_opt.

That's great - I will have a proper read of this now and have a think about how to implement it

from pv_opt.

Here are the logs from running v4.0.0 alpha2
error.log
main.log
pv_opt.log

from pv_opt.

from pv_opt.

Hope you're having a nice holiday. I made some progress by hard coding the inverter serial number in config.yaml (inverter serial number redacted manually - 10 digits, also my Octopus account has an e instead of an m):

Now pv_opt gets further:
error.log
main.log
pv_opt.log

You'll see I'm on the Octopus Flux tariff for import but don't yet have an export tariff. I have submitted the MCS certificate and permission from the DNO but I think it can take weeks to get an export MPAN number

from pv_opt.

following developments

from pv_opt.

I've synced this branch up with the main branch so it should now handle the lack of an export contract OK which was the point of failure before. Also added the inverter_sn to the redaction list. Released as 4.0.0-alpha3

from pv_opt.

Hope you had a good holiday! We got our export MPAN this morning but Octopus don't seem to have taken any readings yet. Perhaps overnight. I reloaded the Octopus integration in HA and the export sensors appeared. I installed pv_opt 4.0.0-alpha4 and ran again. I reverted to the config_sunsynk.yaml from GitHub and used this to overwrite my config.yaml because pv_opt doesn't seem to be picking up some values correctly. I edited it to add the correct value of {inverter_sn}. From the logs it looks like pv_opt isn't picking up {device_name} or {inverter_sn}. Also I think there are a couple of typos in config.yaml:

• inverter_type: "SUNSYNK_SOLARSYNC2" should be inverter_type: "SUNSYNK_SOLARSYNK2"
• "maximum_dod_percent": "sensor.{device_name}_{inverter sn}_battery_shutdown_cap" # presumably should be {inverter_sn}
• "id_battery_soc": " sensor.{device_name}_{inverter sn}_battery_soc" # as above underline character missing
• "id_consumption_today": "sensor.{device_name}_{inverter sn}_day_load_energy" # as above, underline character missing
• "id_grid_import_today": "sensor.{device_name}_{inverter sn}_day_grid_import" # as above, underline character missing
• "id_grid_export_today": "sensor.{device_name}_{inverter sn}_day_grid_import" # as above, underline character missing, also I think import should be export
  error.log
  main.log
  pv_opt.log
  Also I think redaction list needs another line for my MPAN number which is of the form 99e9999999_9999999999999 instead of 99m9999999_9999999999999 (perhaps e and m are region markers?)

from pv_opt.

Thanks for this. In 4.0.0-alpha-5 I have removed config-sunsynk.yaml and merged all the changes in to the main config.yaml. You should just need to un-comment the final block of parameters in this file.

I've also updated the regex pattern for the MPAN.

Hopefully with the correction of SOLARSYNC2 to SOLARSYNK2 it should get a bit further. Let me know how you get on.

from pv_opt.

Thanks - got a lot further this time but still seems to be ending with an error:
ValueError: cannot reindex on an axis with duplicate labels
Redaction mostly working but there are a couple of lines in pv_opt.log still containing inverter serial number and account_MPAN number
One of the defaults in config.yaml still looks wrong :

Think this should read
id_grid_export_today: sensor.{device_name}_{inverter_sn}day_grid_export
instead of
id_grid_export_today: sensor.{device_name}{inverter_sn}_day_grid_import
error.log
main.log
pv_opt.log

from pv_opt.

would really like to get this working

from pv_opt.

Thanks I'll give it a go. Actually I wasn't ready until today - SSD failed and it's taken me a week to get a replacement and recover Home Assistant from backup. We've also got some persistent connectivity problems with Solarsynk as a result of which my updates from a couple of HA automations don't seem to be working. It seems to be affecting all users of Solarsynk so it might be the cloud app that is at fault. On the plus side I'm now exporting to the grid and getting paid for it. As a result I've found out more about the Sunsynk inverter's eccentricities. For example, charge current is not controlled by the timers. Also, to discharge the batteries to the grid I need to change the Work Mode from 'Limited to Home' = 2 to 'Selling First' = 0 in real time because otherwise I can't discharge the battery to Home at other times without exporting as well. I've also found a different Sunsynk HA integration by MorneSaunders360 which also works via the cloud API but has an HA service to update the inverter which might be more appropriate for pv_opt. I'll have a look at that. In the meantime I have updated my documentation - sorry if I've misled you so far!
sunsynk inverter class for pv_opt v3.odt

from pv_opt.

OK - apologies for the delay. Please can you try pre-release 4.0.0-sunsynk-alpha-7 which should address the issues above and also includes various patches made to the production release.

Currently unable to test properly due to ongoing problems with Solarsynk.

Sunsynk.py still has references to "SUNSYNK_SOLARSYNC2" should be "SUNSYNK_SOLARSYNK2" (Lines 72, 86, 117)

error.log
main.log
pv_opt.log

from pv_opt.

4.0.0-sunsynk-alpha-8 should fix the typos and also bring the underlying code up to date with the latest production release

from pv_opt.

I think I've got the latest version but it's reporting

• PV Opt v4.0.0-4.0.0-sunsynk-alpha-7
  in the pv_opt.log

When I start the application it is stuck at 'Initialising PV model'. There is a warning in error.log:

• AttributeError: 'InverterController' object has no attribute 'is_online'
  error.log
  main.log
  pv_opt.log

from pv_opt.

Sorry about that. Fixed both of those so the latest is still 4.0.0-sunsynk-alpha-8

from pv_opt.

Got a lot further this time - stopped at Optimising Charge Plan with an error
error.log
main.log
pv_opt.log

from pv_opt.

from pv_opt.

sunsynk.py - lines;- 7,34,35,36,37,38 require changing from {inverter sn} to {inverter_sn}

from pv_opt.

sunsynk.py - lines;- 7,34,35,36,37,38 require changing from {inverter sn} to {inverter_sn}

Fixed this and added some checks to the SOC in 4.0.0-sunsynk-alpha-9

from pv_opt.

Error during initialize() for pv_opt:

• AttributeError: 'PVOpt' object has no attribute 'redact_patterns'

error.log
main.log
pv_opt.log

from pv_opt.

fixed in 4.0.0-sunsynk-alpha-10

from pv_opt.

I think it's published as alpha-19
It completes a plan!

It probably doesn't help that I lost a week's history when my SSD failed, and also the Solarsynk add-on is still suffering intermittent (but frequent) connectivity problems. Several users of Solarsynk have reported the same symptoms so probably cause is with the add-on or the Sunsynk cloud. This not only causes gaps in the history but any inverter updates are missed. This is fatal at the moment because it is hard to check whether a command has been successful. There's an open issue for this.

One problem I can see with the inverter class for pv_opt is that we are using the Battery Shutdown Capacity (set by the installer to 15 on mine) to define the minimum DOD. Ideally it would be the 'Low Batt' setting (set by my installer to 20) to avoid the battery actually shutting down. Unfortunately this is not mapped to a sensor in Solarsynk. Can I set a hard value in config.yaml?

from pv_opt.

from pv_opt.

Just discovered another eccentricity of the Sunsynk cloud api - in order to enable Grid charging in a timeslot you also have to specify Gen charge ({"time2on": true, "genTime2on": false} instead of {"time2on": true}. If you only specify one, the api responds 'Success' but doesn't do anything. I'll update my document but trying to avoid too many versions in a day!
By the way, thanks for all the time you've put into this so far. It must be more or less impossible to test without a Sunsynk inverter. I was delighted when my dashboard graphs sprang into life!

from pv_opt.

One problem I can see with the inverter class for pv_opt is that we are using the Battery Shutdown Capacity (set by the installer to 15 on mine) to define the minimum DOD. Ideally it would be the 'Low Batt' setting (set by my installer to 20) to avoid the battery actually shutting down. Unfortunately this is not mapped to a sensor in Solarsynk. Can I set a hard value in config.yaml?

You can either map it to a fixed number or an input_number helper entity that you set up yourself.

from pv_opt.

When you've got a minute can you upload a copy of the logs just to make sure there are no funnies.

It is tricky without the same inverter. What's even more confusing is that I'm trying to get a Solax inverter going at the same time. Fortunately the way I've set it up with separate plugins by brand makes it easier to manage.

from pv_opt.

error.log
main.log
pv_opt.log
pv_opt.log.1.txt
sunsynk inverter class for pv_opt v4.odt

from pv_opt.

There's clearly an issue where data is periodically unavailable. You can see this if you search the log for soc_now. At 16:20 it is 92.0 but at 16:30 it is blank. I guess this is down to the issues with the Solarsynk add-on that you've highlighted. I'll add some code to get it to re-try if it fails to get a number.

from pv_opt.

Try 4.0.0-sunsynk-alpha-11

from pv_opt.

Just had to patch to 4.0.0-sunsynk-alpha-12 to fix a bug associated with the clock change

from pv_opt.

Here are the logs from alpha 12
The data coming from Solarsynk is pretty ropey at the moment I'm sure it wasn't like this to start with so perhaps fixable. Difficult to make much progress until Solarsynk is fixed though:

error.log
main.log
pv_opt.log

from pv_opt.

That's pretty poor. For history it's OK as PV_Opt interpolates any gaps but the problem comes when reading current states. Fortunately the optimiser only really needs the current SOC. In alpha-13 I'm setting it to use the last value from the history if it can't get the current state from HA.

Controlling the inverter needs reliable access to the current states and also the ability to write reliably. This, combined with the 5 minute interval you mentioned before could make things tricky. One option would be to control the inverter directly through the sunsynk API rather than solarsynk. What do you think?

from pv_opt.

Hold off on alpha-13 it has a bug

from pv_opt.

Mark

I have been looking at this
https://smarthomeintegrations.co.za/product/smartdeyedonglev4-intl-shipment/

It gives direct access to the inverter for read/write

from pv_opt.

I agree Solarsynk is not looking too promising at the moment. I imagine the connectivity problem will get fixed but the 5 min delay and lack of response to commands are serious weaknesses which can't easily be fixed because the whole add-on runs as a 5 minute batch process. I'm a bit reluctant to connect directly to modbus though. The only easily accessible port on the inverter is already occupied by an e-Linter data logger which is used by Sunsynk and my installer for support as well as feeding the Sunsynk app. I'm not sure it's a good idea to have 2 parallel sources of commands connected at the same time. Also I think using the Sunsynk API might be somewhat safer (though I can believe it would be possible to ruin an inverter by sending a wrong API call),
@alz41 I'm wondering whether the MorneSaunders360 integration would be a better bet. Sounds like you might have tried it so what do you think?

from pv_opt.

@fboundy just re-read your post and realised you're talking about directly connecting to the Sunsynk API, not a wired modbus connection. I think that could work but I don't have any documentation of it apart from unofficial lists of json keys. I guess you could copy one of the integrations already published in Github

from pv_opt.

@ElectricMolehill I'm having the same sort of problems with that integration. Regarding modbus connection iv been running solar assistant connected via splitter on the battery input for six months with no problems.

from pv_opt.

All the necessary API calls appear to be in the solarsync add-on bash script but it would be rather duplicating effort.

alpha-13 should be working now I think

from pv_opt.

alpha-13 - there's a type error:
TypeError: object of type 'bool' has no len()
error.log
main.log
pv_opt.log
Connecting direct to Sunsynk API - yes let's give it a go. It's a shame to duplicate effort but the Solarsynk add-on doesn't have the features we need and it's not really feasible to add them. We could try the MorneSaunders integration but it sounds like that also has a connectivity issue and it would be quite a bit of work before we know whether it's suitable. It's mostly your time so I'm happy to go with whichever you think has the best prospects

from pv_opt.

FIxed in 4.0.0-sunsynk-alpha-14

Once let's see if we can consistently get charge plans in read-only and then we'll make a call on which route to go down for control

from pv_opt.

That's looking good so far. Perhaps I'd better leave it running for a few days to give it a proper run with better data. I missed a day's inverter history in HA yesterday because the Sunsynk dongle lost contact with my local network when the clocks changed and I didn't discover a fix until yesterday evening
Good news is, Solarsynk has been patched to handle connectivity failures more gracefully. Also it sounds like the connectivity issues may have been something to do with verification of SSL certificates since Sunsynk.net changed certificates. The cause of this is still not known so unfortunately the workaround is to disable verification. Still, that might close up the gaps in the data
error.log
main.log
pv_opt.log

from pv_opt.

@fboundy should the pvopt entities be created? With current release

from pv_opt.

from pv_opt.

Should be. If they aren’t it suggests an error. What does error.log say?
…
On 1 Apr 2024 at 17:12 +0100, alz41 @.>, wrote: @fboundy should the pvopt entities be created? With current release — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.>

main.log
error.log
pv_opt.log

from pv_opt.

logs for alpha15

entities still not created for dashboard

error.log
main.log
pv_opt.log

from pv_opt.

The last error.log was empty. Could you please re-upload?

from pv_opt.

from pv_opt.

from pv_opt.

@alz41 is Mosquitto running OK?

from pv_opt.

@fboundy whats strange is the sensors are created but not the helpers

LOG AFTER 30MINS OF RUNNING (ERROR LOG [EMPTY)

error.log
main.log
pv_opt.log

from pv_opt.

OK - I'll try to get an update out tomorrow which is up to date with the main beta version. Might help

from pv_opt.

OK - I'll try to get an update out tomorrow which is up to date with the main beta version. Might help

thanks

Mosquitto log shows connection as below

Mosquitto broker
2024-04-03 19:06:31: New client connected from 172.30.33.6:55967 as localad (p2, c1, k60, u'PV_OPT').

from pv_opt.

I've just released 3.14.0-alpha-16 (decided that this won't be v4 after all) which should have a lot more functioning features. It doesn't write to the solarsynk helper entity but it writes the JSON that it would have written to the log file.

I'm trying to get all these various features into 3.14.0 and get that out asap so let me know what you find

from pv_opt.

3.14.0-alpha-16
helpers still not being created

error.log
main.log
pv_opt.log

Mosquitto.log
2024-04-04 21:51:52: New connection from 172.30.33.6:52653 on port 1883.
2024-04-04 21:51:52: New client connected from 172.30.33.6:52653 as localad (p2, c1, k60, u'PV_OPT').

Supervisor.log
2024-04-04 20:48:11.237 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'PV_OPT'
2024-04-04 20:48:11.711 INFO (MainThread) [supervisor.auth] Successful login for 'PV_OPT'
2024-04-04 20:57:04.842 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'PV_OPT'
2024-04-04 20:57:05.317 INFO (MainThread) [supervisor.auth] Successful login for 'PV_OPT'
2024-04-04 21:51:52.312 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'PV_OPT'
2024-04-04 21:51:53.567 INFO (MainThread) [supervisor.auth] Successful login for 'PV_OPT'

from pv_opt.

from pv_opt.

Does sound like an MQTT problem.

solar assistant works fine with MQTT, ANY IDEA HOW TO DEBUG.
Have already uninstalled rebooted and reinstalled still same error

from pv_opt.

I've successfully debugged MQTT issues with MQTT Explorer in the past.

There is an error being caused by a bug in the sunsynk controller which I will fix for the next release . This isn't related to the MQTT but if we can get everything else running perhaps we can diagnose better.

from pv_opt.

from pv_opt.

Should be fixed in the 3.14.0 release

from pv_opt.

logs from 3.14.0 release
14:37:26 WARNING pv_opt: Unexpected error in worker for App pv_opt:

error.log
main.log
pv_opt.log

from pv_opt.

@alz41 is Mosquitto running OK?

@ElectricMolehill
Yes, Sensors show when i connect with MQTT EXPLORER but not showing in Home Assistant

from pv_opt.

I installed v3.14.1 - it's running fine but I had to add 2 lines to config.yaml:

• battery_voltage: sensor.{device_name}_{inverter_sn}_battery_voltage
• id_solar_power: sensor.{device_name}_{inverter_sn}_pv1_power (i.e. string 1 only)

I had to spell out inverter_sn explicitly in both cases as pv_opt did not pick it up from config
Solarsynk has 1 power sensor for each PV string pv1 and pv2. It doesn't have a total value for pv power but it does for battery related sensors such as battery_power1 / battery_power2 and battery_power so perhaps I could ask for a total to be added

Good news is, Solarsynk is now running reliably with no dropouts since SSL certificate checking was disabled

(ignore the glitch yesterday just after 21:00 - I accidentally pulled the network cable loose)

I think I misunderstood the meaning of 'Hold SOC' when I sent you my documentation. Does it mean - 'maintain SOC for a 15 min timeslot without charging or discharging at all'? If so then I was wrong and there is a way to do this. I'll need to do some more testing to confirm the best way to do it

error.log
main.log
pv_opt.log

from pv_opt.

version 3.14.2 logs

error.log
main.log
pv_opt.log

from pv_opt.

@alz41: 3.14.3 should fix the error in solarsynk_set_helper

@ElectricMolehill: It should also allow you to specify two a list of entities for the solar power:

  id_solar_power: 
    - sensor.{device_name}_pv_power_1
    - sensor.{device_name}_pv_power_2

from pv_opt.

3.14.3 logs

WARNING pv_opt: Unexpected error in worker for App pv_opt:

error.log
main.log
pv_opt.log

from pv_opt.

after changing overwrite_ha_on_restart: to false and ev charger to none everything working as expected.

should PVOPT be making changes to inverter settings for charge/discharge?

from pv_opt.

At present it should just be writing the state of the Solarsynk helper to the log but I've just spotted a typo. I will fix and issue an update but if you want to edit yourself it is line 135 in sunsynk.py. It should be:

    self.rlog(f"Setting SolarSynk input helper {entity_id} to {new_json}")

from pv_opt.

@fboundy

At present it should just be writing the state of the Solarsynk helper to the log but I've just spotted a typo. I will fix and issue an update but if you want to edit yourself it is line 135 in sunsynk.py. It should be:

    self.rlog(f"Setting SolarSynk input helper {entity_id} to {new_json}")

Made the above change,
Clicking send to inverter on the Pvopt test card raises the following error - pandas._libs.tslibs.parsing.DateParseError: Unknown datetime string format, unable to parse: sensor.{device_name}_2301058444_prog1_time

Full logs below
error.log
main.log
pv_opt.log

from pv_opt.

Rebooting HA with read only set true in Pvop config runs, but setting read only false gives error

error.log
main.log
pv_opt.log

from pv_opt.

I've updated my sunsynk document to include some new information such as

• Grid change and Gen charge must be updated together
• Possible ways to achieve hold_soc
• Various corrections / clarifications
  sunsynk inverter class for pv_opt v4.odt

from pv_opt.

Been tied up with other things but will hopefully get back on this next week

from pv_opt.

I've had pv_opt running in read only mode for a couple of weeks now without error. I don't always understand the plan it produces but that is probably because I don't understand the algorithm. Solarsynk is also running reliably now since the CA cert check was removed

from pv_opt.

from pv_opt.

pv_opt.log

from pv_opt.

reboot HA
First load logs
error.log
main.log
pv_opt.log

change ev charge to none @ 17:34
error.log
main.log
pv_opt.log

from pv_opt.