bpwwer

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.

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.

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,

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.

I just pushed a new version that should fix this. Thanks for the report.

Thanks for the report Gary. Looks like WLL refused the connection for some reason, as it started working after the restart, I assume it must be a temporary failure. I added error trapping to the request so it shouldn't crash if it happens again.

Pushed an update that should trap the missing pressure value so it doesn't crash.

The OpenWeatherMap node server no longer works properly with Polyglot Cloud so I'm removing it from the store.

Step #4 was not necessary and may account for some of the issues you're having. Polyglot takes care of all interaction with the ISY, including adding nodes and setting up the node server configuration. Changing things like the ID and password will cause problems with the ISY/Polyglot communication. Given that it's difficult now to know what state everything is in, it may be best to delete everything and start over. Steps 1, 2, and 3 are all correct. After that your step 4 should have been to restart the Admin Console. Once the Admin Console is restarted, all the nodes should show up and start populating with data. Not all fields will necessarily have data, some like wind gust are optional and OpenWeatherMap may or may not send that data. You can try stopping and restarting the node server from the dashboard and then restarting the Admin Console and see if it all starts working, but depending on what you've changed, it may not work and deleting and re-installing would be the only solution. The logging level determines how much information is sent to the node server log file. Off means that almost nothing is sent to the log. You can change that via the drop down menu. All of the other weather service node servers are similar. They differ slightly in the data that they provide, the sources they collect data from, and the forecasting algorithms that they use.

Already did, thanks for the suggestion!

That's a good question and I agree with you about the quality of the documentation given that I'm responsible for a number of node servers with poor documentation. In my case, and I suspect others as well, because we aren't currently being compensated, it tends to be harder to justify the time for it. Having a reasonably good template for documentation and have it be a gate (I.E. done to some standard) before allowing something to be added to the store would help. I'm sure we'll get there eventually. In the meantime, if you see something you'd like better documented in any of my node servers, let me know. I'm always willing to add things to my todo list

Opera, just started happening yesterday for me too.

It looks like it should be reporting it. However, it only reports the reading to the ISY when it changes. If you look at the nodes in the polyglot dashboard. It's GV5 in the main controller node. Does that have a value that matches the data in the log? I think, because I tell the polyglot to only update the ISY when it changes, it's possible that upgrading the ISY, cleared the values in the ISY, but polyglot hasn't seen a change in the value so it hasn't sent an update. It works this way to reduce the load on the ISY. For a lot of my node servers I started forcing polyglot to send the values when the node server starts to as a way to work around this, but this one doesn't do that. I'll have to update it otherwise, you'll probably not see that update until you get more rain.

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.

I can understand your confusion as something has gone wrong. Your understanding of should have happened appears correct. 1) Polyglot cloud is supposed to install the node server to the ISY and create the nodes there. Based on your screen shots, that never happened. There may information in the DarkSky node server log to explain why. Without more information, I can't even make a guess as to why it failed. Have you restarted the admin console since installing the node server? The admin console does need to be restarted as some of the installed node server files are only read when the admin console is started. 2) I believe you should be able to delete any duplicate configuration entries. But they shouldn't cause any issues and if the nodes display from the Polyglot dashboard looks like it's updating the data, then, yes, it is correctly configured. I'm not sure why you had to re-enter the configuration multiple times, that's not normal. 3) Someone with more knowledge of how Polyglot cloud works will probably have to help here. Those buttons should be doing what they say. Again, checking the log may provide some additional information. 4) This seems to be tied to #3, but I'm not sure. Based on your screen shots, it looks like you're only running one instance of the node server. EDIT 2) It is possible to confuse Polygot as it doesn't always do a good job of cleaning things up when something goes wrong. I know I've had my local Polyglot database get into corrupted states that make working with it difficult until it's manually cleaned up. But I have no idea if that's possible with Polyglot cloud, or how you'd clean it up if it does happen.

Ah, that makes more sense now. For some reason I was thinking that rain size had something to do with the size of the raindrops. Since the rain data is reported as bucket tips, I should be using this to do the calculations instead of a fixed 0.01 inches. I'll make that change and switch out the rain size on the display as well. Thanks!

@Jim Unroe You're welcome. Did you get any soil sensors? I'm curious to know if that part of the node server works.

The WeatherLink node server is now available in the node server store.

Just pushed a new version that moves the indoor conditions to a separate node. Also, it will only create the indoor node if indoor data exists. I added processing for soil conditions too and again, will only create a node for those if the data exists. It looks like yours doesn't send any soil conditions (probably needs additional sensors or something). If everything looks good after you've had a chance to test a bit, I'll submit it to the Polyglot store so others can use it too.

I updated rain to be inches instead of counts and pushed the change. I'm thinking of moving the indoor temp/humidity to a separate node. Then I can add the other indoor values there as well, That will de-clutter the main node some. I can also add the soil readings in a separate node.

