bpwwer

I just tried to clone a new node server I'm working on to the Polisy and got this error: sudo: unable to write to /var/run/sudo/ts/admin: No space left on device fatal: could not create work tree dir 'udi-weatherbit-poly': No space left on device A df of /var/polyglot shows [admin@polisy /var/polyglot/nodeservers]$ df . Filesystem 1K-blocks Used Avail Capacity Mounted on zudi/ROOT/default 5298048 5294859 3188 100% / Yes, the polyglot log file was huge and clearing it freed up about 45% of the space on the file system.

The problem is not knowing the mac-id and my router doesn't let me access the list of dynamic IP addresses it's handed out. I did have to use arp to get a list of mac-id/IP addresses and then go through the IP addresses one-by-one until I found the one assigned to the Polisy. Once I found it's IP and Mac-id, it was no problem to add it to the router with a IP reservation and then add it to my local DNS server.

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.

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'})?

@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.

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 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?

So it worked. Looks like I didn't update the profile files so that's why the data field names don't match/make sense. To get the update: cd ~/.polygot/nodeservers/udi-wll-poly 'git pull origin master' It should grab the latest code from the repository Then from the admin console press the "Update Profile" button and it should update the field names. You might have to restart the admin console before it will see the changes.

What you typed above looks like there's an extra '/' character at the end but that shouldn't matter, it works for me both with and without that. Can open it with your browser? The error means bad request, but I don't see anything bad about it. It's the same command used by Polyglot so if you've been able to install any node servers it should just work. I'm sure you entered it correctly, but can you cut-n-paste the command or is that not something you can easily do with your configuration?

Does that mean you can't actually query it unless it's on Wi-Fi and the app is running? If so that's a strange bug. Have you actually tried pointing a browser at it? The docs I have say it should return current condition data at http://<it's ip address>/v1/current_conditions If you get data there, the the node server should work. You can install the node server with the following steps on your RPi. 1. cd ~/.polyglot/nodeservers 2. git clone https://github.com/bpaauwe/udi-wll-poly 3. from the polyglot web interface -> NodeServers -> Add NodeServer 4. select "WeatherLink" from the list of available node servers and add it. The only configuration is to add the IP address in the custom parameters. Once that is entered and saved, it should start doing queries every minute to get the current conditions. Log information will be in ~/.polyglot/nodeservers/udi-wll-poly/logs/debug.log

@garybixler I have a test version running using some sample data I was able find on-line so let me know when you get the hardware setup and I'll get you started on it. Right now it's just grabbing some of the current condition data and I've not tried to access the 2.5 second UDP data. Also, there are a lot of different wind / rain values available, I'm just pulling the basics so you'll have review them and see if there's anything else that would be useful. The node servers also have to be written properly to work this way too. I'm not sure all of mine are. But even so, some of the weather data, especially when it is coming from a local station, can vary slightly with every update. So something like 2.5 second wind speed/direction readings are very likely to change a lot unless it's a very calm day.

I see two different ways to access the data. 1) is by connecting locally to the a WLL device. With this method, current conditions can be polled fairly frequently (10 seconds) and it can also be set up to broadcast some data (wind and rain) every 2.5 seconds over UDP. This is what I was looking at using. With the initial version just polling for current conditions (probably at something more like 1 minute intervals just to not overwhelm the ISY). Setting it up to get the UDP broadcast would be dependent on use case requirements (I.E. do you see a need for that data at that interval?). It sounds like this is what you're looking for too. 2) is to connect to the WeatherLink server over the internet. The polling interval for this is much longer (15 minutes?). This also has a dependency on the internet. However, it could also be run from a cloud base Polyglot. Based on what I found, it sounds like they are updating the API for this method with the new API expected later this year. I'd rather postpone any work related to this until after the new API is releases, if something like this is desired. Do you have a local Polyglot set up? And if so, are you comfortable installing a node server from the command line?

Hi Gary, I don't believe anyone has created one yet, but from what I found searching on-line, it seems like it would be pretty similar to the WeatherFlow node server that I wrote. I don't think it would be too hard, but without direct access to a WL device, it can be a bit time consuming to debug issues getting getting it working. If you're willing to spend the time testing and providing feedback, I'll be happy to create one.

Did a bit more with the new module last night. I associated a Zooz water valve and it worked great. I then created a scene and controlled the value with an Insteon switch. I also re-oriented the ISY to vertical but still have issues communicating with my multi-sensor. The sensor is quite far from the ISY (and farther from any other z-wave device) but it did work well with the old module/external antenna combo.