@slipx got round to doing a bit of a refresh on my card and found the following.

When using the card with a layout card configuration when selecting the card styles it will delete the view_layout section in the card.

Once you've done the selection you can just add it back in yaml and it works just fine.

Granted if you are setting cards up this way you should be used to working in yaml.  Not sure if there would be a way for the card to ignore the veiw_layout lines if you have it setup, tried moving it to the bottom but it still deletes it if you  change the view type.

Also is the prog1_charge supposed to be duplicated or was that meant to be for something else all 3 selection for prog1-6 are listed prog1_charge just seems to be duplicated.

 

Edited December 14, 20232 yr by -cK-

Yes I've also noticed that it removes the layout option. Not sure if there is a way to stop that.

Thanks for catching the mistake. That is meant to be prog5_charge. I'll push a fix 

I have added Energy Mode into the automation. Works fine.

Dont worry about the "Override". That is for my own automation streams 

input_boolean. sunsynk_energymode
 

Still working on the "charge" boolean switches. Having some wierd stuff setting on the sunsynk website

 

Edited December 14, 20232 yr by Gary Waterworth

Must admit it has simplified my own automation flows. All I do now is update the input field 

 

20 minutes ago, Gary Waterworth said:

I have added Energy Mode into the automation. Works fine.

Dont worry about the "Override". That is for my own automation streams 

input_boolean. sunsynk_energymode
 

Still working on the "charge" boolean switches. Having some wierd stuff setting on the sunsynk website

 

Could you tell me why when toggling energy mode I get exited: energyMode: exited - entity not managed on the flow? Time changes and soc changes are working flawless.

Updated the node red flow to the newest available.

Edited December 14, 20232 yr by Ronnie1102

1 minute ago, Ronnie1102 said:

Could you tell me why when toggling energy mode I get exited: energyMode: exited - entity not managed on the flow?

Updated the node red flow to the newest available.

Hmmm , When did you download. I pushed the version with energy mode during this morning to teh stable version 

That message means it is still "disabled" in the var setups 

Just now, Gary Waterworth said:

Hmmm , When did you download. I pushed the version with energy mode during this morning to teh stable version 

That message means it is still "disabled" in the var setups 

Just downloaded it now added the new yaml below and rebooted. I see JSON - Node Red - Export Flow - Option 1 - 1 Plant 1 or 2 Inverters.json has been updated as well but have not imported the updated one yet as it seems to be funky when I import, such as no name just flow  and makes me drag and place it down into node red.

sunsynk_energymode:
   initial: true

5 minutes ago, Ronnie1102 said:

Just downloaded it now added the new yaml below and rebooted. I see JSON - Node Red - Export Flow - Option 1 - 1 Plant 1 or 2 Inverters.json has been updated as well but have not imported the updated one yet as it seems to be funky when I import, such as no name just flow  and makes me drag and place it down into node red.

sunsynk_energymode:
   initial: true

That is just the initial mode

Just repull down the general flow . I have repushed it to make sure. I think I didnt push it after I included the energymode in the array for entities to watch far 

The flow with just the single function is the export to the usable entities. 

You will need to update that one as well as I added energymode and a few others on there 

Just booting up my test vm to import in there and make sure

Edited December 14, 20232 yr by Gary Waterworth

4 minutes ago, Gary Waterworth said:

That is just the initial mode

Just repull down the general flow . I have repushed it to make sure. I think I didnt push it after I included the energymode in the array for entities to watch far 

The flow with just the single function is the export to the usable entities. 

You will need to update that one as well as I added energymode and a few others on there 

Just booting up my test vm to import in there and make sure

Thanks just imported the new flows required json, waiting on your feedback regarding the funky behaviour of the single function when importing then will import that as well.

4 minutes ago, Ronnie1102 said:

Thanks just imported the new flows required json, waiting on your feedback regarding the funky behaviour of the single function when importing then will import that as well.

Fixed it : JSON - Node Red - Export Flow - Option 1 - 1 Plant 1 or 2 Inverters.json

I think when I exported it I only exported one node , not the flow 

 

 

 