I have something wrong with wind speed, I had it working at one point, but then broke something. I'm not sure why the indoor readings aren't showing, everything looks correct there, I'll double check that. The daily rainfall value is in something called 'counts'. I'm not sure what that really means. Maybe it's the tipping bucket count? If I knew what one count equated to in inches or mm I can do the math and report an actual value. Any clue?

Gary, I pushed a new version that includes more data and should fix the problem with it crashing. To update it 1. stop the WeatherLink node server from the polyglot dashboard 2. from your PI terminal window do the 'git pull origin master' 3. start the WeatherLink node server 4. from the admin console, click the 'update profile' button for the WeatherLink node 5. restart the admin console Some of the things you list above aren't available, at least not in the sample data I have. If you can post/attach the log showing the results of the query, that would help. It should look something like: 2019-07-30 16:07:15,003 [NodeServer] [DEBUG] {'error': None, 'data': {'ts': 1531 754005, 'did': '001D0A700002', 'conditions': [{'rainfall_monthly': 63, 'wind_dir _at_hi_speed_last_2_min': 0.0, 'wind_speed_avg_last_2_min': 42606, 'rain_storm_l ast': None, 'lsid': 48308, 'rain_storm': None, 'heat_index': 5.5, 'wind_chill': 6.0, 'rainfall_last_60_min': None, 'temp': 62.7, 'trans_battery_flag': 0, 'rain_ storm_start_at': None, 'wind_speed_hi_last_10_min': 8, 'rainfall_last_15_min': N one, 'rx_state': 2, 'wind_dir_scalar_avg_last_1_min': 15, 'rain_size': 2, 'wind_ speed_avg_last_1_min': 4, 'rainfall_last_24_hr': None, 'dew_point': -0.3, 'data_ structure_type': 1, 'rain_storm_last_end_at': None, 'txid': 1, 'wind_speed_last' : 2, 'wind_dir_last': None, 'wind_dir_scalar_avg_last_2_min': 170.7, 'rain_rate_ hi_last_15_min': 0, 'rainfall_year': 63, 'solar_rad': 747, 'rainfall_daily': 63, 'hum': 1.1, 'rain_storm_last_start_at': None, 'uv_index': 5.5, 'wind_dir_scalar _avg_last_10_min': 4822.5, 'wind_speed_hi_last_2_min': 8, 'rain_rate_hi': None, 'thsw_index': 5.5, 'wind_dir_at_hi_speed_last_10_min': 0.0, 'wind_speed_avg_last _10_min': 42606, 'thw_index': 5.5, 'rain_rate_last': 0, 'wet_bulb': None}, {'moi st_soil_2': None, 'data_structure_type': 2, 'moist_soil_4': None, 'txid': 3, 'ls id': 3187671188, 'wet_leaf_1': None, 'temp_4': None, 'wet_leaf_2': None, 'moist_ soil_1': None, 'temp_1': None, 'temp_3': None, 'rx_state': None, 'trans_battery_ flag': None, 'moist_soil_3': None, 'temp_2': None}, {'data_structure_type': 4, ' lsid': 48307, 'temp_in': 78.0, 'heat_index_in': 8.4, 'dew_point_in': 7.8, 'hum_i n': 41.1}, {'data_structure_type': 3, 'bar_trend': None, 'lsid': 48306, 'bar_abs olute': 30.008, 'bar_sea_level': 30.008}]}}

Can you be more specific about what is not updating? Did you get the 'git pull origin master' command to work? Is it it the field labels that still aren't right? Is it not updating the data on the ISY? Is that log current or just what's there from the first time you started it? From what's shown there, the IP address of the WeatherLink device hasn't been set, but the screen shot you had from before seemed correct.

Yeah, you just manually installed it the same way the store does. The 'cd udi<tab>' should work there. To update a non-store based node server (or even one installed by the store) manually. You get into the directory for the node server and use the 'git pull origin master' command. That the same thing that will be run when you update from the store. You can check if you're in the right place with the 'pwd' command. Here's what it looks like for me: $ pwd /home/pi/.polyglot/nodeservers/udi-wll-poly $ git pull origin master From github.com:bpaauwe/udi-wll-poly * branch master -> FETCH_HEAD Already up-to-date.

It should be the same directory that was created when you did the git clone initially. So if you haven't tried anything else yet, your command window should still be in the nodeservers directory. the 'ls' command will show everything there and you can skip the whole path and just 'cd udi-wll-poly'. Another trick is that you can usually use the <tab> key to do auto completion. So typing 'cd udi<tab>' may fill it out automatically. If not, <tab><tab> should show all the possible matches for what you started to type. Yes, currently it's polling for the current conditions. If I'm reading the docs correctly, the live streaming of data is only wind and rain and can only be run for fixed lengths of time. If you have some documentation that says otherwise, can you point me to it?