49 minutes ago, Gary Waterworth said:

Please send the information asked for a few posts back for a similar problem

 

@Gary Waterworth, sent via DM.

Edited January 13, 20242 yr by HowserMD

Updated version of the Octopus Agile tariff automation working with @Gary Waterworth new version 2.

Made an adjustment to set sstimer1 to nearest 30 minute segment in the past to avoid throwing node warnings and align with the new version 2; sstimer2 is set to 23:30 at all times unless sstimer1 is also 23:30 in which case it changes sstimer2 to 00:00 to avoid issues, the trade off is it will not control the inverter for the last 30 minutes of the day.

For my own personal version I have modified Gary's script slightly so that it accepts 23:55 as an input. If you care enough about controlling the inverter automatically for the last 25 of the 30 minute window between 23:30 and 00:00 you could copy this logic also to avoid any node warnings.

Sunsynk Automation V4.json

Edited January 13, 20242 yr by randomfool

4 hours ago, HowserMD said:

@Gary Waterworth, sent via DM.

Need the rest of the info

But send Screenshots of all the sunsynk_usable_* entities so we can see what is populated ad a sscreenshot of teh flows so we can see what has been successfully completed

Edited January 13, 20242 yr by Gary Waterworth

4 hours ago, randomfool said:

Updated version of the Octopus Agile tariff automation working with @Gary Waterworth new version 2.

Made an adjustment to set sstimer1 to nearest 30 minute segment in the past to avoid throwing node warnings and align with the new version 2; sstimer2 is set to 23:30 at all times unless sstimer1 is also 23:30 in which case it changes sstimer2 to 00:00 to avoid issues, the trade off is it will not control the inverter for the last 30 minutes of the day.

For my own personal version I have modified Gary's script slightly so that it accepts 23:55 as an input. If you care enough about controlling the inverter automatically for the last 25 of the 30 minute window between 23:30 and 00:00 you could copy this logic also to avoid any node warnings.

Sunsynk Automation V4.json 11.82 kB · 1 download

Move away from doing direct web calls.

Rather update these entities and let teh flows manage teh web calls as there is a lot of error checking and failsafes built in.

You will also avoid some possible race conditions

This is what my flows looks like for automation

The update portion of code :

var newmsg = {};

newmsg.payload = {};

newmsg.payload.target = {};

newmsg.payload.data = {};

newmsg.payload.target.entity_id = global.get("SS.mapping.inverter.cap2.entityid");

newmsg.payload.data["value"] = msg.payload;

newmsg.payload["service"] = "set_value";

newmsg.payload["domain"] = "input_text";

return newmsg;

 

Edited January 13, 20242 yr by Gary Waterworth

8 minutes ago, Gary Waterworth said:

Need the rest of the info

But send Screenshots of all the sunsynk_usable_* entities so we can see what is populated ad a sscreenshot of teh flows so we can see what has been successfully completed

Here are the screenshots

 

14 minutes ago, HowserMD said:

Here are the screenshots

 

 

 

Look slike your secrets file is not being read properly

Check it again for space before and after the sn and plant id

Then reboot the home assistant device , not just a home assistant restart

This will reset the global context data which survives a HA restart

Also send me a screenshot of teh flows so I can see if everything has run correctly

Edited January 13, 20242 yr by Gary Waterworth

9 minutes ago, Gary Waterworth said:

Look slike your secrets file is not being read properly

Check it again for space before and after the sn and plant id

Then reboot the home assistant device , not just a home assistant restart

 

Also send me a screenshot of teh flows so I can see if everything has run correctly

I checked the secrets (attached below). Could not find any spaces after. Rebooted the home assistant in any case.

 

11 minutes ago, HowserMD said:

I checked the secrets (attached below). Could not find any spaces after. Rebooted the home assistant in any case.

 

And teh rest of teh info requested ?

Cant help if I cant see what is going on.

Also check this entity

 

Edited January 13, 20242 yr by Gary Waterworth

20 minutes ago, Gary Waterworth said:

Look slike your secrets file is not being read properly

Check it again for space before and after the sn and plant id

Then reboot the home assistant device , not just a home assistant restart

This will reset the global context data which survives a HA restart

Also send me a screenshot of teh flows so I can see if everything has run correctly

Rebooted home assistant.

Here is the screenshot of the flows

2 minutes ago, HowserMD said:

Rebooted home assistant.

Here is the screenshot of the flows

That looks correct for teh flows that matter for gathering. Can you also show me that single flow that is on its own tab

