Hello,
I'm looking for some guidance on my first triggercmd application.
Background: I run an automated sports facility that uses TPlinkKasa's to turn on and off projectors. My current method uses "schedules" in TPlink Kasa's API to follow bookings and changes in bookings. The issue is that Kasa only allows schedules up to 7 days in advance and also triggers are every minute, so the device cannot turn off at HH:MM:SS (ie (07:00:00), and then turn on at (07:00:01) . instead, the devices need to turn off at 07:00:01 and then turn on at 07:01:00 . You can see how this creates a problem for extended bookings or any back to back bookings where people dont want that 1 miute delay. Also when someone books at 7am, they expect to start at 7am , not 7:01am.
I was thinking the solution for this, and also the "max 7 days advance booking" problem, is to use kasa via Alexa, via TriggerCMD.
I understand the workflow, I just dont know how to set this up, as I'm no coder at all.
- new skedda booking
- pull data of booker, phone number, start time, end time, projector #
- put this all into a google sheets data base
- have triggercmd send a command to alexa to turn the specific projector # at the specific time.
- IF a booking is cancelled, or gets editted, then I would receive an email.
- Parse that email for the new information and update the start / end times.
- If the booking is cancelled, then delete the row, and triggercmd wont run at all.
- when the end time happens, then trigger a new alexa command to turn off the projector.
- if there is a back to back booking, immediately turn the projector back on.
[OR , use some webscraper to check to see if theres a back to back booking, and if there is, then skip turning off the projector]
Any help is appreciated!!