FYI : Sunsynk is importing the historical data atm. Had a nice "problem" I had to fix in my energy sensors this morning 

 

Thanks @Gary Waterworth importing and rebooting then will test.

 

8 minutes ago, Gary Waterworth said:

FYI : Sunsynk is importing the historical data atm. Had a nice "problem" I had to fix in my energy sensors this morning 

 

I see my total energy sensors are also funky and abnormally high, yesterday my solar was showing 1600kWh and today I see the total grid, total return to grid and the total battery charge and discharge is showing some super high numbers.

12 minutes ago, Ronnie1102 said:

Thanks @Gary Waterworth importing and rebooting then will test.

 

I see my total energy sensors are also funky and abnormally high, yesterday my solar was showing 1600kWh and today I see the total grid, total return to grid and the total battery charge and discharge is showing some super high numbers.

You need to fix this through developer. Look on your energy screen to get an approximate time then in developer -> statistics

This is only a problem for the long term stats recorder. The short term stuff falls away after 7 days or so 

Click on the icon on teh right

Go forward and back 30 minutes at a time and find teh large value and then 0 it out

 

Edited December 14, 20232 yr by Gary Waterworth

4 minutes ago, Gary Waterworth said:

You need to fix this through developer. Look on your energy screen to get an approximate time then in developer -> statistics

This is only a problem for the long term stats recorder. The short term stuff falls away after 7 days or so 

Click on the icon on teh right

Go forward and back 30 minutes at a time and find teh large value and then 0 it out

 

Ahhh thanks will look through and sort that out, all working now by the way appreciate your work!

On 2023/12/13 at 12:29 PM, Gary Waterworth said:

I see you use teh battershutdowncap. Will add that one to the invertor entity

Edded a it and a few extra

Just wanted to check was the battershutdowncap added in the last update you pushed as well.  Think that was the only thing I saw I used on the old setting attr that wasn't there the rest should be a relatively easy switch as soon as I get time to do it.  Hopefully this weekend or the next.  Excited to start playing with V2 now 😅

2 minutes ago, -cK- said:

Just wanted to check was the battershutdowncap added in the last update you pushed as well.  Think that was the only thing I saw I used on the old setting attr that wasn't there the rest should be a relatively easy switch as soon as I get time to do it.  Hopefully this weekend or the next.  Excited to start playing with V2 now 😅

Yup

@Gary Waterworth Sorry but I need some assistance having a blond moment or am just blind as a bat.

##### sn_data:          Inverter SN to use for single data values
#####                   Do a run through then in node red look at global context data under 
#####                   SS_Consolidat -> Config Data -> Inverter Plant
#####                   [Inverter SN]:[Plantid]
##### sn_flow:          Plant ID to use for flow data
#####                   Do a run through then in node red look at global context data under 
#####                   SS_Consolidat -> Config Data -> Inverter Plant
#####                   [Inverter SN]:[Plantid]

Where to I get the global context data in node-red to get this info.  I tried my serial number on the inverter but then I get some sensor pulling data and some still as unavailable breaking some of my cards.

Or can I look this up on the v1.1 section and just input it and hit go.

if so lets say the id is 1234 and sn is 5678

which is which or do you mean both should be set as 5678:1234

[Inverter SN]:[Plantid] this is confusing me as well probably because I'm not seeing it where I should 🤷‍♂️

Node-red noobnish showing here 👀

[edit] See now you clearly say which is which and I think these are custom sensor I had setup that needs remapping, let me check that out gonna try those 2 ID's and see if things work.

Thanks

[edit] Found the problem, proper case...

Some needed remapping and some had Capital letters that is now lower case.  Think I've got most sorted and the other sensor showing as unavailble might be because I didn't delete the old flow just disabled it to easily revert to v1.1 if needed.

Will have a look throught everything again before loading the changable card, my one markdown card is still broken but think that is also just a remapping all the reference sensors needed for it will have a look at that tomorrow.

 

Edited December 14, 20232 yr by -cK-

