I would like to see the rain sensor state in HS4 if possible, its visible on the web and in the app so would hope its possible
Announcement
Collapse
No announcement yet.
Could we add the rain sensor state please ?
Collapse
X
-
Here is a work-a-round I use and it works well.
I thought I would pass this along. Rachio has added to their API "RainSensorTripped:True/Flase". Now with the ability to couple the DEBUG Log as a file from the HS4 plugin setup coupled with a Log Parser ( I use BLLogMonitor) I have been able to read the debug log and look for the flag in the API. Every time the PI contacts Rachio, that is part of a large spill of data. I then created two events that look for the text. Both events ping/pong whether one or the other is active. So one event looks for FALSE (Rain sensor DRY), if it finds it, it does stuff and then activates the event that looks for TRUE and then deactivates itself. The other Event, now active, looks for TRUE and when it finds it, does stuff and then activates the FALSE event and deactivates itself. Last I have a timer that is evaluated when the sensor reports FALSE. If it hits three days, It irrigates the next morning. I water every three days unless it rains. This way, my schedule always floats waiting for 3 days of dry and then it waters. After watering the timer is reset. The timer is also reset when the Rain sensor gets a TRUE indication. This way if it keeps raining for 3 days straight, no watering. If it rains every two days, no watering, etc....
Thought I would pass it along.
-Nacman
-
Originally posted by mikee123 View PostI use Ultralog so should be able to do something similar. Just think it could be in the PI, I dont think we are the only ones who have Rachio and a connected rain sensor
Just had a look in my log. Searching for RainSensorTripped yields no results
I use the log with my log monitor. I also use Jon00 scripting event killer. I hate logs growing in size especially when using it as an evaluation log. So when the log monitor sees the event go true or false, it acts appropriately first, then kills the log monitor so I can then run a batch file and delete the log rachio produces. The TRACE log will get big fast depending on how often you are connecting/polling rachio. Once the log file is not locked, I can delete it, restore a "seed" log, restart the monitor and it doesn't skip a beat. In BLLogmonitor, if the PI is running and the log is deleted, it stops processing the logged events. But stopping it and then restarting it with the log present causes me no issue.
All this will be for nothing, except in not giving up :-) when this is written into the plugin. My floating schedue will still be needed, but I will be able to evaluate a device instead of a log entry. Snippet below
Comment
-
Here is a snippit from Rachio.txt in \Logs
Every 3 days end by 7:00 AM","cycleSoakStatus":"OFF","startDate":1597464000000,"name" :"Every 3 days","enabled":false,"startDay":15,"startMonth":8,"startYea r":2020,"totalDuration":4980,"etSkip":true,"cycleSoak":false ,"externalName":"Every 3 days"}],"serialNumber":"XXXXXXXX","macAddress":"XXXXXXXXXXX","on":t rue,"flexScheduleRules":[],"model":"GENERATION3_8ZONE","scheduleModeType":"MANUAL","de leted":false,"rainSensorTripped":false,"homeKitCompatible":false,"utcOffset":-14400000}],"deleted":false}
Comment
-
Originally posted by spud View PostI logged this as a feature request (PIR-5) and it will be probably added to the next version as it is easy to implement.
Comment
-
Originally posted by Nacman View PostHey there. I don't immediately upgrade to a newer versions but if you have released the updated plug-in to recognize the state of the rain sensor that would be a reason for me to upgrade. Can you advise if that's been done yet as you alluded to in your post?
Comment
-
Originally posted by Nacman View PostHey there. I don't immediately upgrade to a newer versions but if you have released the updated plug-in to recognize the state of the rain sensor that would be a reason for me to upgrade. Can you advise if that's been done yet as you alluded to in your post?
Comment
Comment