December 15, 20232 yr 15 minutes ago, Gary Waterworth said: 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 Shot thanks, yea caught those initial SOC in the config after a while but luckily before I got this to work so set them to my defaults 👍 Just one more thing as I'm not sure if it is mentioned in your notes and I just missed it but might need to point out the custom card used for the below needs to be installed as well custom:multiple-entity-row 😉 Edited December 15, 20232 yr by -cK-
December 15, 20232 yr Author 22 minutes ago, -cK- said: Shot thanks, yea caught those initial SOC in the config after a while but luckily before I got this to work so set them to my defaults 👍 Just one more thing as I'm not sure if it is mentioned in your notes and I just missed it but might need to point out the custom card used for the below needs to be installed as well custom:multiple-entity-row 😉 Thanks , forgot about that one. My HA is very customised, so hard to track what is absolutely needed by a new user. The Charge settings are not in automation yet. Had a few issues so just need to spend some time and figure them out Edited December 15, 20232 yr by Gary Waterworth
December 15, 20232 yr No Probs Yea I have no individual charge slots active for myself but can see the benefit of getting those to work as well. As long as I can set the priority load/batt and usetimer on/off I can start writing a few automation's that should help automate things on bad weather days so that I don't have to touch a thing myself or micro manage it anymore 🤞
December 15, 20232 yr Hi Gary / Others, I've been struggling to get things working on my Pi 4. Before I totally give up, in desperation to get things working I thought I would reach out I had my Pi working to a degree, pulling dat from my sunsynk using V1.0, but could never get it to show the actual figures on the powerflow card, perhaps a mapping issue. Recently I have re-installed Hassio and started from scratch, but I'm now having an issue when importing the flow using V2 where im getting this error What would really help me and I'm sure others is a simple guide, perhaps using one of the spare "blank" posts at the beginning of this thread or a guide like https://kellerza.github.io/sunsynk/ ? Perhaps this is something that could be built by a shared select few for everyone to benefit from, I for one would be happy to contribute if this was available to simplify things - idiots guide so to speak I.e. How to install on a Pi from scratch The basics 1.) Flash SSD with Hassio Pi image using Raspberry Pi Imager 2.) Install File Editor - Any specific instructions 3.) Install Advanced SSH & Web Terminal - Any specific instructions 4.) Install Node Red - Enter any "credential secret" in the configuration page and turn off SSL 4.)a - Start Node Red, Launch Web GUI, Import flows from "here", etc 5.) Import xyx files using the file editor into yaml / secrets files etc 6.) Enter specific user information i.e. synsynk username, SN into xyz files Methods Pulling from Sunsynk Web (Default) easier for majroity of users MQTT with RS485 cable etc MQTT with ESP32 Dashboards 7.) How to setup a really cool dashboard Install xyz additional packages Create dashboard, add card, import code from a here add additional cards from here... Automations Install x Drop x code into y files This is ultimately where everyone is trying to go, to help with the DSF, how to export and import easily with a single click or using automations
December 15, 20232 yr Author 47 minutes ago, chessmaster said: Hi Gary / Others, I've been struggling to get things working on my Pi 4. Before I totally give up, in desperation to get things working I thought I would reach out I had my Pi working to a degree, pulling dat from my sunsynk using V1.0, but could never get it to show the actual figures on the powerflow card, perhaps a mapping issue. Recently I have re-installed Hassio and started from scratch, but I'm now having an issue when importing the flow using V2 where im getting this error What would really help me and I'm sure others is a simple guide, perhaps using one of the spare "blank" posts at the beginning of this thread or a guide like https://kellerza.github.io/sunsynk/ ? Perhaps this is something that could be built by a shared select few for everyone to benefit from, I for one would be happy to contribute if this was available to simplify things - idiots guide so to speak I.e. How to install on a Pi from scratch The basics 1.) Flash SSD with Hassio Pi image using Raspberry Pi Imager 2.) Install File Editor - Any specific instructions 3.) Install Advanced SSH & Web Terminal - Any specific instructions 4.) Install Node Red - Enter any "credential secret" in the configuration page and turn off SSL 4.)a - Start Node Red, Launch Web GUI, Import flows from "here", etc 5.) Import xyx files using the file editor into yaml / secrets files etc 6.) Enter specific user information i.e. synsynk username, SN into xyz files Methods Pulling from Sunsynk Web (Default) easier for majroity of users MQTT with RS485 cable etc MQTT with ESP32 Dashboards 7.) How to setup a really cool dashboard Install xyz additional packages Create dashboard, add card, import code from a here add additional cards from here... Automations Install x Drop x code into y files This is ultimately where everyone is trying to go, to help with the DSF, how to export and import easily with a single click or using automations I dont like putting documentation in one forum where not all users come from. Anyone can branch the code and develop and then ask for a merge. My time is available on a free time basis as and when I have it. I have a fairly demanding job, so cannot allways be available and a lot of what has been done here has been through a lot of reverse engineering. There is VERY little official documentation and that what there is is years out of date and incomplete. As far a Pi4 goes I cant help with teh basic config. I own a few Pi3's but they are in a box gathering dust. I moved to mini pc's a long time ago. Tiny bit more money, but far more usable. For the base install of any of the options there are far better guides available on the internet. Back to your problem:= You have'nt followed all the steps here. You are missing the extra palette in node red https://github.com/gdwaterworth/Home-Assistant---E-Linter-Logger---Sunsynk/wiki V2 is very new and I still need to put up more detailed information V1 had a very specific use case ( ie was designed around my installation at home ) , so without more examples and data extracts I cannot comment further. It was not designed for multi invertor plants. The data was all there, but you had to setup the sensors manually. V2 was a full rewrite to try cater for the shortfall and limitations in V1 , it was designed as the base that could be built on, but atm is still specific, so depending on your plant/invertor setup there may be some work to do. I dont have a lab and I refuse to change my implementation at home , so the only way I can cater for other setups is for someone to give me access to their system so I can see how teh data extract and plant looks or for them to get more knowlegable in node red. One kind gent did that and that is now the reason that we can populate the generator data. One missing bit of information gathering is still the mini invertor data which is still a big (?). What I dont have time for is someone who says, ok you can look at my system but you only have 4 days ( and yes that has happened ). I was actually on a business trip in Germany, so I just shrugged my shoulders. Edited December 15, 20232 yr by Gary Waterworth
December 15, 20232 yr Thanks Gary, appreciate everyone has their day job too Didn't notice the wiki before, that is useful! Doh! 🤪 I've now followed those steps and added the flows into node red, also wasnt sure if I needed to add sensors to the yaml file? from https://github.com/gdwaterworth/Home-Assistant---E-Linter-Logger---Sunsynk/blob/Stable-Release/V1.1/Templates ( Region 2 ) - Sunsynk.txt I'm now getting a "No Items Set" in the node: Setup Global Vars Also can't see any entities being pulled through in Dev Tools - States, yet! config yaml file.txt Edited December 15, 20232 yr by chessmaster more info
December 15, 20232 yr 2 hours ago, Gary Waterworth said: I dont like putting documentation in one forum where not all users come from. Anyone can branch the code and develop and then ask for a merge. My time is available on a free time basis as and when I have it. I have a fairly demanding job, so cannot allways be available and a lot of what has been done here has been through a lot of reverse engineering. There is VERY little official documentation and that what there is is years out of date and incomplete. As far a Pi4 goes I cant help with teh basic config. I own a few Pi3's but they are in a box gathering dust. I moved to mini pc's a long time ago. Tiny bit more money, but far more usable. For the base install of any of the options there are far better guides available on the internet. Back to your problem:= You have'nt followed all the steps here. You are missing the extra palette in node red https://github.com/gdwaterworth/Home-Assistant---E-Linter-Logger---Sunsynk/wiki V2 is very new and I still need to put up more detailed information V1 had a very specific use case ( ie was designed around my installation at home ) , so without more examples and data extracts I cannot comment further. It was not designed for multi invertor plants. The data was all there, but you had to setup the sensors manually. V2 was a full rewrite to try cater for the shortfall and limitations in V1 , it was designed as the base that could be built on, but atm is still specific, so depending on your plant/invertor setup there may be some work to do. I dont have a lab and I refuse to change my implementation at home , so the only way I can cater for other setups is for someone to give me access to their system so I can see how teh data extract and plant looks or for them to get more knowlegable in node red. One kind gent did that and that is now the reason that we can populate the generator data. One missing bit of information gathering is still the mini invertor data which is still a big (?). What I dont have time for is someone who says, ok you can look at my system but you only have 4 days ( and yes that has happened ). I was actually on a business trip in Germany, so I just shrugged my shoulders. That’s strange, it’s not like you were planning to do anything with their system 😳. by all means if there is anything you ever need I am willing to share my system for as long as you need if I use the specific part of that system.
December 15, 20232 yr 50 minutes ago, chessmaster said: Thanks Gary, appreciate everyone has their day job too Didn't notice the wiki before, that is useful! Doh! 🤪 I've now followed those steps and added the flows into node red, also wasnt sure if I needed to add sensors to the yaml file? from https://github.com/gdwaterworth/Home-Assistant---E-Linter-Logger---Sunsynk/blob/Stable-Release/V1.1/Templates ( Region 2 ) - Sunsynk.txt I'm now getting a "No Items Set" in the node: Setup Global Vars Also can't see any entities being pulled through in Dev Tools - States, yet! config yaml file.txt 34.81 kB · 1 download If you are setting up v2 you must use only the v2 yaml's. I'm seeing stuff from v1 still in the config as well. The old mapping for slipx's card for one. You might need to check your file and do a bit of clean up and reshuffeling. For instance you have template: setup in 2 locations See below example e.g. if I where to add a second template: to my config in the wrong location. Not sure if that was your full file but try the below structure and see if that might help. Just to confirm you've setup your secret.yaml as well with the correct credentials? config cleaned up.yaml.txt Edited December 15, 20232 yr by -cK-
December 15, 20232 yr @Gary Waterworth two questions: 1) Any reason why I'm still seeing the old sensors from v1 in my developer tools -> states as unavailable? I've deleted the v1 flow from node-red and and from my config file and I've rebooted HA. 🤷♂️ 2) The purge recorder is it supposed to be referencing the old entities or should those be the new ones? sensor.sunsynk_usable_XXX Purging these won't affect my ploty card data as long as they are not included in the list? e.g. that 90 day looks at these Those are pulled from these effectively: - sensor: - name: "Sunsynk Grid Today" state_class: total_increasing unique_id: "sensor.sunsynk_grid_today" device_class: energy unit_of_measurement: kWh state: > {{state_attr('sensor.sunsynk_usable_grid', 'dailyusedin')|float}} - sensor: - name: "Sunsynk Grid Export Total" state_class: total_increasing unique_id: "sensor.sunsynk_grid_export_total" device_class: energy unit_of_measurement: kWh state: > {{state_attr('sensor.sunsynk_usable_grid', 'totalusedout')|float}} - sensor: - name: "Sunsynk Load Today" state_class: total_increasing unique_id: "sensor.sunsynk_load_today" device_class: energy unit_of_measurement: kWh state: > {{state_attr('sensor.sunsynk_usable_load', 'dailyused')|float}} Thanks Edited December 15, 20232 yr by -cK-
December 15, 20232 yr 1 hour ago, -cK- said: If you are setting up v2 you must use only the v2 yaml's. I'm seeing stuff from v1 still in the config as well. The old mapping for slipx's card for one. You might need to check your file and do a bit of clean up and reshuffeling. For instance you have template: setup in 2 locations See below example e.g. if I where to add a second template: to my config in the wrong location. Not sure if that was your full file but try the below structure and see if that might help. Just to confirm you've setup your secret.yaml as well with the correct credentials? config cleaned up.yaml.txt 22.37 kB · 1 download Thanks CK Have used your file, but still getting the "No Items Set in "Setup Global Vars" in nodered. Have also setup the secrets file with email, password / Set sunsynk_sn_flow to 0 with the serial number for SN_data Struggling to figure out how do to these checks, perhaps could be related to the error im getting: ##### 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]
December 15, 20232 yr 13 hours ago, Gary Waterworth said: 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 You should find the SN and ID here. 👆 Not sure if your "No Items Set in "Setup Global Vars" is related to that or not.
December 15, 20232 yr 14 minutes ago, -cK- said: You should find the SN and ID here. 👆 Not sure if your "No Items Set in "Setup Global Vars" is related to that or not. Mine appears to be missing, SS_Consolid
December 15, 20232 yr Author 2 hours ago, chessmaster said: Thanks Gary, appreciate everyone has their day job too Didn't notice the wiki before, that is useful! Doh! 🤪 I've now followed those steps and added the flows into node red, also wasnt sure if I needed to add sensors to the yaml file? from https://github.com/gdwaterworth/Home-Assistant---E-Linter-Logger---Sunsynk/blob/Stable-Release/V1.1/Templates ( Region 2 ) - Sunsynk.txt I'm now getting a "No Items Set" in the node: Setup Global Vars Also can't see any entities being pulled through in Dev Tools - States, yet! config yaml file.txt 34.81 kB · 1 download Check your 2 x global configuration nodes. I dont think you have put in a long life token . step 7 in : https://github.com/gdwaterworth/Home-Assistant---E-Linter-Logger---Sunsynk/wiki
December 15, 20232 yr On 2023/07/27 at 10:37 PM, slipx said: Make sure you tick the "Enable global context store" when setting up your server node Mayby check this, on v1 someone else also had a similar error and this I think resoved it. Check page 16. Might be a miss configuration of node-red
December 15, 20232 yr Author 1 hour ago, -cK- said: @Gary Waterworth two questions: 1) Any reason why I'm still seeing the old sensors from v1 in my developer tools -> states as unavailable? I've deleted the v1 flow from node-red and and from my config file and I've rebooted HA. 🤷♂️ 2) The purge recorder is it supposed to be referencing the old entities or should those be the new ones? sensor.sunsynk_usable_XXX Purging these won't affect my ploty card data as long as they are not included in the list? e.g. that 90 day looks at these Those are pulled from these effectively: - sensor: - name: "Sunsynk Grid Today" state_class: total_increasing unique_id: "sensor.sunsynk_grid_today" device_class: energy unit_of_measurement: kWh state: > {{state_attr('sensor.sunsynk_usable_grid', 'dailyusedin')|float}} - sensor: - name: "Sunsynk Grid Export Total" state_class: total_increasing unique_id: "sensor.sunsynk_grid_export_total" device_class: energy unit_of_measurement: kWh state: > {{state_attr('sensor.sunsynk_usable_grid', 'totalusedout')|float}} - sensor: - name: "Sunsynk Load Today" state_class: total_increasing unique_id: "sensor.sunsynk_load_today" device_class: energy unit_of_measurement: kWh state: > {{state_attr('sensor.sunsynk_usable_load', 'dailyused')|float}} Thanks 1. Old Entities :- You need to clean those up . They are unavailable as you are not providing them anymore Settings -> Entities -> select them, delete/erase 2. I will fix the purge recorder 😕 3. Any entity referencing a purged entity is fine. Keeps its own statistical Entities having main data in statistics wont have attributes ( which most of my core ones are ) as statistical data.
December 15, 20232 yr 5 minutes ago, Gary Waterworth said: Check your 2 x global configuration nodes. I dont think you have put in a long life token . step 7 in : https://github.com/gdwaterworth/Home-Assistant---E-Linter-Logger---Sunsynk/wiki Top Man! Re-applied Long life tokens and restarted home assistant and its working now, getting entities now 🤩 Forgot to say earlier, 8kw Sunsynk here in the UK with two Seplos Mason upright batteries Now to create some dashboards, although might be one for Sunday when I have some time again - Any tips much appreciated in the meantime, but glad I moved forwards today
December 15, 20232 yr Author 23 minutes ago, chessmaster said: Mine appears to be missing, SS_Consolid ss_consolid and ss_export will only appear after a successful run through. Flow is being stopped on the main setting up or variables. I dont think you have secrets.yaml or your long life token correct
December 15, 20232 yr Author There is some cleanup/ housekeeping to be done from moving v1 to v2 unfortunately. But that being said Running HA , you should eb looking at that regularly anyway
December 15, 20232 yr Author 32 minutes ago, -cK- said: Mayby check this, on v1 someone else also had a similar error and this I think resoved it. Check page 16. Might be a miss configuration of node-red Enable these and make your life easy. Should be default if I remember correctly As long as teh Node Red Companion integration is added it will work. Then teh long life token will only be needed for teh other config node Edited December 15, 20232 yr by Gary Waterworth
December 15, 20232 yr Author 15 minutes ago, chessmaster said: Basic, but at least it's working At least you have a straight forward implementation. I am a fan of the minimal looks. I do have a seperate sheet with detailed information I use home assistant to keep track of camera's/alarms/solar and also starting with other home automation stuff with sonoff's and smart devices ( tv/aircon etc ) Some simple stuff like turning outside light on as sundown etc and then getting into more complex logic as well Someone asked me a while back why I dont create a proper integration. 1. Time 2. I like teh modularity of Node Red. Can do changes quickly and I use it for other device hacking like camera's etc Edited December 15, 20232 yr by Gary Waterworth
December 15, 20232 yr Author Note for anyone else: To check if Node Red is connected to Home Assistant ( ie long life token or other ) , under global context expand Edited December 15, 20232 yr by Gary Waterworth
December 15, 20232 yr Author 1 hour ago, chessmaster said: Thanks CK Have used your file, but still getting the "No Items Set in "Setup Global Vars" in nodered. Have also setup the secrets file with email, password / Set sunsynk_sn_flow to 0 with the serial number for SN_data Struggling to figure out how do to these checks, perhaps could be related to the error im getting: ##### 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] Extra note for others : Dont do this ... Set sunsynk_sn_flow to 0 with the serial number for SN_data Only put in the plant and sn id's when you have them The flows look for xxx as an error check //Errors to Check var ErrorCk = [undefined, "unavailable", "DONOTEDIT", "", "0000000", "[email protected]", "xxx" ]; Edited December 15, 20232 yr by Gary Waterworth
December 15, 20232 yr 1 minute ago, Gary Waterworth said: Extra note for others : Dont do this ... Set sunsynk_sn_flow to 0 with the serial number for SN_data Only put in the plant and sn id's when you have them The flows look for xxx as an error check 😀 I must go back and sort this Dashboards look great btw, curious as to what you have in your Automations tab?
December 15, 20232 yr Author 9 minutes ago, chessmaster said: 😀 I must go back and sort this Dashboards look great btw, curious as to what you have in your Automations tab? This is South Africa Specific 1. Calculate ETA next load shedding and length of it 2. Modify 2 x SOC values based on weather predictions 3. Make sure that when load shedding is due I have a specific SOC in the battery by manipulating the "use timer" to force charge if needed. Fairly complex logic calculation taking into account : a. current pv b. time of day c. weather predictions ( current and future ) d. when is load shedding e. how long is it going to be and some other variables 4. Also some notifications on grid/use timer change. had to rewrite some of this to ude teh new v2 base to set inverter values instead up updating the sunsynk directly 5. Also a lot of error checking that logger is connected, sane data is being fetched etc Edited December 15, 20232 yr by Gary Waterworth
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.