@bravenel any ideas? The issue is still occurring
Need to see logs for the app -- use screenshots only.
They should both have switched at 2330 but they didn’t. Some other events did trigger during the day.
Eg this one missed the switch at 0900, 1530 and 2330 but did hit 0630 and 1700
Device logs don't tell anything about the app. If you want help, you have to post the app logs. for a period when it is supposed to do something. Also, post the Scheduled Jobs from the App Status page (gear icon).
Sorry yes I realised that after I posted it and edited the post above to replace with app logs. Here’s the scheduled tasks.
Go into the app itself, turn on debug logging and post those...
Any ideas what I should do? Is there a way to force it to recreate the scheduled tasks?
Just open the app and hit Done. Then look at the Scheduled Jobs at the bottom of the App Status page.
I will dig in further....
Today i tried cloning the thermostat scheduler child, and the cloned app also does not correctly follow the programmed schedules.
Is there anything i can do to collect more logs? Leaving the heating running all day in empty rooms is starting to get expensive with winter approaching!
I can confirm that cloning Thermostat Scheduler 2.0 does not establish its schedules correctly.
I updated to 2.3.4.116
Then I tried reinitialising the app, and tried cloning it again, and its still not working:
first, the clone i created yesterday. I tried "reinitialising" it by going in and pressing "done" this morning but it hasnt added scheduled tasks:
I updated tI tried cloning that again this morning:
i have the json of the exported app. Would it help you? i cant attach it here as .json isnt an allowed file type.
As for the away mode with Eco setting, this morning all worked as planned, I'll do some simulations during the day for different scenarios and will report back if I see something wrong.
Thanks!
This is a confirmed bug. See Known Issues in Release 2.3.5.152
Fix in the next release. When it comes out I would suggest that you open each of these actions as if to edit it, and just hit Done Editing -- that will fix the internal problem. Also, if you want, as interim work-around you could put two of these actions each in their own rule, just as a single action, and run those rules from the main one. Right now, as you've discovered, only a single Set Thermostat Scheduler actions in a given rule.
1 Like
happy to wait if i know the fix is on the way. This is a new feature, i'm just happy that it was added and that you're so responsive to issues.
I’m now on 2.3.4.117
Through trial and error I’ve discovered that thermostat scheduler fails to set schedules when a variable is used as the temperature. For example, with variables (and after hitting done)
If I remove the variable temperatures and hit done:
Here’s the device logs:
See this:
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
