Thanks for your reply. It looks like it is the personal weather station that was not reporting any data(observations) on July 11th. The plugin gives an error anytime it is unable to so something to let you know it is having trouble. You should only be concerned if it keeps coming back, but it is an issue with that station.
I assume it is the same problem with Robert.
Also I hope in the future to include anhman’s changes
I am getting the error: VRainSensor : Error, precip section not found in conditions data.
My key is valid and I tried updating the precipitation data a few time with always the same error.
is it possible to fix it?
thanks
Is there a way to install two instances on my Edge? Otherwise I can’t see a way to have two trips: one short term with a low threshold and another with a longer term with a higher threshold.
I’ve been running Virtual Rain Sensor to fire two triggers, called “insufficient rain” and “sufficient rain” (based on my thresholds, using the past 2 days actual rain and the current and next day’s forecast rain). Those triggers in turn drive scenes which either turn off or on a Zwave switch that is in series with my lawn irrigation system timer relay. The net result is that I don’t irrigate if sufficient rain has occurred or is forecast.
This has been working great for some years now. But recently, I notice that it’s been throwing an error ever time it has run: “VRainSensor : Error, observation precip section not found in history data.” Looking back in the trigger history, it seems that this failure started on “pie day”, March 14 (03/14).
I saw some similar errors reported in this forum, that seemed to be fixed by updating the VRS’s WUG station or location so that a non-private reporting station would be used, so that WUG would provide the historical data. I’ve played around with this, using several different available stations by name, but always the same error … missing the historical data.
As I was poking around the WUG website’s API section, under my “Key settings” page, in the pricing options, they now have a “History add on?” header with a link to “Get in touch if you would like access to our history data.” Well I clicked on that link and followed the directions (as a free user with fewer than 10 hits per day to their API) to submit my request for history data for my API key. I filled in lots of information about how I’m using it in their Comments Section for that submission.
I don’t know how long it’s supposed to take for me to receive a response on this, but hopefully it will be quick and positive. I’ll update this posting once I get approval (or not), and whether or not it resolves my Virtual Rain Sensor error.
You can always store the data yourself for the few days of historical data you’re looking for. These services think they can extract money from everyone for every little thing and, in the end, they’ll realize they can’t…
I am not aware of any changes to the API but yes you need a developer API key that will allow access to the history section. There is no need to track anything locally. It will query the history for the station you select. There are sometimes problems when the station goes offline there will be missing information on the day and it will throw that error. It should show NA on the data tab for that day if I remember correctly. Let me know how it works out. This plugin should still work but I know there are changes on UI7 and this was developed on UI5.
This plugin should still work but I know there are changes on UI7 and this was developed on UI5.
FYI, I upgraded a few days ago from my Vera3 (UI5) to VeraPlus (UI7), and am happy to report that the Virtual Rain Sensor (version 3.2) is working beautifully.
My earlier “missing historical data” problem just went away on my Vera3 earlier. I’d forgotten to check when exactly it corrected itself. But in the meanwhile I purchased and set up my own weather station connected to the Weather Underground (https://www.wunderground.com/personal-weather-station/dashboard?ID=KFLPORTO34), which I may have automatically granted me “Historical Data” capability. I really don’t know what fixed it, but it’s fixed now anyway…
… and remains fixed in my upgrade to VeraPlus UI7. I have my Virtual Rain Sensor configured to check the prior 3 actual rain and future 3 day forecast, with a trigger on 0.5 inches total. And it’s working great.
Trying to update the Virtual rain Sensor, I have been using 2.2, on VeraLite and UI5.
Couldn’t figure out how to upgrade, so I decided to re-install. The uninstall button on the apps.mios.com page did nothing, so I decided to delete the app and install it again. Now the situation is virtual rain sensor is gone from my system, but the apps.mios.com page still reports that is is installed, and the uninstall button still doesn’t work.
I have a scene in UI7 that start my sprinklers at some time on the day on some days of the week. My scene has a simple trigger “schedule”
Now I know that you can add a specific code “to the trigger”, and here is where I liked to use the plugin.
I already have it installed and is giving me accurate info about the rain for the past 2 days.
So basically the condition hast to be to fire the trigger scheduled only if the Virtual Rain Sensor is not tripped.
My question is how this code will be, because I couldn’t make it work with the examples at the beginning of this thread
Thank you for the help
The following code I use to switch ON/OFF the sprinkler based on a start/stop schedule and treshold set in vrain plugin:
– Get current status sprinkler switch
local switch_status = luup.variable_get(“urn:upnp-org:serviceId:SwitchPower1”, “Status”, id_sprinkler)
– If switch is ON THEN switch it off
if (switch_status == “1”)
then
– Turn Sprinkler OFF
luup.call_action(“urn:upnp-org:serviceId:SwitchPower1”, “SetTarget”, {newTargetValue = “0”}, id_sprinkler)
return true
else
–Switch Sprinkler ON depending on vrain
–Force update virtual rain sensor(this step optional)
luup.call_action(“urn:upnp-org:serviceId:VRainSensor”, “Update”, {}, id_vrain)
–Get current state virtual rain sensor
local rain = luup.variable_get(“urn:micasaverde-com:serviceId:SecuritySensor1”,“Tripped”, id_vrain)
if (rain == “0”)
then
luup.call_action(“urn:upnp-org:serviceId:SwitchPower1”,“SetTarget”,{ newTargetValue=“1” },id_sprinkler)
– Register action in database
luup.call_action(“urn:micasaverde-com:serviceId:HomeAutomationGateway1”, “RunScene”, {SceneNum = “3”}, 0)
return true