check your statistics as it looks like sunsynk is importing data or something, the stats in the energy dashboard is off.

19 minutes ago, Ronnie1102 said:

check your statistics as it looks like sunsynk is importing data or something, the stats in the energy dashboard is off.

Probably part of the history data migration and why the app is down, see I'm at 312MW for today 😅

Sunsynk could at least have send out a notice to all end users, luckily my installer did send out a notice the app is down to his clients this morning.  Guess he was bombarded with queries, eish, but that is why I first check the facebook Sunsynk groups when things look funky because I woke up to HA shouting to me Battery low, swithing to battery priority mode etc. at least I know my automations work 😆

Maybe just a headsup, saw the app seems to be back up, at least mine is, but all of my SOC % was at 0 so perhaps just need to double check that.

Edit:

Checked with my neighbour but his SOC's was fine so not sure if this is HA related thing or Sunsynk but rather safe than sorry. 

Edited January 28, 20242 yr by -cK-

Sunsynk website has been fubar the whole day. I think they dropped a db lol

18 minutes ago, Gary Waterworth said:

Sunsynk website has been fubar the whole day. I think they dropped a db lol

Was also unable to refresh the whole morning until early this afternoon.

Not the first Sunday I’ve picked up downtime; but normally it’s much shorter.

Had to review todays stats on the inverter screen instead - felt like I was back in 2015 for a minute there!

Looks like it’s fine now, though.

Edited January 28, 20242 yr by JayMardern

1 hour ago, Gary Waterworth said:

Sunsynk website has been fubar the whole day. I think they dropped a db lol

It looks like every second Query results in Node-red errors,


which results in null states and the card is then without valid data (card with data followed by card with null values)

it was down then up for a bit and I see it's now down again. sigh.

At least I did not screw something up on my end 😄

I’ve got figures coming though since about 1pm but my automation to force charge seems to be failing since the downtime. What’s the best way to debug this?

3 hours ago, Benseb said:

I’ve got figures coming though since about 1pm but my automation to force charge seems to be failing since the downtime. What’s the best way to debug this?

depends on how it was written

I can see the automation run but the “use timer” didn’t update on the inverter. 
 

it’s run a few times today and not updated. It was fine before the outage?

What’s the quickest way debug this in node  red, as I still can’t make any changes from HA  

 

Edited January 29, 20242 yr by Benseb

2 hours ago, Benseb said:

What’s the quickest way debug this in node  red, as I still can’t make any changes from HA  

 

Which automation and flows are you using ?show me a screenshot of your flows 

Edited January 29, 20242 yr by Gary Waterworth

24 minutes ago, Gary Waterworth said:

Which automation and flows are you using ?show me a screenshot of your flows 

I’ve not changed the flows. Just using the basic ones from the repo plus an HA automation to toggle the binary sensor input_boolean.sunsynk_usetimer

 

will pop a screenshot up from my laptop shortly 

Hmmm. Something I’ve just noticed end in Node Red

 

one minute it’s showing loads of connection errors, a few moments after it runs again OK

 

 

Edited January 29, 20242 yr by Benseb

This is what was showing. However I’ve just redeployed the flows and haven’t seen the connection errors since….

There are nodes showing connection errors.

Go to the wiki and follow all steps and check the global config nodes.

This is the connection between node red and ha which is not done correctly

 

Edited January 30, 20242 yr by Gary Waterworth

On 2024/01/30 at 2:31 AM, Gary Waterworth said:

There are nodes showing connection errors.

Go to the wiki and follow all steps and check the global config nodes.

This is the connection between node red and ha which is not done correctly

 

Hey @Gary Waterworth,

Thank you for developing your scripts, they are great!

I had some issues however when setting up your scripts, due to various issues, such as:

• Using complete docker compose/swarm setup, where it was not an "addon"
• Performance issues when trying to check inverters which don't exist in a master/slave setup
• Requesting plant list from a complex account of different inverters, setups, masters and slaves - due to a multi-plant account