Are the input helpers supposed to be read only?  When I tried to test the card to switch priotity load to priority batt it would show the toggle was turned off but after a minute or so it would flip back on same with the soc % I set it and then a minute or so later it resets to what it was so the inverter seems to still override it.  Am I I missing a step or where can I look or debug what the issue might be?

 

Edited December 14, 20232 yr by -cK-

3 hours ago, -cK- said:

Are the input helpers supposed to be read only?  When I tried to test the card to switch priotity load to priority batt it would show the toggle was turned off but after a minute or so it would flip back on same with the soc % I set it and then a minute or so later it resets to what it was so the inverter seems to still override it.  Am I I missing a step or where can I look or debug what the issue might be?

 

  enable_sunsynk_auto_mode:
   initial: false 

The Initial is set to false ( deliberately ) to stop people just having auto updates without checking their configs 

Put a switch on your dashboard somewhere and toggle it on 

So when it is disabled , after a minute and a bit ( There is a forced delay once an update is done to allow teh inverter to get in sync before the next data fetch ) the switches will return to settings actually on the inverter.

 

Global Context 

You may need to open teh debug view then pulldown top right , select context data , hit refresh button 

SS :- General Work Area 

SS_Consolid :- All Data actually pulled from account 

SS_EXport_Data :- Processed Data that will be populated to the sunsynk_usable.* entities 

This is the single function that is on it's own on that extra flow page. 

Designed that way so it can be swopped in and out for different plant inverter setups.

Needs a lot of documentation so people can see how to edit it for their own needs

 

Because we are exploring all plants and inverters in an account , we cant just export everything to a single entity. I tried it and HA was not happy with a sensor of over 16k bytes

 

Edited December 15, 20232 yr by Gary Waterworth

Thanks @Gary Waterworth got the correct plant ID now, freaking blind as a bat.

So do I need to set this to enabled then?  Flipping the sunsynk_auto_mode helper does nothing to the flow itself so I'm guessing that is just the indicator it use to trigger the 0 minutes to push the HA values through instead of pulling the data when it is set to enabled.

 

Edited December 15, 20232 yr by -cK-

11 minutes ago, -cK- said:

Thanks @Gary Waterworth got the correct plant ID now, freaking blind as a bat.

So do I need to set this to enabled then?  Flipping the sunsynk_auto_mode helper does nothing to the flow itself so I'm guessing that is just the indicator it use to trigger the 0 minutes to push the HA values through instead of pulling the data when it is set to enabled.

 

The input_boolean Sunsynj auto mode needs to be enabled.

That flow node should already be enabled

It will only show when a messages reaches it. So enable and then try change something

Edited December 15, 20232 yr by Gary Waterworth

Awesome got it working 👍 not sure what the problem was but it's working now 😅

So if all is working properly I can just as well set this to true otherwise if HA restarts it will go to Off again.

Best practice I guess would be to just flip that to false each time the V2 flows gets updated in node-red during development to first test it then flip it back to default true once I've tested it and happy it works etc.

Edited December 15, 20232 yr by -cK-

3 minutes ago, -cK- said:

Awesome got it working 👍 not sure what the problem was but it's working now 😅

So if all is working properly I can just as well set this to true otherwise if HA restarts it will go to Off again.

Best practice I guess would be to just flip that to false each time the V2 flows gets updated in node-red during development to first test it then flip it back to default true once I've tested it and happy it works etc.

Yes it will go off again, my HA does not reboot often by itself but I have a automation that reboots every morning at 06:45 and then I have a automation that enables the auto mode at 07:55 so my load shedding automations can still trigger battery caps at certain times.

50 minutes ago, -cK- said:

 

So if all is working properly I can just as well set this to true otherwise if HA restarts it will go to Off again.

Just check the default SOC values

The initial are what my system is configured as 

I deliberately set it to disabled to stop the complaining brigade. 

"I loaded your flows and my settings weer broken" 

At least this way you have to deliberately go turn it on 

Mine is set to initial true and I have no problems.

My HA runs in a VM on a Intel NUC device. So lots of capacity and I dont need reboots. I have another asus mini pc I am looking to migrate so so I have access to usb ports. Want to look at active pylontech battery monitoring 

Edited December 15, 20232 yr by Gary Waterworth