cp2023

i copied the fix from solarsynkv3 and applied it to my fork (https://github.com/cpether/Home-Assistant---E-Linter-Logger---Sunsynk), so this should be working again if anyone wants it.

i copied the fix from solarsynkv3 and applied it to my fork (https://github.com/cpether/Home-Assistant---E-Linter-Logger---Sunsynk), so this should be working again if anyone wants it.

Here's a fork of Gary's repo with the new authentication flow included. It's working for me, but let me know if anyone sees any issues.
GitHub
GitHub - cpether/Home-Assistant---E-Linter-Logger---Sunsynk
Contribute to cpether/Home-Assistant---E-Linter-Logger---Sunsynk development by creating an account on GitHub.

i was getting warnings when using that field that node-RED had deprecated it, that why i changed it to "use". Just hadn't updated the request correctly to use POST. I've committed a fix now.

Have added it into teh configuration.yaml file. Will get published when I do a main publish after some changes I am busy on 
I dont export, so was overlooked
Thanks

no other way I know of. I removed all config out of the flows to make it easier 

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