rccoleman

It's a way to change the on-level of a responder in a scene. I use it to ensure that motion-controlled lights come on at night and not during the day, as shown here (first program). You could use that method by changing all of the levels of the devices in the scene periodically, but keep in mind that each "adjust scene" command involves changing a responder record in a device and sometimes those changes can be missed due to comms problems. Just a caveat. Do you mean turning the LED on that one button on and off? Add that button to a scene as a responder and turn the scene on and off to control the LED. I have several scenes with only a single button as a responder to do exactly that. Rob

I have a similar program and have found that it’s a little flakey in terms of whether it triggers and succeeds. To eliminate the uncertainty, I carry a laptop around with me to watch the writes happen and make sure they go through. Sometimes I have to walk through the same area a few times, and I’ve found that adding a short delay (like 2s) before writing updates tends to help.

I replace my baseboards with a taller version and had to use quarter round in some cases where I can run some wiring between the hardwood and the baseboard. I when I saw with and without, I asked him to add quarter round everywhere because it added some nice detail and broke up the large flat portion.

You’re not the only one: https://discussions.apple.com/thread/8090828. Are you using 11.2.1?

Bizarre. Mine’s not grayed out. I got nothin’.

And if you tap Filters at the top left?

Hmmm, it works for me on my iPad Pro running 11.2.1. You don’t see/get this?

It looks like it's an iPhone app (change the filter to see it) and runs in portrait mode if installed on the iPad.

Good to see it in the app store! Would you consider it to be compatible with the 5.0.x firmware? When I beta tested this earlier, I think you were still running 4.x and some things were a bit wonky with 5.0.x.

Zwave or Insteon door locks are examples of battery-operated devices that listen and respond to commands, but I agree that there don’t appear to be battery-powered relays for either system. There’s a lot of discussion about building your own on the SmartThings forums, such as this: https://community.smartthings.com/t/zigbee-zwave-control-for-any-battery-powered-device/43429/5

I had the same "not responding" problem yesterday morning (Sunday) when the same scene worked the night before (Saturday). Nothing short of unlinking the v3 skill and adding it back again solved the problem - I first tried forgetting all devices and rediscovering without success. I don't think that I had orphaned spokens, but I suppose that it's possible. I also notice that my devices all have "There was a problem" in a banner at the top of each device page in the iOS app, despite the fact that they seem to work fine. If I tap on the icon to toggle the device state, it works, the banner disappears, and then it returns in a second or so. None of the devices mention "offline". Rob

I'm still unclear as to whether you think it's a viable solution, but I'll leave it to the OP to evaluate.

So you're saying that he can't do what I'm suggesting? I don't see why not. If the ISY can't communicate with an Insteon device because the PLM is flaky or has failed, the polling will fail to respond as expected. The ISY can then send an email or push notification. This could be as simple as a heartbeat program that loops while turning a device on and off, a program that responds to the device turning on and off and changing a counter, and a watchdog program to detect an irregular count. It would be similar to the programs that monitor water sensors.

This is what he asked: Is there anyway I can poll the PLM periodically and send a message if the ISY doesn't get a proper response? The answer to that is "no", but he can poll a device (set status and query) and send an email or push notification from the ISY if it doesn't act as expected. From your responses, it sounds like you're trying to solve the problem of the ISY dying. As long as the ISY doesn't commit suicide and go into safe mode if the PLM fails, it'll continue to work just fine and be able to send notifications through the network about unexpected behavior that it sees with Insteon devices. There's no mention of Z-Wave in the original message, so I don't see how that enters into this.

He's specifically asking about how he can detect a failing PLM, so it doesn't sound like Z-Wave is part of the equation here. If he uses the ISY firmware that won't go into safe mode when it can't communicate with the PLM, it would be able to attempt to communicate with Insteon devices and send a notification if it was unable to do so.

Couldn't a program try to set and query a hidden lamplinc or something similar? Loop to retry a few times to handle any comms issues.

That requires a substantial investment in Mobilinc and an additional purchase of the geofence module, while this is free. I do have Mobilinc, but chose not to rely on their geofence solution because I’ve generally found them to be unreliable. That was my original motivation for moving to this, but I’ve since transitioned to the free Locative app that has reliable geofence support and a more friendly interface. I think that the problem with most geofence apps is that they’re likely to crash when they trigger due to issues around network reliability, and this works around that by relying on Apple’s presumably hardened Find my iPhone service. I certainly see this problem with IFTTT geofences, and they almost never work properly for me. Maybe Mobilinc is more reliable, but this is a free alternative that takes a new and creative approach.

Ah, yes. I have a bunch of echoes and Dots, so it was buried in Settings.

It’s not actually under the Settings section, but it’s a top-level item (and peer to Settings) in the menu (hamburger icon). At least that’s where it is in iOS.

That’ll be a great feature! I’ve already set up Good Morning and Good Night. Thanks for the heads up.

I’m using Locative now, but 2FA was working fine for me with this script a while ago.

Coincidentally or not, two of my 5 leak sensors have given me a "missing heartbeat" alert twice yesterday after being quiet and happy for quite a long time. It doesn't seem like those log messages would be related, though. Mine are all fine now, and looking at the status variables I see that I forgot to init the latest one to 1 and that may look like a failure after a reboot of the ISY994. Under normal conditions, "missing heartbeat" could indicate that the battery died (which should take 10 years) or it malfunctioned in some way. I would go hit the button on the top and see if the green light shows up. Rob

Just pull the power, wait a few seconds, and plug it back in.

I do wish that the dialog box was clearer about what it's busy doing. Sometimes it's hard to tell if it's timing out waiting for something to happen, or if it's actually busy working. And there's no way to stop it, so you just have to sit and wait for it to finish whatever it's doing. It could be more transparent about what's going on, and that might help diagnose problems.

They've started contacting me when I report that Alexa didn't understand me (even when I don't check the box), but I don't know if that's due to increased interest from customer service or my long history of reporting these issues. Amid a sea of words, the two meaningful suggestions that they've made are to re-do the voice training that I did some time last year and to rename the problematic words to a more distinctive term (they suggested "night mode" rather than "night", which often conflicts with "light"). They also said that my devices were still under warranty and could be replaced for free in case they're defective, but this doesn't seem to be a hardware problem. Swearing at it makes me feel a little better (and results in the humorous "Sorry, I can't find f<beep> you"), but it doesn't help it respond correctly Rob