f11 Posted April 23, 2020 Posted April 23, 2020 Oops, not quite. Instruction <git branch --set-upstream-to=origin/master master> returns error: the requested upstream branch 'origin/master' does not exist hint: hint: If you are planning on basing your work on an upstream hint: branch that already exists at the remote, you may need to hint: run "git fetch" to retrieve it. hint: hint: If you are planning to push out a new local branch that hint: will track its remote counterpart, you may want to use hint: "git push -u" to set the upstream config as you push. Is there a typo in the instruction, or should I be running "git fetch" before re-running it? Quote
f11 Posted April 23, 2020 Posted April 23, 2020 (edited) Thanks, xKing - that got me past that obstacle. Now I'm back to the original issue: my SE inverter models are 'SE3800A' and 'SE3800H', once your code truncated the -xxxxxx info. Suddenly they're reported as unsupported when they were working previously. Can you foresee any issue with me just adding 'SE3800A' and 'SE3800H' to the SINGLE_PHASE model set in the Polisy code, so that my inverters are supported again? I'm still not sure how they were considered supported with previous code which had the same SINGLE_PHASE set of models as v0.06. But previous to this update, they WERE reporting the same data to my ISY as the inverter displays were reading. [ Edit: I added 'SE3800A', 'SE3800H' to your SINGLE_PHASE model set, inserted just after 'SE3800' (I left that unchanged in case there IS a model SE3800), then started the SolarEdge NS. its now running normally again, reporting: 2020-04-23 17:58:03,590 [Controller] [INFO ] Updating Driver 277630 - ST: 0, uom: 73 2020-04-23 17:58:04,848 [Controller] [DEBUG] {'data': {'count': 12, 'telemetries': [{'date': '2020-04-23 16:58:09', 'totalActivePower': 2548.0, 'dcVoltage': 369.438, etc - BIG SNIP}}]}} 2020-04-23 17:58:04,851 [Controller] [INFO ] Updating Driver 7f12b562a8 - ST: 888.0, uom: 73 2020-04-23 17:58:04,854 [Controller] [INFO ] Updating Driver 7f12b562a8 - GV0: 89.5, uom: 56 2020-04-23 17:58:04,856 [Controller] [INFO ] Updating Driver 7f12b562a8 - CPW: 893.0, uom: 56 2020-04-23 17:58:04,858 [Controller] [INFO ] Updating Driver 7f12b562a8 - CLITEMP: 33.7139, uom: 4 2020-04-23 17:58:04,862 [Controller] [INFO ] Updating Driver 7f12b562a8 - CV: 241.359, uom: 72 2020-04-23 17:58:04,864 [Controller] [INFO ] Updating Driver 7f12b562a8 - GV1: 364.688, uom: 72 2020-04-23 17:58:04,866 [Controller] [INFO ] Updating Driver 7f12b562a8 - GV2: 3.7, uom: 1 2020-04-23 17:58:04,868 [Controller] [INFO ] Updating Driver 7f12b562a8 - GV3: 60.0, uom: 90 2020-04-23 17:58:04,871 [Controller] [INFO ] Updating Driver 7f12b562a8 - GV4: 2, uom: 25 2020-04-23 17:58:05,065 [Controller] [DEBUG] {'data': {'count': 11, 'telemetries': [{'date': '2020-04-23 16:59:54', 'totalActivePower': 3002.92, 'dcVoltage': 390.806, etc - BIG SNIP}}]}} 2020-04-23 17:58:05,068 [Controller] [INFO ] Updating Driver 731c2111c1 - ST: 2495.0, uom: 73 2020-04-23 17:58:05,070 [Controller] [INFO ] Updating Driver 731c2111c1 - GV0: 277.057, uom: 56 2020-04-23 17:58:05,072 [Controller] [INFO ] Updating Driver 731c2111c1 - CPW: 2510.34, uom: 56 2020-04-23 17:58:05,074 [Controller] [INFO ] Updating Driver 731c2111c1 - CLITEMP: 36.2592, uom: 4 2020-04-23 17:58:05,077 [Controller] [INFO ] Updating Driver 731c2111c1 - CV: 243.538, uom: 72 2020-04-23 17:58:05,080 [Controller] [INFO ] Updating Driver 731c2111c1 - GV1: 387.644, uom: 72 2020-04-23 17:58:05,082 [Controller] [INFO ] Updating Driver 731c2111c1 - GV2: 10.3, uom: 1 2020-04-23 17:58:05,083 [Controller] [INFO ] Updating Driver 731c2111c1 - GV3: 60.0, uom: 90 2020-04-23 17:58:05,086 [Controller] [INFO ] Updating Driver 731c2111c1 - GV4: 2, uom: 25 I only made this change in my own Polisy, I won't upload it to your github code as I don't fully understand the ramifications of doing so, and don't want to break anything for other people. Was there a deliberate reason to knock out the SE3800A/H inverters from the original code where they were considering supported? ] Edited April 24, 2020 by f11 Quote
xKing Posted April 24, 2020 Posted April 24, 2020 I never remove any models from supported list. Just added SE3800A and SE3800H, should work do git pull please Quote
f11 Posted April 24, 2020 Posted April 24, 2020 Thanks, xKing - Will do !! Your help is greatly appreciated. Quote
GQuack Posted June 11, 2020 Posted June 11, 2020 On 12/10/2019 at 9:49 AM, bpwwer said: I've been following this because I'm going to have a SolarEdge inverter soon and would like to use this node server after it's installed. So I took a look at your log. I think the problem is the way that polyglot (and specifically the cloud version) is handling the parameter update. The node server doesn't get the updated value after you enter it. Try doing things in this order: 1) Install the node server 2) Enter the api_key parameter key and value. Save the changes 3) Stop the node server 4) Restart the node server 5) Check the admin console to verify the nodes exist. You should see a SolarEdge Controller node, a Quackenbush1 node with two subnode for battery. Since you already have the key entered (per screen shot), just start with step 3, stop and restart the node server and it should discover your inverter. On 12/10/2019 at 9:49 AM, bpwwer said: I've been following this because I'm going to have a SolarEdge inverter soon and would like to use this node server after it's installed. So I took a look at your log. I think the problem is the way that polyglot (and specifically the cloud version) is handling the parameter update. The node server doesn't get the updated value after you enter it. Try doing things in this order: 1) Install the node server 2) Enter the api_key parameter key and value. Save the changes 3) Stop the node server 4) Restart the node server 5) Check the admin console to verify the nodes exist. You should see a SolarEdge Controller node, a Quackenbush1 node with two subnode for battery. Since you already have the key entered (per screen shot), just start with step 3, stop and restart the node server and it should discover your inverter. Hi all, I’m revisiting this post because I’ve just upgraded my system and added a 2nd inverter with attached battery. I’m thinking there are several options and wanted to reach out here to get these added to the ISY. 1) Stop and restart the node server and see if the new nodes show up since the new components are now part of the overall SolarEdge site. (answer: tried this and they don’t) 2) Delete the existing nodes within the ISY, then add all nodes again (seems like a more likely approach) 3) Try to add all nodes within the ISY and see if the new nodes show up (answer: tried this and they don’t) 4) other? Quote
bpwwer Posted June 11, 2020 Posted June 11, 2020 1 hour ago, GQuack said: Hi all, I’m revisiting this post because I’ve just upgraded my system and added a 2nd inverter with attached battery. I’m thinking there are several options and wanted to reach out here to get these added to the ISY. 1) Stop and restart the node server and see if the new nodes show up since the new components are now part of the overall SolarEdge site. (answer: tried this and they don’t) 2) Delete the existing nodes within the ISY, then add all nodes again (seems like a more likely approach) 3) Try to add all nodes within the ISY and see if the new nodes show up (answer: tried this and they don’t) 4) other? That's basically the system I have too. Two inverters with a battery connected to one of them. What I'm getting with this node server is a Site node which has an aggregate of the two inverters that has a single child node for the battery. However, I installed the node server after everything was installed. As a last resort you could delete the node server and re-install it. Quote
GQuack Posted June 12, 2020 Posted June 12, 2020 (edited) When you say aggregate of the two inverters, you see a total of the two and not separate nodes, that seems odd. They have a similar approach on their web portal which aggregates both inverters and both batteries which I don’t care for. I have two strings of panels with each string feeding their respective inverter with their respective attached battery but everything gets lumped together. Edited June 12, 2020 by GQuack Update Quote
bpwwer Posted June 12, 2020 Posted June 12, 2020 5 minutes ago, GQuack said: When you say aggregate of the two inverters, you see a total of the two and not separate nodes, that seems odd. They have a similar approach on their web portal which aggregates both inverters and both batteries which I don’t care for. I have two strings of panels with each string feeding their respective inverter with their respective attached battery but everything gets lumped together. Yup, I suspect the portal and the node server are using the same API calls to get the information. While I have the node server running, I'm not currently using it for anything. I am collecting data locally from the inverters and meter via modtcp and via an external meter. I dump this into a database and generate my own charts. The one things I'm missing is info on the battery. When the battery is charging, it looks like I'm not producing as much, but when the battery is discharging I see it as if I have PV production happening. So it works out in the end, but I was looking into the API to see if I could get some additional data on what's happening with the battery. There is access to a lot of different data vial the API but my understanding is that it's not real-time, Quote
GQuack Posted June 12, 2020 Posted June 12, 2020 I may be able to help. You should have admin rights to your site, yes? Look for “charts.” Took me a few tries to figure it out but you can select the component in the left frame (battery or inverter1 or 2), and the data items you can “chart” show up on the right. Select which one(s) you want to see and the portal will draw a chart using Adobe Flash for the time period you select. You can then export that in a .csv format for Excel. Lots of detail info... Quote
bpwwer Posted June 12, 2020 Posted June 12, 2020 16 minutes ago, GQuack said: I may be able to help. You should have admin rights to your site, yes? Look for “charts.” Took me a few tries to figure it out but you can select the component in the left frame (battery or inverter1 or 2), and the data items you can “chart” show up on the right. Select which one(s) you want to see and the portal will draw a chart using Adobe Flash for the time period you select. You can then export that in a .csv format for Excel. Lots of detail info... Yes, I've played around with the charts on the portal. I was really looking for real-time (at least every minute) info on battery charge/discharge rates that I can feed automatically to my database. While the charts are interesting, they're not real-time. I think the data only updates every 15 minutes and you have to regenerate the chart to see any updated data. I believe the API provides data updates every 5 minutes. It seems like the data should be available over the modbus, and that's probably how the battery communicates it's status to the inverter, but I haven't found any documents that indicate it's possible to access that data over the local network port. Quote
GQuack Posted June 12, 2020 Posted June 12, 2020 OK, interesting.... I tried tonight to get my new configuration to load. Without deleting the node, I first stopped and started the node server and tried adding all nodes. In the log, I can see the messages where the two inverters and two batteries are found but also seeing a message where the model of inverter is not supported. Would explain why I get no values at all in the ISY under the Inverter node but the node for the battery looks OK but bpwwer to your point, the values look aggregated. Any thoughts on why the the inverter model is not supported? This is a standard SolarEdge inverter model. solaredge-0021b90250ef-2 (1).txt Quote
xKing Posted June 12, 2020 Posted June 12, 2020 Looks like you using older node server from my GitHub, I moved it to the UDI GitHub a while back. Just re-install the node server and you should get the one with SE3800A included. Quote
bpwwer Posted June 12, 2020 Posted June 12, 2020 After uninstalling and re-installing I'm still getting Model SE7600A-USS20NHB2 is not yet supported Interestingly that's the older of the two models I have. Quote
bpwwer Posted June 12, 2020 Posted June 12, 2020 19 minutes ago, xKing said: can you git pull now? I've added it That did it, both are showing up now, thanks! Quote
GQuack Posted June 13, 2020 Posted June 13, 2020 OK, the lengthy loading issue is behind me, not sure what that was, but added the node server, both inverters are now there. Thank you xKing and bpwwer! 1 Quote
starmanj Posted January 2, 2021 Posted January 2, 2021 Solar Edge used to work for me, but now I get: 2021-01-02 14:47:25,596 [NodeServer] [ERROR] Model SE10000A-USR00NNU2 is not yet supported It worked before. Can the Polyglot Cloud server be updated to re-enable my solar inverter? Thanks! Quote
Michel Kohanim Posted January 4, 2021 Posted January 4, 2021 @starmanj, That's really odd. Is it really possible that they changed their model number? Anyway, we added it to the list. Please restart your node server. With kind regards, Michel Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.