Time based events failing?

@JDRoberts What are your reasons for preferring zigbee with Z-Wave instead of all Z-wave?

I’m ambivalent.

While I totally empathize that a lot of really good and skilled people are just not good at ā€œCustomer facingā€ roles (perhaps myself included … I don’t always rub folks the right way, obviously :speak_no_evil:) … I have read enough examples of this strategy being successful that I think the benefits may outweigh the discomfort.

There is a spectrum of possible strategies… Perhaps Customer facing rotations would only be used for (line level development & operations) managers who, in general, ought to have more rounded skillsets than the engineers in the trenches. Or engineers could be assigned in a ā€œread-only / listen-in modeā€, such that they are required to be familiar with the actual experiences voiced by Customers, but be paired with customer support communication specialists who handle the actual response communication as usual.


Something about SmartThings’s organizational structure and/or management strategy is failing to prioritize and accurately address / fix issues, bugs, and features that we here constantly highlight. Is it internal communication failure? Lack of goal alignment? Or alignment to milestones and a long-term strategy that ā€œweā€ just don’t know enough about and don’t agree with the visible short-term consequences?

That last point is the biggest risk / drawback to regularly giving engineers Customer facing exposure: they may become frustrated or disillusioned with the projects and goals they are assigned if these suddenly don’t appear to be directly beneficial to those Customers. In other words… Yup… Don’t read the comments section / Amazon Reviews / Community Forum. :cry:

1 Like

Everybody has their own preferences. I’ve talked about this before in the forums.

Zigbee devices are typically smaller with better battery life. They’re also a little better getting signal through rain, although zwave has a slightly longer range overall.

There is the issue of potential WiFi interference (which you don’t get with Zwave), but with sensors it’s usually easy to reposition them to avoid the interference. I have a zwave doorlock in part because I knew I wasn’t going to be able to just move it two feet to the left and I knew I’d need a strong wifi signal in that area for security cameras.

I’m also interested in seeing what happens with Thread (the same device can transmit both Thread and Zigbee messages) although that’s still future maybe maybe stuff.

Mostly battery life really. But it’s a case by case evaluation for me. I like to have the choice. :sunglasses:

I have been following this thread but I was not having any recent time based failures.

That is until this morning. Good Morning did not run at it’s scheduled time. Apparently this issue is spreading. =(

I had my good night routine not fire again last night for the second night in a row. I just performed @tslagle13’s temp fix of changing the time and then changing it back. Hopefully that will fix it, if not I will send in a ticket. I’m just glad I am not in this alone, either way I am sure it will be fixed soon.
Scott

Events are not firing again this morning. Opening another ticket.

I take it the attempt to fix this would be adjust time, save, test? My Good Morning, Good Night, and Time based Smart Light apps all last worked on Friday.

I just adjusted the time on all of them and saved.

It would be great if under the announcements, ST could acknowledge some of these issues and potential work arounds/fixes.

All my timing is working just fine. I wonder what exactly the issue is here, a particular server, particular accounts, certain device types?

1 Like

My pool pump stopped running after the update so it created quite a big headache for me. The lights not coming on at dark was just a minor inconvenience.

I just adjusted time for the time-bases Smart Lighting, and it worked. I will adjust Good Morning and Good Night to five minutes from now to watch and test them.

Made two attempts to adjust ā€œGood Morningā€ routine start time. Neither attempt worked. I thought I was on to something when I realized I could swipe to delete the time setting in the routine, vs adjusting it. I tried both, and saved, but neither fired.

Sigh. My enthusiam for ST has faded fast. No multi user, no reliable time based triggers, (barely) no local processing on v2.

Good Morning! triggered based on Things started happening. The app still showed ā€œNightā€ mode till I killed the app and restarted. Lights off at specific time did not trigger.

Update: Changed the time by a few minutes and saved it. Looks like it triggered.

I deleted ā€œGood Morning!ā€ and created a new one (Gooder Morning) and the time based trigger worked. Renamed it back, and set for the updated real time, and will see if it works tomorrow.

I guess I’ll try the same approach with Good Night.

Just wanted to get back to you and say thanks - it worked perfectly! From the tone of your message, it sounds like this is a known issue (at least to you). It’s kind of odd to see the virtual switch in the On state and the actual switch Off, but it all works fine.

Sorry I didnt get back to you sooner but it looks like you figured it out. From what I remember he said to change it by a minute, save, then change back and save.

Are the time trigger issues limited to this, or are other time events also having issues? What I mean is for ā€œTurn off after motion stopsā€, and choosing ā€œAfter this number of minutesā€ and setting it to 5 for example. Are there cases of these time triggers also broken?

I am having issues with ā€œturn off after number of minutesā€ Started last Thursday and is hit or miss if it will work.

I have a time-based routine that adjusts my thermostat if someone is staying home past a certain time. I have had to delete and re-create it about three times in the past because it simply stopped working. At some point over the last few days, it stopped working yet again.

I’ve also noticed that some of my lights aren’t turning back off when motion stops. I was sick this weekend and didn’t feel like troubleshooting them. Looks like these issues are related.

Instead of opening another ticket you can just respond to your current ticket with additional details. Multiple tickets for the same issue makes response times slower for everyone.


On a side note: Gonna dig into this today. I’ll update you guys when I have something.

3 Likes

Ok all, I have this list so far for data points. Are there any other data points you have seen that I am missing?

  • Seems to affect routines more than other smartapp schedules
  • sunrise/sunset are affected for some users
  • Changing the original schedule to a new time (+/- 1 minute) can solve a schedule issue but most people find the schedule fails again in a few days.

EDIT: Keep this specific to time based events failing

3 Likes