3 minutes ago, SteveRCT said:

@Gary WaterworthI managed to get it all working I had to comment api.sunsynk and change pvinteless to uncommented in the 1st node all seems to be working really well now I can see mostly everything.  just assessing now about the 2 inverters and if it is tracking.

Then you were using the region 2 flows, not region 1

4 minutes ago, Gary Waterworth said:

Then you were using the region 2 flows, not region 1

Then I really don't know, because I ended up deleting all my flows, recopied the tempate for region 1. Then downloaded the json from the link you sent above, imported the json. Copied in the longlife token and still didnt work. Then i clicked around hunting for something i could change and found a // in front of pv.inteless...and removed it...maybe I'm just not understanding how to delete a flow properly...

@Gary Waterworth thanks again for all the hard work on these integrations etc.  I'm having fun finally being able to visualise all this in home assistant! Now just to attempt to pull values from the 2nd inverter and we'll be golden. Also showing the 2nd inverter in flows but I'm celebrating the first big win of being able to grab the content!

13 minutes ago, SteveRCT said:

@Gary Waterworth thanks again for all the hard work on these integrations etc.  I'm having fun finally being able to visualise all this in home assistant! Now just to attempt to pull values from the 2nd inverter and we'll be golden. Also showing the 2nd inverter in flows but I'm celebrating the first big win of being able to grab the content!

Do you not eat to use aggregate values for the visualisation? Then you can use individual values on a more detailed dashboard

6 minutes ago, mzezman said:

Do you not eat to use aggregate values for the visualisation? Then you can use individual values on a more detailed dashboard

IN principle yes, but the calculation fields to use agregates for both are not done yet. I only have a single invertor setup, so have no idea how the api passes the 2nd invertor value back . In principle the correct values should be extracted in the sensor attributes so they can be used

 

Edited April 25, 20233 yr by Gary Waterworth

OK, makes sense 

@randomfool Quick question I see the monthly Production has started populating and is summing the daily values into the month.

My question is more about the bar width.  From what I can figure it is supposed to give you your last 6 months at a glance per month.  But is would seem it is condencing the sum totals on the first day of the month and not spanned over the complete month so the 6 month will have very thin bars spaced out really far or am I missing something perhaps 🤷‍♂️  It started populating on the 1st for me so after 3 days it is still just showing on the first with these thin bars so not sure if I'm jumping the gun again 😁

Was this the intend view or is this something that will need to be tweeked.  I've tried to firgure out and to tried to widen the bars with no luck so far.

Default

If I double click on it, it seams to jump to a single month I've clicked on where you can see it looks to be x axis is listing all the days of the month and the sum is happening on the 1st day.

Thanks

Sorry if this was asked/answered already.

Can anyone confirm if this will also work with Deye inverters? If so, what is the extent of the code change?

I need to decide if im going to go with Deye or Sunsynk for my 3phase setup.

Thanks so much

It's not been asked yet @Jack007 and I think it will depend on the dongle you get with the Deye.  If it is the E-linter dongle it might but don't quote me on that, @Gary Waterworth wrote the nodes so think best would be for him to confirm or give insights on this.

2 hours ago, Jack007 said:

Sorry if this was asked/answered already.

Can anyone confirm if this will also work with Deye inverters? If so, what is the extent of the code change?

I need to decide if im going to go with Deye or Sunsynk for my 3phase setup.

Thanks so much

Deye uses the Solarman logger and this integration wont work with that logger. You will need to use another integration into HA

17 hours ago, -cK- said:

@randomfool Quick question I see the monthly Production has started populating and is summing the daily values into the month.

My question is more about the bar width.  From what I can figure it is supposed to give you your last 6 months at a glance per month.  But is would seem it is condencing the sum totals on the first day of the month and not spanned over the complete month so the 6 month will have very thin bars spaced out really far or am I missing something perhaps 🤷‍♂️  It started populating on the 1st for me so after 3 days it is still just showing on the first with these thin bars so not sure if I'm jumping the gun again 😁

Was this the intend view or is this something that will need to be tweeked.  I've tried to firgure out and to tried to widen the bars with no luck so far.

Default

If I double click on it, it seams to jump to a single month I've clicked on where you can see it looks to be x axis is listing all the days of the month and the sum is happening on the 1st day.

Thanks

I think plotly does not have enough data yet so it doesn't know how wide to make the bars.  You can try adjust the width and offset by adding the following to each data set. I suspect that you will need to remove once you have a months data.  Play around with the values to adjust the width. Also you cant use the same offset for every entity as they will draw on top of each other

 

entities:
  - entity: sensor.daily_pv_power_kwh
    statistic: state
    name: |
      $fn ({ ys,meta }) =>
        "Solar" + "🔆" + "(" +ys[ys.length - 1]+"kWh)"
    period: day
    type: bar
    texttemplate: '%{y}'
    filters:
      - filter: i>0
    marker:
      color: rgb(255, 155, 48)
    width: $fn() => 1000*60*60*3
    offset: $fn() => 1000*60*60*3.5

 

9 minutes ago, mzezman said:

Deye uses the Solarman logger and this integration wont work with that logger. You will need to use another integration into HA

