Oddly enough I'm getting a timeout request error on my phone's sunsynk app as well though I can log in on the website and access stuff.

So yea sunsynk doing sunsynk stuff again 🙄

55 minutes ago, -cK- said:

Oddly enough I'm getting a timeout request error on my phone's sunsynk app as well though I can log in on the website and access stuff.

So yea sunsynk doing sunsynk stuff again 🙄

To fix the issue, I checked the SSL/TLS option on all HTTP requests.

Add a new config if one doesn't exist, and uncheck 'Verify server certificate' and Update.

Redeploy the node and that should fix the issue.

https://stackoverflow.com/questions/42983635/error-unable-to-verify-the-first-certificate-in-node-red

Edited March 13, 20242 yr by huzii7

Hello @Gary Waterworth,

I am trying to understand the following error.

13/03/2024, 15:59:42node: Export Data Export To Entity
function : (error)
"Logger In Warning Mode, continuing"

How can I diagnose this? I am not sure if it because I am missing a entity in the templates or something else I have done wrong. This is on both sites I have assisted with.

2 hours ago, WazzaCPT said:

Hello @Gary Waterworth,

I am trying to understand the following error.

13/03/2024, 15:59:42node: Export Data Export To Entity
function : (error)
"Logger In Warning Mode, continuing"

How can I diagnose this? I am not sure if it because I am missing a entity in the templates or something else I have done wrong. This is on both sites I have assisted with.

Ignore it. An artifact of teh sunsynk move to the uk. It is ignoring that check atm

Logger state is 1 instead of 0. Leaving it alone for now untill they fix it or I will regard 1 as good 😕

Edited March 13, 20242 yr by Gary Waterworth

2 hours ago, huzii7 said:

To fix the issue, I checked the SSL/TLS option on all HTTP requests.

Add a new config if one doesn't exist, and uncheck 'Verify server certificate' and Update.

Redeploy the node and that should fix the issue.

https://stackoverflow.com/questions/42983635/error-unable-to-verify-the-first-certificate-in-node-red

No need . They fixed their f.... up

So, been observing some strange behaviour before and after midnight the last few days. Anyone else seeing strange data?

1 hour ago, WazzaCPT said:

So, been observing some strange behaviour before and after midnight the last few days. Anyone else seeing strange data?

define strange 

 

Receiving solar energy data between 11pm and 1am and relatively large amounts. Also getting random grid sell amount during those times as well.

 

I have included the filtering but am not sure if I should be filtering on the daily totals.

Edited March 25, 20242 yr by WazzaCPT

Daily totals will be a problem as they reset. Reason I don't use them in graphs or put filtering on them

2 minutes ago, Gary Waterworth said:

Daily totals will be a problem as they reset. Reason I don't use them in graphs or put filtering on them

Do you then use the total total data in you energy dash board?

1 hour ago, WazzaCPT said:

Do you then use the total total data in you energy dash board?

yes 

15 hours ago, Gary Waterworth said:

yes 

Hello Gary,

What is strange is that this is only happening at one of the two sites I have setup. So not sure if there is some issue with that site or the added complexity of a solar source other than Sunsynk.

I will look at using the totals for the energy dashboard instead.

Many thanks as always.

Hello Gary,

Have you looked into using availability within your template sensors instead of the filtering?

 

Availability for Template Sensors

Edited March 26, 20242 yr by WazzaCPT
Added a reference link

The problem is not whether there is a data value or not ( available/unavailable ) the problem is when a data value of 0 is returned by Sunsynk. That is why I use teh forever totals and not the today totals in the energy graphs. The today totals never seem to reset at the same time and if I use teh forever totals then it is easy as they can never be 0 and also teh energy graphs will "catch up" when there is an outage

 

There is probably a use case for it in some of teh other values, but will see when I have time. 

Edited March 26, 20242 yr by Gary Waterworth

2 hours ago, WazzaCPT said:

Hello Gary,

What is strange is that this is only happening at one of the two sites I have setup. So not sure if there is some issue with that site or the added complexity of a solar source other than Sunsynk.

I will look at using the totals for the energy dashboard instead.

Many thanks as always.

The error is a SSL cert that cannot be checked . This is their api website. 

You could change the https to http ( so there are no certs ) , but couldnt be bothered to be honest unless they really mess up on that front . Not sure if their api support plain http

Ive been getting the message “Unable to verify the first certificate” recently. 
 

any ideas what could be causing it? I notice the Sunsynk SSL cert renewed 2 weeks ago but can’t see any reason why that wouldn’t be recognised?

 

for now I’ve changed Node Red to skip verifying the SSL cert (not ideal)

Many thanks to Gary, slipx06 and all the other contributors to this topic of integrating the Sunsynk inverter into Home Assistant.

By following the instructions and by changing various nodes where errors have occurred, according to threads in this forum, I now have the values from my inverter coming through to Node-red that are visible in the Context Data tab and that match the values on my Sunsynk app. However, none of these values appear in Home Assistant sensors as they are all unavailable. I still have some issues to resolve and being very new to Home Assistant and Node-red I'm not sure how to proceed.

1. On Node: Run Through Plant Inv List, I get this error reported in the debug window

"Gateway is bad. Not configured for <= 60s cycle rate. Updates Disabled"

How do I overcome this? Is there a setting in a node or nodes that I can change to reduce the updates to say every five minutes just to get the updates going?