Therefore, ive fixed many issues, and I've put a PR on Github

Here are the list of changes on the PR - https://github.com/gdwaterworth/Home-Assistant---E-Linter-Logger---Sunsynk/pull/52 

Please note: Myself and Gary are currently working through before merging the changes, so they may change!

• Multiple lists of plants can have master and slaves and different size inverters, which broke part of the flow -some common errors ive seen other users post here should now be fixed.
• Time uploads broke as didn't follow the correct format - mainly due to slave plants trying to send zero
• This config has been tested with the latest Docker containers of HA 2024 and NR v3
• Added additional debugging for debug mode
• Display the debug and warnings state is enabled/disabled within Flow and debug msgs
• Performance improvements, which skip Plant ids where an inverter id and data doesn't exist (usually slave plants) - this helps with multi-plant accounts, also where an inactive plant may exist within the list also
• Tidy up debug messages,
• Added friendly Warnings to help with setup issues for first setup, as current wiki not clear

 

If anyone would like to try my changes, please backup your current flow first, try at your own risk, etc - the changes are here: https://github.com/t0mtaylor/Home-Assistant---E-Linter-Logger---Sunsynk/tree/Stable-Release

Next changes I may look at, is allowing the script to support multiple plant and inverters being submitted to Home Assistant

Thanks

Tom

Edited February 1, 20242 yr by Tom Taylor

Hey all

 

I’m trying to get the slipx card working

 

I’ve imported all the custom sensors and can see them reporting values, but they do seem to have different names than the card suggests?

 

eg card: day_pv_energy_108

sensor: sensor.sunsynk_daily_pv_108

 

however when I go to the card, and edit entities, none of them show up within the search box? Eg if I type 108  

 

I’ve tried just typing them in without the lookup but no data is returned

 

what am I doing wrong?

 

 

Ignore me, seems I had an old version of the card code. 

So there was some downtime reported with Sunsynk today. 
 

when this happens we seem to get a bit of a situation

 

Our SOC(1-6) values get set to zero

 

Im not sure if the API is reporting zero or not (but lots of zeros show in the app when it’s down). I then waited to see if HA recovered to the corrext values once API up again, but it seems they get stuck on zero without any manual intervention from me. 
 

thankfully the shutdown % prevents the battery from draining to zero, however if I’m not careful and spot this, it won’t charge up off peak overnight as the target SOC for those slots are 0

 

feels like there may need to be some error handling/catching around this?

Edit : I have changed teh sanity check to only accept "set inputs" between 20 and 100 for those capacity entities. Justy checking things and will push a new version to GIT

There are some changes another member has proposed that I am look at that "may" help with this.

I have seen the problem and bascially the api is reporting the 0's back which makes error handing on the request itself difficult 

Edited February 5, 20242 yr by Gary Waterworth

18 minutes ago, Gary Waterworth said:

Edit : I have changed teh sanity check to only accept "set inputs" between 20 and 100 for those capacity entities. Justy checking things and will push a new version to GIT

There are some changes another member has proposed that I am look at that "may" help with this.

I have seen the problem and bascially the api is reporting the 0's back which makes error handing on the request itself difficult 

Could that change just be to look for non zero values?

 

our minimum SOC is 12%

8 minutes ago, Benseb said:

Could that change just be to look for non zero values?

 

our minimum SOC is 12%

Will drop it down to 10% 

This 0 nonsense is also the cause for the oddities in the energy graphs. I could also be due to a restart of HA. There are a few changes included to see if it will help with that. Time will tell

 

Edited February 5, 20242 yr by Gary Waterworth

Hi All I've attached some screen shots from HA. My energy reporting is all over the show

On the 2nd it looked normal but on the other days I've got all sorts of erratic readings some showing solar production in the MW which would be cool if it was true. Sunsynk is showing all the correct data.

 

any ideas?