Thank you, so it can/has been done/implemented on the Deye side with different software or has nobody done this yet with a deye?

@Jack007 I think solarman loggers use this one https://github.com/StephanJoubert/home_assistant_solarman

@slipx I think I might be jumping the gun again and the bars will widen as the data set increases, I think the 3 day data was still to little to see a notable difference but it looks like it but will confirm once I'm home tonight that it's not just an optical illusion being on a different monitor at work 😅

2 hours ago, -cK- said:

It's not been asked yet @Jack007 and I think it will depend on the dongle you get with the Deye.  If it is the E-linter dongle it might but don't quote me on that, @Gary Waterworth wrote the nodes so think best would be for him to confirm or give insights on this.

It needs to be the e-linter dongle. I cannot comment on what is shipped with Deye's . From what I have read, the elinter dongle should work on deye's

Edited May 4, 20233 yr by Gary Waterworth

8 hours ago, slipx said:

I think plotly does not have enough data yet so it doesn't know how wide to make the bars. 

 

Looks like you are right again, not enough data yet. Looks a little thicker today vs yesterday so should fill up the month once a full month have passed 👍

Think I must be completely lost.

 

Imported the flows, updated config.yaml and getting the following error on nodered. any ideas?

6 hours ago, francoisj1 said:

Think I must be completely lost.

 

Imported the flows, updated config.yaml and getting the following error on nodered. any ideas?

You need to add the palatte to Node Red

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

"node-red-contrib-hass"

and then configure it

14 hours ago, francoisj1 said:

Think I must be completely lost.

 

Imported the flows, updated config.yaml and getting the following error on nodered. any ideas?

I have installed vir nodered pallette - now completes the flow. R00kie error

On 2023/03/11 at 7:30 PM, Craig1970 said:

Hi @Gary Waterworth, so excited to find your solution. I am relatively new to HA, but loving it and especially the collaboration. I too am ultimately wanting to edit Sunsynk settings if SOC is low and load-shedding is coming soon. Again, thank-you for your work to date.

I have followed the steps best I can, and the entities are appearing, but sensors show "unavailable".

When looking at Developer Tools, States most of the sensor.sunsynk....... are unavailable, except the plant list, which returns correct info. The sensor.sunsynk_flow is returning data in the attributes. Is this to be expected, and one must create new sensors using templates? Possibly the issue described below is stopping data-flow. 

On the Node-Red Debug notes the script seems to generally be running, but getting stuck on Inverter Serial Number.

 

also stuck on the plant list and amount of inverters it is displaying. i have two inverters and the code only reveals one inverter that is top of the list in the page. although changing the inverter index for 2nd inverter, i feel that this might not be the right parameter for individually setup inverters for home and flat independently, rather for parallel configs?

 

code reflects:

 

##### Put in your Plant Index for your Plant. 0 should work 
  - sensor: 
      - name: "Sunsynk plant index"
        state: "0"
        unique_id: "sensor.sunsynk_plant_index"
##### Put in your Invertor Index for your 1st Invertor. 0 should work 
  - sensor: 
      - name: "Sunsynk Invertor 1 index"
        state: "0"
        unique_id: "sensor.sunsynk_invertor_1_index"
##### Put in your Invertor Index for your 2nd Invertor. Only Change if you have 2 Invertors. default value is DONOTEDIT
  - sensor: 
      - name: "Sunsynk Invertor 2 index"
        state: "DONOTEDIT"
        unique_id: "sensor.sunsynk_invertor_2_index"

 

 

On 2023/04/25 at 8:28 PM, SteveRCT said:

@Gary Waterworth thanks again for all the hard work on these integrations etc.  I'm having fun finally being able to visualise all this in home assistant! Now just to attempt to pull values from the 2nd inverter and we'll be golden. Also showing the 2nd inverter in flows but I'm celebrating the first big win of being able to grab the content!

if you manage to get the 2nd inverter from same plant, lets compare notes. I get errors and dont know if it due to independent setups of one inverter in home and another in cottage that is not linked on comms port?

 

Sorry to disappoint,  but i took a very ghetto approach to the 2nd inverter because i have 2 in parallel i just doubled all the sensor readings, completely wrong way to do it but i don't know how to code... I'm only about 5w off from the true readings though

I need to do some work on the 2nd invertor. I will work on the wiki today/tomorrow to add a section to select seperate plants and setup the variable so it gets data for a 2nd invertor.

 

There may be some back and forth as I use a single 8kw Sunsynk and may request you to send me some sensor data.

10 hours ago, francoisj1 said:

if you manage to get the 2nd inverter from same plant, lets compare notes. I get errors and dont know if it due to independent setups of one inverter in home and another in cottage that is not linked on comms port?

 

Plant And Invertor Index Numbers · gdwaterworth/Home-Assistant---E-Linter-Logger---Sunsynk Wiki (github.com)

Oooh exciting!! Thanks! Going to try this right away! Thanks Gary!

Excellent, after applying the inverter index I'm able to see the 2nd inverter's input and output in developer tools. I think now just adding the 2 together is the next step. Seeing the configuration file the Sunsynk PV uses 'sensor.sunsynk_input' rather than sensor.sunsynk_input+sensor.sunsynk_input2'