Jump to content

Rainmachine request

paulbates

By paulbates
in NodeLink

Recommended Posts

paulbates Advanced

paulbates

Posted
Posted

Hey io_guy

I'm requesting adding a couple values from the rainmachine API, adding to the main rainmachine node. Its for qpf - quantitative precipitation forecast.

Its 0 for no rain forecast, or a number (##.##) if there is rain forecast. Qpf is value in the json located under /api/4/mixer/YYYY-MM-DD   
I'm requesting the current day, day -1 (yesterday) and day -2 (day before yesterday)  be populated as QPF fields under the main rainmachine node.

The purpose is I've had problems this summer, where WX (both NOAA in the RM and other sources) say there will be a lot of rain in my area, and none falls directly on my property. The RM mixer hedges on qpf and does not run the program. I've had a 4 day stretch currently and the lawn is starting to brown out.  A rolling 3 day view will catch that happening.

I have rain guage and track what actually fell in the ISY to compare to qpf by adding the 3 together, compare to a value and have the ISY re-run it. TBH I'm going to have to use it a bit to tune it for the right value and issuing commands to the RM by observation and the values that show up. By looking at my RM I have something to start with.

In ISY IF statements, I can use '>' to decide to have the RM run it again.

Paul

 

paulbates Advanced

paulbates

Posted
  • Author
Posted

Thanks!

There is a value under /program (futurefield1) that describes what sounds sorta like the same thing but worded differently. I didn't have luck getting values from my RM for it or a good explanation of what would actually get presented as data. Kicked a few messages back and forth with RM tech support -- they couldn't explain it.. And because its called futurefield1, i saw comments it would be renamed at some point.

Paul

  • 2 months later...
paulbates Advanced

paulbates

Posted
  • Author
Posted

Hey io_guy

Thanks for the weather/qpf values from the rainmachine. It rained yesterday and today so they have good values I can compare to. Once I determine the values that work for me I'll post how I'm using them

Paul

  • 2 weeks later...
paulbates Advanced

paulbates

Posted
  • Author
Posted

io guy

I have one to report with the QPF values. In the admin console, the last values stay are reported until the Nodeserver is restarted. It can be over a number of days. Once I restart nodelink and query the node, its fine. The rainmachine can be controlled by the AC, I can turn on master valve and here them click.

Here's the log I came home to: <both logs set with RM at debug logging level> 

2019-11-03 07:42:37 - ISY NodeLink Server v0.10.0 started
2019-11-03 07:42:37 - OS: Linux Nodelink 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
2019-11-03 07:42:37 - Web config server started (http://REMOVED)
2019-11-03 07:42:38 - ISY resolved to REMOVED (5.0.16)
2019-11-03 07:42:38 - ISY Node Server config detected (profile 1)
2019-11-03 07:42:39 - Auto-Update: Error updating file: The remote server returned an error: (404) Not Found.
2019-11-03 07:42:39 - ISY Warning: Duplicate node names exist on the ISY (Couch Lamp)
2019-11-03 07:42:39 - ISY Warning: Duplicate node names exist on the ISY (Attic Light)
2019-11-03 07:42:39 - ISY Warning: Duplicate node names exist on the ISY (Table Lamp)
2019-11-03 07:42:39 - ISY Warning: Duplicate node names exist on the ISY (Recessed)
2019-11-03 07:42:39 - ISY Warning: Duplicate node names exist on the ISY (Sink)
2019-11-03 07:42:42 - Relay Server: Started on port 2405
2019-11-04 04:00:01 - Auto-Update: Error updating file: The remote server returned an error: (404) Not Found.
2019-11-05 04:00:00 - Auto-Update: Error updating file: The remote server returned an error: (404) Not Found.
2019-11-06 04:00:00 - Auto-Update: Error updating file: The remote server returned an error: (404) Not Found.
2019-11-07 04:00:00 - Auto-Update: Error updating file: The remote server returned an error: (404) Not Found.
2019-11-08 02:45:47 - Venstar: Get Error - Timeout [venstarus]
2019-11-08 02:45:58 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-08 02:46:04 - Venstar: Get Error - Timeout [venstarfr]
2019-11-08 02:46:06 - ISY Error: Timeout from the ISY (ns/1/nodes/n001_isydata/report/status/GV2/46/25) [5]
2019-11-08 02:46:17 - Venstar: Get Error - No route to host [venstarus]
2019-11-08 02:46:22 - RainMachine: Web Error - No route to host [rainmachi]
2019-11-08 02:46:37 - Venstar: Get Error - No route to host [venstarfr]
2019-11-08 02:46:46 - RainMachine: Web Error - No route to host [rainmachi]
2019-11-08 02:46:47 - Venstar: Get Error - No route to host [venstarus]
2019-11-08 02:47:10 - RainMachine: Web Error - No route to host [rainmachi]
2019-11-08 02:47:11 - Venstar: Get Error - No route to host [venstarfr]
2019-11-08 02:47:17 - Venstar: Get Error - No route to host [venstarus]
2019-11-08 02:47:31 - RainMachine: Web Error - Network is unreachable [rainmachi]
2019-11-08 02:47:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_isydata/report/status/GV3/448008/25)
2019-11-08 02:47:44 - Venstar: Get Error - No route to host [venstarfr]
2019-11-08 02:47:44 - Venstar: Get Error - Network is unreachable [venstarus]
2019-11-08 02:47:44 - Venstar: Get Error - Network is unreachable [venstarus]
2019-11-08 02:47:55 - RainMachine: Web Error - No route to host [rainmachi]
2019-11-08 02:48:14 - Venstar: Get Error - No route to host [venstarus]
2019-11-08 02:48:45 - Venstar: Get Error - No route to host [venstarus]
2019-11-08 04:00:00 - Auto-Update: Error updating file: The remote server returned an error: (404) Not Found.
2019-11-08 08:01:29 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-08 08:02:19 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-08 08:04:14 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-09 04:00:00 - Auto-Update: Error updating file: The remote server returned an error: (404) Not Found.
2019-11-09 07:13:50 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-09 07:14:16 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-09 07:15:31 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-09 07:15:57 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-09 07:16:23 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-10 04:00:00 - Auto-Update: Error updating file: The remote server returned an error: (404) Not Found.
2019-11-10 08:15:27 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-10 08:15:53 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-10 08:16:45 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-10 17:13:22 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-10 18:46:17 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-11 04:00:00 - Auto-Update: Error updating file: The remote server returned an error: (404) Not Found.
2019-11-11 08:19:16 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-11 08:19:43 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-11 13:15:10 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-11 13:15:57 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-11 15:14:53 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-11 15:15:22 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-11 15:15:48 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-11 15:16:16 - RainMachine: Web Error - Timeout [rainmachi]
2019-11-11 15:16:45 - RainMachine: Web Error - Timeout [rainmachi]

Here is after restarting nodelink: 

2019-11-11 15:44:02 - ISY NodeLink Server v0.10.0 started
2019-11-11 15:44:02 - OS: Linux Nodelink 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
2019-11-11 15:44:02 - Web config server started (http://192.168.0.102:8090)
2019-11-11 15:44:03 - ISY resolved to 192.168.0.99 (5.0.16)
2019-11-11 15:44:03 - ISY Node Server config detected (profile 1)
2019-11-11 15:44:04 - Auto-Update: Error updating file: The remote server returned an error: (404) Not Found.
2019-11-11 15:44:04 - ISY Warning: Duplicate node names exist on the ISY (Couch Lamp)
2019-11-11 15:44:04 - ISY Warning: Duplicate node names exist on the ISY (Table Lamp)
2019-11-11 15:44:04 - ISY Warning: Duplicate node names exist on the ISY (Recessed)
2019-11-11 15:44:04 - ISY Warning: Duplicate node names exist on the ISY (Attic Light)
2019-11-11 15:44:04 - ISY Warning: Duplicate node names exist on the ISY (Sink)
2019-11-11 15:44:07 - RainMachine: Response data - {"access_token": "REMOVED", "checksum": "REMOVED", "expires_in": 157680000, "expiration": "Sat, 09 Nov 2024 20:44:07 GMT", "statusCode": 0}(P) [rainmachi]
2019-11-11 15:44:07 - Relay Server: Started on port 2405

 

This is not high priority for me as there's snow on the ground right now :D

Paul

io_guy Advanced

io_guy

Posted
Posted

Sorry, what do you mean by last values stay are reported?  I'm not clear what the issue is?  Are you saying the QPF values never update?

glarsen Advanced

glarsen

Posted
Posted

I notice that the QPF values seem to be reversed.  The QPF (2 days ago) displayed on the admin console is the number shown on the Rainmachine graph for today.  The numbers for today and yesterday are both 0 so I can't tell whether they are correct or not.

 

Thanks!

io_guy Advanced

io_guy

Posted
Posted
1 hour ago, glarsen said:

I notice that the QPF values seem to be reversed.  The QPF (2 days ago) displayed on the admin console is the number shown on the Rainmachine graph for today.  The numbers for today and yesterday are both 0 so I can't tell whether they are correct or not.

 

Thanks!

Yep, you're right.  I'll fix that shortly.

paulbates Advanced

paulbates

Posted
  • Author
Posted
11 hours ago, io_guy said:

Sorry, what do you mean by last values stay are reported?  I'm not clear what the issue is?  Are you saying the QPF values never update?

When I use the AC to look at the values on a certain day, close the ac and go back later, the same values remain there until I restart the NS. I tried removing / reinstalling the  node, I'll give that a day and see what happens

Paul

paulbates Advanced

paulbates

Posted
  • Author
Posted

@io_guy 

 

I see what's happening. My Nodelink hasn't updated since initial install and is at 10.0.  I reset the autoupdate time a few times and I'm getting this. config.xml seems clean to me

  

2019-11-13 18:29:27 - ISY NodeLink Server v0.10.0 started
2019-11-13 18:29:27 - OS: Linux Nodelink 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
2019-11-13 18:29:27 - Web config server started (http://x)
2019-11-13 18:29:28 - ISY resolved to x (5.0.16)
2019-11-13 18:29:28 - ISY Node Server config detected (profile 1)
2019-11-13 18:29:29 - Auto-Update: Error updating file: The remote server returned an error: (404) Not Found.
2019-11-13 18:29:29 - ISY Warning: Duplicate node names exist on the ISY (Attic Light)
2019-11-13 18:29:29 - ISY Warning: Duplicate node names exist on the ISY (Sink)
2019-11-13 18:29:29 - ISY Warning: Duplicate node names exist on the ISY (Recessed)
2019-11-13 18:29:29 - ISY Warning: Duplicate node names exist on the ISY (Couch Lamp)
2019-11-13 18:29:29 - ISY Warning: Duplicate node names exist on the ISY (Table Lamp)
2019-11-13 18:29:32 - RainMachine: Response data - {"access_token": "x", "checksum": "x", "expires_in": 157680000, "expiration": "Mon, 11 Nov 2024 23:29:32 GMT", "statusCode": 0}(P) [rainmachi]
2019-11-13 18:29:32 - Relay Server: Started on port 2405
2019-11-13 18:33:59 - Auto-Update: Error updating file: The remote server returned an error: (404) Not Found.
2019-11-13 18:35:00 - Auto-Update: Error updating file: The remote server returned an error: (404) Not Found.

 

Maybe if I got the link to the latest nodelink.exe, I could replace it.

Paul

paulbates Advanced

paulbates

Posted
  • Author
Posted

That did it. Thanks!

Also, I set the autoupdate time to be a minute in the future. It ran, no 404. Wondering if it was something in 10.0?

Paul

  • 8 months later...
GDavis01 Advanced

GDavis01

Posted
Posted
On 8/14/2019 at 8:02 PM, paulbates said:

Hey io_guy

I'm requesting adding a couple values from the rainmachine API, adding to the main rainmachine node. Its for qpf - quantitative precipitation forecast.

Its 0 for no rain forecast, or a number (##.##) if there is rain forecast. Qpf is value in the json located under /api/4/mixer/YYYY-MM-DD   
I'm requesting the current day, day -1 (yesterday) and day -2 (day before yesterday)  be populated as QPF fields under the main rainmachine node.

The purpose is I've had problems this summer, where WX (both NOAA in the RM and other sources) say there will be a lot of rain in my area, and none falls directly on my property. The RM mixer hedges on qpf and does not run the program. I've had a 4 day stretch currently and the lawn is starting to brown out.  A rolling 3 day view will catch that happening.

I have rain guage and track what actually fell in the ISY to compare to qpf by adding the 3 together, compare to a value and have the ISY re-run it. TBH I'm going to have to use it a bit to tune it for the right value and issuing commands to the RM by observation and the values that show up. By looking at my RM I have something to start with.

In ISY IF statements, I can use '>' to decide to have the RM run it again.

Paul

 

I recently bought a RainMachine HD16 that I have started playing with... I am using Wunderground and METNO as my weather services. NOAA wouldn't work for me here in Canada!

I set it up in NodeLink and I am confused about the QPF values! 

The ISY Weather node reports the QPF values as follows: Today as 2.1; Yesterday as 0.18; 2 Days Ago as 1.9  (this is on July 14th)

However when I look at the RainMachine API with /api/4/mixer/YYYY-MM-DD I see the QPF value for Today (July 14th) as 0;  and Yesterday (July 13th) as 1.05; 2 Days Ago (July 12th) as 0.18, and 3 Days Ago (July 11th) as 1.9! It appears the Yesterday and 2 Days Ago values are off by a day and I have no explanation of today's value!

Am I reading the data correctly? Should the QPF values in the Weather node be the Mixer values? 

Out of curiosity, given that the RainMachine API allows access to so much weather data, why have I not seen requests to add other metrics to NodeLink ?

 

EDIT  I started wondering if the Weather node was not being updated which would explain why the data in the node was stale... so I restarted NodeLink and the node is now showing the correct QPF values!! So it appears that it's only the Weather node that isn't updating, because the heartbeat for the RainMachine was okay!! 

GDavis01 Advanced

GDavis01

Posted
Posted

@io_guy  it appears that I am having an issue with the RainMachine Weather node! The node, with the QPF values, doesn't update until I restart NodeLink! (You might remember that in the another thread I had raised the issue that I was originally having problems with the setup of the Weather node and that it was causing the RainMachine heartbeat to stop... but then for some reason, when I got back to my cottage and tried again, I was able to set up the Weather node and everything seemed okay... perhaps this is related!)

I set the RainMachine and the Main tab to 'debug'... here is the log (the log seems sparse... shouldn't there be a regular polling for the RainMachine heartbeat showing up in the log?) 

2020-07-14 22:13:58 - Relay Server Error: Error: OnClientConnection - Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'.
2020-07-14 22:13:58 - DSC Error: Data Arrival Init - Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'. [dsc1]
2020-07-14 22:14:00 - ISY resolved to 10.0.2.141 (5.0.16C)
2020-07-14 22:14:00 - ISY Node Server config detected (profile 1)
2020-07-14 22:14:02 - WeatherFlow: UDP (10.0.2.96:50222) - {"serial_number":"SK-00012738","type":"rapid_wind","hub_sn":"HB-00010608","ob":[1594779242,0.00,0]}[flow1]
2020-07-14 22:14:02 - WeatherFlow: UDP (10.0.2.96:50222) - {"serial_number":"SK-00012738","type":"rapid_wind","hub_sn":"HB-00010608","ob":[1594779242,0.00,0]}[flow1]
2020-07-14 22:14:02 - Relay Server: Started on port 2405
2020-07-14 22:14:03 - RainMachine: Response data - {"access_token": "f2303a7d22f4c8122376d1c2aeff1a190660b0515bbebd6b8622058b", "checksum": "ee04050236b4685efdebfd69a14680011d2fa0c1953de83a61663346b8cfaf50812b2091ef7807ffd79442affe062f1cb9c4baba6a5eace9", "expires_in": 157680000, "expiration": "Mon, 14 Jul 2025 02:14:03 GMT", "statusCode": 0}(P) [rain1]
2020-07-14 22:14:05 - WeatherFlow: UDP (10.0.2.96:50222) - {"serial_number":"SK-00012738","type":"rapid_wind","hub_sn":"HB-00010608","ob":[1594779245,0.00,0]}[flow1]
2020-07-14 22:14:05 - WeatherFlow: UDP (10.0.2.96:50222) - {"serial_number":"SK-00012738","type":"rapid_wind","hub_sn":"HB-00010608","ob":[1594779245,0.00,0]}[flow1]
2020-07-14 22:14:06 - WeatherFlow: UDP (10.0.2.96:50222) - {"serial_number":"HB-00010608","type":"hub_status","firmware_revision":"49","uptime":22427,"rssi":-39,"timestamp":1594779246,"reset_flags":"BOR,PIN,POR","stack":"1224,1080","seq":2184,"fs":"1,0"}[flow1]
2020-07-14 22:14:06 - WeatherFlow: UDP Data Error - Expecting state 'Element'.. Encountered 'Text'  with name '', namespace ''.[flow1]
2020-07-15 08:44:02 - DSC TCP: No poll response, attempting to reconnect to alarm [dsc1]
2020-07-15 08:44:02 - DSC: Reconnecting To Server [dsc1]
2020-07-15 08:44:02 - DSC Error: Data Arrival Init - Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'. [dsc1]
2020-07-15 08:44:02 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1]
2020-07-15 08:44:32 - DSC: Reconnecting To Server [dsc1]
2020-07-15 11:14:07 - Relay Server Error: Error: OnClientConnection - Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'.
2020-07-15 11:14:07 - DSC Error: Data Arrival Init - Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'. [dsc1]
2020-07-15 11:14:09 - ISY resolved to 10.0.2.141 (5.0.16C)
2020-07-15 11:14:09 - ISY Node Server config detected (profile 1)
2020-07-15 11:14:11 - Relay Server: Started on port 2405
2020-07-15 11:14:12 - RainMachine: Response data - {"access_token": "3627395b961774cb0a90a6d33813200df4e413e5bfa95913b1d80d27", "checksum": "42affe0c4baba65efdebf166334680011d2b8cfaf53de83a6236b468d69a14691ef78062f1cb97ffd7940812b20fa0c195ee04050a5eace9", "expires_in": 157680000, "expiration": "Mon, 14 Jul 2025 15:14:12 GMT", "statusCode": 0}(P) [rain1]

The QPF values on the ISY Weather node only updated this morning, after I restarted NodeLink at 11:25am. Do you know why this is happening?

 

I also note that when I restart NodeLink, with Debug enabled, I seem to get the following 2 errors , is this normal?

2020-07-15 11:25:58 - Relay Server Error: Error: OnClientConnection - Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'.
2020-07-15 11:25:59 - DSC Error: Data Arrival - Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'. [dsc1]
 

Thanks...

 

paulbates Advanced

paulbates

Posted
  • Author
Posted
On 7/14/2020 at 2:27 PM, GDavis01 said:

Out of curiosity, given that the RainMachine API allows access to so much weather data, why have I not seen requests to add other metrics to NodeLink ?

Nodelink users have to have a need, find the appropriate data point in the API to support it and define how to use it, and make a specific request that io_guy can design around and implement practically in nodelink.

You can certainly make these requests to io_guy, he always listens and responds. The rainmachine does 90% of what I need all on its own, and the few watering problems I've observed were solved with the requests I've already made, I don't anticipate asking for anything else.

GDavis01 Advanced

GDavis01

Posted
Posted
On 7/16/2020 at 8:49 AM, paulbates said:

Nodelink users have to have a need, find the appropriate data point in the API to support it and define how to use it, and make a specific request that io_guy can design around and implement practically in nodelink.

You can certainly make these requests to io_guy, he always listens and responds. The rainmachine does 90% of what I need all on its own, and the few watering problems I've observed were solved with the requests I've already made, I don't anticipate asking for anything else.

I agree with your points... I only recently acquired my RainMachine and it will take a while before I figure out how I want to best use it. My comment was because I felt like a kid in a candy store when I saw all the weather data available through the API! I am also in the process of setting up my WeatherFlow weather station and I am seeing access to more weather data through their API! So, as I figure out where I am headed, I may make requests of io_guy or write some Python scripts and grab the data I want. 

Back in November you wrote "Once I determine the values that work for me I'll post how I'm using them" I would appreciate understanding how you use them and whether you are using ISY or RainMachine programs.

Bumbershoot Advanced

Bumbershoot

Posted
Posted
56 minutes ago, GDavis01 said:

I am also in the process of setting up my WeatherFlow weather station and I am seeing access to more weather data through their API!

Have a look here if you're interested in getting your WeatherFlow data to your Rainmachine:

https://github.com/sprinkler/rainmachine-developer-resources/blob/master/sdk-parsers/RMParserFramework/parsers/wf-parser.py

 

Archived

This topic is now archived and is closed to further replies.

Go to topic listing
×
×
  • Create New...