It was a device I was using for testing to deal with some other issues that were fixed.
I went back to Initial Set-Up: un checked the device, clicked update, then clicked Update/Store Schedules .... , then Done. Not sure why its still tied to the app, it doesn't show on the config page.
I couldn't repeat that issue after removing a device and waiting for its previous trigger time to show up. Does it cause an issue with the existing devices or is it just a error log?
If I go here can see the old device still there in the source list but no schedule for it and not listed as in "DeVices" so it wouldn't have tried to trigger.
Did you happen to remove it after it turned on and before it could turn off?
EDIT: Even thought I couldnt't repeat the issue I might have a fix for removed devices sticking around in the source subscriptions. Uncomment line 555 to look like this.
It should trigger around 1900 eastern time.
Will report back.
I could not repeat this type of error so its tough to find. You make that change and update and hit done? Im sure there are situations I haven't tested so your feed back is valuable.
Since I cant repeat it maybe just delete this instance of app, open a new instance of the app and name it differently, configure, hit done.
Edit: can you confirm this device and others in the table are actually connected and working outside the app?
I just toggled it off on the device page and got one more error, I start a new instance.
As far as the other devices its kind of quirky the way they are working.
Zone 3 shows an on count of 4 and it should only be 2. Zone 4 shows a total time of 30 and it should only be 20.
Can I use this with a virtual switch, when it is turned on elsewhere, then have this turn it back off after a set duration?
Should work
@wes.hinchey I also have an app called "Automatic Timer" that will turn off a switch after a designated amount of time. I use this for several lights and virtual switches.
@kampto thanks fir this app. Was wondering if there's a way to leave 2 valves open when the rain sensor isolates the system due to rain. I have 2 garden beds under awnings that don't get any rain.
Thats doable, will see if I can find some time to tinker with the app.
In the short term you can install 2 different instances of the App with different names, "... Outside", "...Awning" or something like that and configure one to respond to rain or moisture pause triggers with the appropriate devices loaded.
That would be great. I ha an irrigation controller a few years ago that had a radio button on each valve that was on if a rain sensor was connected and you wanted to use it on a particular valve, you could turn it off to override that particular valve or not. The default was that it was on if the rain sensor was installed and you set it to be active. This could also be done for a moisture meter as I would think different parts of a garden would have different soil types and thus different moisture content. Thanks for looking into this.
Two new features added:
--Ability to select which devices use modes. Adds the ability to run schedules normally or have a single schedule you only want to run when away like a night security light. All within the same table.
--Ability to Ignore a pause cause. This allows to to more easily mix sprinklers and lighting in the same table. So if Ignore checked that device wont be paused say if your sprinklers moisture sensor threshold is reached. Requested by @greghoward1962.
I've tested parts of it but not everything yet. Ver 1.5.0
https://raw.githubusercontent.com/kampto/Hubitat/main/Apps/Switch%20Scheduler%20and%20More
Thanks very much @kampto I'll give a try when I get back from holidays.
Ha!!! Now that I added single mode(home, Away..) selection per devices I have a use case at home where I want different modes for different devices.... Need to think about how to make this new implantation, it never ends.. A drop down menu for modes in the table? No idea how to do that..
