I happen to use my ST setup as my alarm clock. It’s so much harder to hit snooze if your bedroom light is on! But because of random days off or late start days I’d have to keep modifying the routine. Thus GCal-Search is born. I created a Google Calendar and can stick events on it that my routines can deal with via virtual switches and/or contact sensors.
If the polling/scheduling continues to improve this should end up working out well. Thus far I’ve had it run all weekend looking at my calendars and it hasn’t failed yet. crosses fingers
The app works by creating sub-apps that have a virtual device with the contact and switch capabilities. This will allow you to select a single calendar per sub-app and also create a search string so that you can have it only look at events that match instead of all events. This allows me to have a single calendar that I look for entries for Holiday for one virtual sensor and a second one that looks for LateStart as a second sensor.
I use this in combination with RuleMachine and even Routines. So that my Rules/Routines don’t activate if the sensor/switch is open/on. And since it acts as a switch/sensor you can trigger other rules to happen at the time.
Why not use IFTTT?
- More customization and 1 less link in the chain that can break.
Installation with GitHub Integration:
To get the latest updates for GCal-Search, the best way is to enable the GitHub Integration in your IDE, and then:
- Go to My SmartApps in the IDE
- Click on Settings
- Click on Add New Repository
- Owner=mnestor, Name=GCal-Search, Branch=master
- Goto My Device Handlers in the IDE
- Repeat steps 2, 3, and 4
I have been bad about keeping this updated. @MichaelS has contributed a lot towards a better UI for us and fixing and refixing minor bugs dealing with the ST API. The updates aren’t anything required at this point (20160304) but you can never be too sure.
- 20160302.1 - Versioning information listed now
- 20160304.1 - Various UI changes
- 20160229.1 - UI/UX improvements and custom icons all contributed by @MichaelS
20160223.2 - Don’t make a quick change and forget to test
20160223.1 - Error checking - Force check for Device Handler so we can let the user have a more informative error