2. On Node: Update Sensor, all of the API calls appear to be unauthorised. I get this list of errors reported in the debug window.

hass-post: API call http://localhost:8123/api/states/sensor.sunsynk_errors, statusCode 401
hass-post: API call http://localhost:8123/api/states/sensor.sunsynk_usable_load, statusCode 401
hass-post: API call http://localhost:8123/api/states/sensor.sunsynk_usable_battery, statusCode 401
hass-post: API call http://localhost:8123/api/states/sensor.sunsynk_usable_output, statusCode 401
hass-post: API call http://localhost:8123/api/states/sensor.sunsynk_usable_gen, statusCode 401
hass-post: API call http://localhost:8123/api/states/sensor.sunsynk_usable_flow, statusCode 401
hass-post: API call http://localhost:8123/api/states/sensor.sunsynk_usable_grid, statusCode 401
hass-post: API call http://localhost:8123/api/states/sensor.sunsynk_usable_temp, statusCode 401

I'd be very grateful if someone could point me in the right direction with this please. If there are there any logs that would be useful to solve the problem please let me know.

2 hours ago, dpn said:

Many thanks to Gary, slipx06 and all the other contributors to this topic of integrating the Sunsynk inverter into Home Assistant.

By following the instructions and by changing various nodes where errors have occurred, according to threads in this forum, I now have the values from my inverter coming through to Node-red that are visible in the Context Data tab and that match the values on my Sunsynk app. However, none of these values appear in Home Assistant sensors as they are all unavailable. I still have some issues to resolve and being very new to Home Assistant and Node-red I'm not sure how to proceed.

1. On Node: Run Through Plant Inv List, I get this error reported in the debug window

"Gateway is bad. Not configured for <= 60s cycle rate. Updates Disabled"

How do I overcome this? Is there a setting in a node or nodes that I can change to reduce the updates to say every five minutes just to get the updates going?

2. On Node: Update Sensor, all of the API calls appear to be unauthorised. I get this list of errors reported in the debug window.

hass-post: API call http://localhost:8123/api/states/sensor.sunsynk_errors, statusCode 401
hass-post: API call http://localhost:8123/api/states/sensor.sunsynk_usable_load, statusCode 401
hass-post: API call http://localhost:8123/api/states/sensor.sunsynk_usable_battery, statusCode 401
hass-post: API call http://localhost:8123/api/states/sensor.sunsynk_usable_output, statusCode 401
hass-post: API call http://localhost:8123/api/states/sensor.sunsynk_usable_gen, statusCode 401
hass-post: API call http://localhost:8123/api/states/sensor.sunsynk_usable_flow, statusCode 401
hass-post: API call http://localhost:8123/api/states/sensor.sunsynk_usable_grid, statusCode 401
hass-post: API call http://localhost:8123/api/states/sensor.sunsynk_usable_temp, statusCode 401

I'd be very grateful if someone could point me in the right direction with this please. If there are there any logs that would be useful to solve the problem please let me know.

1. This is a problem where your gateway is set to 5 min updates. There is a problem with 5 min logger updates and that is why it is not allowed to do dynamic updates when the refresh is that long. Trying to force enable will generate race conditions and result in flip flopping. Rather ask your installer to help you request your logger to be changed to 60s updates

2. You need to put in a long life token into the hass-config node 

https://github.com/gdwaterworth/Home-Assistant---E-Linter-Logger---Sunsynk/wiki

The procedure to get long lived access tokens is documented in the HA documentation. 

 

Edited April 4, 20242 yr by Gary Waterworth

Hi Gary

Thanks for your quick response.

1. I asked my installer to change the logger to update every 60s and he's done it already!

2. I put a long life token into hass-config node two days ago.  I created a new one and replaced it a few minutes ago and now the data is coming through to Home Assistant!  I assume I must have changed something and lost the previous long life token.

Many thanks for your reply and with your help I now have a working Inverter dashboard.

Hi all - brand new to Home Assistant and want to get my Sunsynk connected, I've got an IT background though so am trying to work things through...

 

I believe I should be using the latest version of the connection 2.4, but the video relates to v1.1, I can see the files for this which means I could follow it, but doesn't feel right...

 

Anyone got a basic video walkthrough of how to install the latest version?

https://github.com/gdwaterworth/Home-Assistant---E-Linter-Logger---Sunsynk/wiki

Have a look at the wiki guide this should guide you through the setup process.  No video guide for 2.4 that I know of but if you've watched the v1 video the wiki guide should get you up and running.

 

FYI : On the cert issue. I have added a config option to "not check" the certs they provide. It is in the development stream for now. Will monitor and make sure I havent broken anything else for now. Also updated some request headers, but that wont "fix" certs

 

On 2024/04/08 at 11:18 AM, Gary Waterworth said:

FYI : On the cert issue. I have added a config option to "not check" the certs they provide. It is in the development stream for now. Will monitor and make sure I havent broken anything else for now. Also updated some request headers, but that wont "fix" certs

 

How is this going Gary?

It is in the devlopment branch and seems to be fine

Will look at merging it this weekend 

I have a 3 phase 12Kw sunsynk, just wondering what I need to use from Node-Red SunSynk Automation to be able to configure the Energy Dashboard (at the least Solar Panels and Home battery storage).