bpwwer

I think that's something I'll have to change in the node server. I've made most of them pretty verbose w.r.t. logging.

Ok, so I tried something that I didn't think would work, and it didn't, but it also left the Polisy in a bit of strange state. I'm currently developing a node server on my RPi so it's not yet listed in the store, but is installed locally. I backed up the RPi Polyglot and then restored it on the Polisy. Polyglot thinks everything is fine. It lists the node server in the proper slot, says it's connected, all the configuration and node information is there. So from the GUI, it looks like everything is running just fine. However, the git repository is not present on the Polisy. Hence, I can't view the log and there is no node server process running. So even though it says it's connected, it obviously isn't. I did get this in the log: 2019-10-31 15:30:01 [polyglot] info: RESTORE: WeatherBit.io configured in slot 3 on ISY Sucessfully 2019-10-31 15:30:01 [polyglot] info: RESTORE: WeatherBit.io ISY Restored verifin g WeatherBit.io code installation... 2019-10-31 15:30:01 [polyglot] error: NodeServer WeatherBit.io not found in the store. Can't reinstall. 2019-10-31 15:30:01 [polyglot] info: RESTORE: Restore has been completed. Shutti ng down Polyglot in 5 seconds. It seems like the backup/restore should either include the git repositories or should actually fail to install the node server if it can't find it in the store.

How about adding vim so we can have a good version of vi.

The DarkSky node server (as well as the other weather service node servers) does have a lot of values to update. When it starts, it will typically try to update them all. If those are failing, it would explain the quantity of messages. Once started, it will only update values when they actually change so normally that's only a couple of values on an update. I don't think there's anything I can do about this.

As far as I know, those errors are coming from Polyglot not the node server. I would suspect that Polyglot is having problems communicating with the ISY. I've randomly seen these messages also while testing. Node server errors would show up in the real-time log. One thing that's a bit strange is the node server version number. The latest DarkSky node server is version 1.1.3 and I believe that Polyglot cloud loads the most current version every time it starts so it would be helpful if it would display the version number of what's actually running vs. what was probably originally installed.

So what's the recommended way to remove these node servers? Can I just delete them from the database I.E. db.nodeservers.remove({'name': 'SolarEdge'})?

I think it reports what it shows in the store and the store only checks for new versions periodically. However, when it actually starts the node server, it gets the latest copy from github.

Power's back on now, but may go off again tomorrow. I think I have it fixed now. I believe you just have stop and restart the node server to have it pick up the latest version (which is 1.0.2).

@Michel Kohanim, I wouldn't say my network is complex, in fact, probably the opposite. My router is quite old and its DHCP support is pretty basic. When I add devices to my network, I also add a DHCP reservation and manually update my DNS. I need the MAC address to create the reservation. I do have a range of IP's that get assigned if no reservation exist for the device so they work. Many devices include the MAC address on the packaging and I find that helpful. This was just a small issue. If it's not possible to provide the MAC address in the packaging, it's not a big deal. Now that power just came back on, I'll have a chance to play around with it some more.

It's a bug in the node server. I'm not sure what changed in Cloud Polyglot but it's now calling the node server's process config function before the controller node class has finished initializing. I need to add more checks to make sure that the controller node has finished initializing before before processing any of the config changes. Unfortunately, I'm currently without power so I don't have access to my development system to make changes like this. This issue may be effecting my other cloud based node servers as well.

I only got to play with mine very briefly before the power went out (PG&E). The only issue I had was finding the IP address it was assigned. The DHCP server on my router doesn't provide any information on the leases it hands out so I had to work through the list of currently active leases to find the right one. Knowing the MAC address before hooking it up would have been a big help.

I commented in the git hub issue, but I'll repeat it here in case anyone else has this happen as well. That error indicates that some other application on the RPi is already listening for data from the hub. By default, only one application on the machine can listen for the data unless it is configured specifically to allow sharing with other applications. The node server is configured to allow sharing but it looks like something else is already running that's not configured to share.

Yes, even with a local weather station, forecasting would come from a service and still suffer inaccuracies from location, but that's pretty much true of any forecast data you get today. For actual automation, at least what I'm doing, it's the current condition data that's really important. For example, I have a rule that is something like this: if a window is open AND the outside temp is less than the inside temp, then turn on the whole house fan. For this to work, I need to know the real outside temperature. When I was trying to use the climate module for this, it was a problem. Both because the temperature reported wasn't very close and because the update interval was so long. That's another think about the various services, the time between updates can vary. Getting a temperature reading once an hour during morning or evening hours when the temperature is changing much more quickly can also be a problem. Note, the node serves that I listed as under development aren't available in the store yet.