5 minutes ago, Gary Waterworth said:

And teh rest of teh info requested ?

Also check this entity

 

@Gary Waterworth, here is the requested entity

2 minutes ago, Gary Waterworth said:

That looks correct for teh flows that matter for gathering. Can you also show me that single flow that is on its own tab

1 minute ago, HowserMD said:

Expected that . ok no errors on there

Now screenshot context data so we can see what sunsynk has sent :

 

5 minutes ago, Gary Waterworth said:

Expected that . ok no errors on there

Now screenshot context data so we can see what sunsynk has sent :

 

@Gary Waterworth, context data as requested.

7 minutes ago, HowserMD said:

@Gary Waterworth, context data as requested.

 

 

Turn off all the debug nodes that you have turned on . This is looking definately like a plant id/sn issue

The source data is fine. The exporting to usable sensors isnt and it looks like all values where a "sn" is used

Where teh "tab" is extended

Then clear debug mesages

Wait for a gather run and send me the debug messages list

There is not a lot of error checking in that export node yet, so may have to add some

 

 

Edited January 13, 20242 yr by Gary Waterworth

What version node red are you on and what hardware platform ?

Edited January 13, 20242 yr by Gary Waterworth

Just an observation from my end but are you sure your serial numbers are the correct way around?

my sn_flow is a 6 digit number

my sn_data is a 10 digit number

It kinda looks reversed on your screenshot @HowserMD

Edited January 13, 20242 yr by -cK-

10 minutes ago, Gary Waterworth said:

What version node red are you on and what hardware platform ?

13 minutes ago, -cK- said:

Just an observation from my end but are you sure your serial numbers are the correct way around?

my sn_flow is a 6 digit number

my sn_data is a 10 digit number

It kinda looks reversed on your screenshot @HowserMD

You are right, will swap them around and restart.

1 hour ago, HowserMD said:

You are right, will swap them around and restart.

Did that and most of the issues are resolved. Not sure about Enable SunSynk Auto Mode.

 

Question, does this work both ways, that is updates from home assistant to sunsynk and visa versa or is it only display only from home assistant?

 

4 hours ago, Gary Waterworth said:

Move away from doing direct web calls.

Rather update these entities and let teh flows manage teh web calls as there is a lot of error checking and failsafes built in.

You will also avoid some possible race conditions

This is what my flows looks like for automation

The update portion of code :

var newmsg = {};

newmsg.payload = {};

newmsg.payload.target = {};

newmsg.payload.data = {};

newmsg.payload.target.entity_id = global.get("SS.mapping.inverter.cap2.entityid");

newmsg.payload.data["value"] = msg.payload;

newmsg.payload["service"] = "set_value";

newmsg.payload["domain"] = "input_text";

return newmsg;

 

Superb advice thank you will look into this tomorrow.

3 hours ago, -cK- said:

Just an observation from my end but are you sure your serial numbers are the correct way around?

my sn_flow is a 6 digit number

my sn_data is a 10 digit number

It kinda looks reversed on your screenshot @HowserMD

Will check teh code tomorrow and make sure 

 

1 hour ago, HowserMD said:

Did that and most of the issues are resolved. Not sure about Enable SunSynk Auto Mode.

 

Question, does this work both ways, that is updates from home assistant to sunsynk and visa versa or is it only display only from home assistant?

 

Enable Sunsynk Auto Mode is a Boolean entity that when set true will set settings in the inverter.

Be carefull and go check the initial value I set in the configuration.yaml

If you enable this IT WILL go set your inverter.

With it enabled then that dashboard will update Sunsynk with any changes you make. 

 

In my automation dashboard I have a boolean switch I enable to allow updates to Sunsynk 

Edited January 13, 20242 yr by Gary Waterworth

10 hours ago, Benseb said:

Hi all

 

yhis looks great. Been looking for an automation that doesn’t rely upon direct cabling into the inverter

 

my main use case is to automate force charging when we get a cheap period on our so toous Intelligent tarrif outside of the normal hours. 
 

Before I start integrating can I check…

 

1. This will allow me to force charge (maybe my toggling the “Use timers” setting?

 

2. Presume it’s best to use v2?

 

I have a 10kW 3 phase Sunsynk inverter 

Yes to both q . I will be archiving v1

Added error checking that plant and invertor sn's configured are in discovered plant and inverter lists for gathering and setting of values.

Will debate on the merits of auto configuring, but it may have some downsides.