November 16, 20232 yr Author Everyone be carefull of the homeassistant node red update yesterday. Make a backup of your flows I lost all my flows and had to revert to one of my backups.
November 16, 20232 yr 2 hours ago, Gary Waterworth said: Everyone be carefull of the homeassistant node red update yesterday. Make a backup of your flows I lost all my flows and had to revert to one of my backups. Thank you for the headsup.
November 17, 20232 yr On 2023/11/16 at 6:57 AM, Gary Waterworth said: Everyone be carefull of the homeassistant node red update yesterday. Make a backup of your flows I lost all my flows and had to revert to one of my backups. And that is why my auto-update is set to disabled 😉
November 17, 20232 yr On 2023/11/16 at 6:57 AM, Gary Waterworth said: Everyone be carefull of the homeassistant node red update yesterday. Make a backup of your flows I lost all my flows and had to revert to one of my backups. I wonder why. I had no issues with the update but I always make a backup of the addon before just in case. Running 16.0.2
November 18, 20232 yr Good day genst and ladies. I need your assistants. I want to add more than one plant to my Node red and push all to Grafana etc. How do I add more than one plant?
November 18, 20232 yr Author It is not designed for more than 1 plant currently You will have to do some investigation on Grafana. I dont use that
November 18, 20232 yr 4 hours ago, Gary Waterworth said: It is not designed for more than 1 plant currently You will have to do some investigation on Grafana. I dont use that If you can help me with the API request. The rest I can do with grafana etc.
November 19, 20232 yr Author 11 hours ago, idb said: If you can help me with the API request. The rest I can do with grafana etc. Have a look at the git repo and the work I have done. Links should be in post 1
November 20, 20232 yr @Gary Waterworth quick question, with the upcoming region change looming if we get migrated to region 2 do we just amend this section in setup global vars to switch between the regions to get the gather flows working again? Region 1 Region 2 global.set("SS.url.hostname","https://api.sunsynk.net") ; // global.set("SS.url.hostname","https://pv.inteless.com"); Thanks Edited November 20, 20232 yr by -cK-
November 20, 20232 yr Hi, @Gary Waterworth. Thanks for the work you have done. I have a 8kW Sunsynk inverter. I am running home assistant on a raspberry Pi 4. I followed the Youtube video on your github site, but after completing none of the sensor values are coming through. Is there something missing from the video? Not sure how to proceed to debug this? Please help. I am on Region 1 and have checked I can login on pv.inteless.com. Debug info 11/22/2023, 7:51:27 PMnode: Setup Global Varsfunction : (error) "PlantID Set" 11/22/2023, 7:51:27 PMnode: Setup Global Varsfunction : (error) "Invertor 1 Set" 11/22/2023, 7:51:27 PMnode: Setup Global Varsfunction : (error) "PlantID Set" 11/22/2023, 7:51:27 PMnode: Setup Global Varsfunction : (error) "Invertor 1 Set" 11/22/2023, 7:51:27 PMnode: Setup Global Varsfunction : (error) "Edit state setting in template please for login/password" Edited November 22, 20232 yr by DuncanR
November 20, 20232 yr Author 43 minutes ago, -cK- said: @Gary Waterworth quick question, with the upcoming region change looming if we get migrated to region 2 do we just amend this section in setup global vars to switch between the regions to get the gather flows working again? Region 1 Region 2 global.set("SS.url.hostname","https://api.sunsynk.net") ; // global.set("SS.url.hostname","https://pv.inteless.com"); Thanks Yes Regards
November 20, 20232 yr Author I am busy on a major rewrite atm. Bascially there wont be 2 seperate repos for region 1 or 2. It will be a config item Also in future all plants and inverters will be auto gathered and the sensors for each automatically populated The main think I am looking at now is how to present data for workflows and graphs etc It is actually a lot more compact so far Basically all data is gathered into a single context tree and then after that will be exported in a single sensor with a "crap ton" of attributes. I Will make a second sensor available that will have a cut down version that will be easier to use for graphs/flows etc. This is teh one taht will sum grid power / pv power etc Currently the part I still need to build Edited November 20, 20232 yr by Gary Waterworth
November 22, 20232 yr On 2023/11/20 at 1:53 PM, DuncanR said: Hi, @Gary Waterworth. Thanks for the work you have done. I have a 8kW Sunsynk inverter. I am running home assistant on a raspberry Pi 4. I followed the Youtube video on your github site, but after completing none of the sensor values are coming through. Is there something missing from the video? Not sure how to proceed to debug this? Please help. I am on Region 1 and have checked I can login on pv.inteless.com. Debug info 11/22/2023, 7:51:27 PMnode: Setup Global Varsfunction : (error) "PlantID Set" 11/22/2023, 7:51:27 PMnode: Setup Global Varsfunction : (error) "Invertor 1 Set" 11/22/2023, 7:51:27 PMnode: Setup Global Varsfunction : (error) "PlantID Set" 11/22/2023, 7:51:27 PMnode: Setup Global Varsfunction : (error) "Invertor 1 Set" 11/22/2023, 7:51:27 PMnode: Setup Global Varsfunction : (error) "Edit state setting in template please for login/password" Don't worry I managed to figure it out. Just a typo.
November 28, 20232 yr I've been playing around with HA for a while, got data from our old inverter, but now we have a sunsynk as well, it made sense to add that. So I followed the video. And although the various parts are all there all the inputs are either blank or are at defaults. The "New SunSynk Update Status" has not been called. Am I missing something?
November 29, 20232 yr Author 19 hours ago, Javac said: I've been playing around with HA for a while, got data from our old inverter, but now we have a sunsynk as well, it made sense to add that. So I followed the video. And although the various parts are all there all the inputs are either blank or are at defaults. The "New SunSynk Update Status" has not been called. Am I missing something? Not much information given. Did you put in your login and password ? Did you add in the template to your config file ? Are there any debug images ?
November 30, 20232 yr Author I have been working on a version 2 which is a major rewrite I have put a preview up under the "developement" branch on Git and it will be getting regular changes There may be bugs ( probably will be ) The same flows are for region 1 and region 2 I dont recommend this for anyone yet who does not know nodered / homeassistant well Basically changes are Centralised Config Iteration of all plants and inverters All gathered data stored in the global context data area Selected data exported to major entities for flows/graphs etc. This data extract logic is easily and highly editable to cater for many scenarios. Slipx flow card entities changed to use the flow data. Means you can see exactly what you see in the sunsynk app. Edited November 30, 20232 yr by Gary Waterworth
November 30, 20232 yr Hi Everyone, I am very new to this and I have managed to get the data and card setup when we have 1 inverter. However we had a second inverter installed with 2 extra PV connections. I amended the Configuration.yaml to the second Inverter which is showing. How do I create the entities for PV3 and PV4 From inverter 2 ? I expect it would be here in the attachment however its under the section (##### DO NOT EDIT ANYTHING UNDER HERE) Edited November 30, 20232 yr by Lilmonsta10
November 30, 20232 yr 2 hours ago, Lilmonsta10 said: Hi Everyone, I am very new to this and I have managed to get the data and card setup when we have 1 inverter. However we had a second inverter installed with 2 extra PV connections. I amended the Configuration.yaml to the second Inverter which is showing. How do I create the entities for PV3 and PV4 From inverter 2 ? I expect it would be here in the attachment however its under the section (##### DO NOT EDIT ANYTHING UNDER HERE) I only have a single inverter setup but I think you will need to identify the correct sensors under the developer tool section under states first and see what the actual attributes are for the additional sensors. It might be listed under sensor.sunsynk_input or maybe sensor.sunsynk_input_2 once you have this you should add those sensors in the config file. Below is just an example so please amend it as needed, the assumption here was the additional sensor was under sensor.sunsynk_input but I suspect it is going to be under input_2. Also note there is one small mistake in your config, Current 112 should reference pvIV_1_ipv not 2 😉 ####pv1_power_186: sensor.sunsynk_pv1_186 ####pv2_power_187: sensor.sunsynk_pv2_187 ####pv3_power_188: sensor.sunsynk_pv3_188 ####pv4_power_189: sensor.sunsynk_pv4_189 ####pv1_voltage_109: sensor.sunsynk_pv1_voltage_109 ####pv1_current_110: sensor.sunsynk_pv1_current_110 ####pv2_voltage_111: sensor.sunsynk_pv2_voltage_111 ####pv2_current_112: sensor.sunsynk_pv2_current_112 ####pv3_voltage_113: sensor.sunsynk_pv3_voltage_113 ####pv3_current_114: sensor.sunsynk_pv3_current_114 ####pv4_voltage_115: sensor.sunsynk_pv4_voltage_115 ####pv4_current_116: sensor.sunsynk_pv4_current_116 - sensor: - name: "Sunsynk Daily PV 108" state: > {{state_attr('sensor.sunsynk_input', 'etoday')|float(0)|round(1)}} - sensor: - name: "Sunsynk PV1 186" state: > {{state_attr('sensor.sunsynk_input', 'pv1')|float(0)|round(0)}} - sensor: - name: "Sunsynk PV2 187" state: > {{state_attr('sensor.sunsynk_input', 'pv2')|float(0)|round(0)}} - sensor: - name: "Sunsynk PV3 188" state: > {{state_attr('sensor.sunsynk_input', 'pv3')|float(0)|round(0)}} - sensor: - name: "Sunsynk PV4 188" state: > {{state_attr('sensor.sunsynk_input', 'pv4')|float(0)|round(0)}} - sensor: - name: "Sunsynk PV1 Voltage 109" state: > {{state_attr('sensor.sunsynk_input', 'pvIV_0_vpv')|float(0)|round(1)}} - sensor: - name: "Sunsynk PV1 Current 110" state: > {{state_attr('sensor.sunsynk_input', 'pvIV_0_ipv')|float(0)|round(1)}} - sensor: - name: "Sunsynk PV2 Voltage 111" state: > {{state_attr('sensor.sunsynk_input', 'pvIV_1_vpv')|float(0)|round(1)}} - sensor: - name: "Sunsynk PV2 Current 112" state: > {{state_attr('sensor.sunsynk_input', 'pvIV_1_ipv')|float(0)|round(1)}} - sensor: - name: "Sunsynk PV3 Voltage 113" state: > {{state_attr('sensor.sunsynk_input', 'pvIV_2_vpv')|float(0)|round(1)}} - sensor: - name: "Sunsynk PV3 Current 114" state: > {{state_attr('sensor.sunsynk_input', 'pvIV_2_ipv')|float(0)|round(1)}} - sensor: - name: "Sunsynk PV4 Voltage 115" state: > {{state_attr('sensor.sunsynk_input', 'pvIV_3_vpv')|float(0)|round(1)}} - sensor: - name: "Sunsynk PV4 Current 116" state: > {{state_attr('sensor.sunsynk_input', 'pvIV_3_ipv')|float(0)|round(1)}} If those are under input_2 it might look something like this then ####pv1_power_186: sensor.sunsynk_pv1_186 ####pv2_power_187: sensor.sunsynk_pv2_187 ####pv3_power_188: sensor.sunsynk_pv3_188 ####pv4_power_189: sensor.sunsynk_pv4_189 ####pv1_voltage_109: sensor.sunsynk_pv1_voltage_109 ####pv1_current_110: sensor.sunsynk_pv1_current_110 ####pv2_voltage_111: sensor.sunsynk_pv2_voltage_111 ####pv2_current_112: sensor.sunsynk_pv2_current_112 ####pv3_voltage_113: sensor.sunsynk_pv3_voltage_113 ####pv3_current_114: sensor.sunsynk_pv3_current_114 ####pv4_voltage_115: sensor.sunsynk_pv4_voltage_115 ####pv4_current_116: sensor.sunsynk_pv4_current_116 - sensor: - name: "Sunsynk Daily PV 108" state: > {{state_attr('sensor.sunsynk_input', 'etoday')|float(0)|round(1)}} - sensor: - name: "Sunsynk PV1 186" state: > {{state_attr('sensor.sunsynk_input', 'pv1')|float(0)|round(0)}} - sensor: - name: "Sunsynk PV2 187" state: > {{state_attr('sensor.sunsynk_input', 'pv2')|float(0)|round(0)}} - sensor: - name: "Sunsynk PV3 188" state: > {{state_attr('sensor.sunsynk_input_2', 'pv1')|float(0)|round(0)}} - sensor: - name: "Sunsynk PV4 188" state: > {{state_attr('sensor.sunsynk_input_2', 'pv2')|float(0)|round(0)}} - sensor: - name: "Sunsynk PV1 Voltage 109" state: > {{state_attr('sensor.sunsynk_input', 'pvIV_0_vpv')|float(0)|round(1)}} - sensor: - name: "Sunsynk PV1 Current 110" state: > {{state_attr('sensor.sunsynk_input', 'pvIV_0_ipv')|float(0)|round(1)}} - sensor: - name: "Sunsynk PV2 Voltage 111" state: > {{state_attr('sensor.sunsynk_input', 'pvIV_1_vpv')|float(0)|round(1)}} - sensor: - name: "Sunsynk PV2 Current 112" state: > {{state_attr('sensor.sunsynk_input', 'pvIV_1_ipv')|float(0)|round(1)}} - sensor: - name: "Sunsynk PV3 Voltage 113" state: > {{state_attr('sensor.sunsynk_input_2', 'pvIV_0_vpv')|float(0)|round(1)}} - sensor: - name: "Sunsynk PV3 Current 114" state: > {{state_attr('sensor.sunsynk_input_2', 'pvIV_0_ipv')|float(0)|round(1)}} - sensor: - name: "Sunsynk PV4 Voltage 115" state: > {{state_attr('sensor.sunsynk_input_2', 'pvIV_1_vpv')|float(0)|round(1)}} - sensor: - name: "Sunsynk PV4 Current 116" state: > {{state_attr('sensor.sunsynk_input_2', 'pvIV_1_ipv')|float(0)|round(1)}} Again I'm not sure what your actual attributes will be, perhaps post a screenshot of the sensors from the developer tool so we can assist you better with the actual config. Edited November 30, 20232 yr by -cK-
November 30, 20232 yr -CK- You Star !!! That has got me going. The only hiccup I have now is the Value for Load is now across both Devices. Can you combine Sensors to create a new one Something like - sensor: - name: "Sunsynk Total Load Inverters" state: > {{state_attr('sensor.sunsynk_Load', 'TotalPower') + state_attr('sensor.sunsynk_Load_2', 'TotalPower')
November 30, 20232 yr 28 minutes ago, Lilmonsta10 said: -CK- You Star !!! That has got me going. The only hiccup I have now is the Value for Load is now across both Devices. Can you combine Sensors to create a new one Something like - sensor: - name: "Sunsynk Total Load Inverters" state: > {{state_attr('sensor.sunsynk_Load', 'TotalPower') + state_attr('sensor.sunsynk_Load_2', 'TotalPower') You can do it easily using a helper
December 3, 20232 yr Author Been working on something new that has been asked for a few time How do I change settings on the Inverter I think I have a basic framework setup now that is a step towards allowing this to happen "easily". Still a lot of work needed before it can become reality Basically monitor for "state change" events and then check if it is a entity we are worried about I also setup a lookup table to map that entity to the part that the sunsynk website knows. In theory it will work, just need to now flesh it out. Still have to write the functions that do the actual sunsynk update, but that is easy as I have already been doing that for a while. The rewritten Gather and my current automation seems to be pretty stable. It is a lot more complex now, so a documentation rewrite is going to be required Edited December 3, 20232 yr by Gary Waterworth
December 4, 20232 yr Got migrated to region 2 today so if your readings look stuck just go check if you can login on Region 2, if so then just change the setting in node-red and presto 😉
December 4, 20232 yr 34 minutes ago, -cK- said: Got migrated to region 2 today so if your readings look stuck just go check if you can login on Region 2, if so then just change the setting in node-red and presto 😉 Hey -cK-, I am clearly missing something but please can you tell me where on Node red you changed this and what exactly changed? I did this once to set it up and haven't messed with it since since it was tricky....so slightly confused now, thanks so much Updated, figured it out...thanks though! Edited December 4, 20232 yr by charliw update
December 4, 20232 yr Just double click the Setup Global Vars, scroll down to around line 87 or 88 It should still be on pv.inteless.com if region 1 just add // in front of line 88 and delete the // in front of api.sunsynk.net. This should look like this then. Hit done and hit deploy at the top as well. Both buttons should be red so can't miss it 😉 I tested my region on the sunsynk login page to confirm I was able to log in on region 2 first though. https://sunsynk.net/login Edited December 4, 20232 yr by -cK-
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.