I don't think 'best' really applies when looking at the different node servers I've created. The node servers that pull data from specific hardware are obviously tied to the hardware capabilities so you'd have to first define which hardware is best for your if you're looking for a personal weather station (which I understand you are not). It doesn't make sense to really compare those node servers with the ones that pull data from on-line weather services. If you look at the various node servers I've created for weather services (in alphabetical order): udi-apixu-poly: Going away as the service is being discontinued and replaced by a new API called WeatherStack udi-darksky-poly udi-owm-poly (OpenWeatherMap.org) udi-weatherbit-poly (under development) udi-weatherstack-poly (under development) There are slight differences in the actual data returned by each service, but in general, they all support the same basic set of data. There are differences in the plans each offer. Right now, I've coded these to support what data is returned by the 'free' plans. With paid plans, more data is available (typically things like longer forecasts and air quality type data). The terms of use for each is different so that may effect which is better for you personally. The biggest difference would be related to where and how these services get the data they provide. They mostly don't disclose this information, but it can effect how accurate the data is for your location. I.E. one service pulls current conditions from an airport 60 miles away while another gets data from a college 2 miles away. You'd have to try the different services to see what one tracks best with your location. The location issue is the main reason I started writing these. I live in a foothill area at about 1300ft elevation. When looking at data from weather services it either comes from an airport that is at about 200ft elevation or one that is about 3000ft elevation. Those can be up to about 10 degrees different in temperature from my location, which makes using the data to adjust things like HVAC and and a whole house fan difficult. I'm currently using a WeatherFlow personal weather station to get local condition data. The ISY climate module is getting it's data from Aeris weather service. It's similar to the above services but doesn't offer a free plan. The main difference right now is that it offers a little bit better integration with the ISY and integrates with the irrigation module. That's one area where the weather node servers need some work to catch up.

I believe that it is suppose to automatically update when stopping and then restarting. You can try the latest and see if it works any better for you. It shouldn't have any errors now, but I'm having all kinds of strange problems with polyglot cloud. If I reload the web page after making any changes it seems to make things work sometimes. I'd suggest deleting the node server and re-installing it from the store. That way you know you're running the latest version (which should be 0.1.4 now).

It is. Apparently you're the first person to try and run this from Polyglot cloud. There was a change in the module name quite a while back, shortly after I wrote this. It's been broken since then. I just pushed version 0.1.3 so it should show up in the store in a hour or so.

I believe that the reboot is no longer needed. The instructions need to be updated to remove that step. This is a long standing issue with the cloud based polyglot. The PI based version will pre-populate the custom configuration values with defaults so that they show up on the configuration screen. The cloud based polygot does not so you have to guess. The other long standing issue with the cloud based polyglot is that it won't display the configuration help instructions so there's no way for the node server to help you out with what needs to be configured. You have to add both the 'key' and the 'value' for the following custom configuration parameters: key = macAddress value = <your station mac address> key = APIKey value = <your api key> The keys need to be entered exactly as above, including the case. Once you enter these and save them, the node server should connect to the Ambient servers and start sending data to the ISY. What may be missing in the instructions is that you do need to restart the admin console after the node server is installed so that it will pick up the new nodes created by the node server.

Just pushed version 1.1.6 that fixes the rain rate and chance of rain (which are actually precipitation rate and chance of precipitation, so should reflect snow as well). What's missing is the type of precipitation so that's what's on the TODO list.

Oops, looks like I never hooked up rain rate or chance of rain. I never noticed since we don't really get any rain until November. I'm not sure why climate conditions didn't update, it should reflect what DarkSky is reporting. I'll add snow data to the TODO list.

Darksky has dewpoint and apparent temperature, Open Weather Map doesn't have any of them. Although I believe those can all be calculated from the data available. That sounds like a good enhancement request for the node servers, so I've added it to my todo lists.

I started looking at the Weatherstack API and the data you get with a free account is much more limited than what was available with APIXU. I may still continue to try and get a Weatherstack node server going as I have time but I'm not sure it's going to be worth it. Both DarkSky and OpenWeatherMap are probably better alternatives.

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.

It's been so long since I looked at WeeWX that I honestly don't remember if support was possible or not. If it was easy, I think I would have added it. The key is if WeeWX has a feature where it can send its data to a user specified URL. If so, it's just a matter of adding a simple parser to parse the data from the WeeWX http request. I think I concluded that it would take a bit of code to make WeeWX do this, but like I said, it was a while ago. I am currently running WeeWX on a RPi, but I don't actively use it for anything. If you do some experimenting with WeeWX and find that it has a way to publish the data to a URL, let me know. I'd be happy to add the support in the node server.

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.