[Update: v1.3.0.0]
Version 1.3.0 is available in HPM and on Git.
This version has the complete skip/restore program logic and fixes the UI issue @JimB ran into which was a symptom of the incomplete restore piece.
Here's what else is new:
Highlights
What’s New in v1.3.0.0
-
Added the ability to restore skipped programs.
-
Fixed latent alert messages in the child driver attribute.
-
Completed work on the Astronomical cache. Events are now cached for a full week in advance. Astronomical based programs (dawn, dusk, etc) will continue to work even if the hub loses internet connectivity or the API is unavailable.
-
The notification system is finally complete! WET-IT now generates notification events for external delivery through the Hubitat Notifications app.
Notifications are not sent directly by WET-IT. Instead, the application publishes events that can be routed by the Notifications app to devices such as:
- Mobile Push Notifications
- Text Messages
- Speech Devices
- Voice Assistants
Notification Event Categories
WET-IT emits several types of notification events that can be subscribed to in the Notifications app.
| Event Type |
Description |
| Weather Alerts |
Freeze, rain, wind, and forecast availability notifications |
| Program Lifecycle |
Program start and completion events |
| Zone Activity |
Zone activation and shutdown events |
These event categories allow notification rules to be tailored to specific types of irrigation activity.
Example Notifications
Typical messages include:
Program Lawn Front now activeZone 3 now activeProgram Garden Beds completeWeather alerts clearedForecast data restored
These event notifications mirror the Rain Bird, Rain Bird has detected a rain event and Rachio's Rain Sensor Activated.
WET-IT has always acted upon these events and reported it in the attributes and JSON. This update lets WET-IT send them directly to the Hubitat mobile app and/or an SMS message without having to create a rule or piston to monitor the alerts.
It also sends alerts when various internal items are degraded (e.g., multiple forecast skips, child driver version mismatches, failed API calls, etc.).
The documentation to how to set up the Notification app is here and the Logging & Tools section has a direct link to the doc.
As an aside...
I had a huge 
event yesterday during testing. I have one program set up to use the Echo. Once I had the notifications in place, I was able to tell the Echo to “Turn on the sprinkler,” which it did and then announced back with the following verbal progress updates:
- Sprinkler now active. (Program Start)
-- Zone 1 now active. (Zone Start)
-- Zone 2 now active. (Next zone Start)
- Sprinkler is complete. (Program End - Watering complete.)
All of that with no webhook/Lambda/cloud middleware dependency beyond the built-in Echo skill and Notification app.
I don't see me using the voice control often but this sure beats Rain Bird's Echo skill requirement and having to say, “Alexa, ask Rain Bird to begin watering sprinkler.”
when you refer to the next N programs across multiple controllers. There's no way for WET-IT to see programming from another controller.
