ISY Newbie

You solved it! I checked "Use SNI" box and changed the mode to "C Escaped" from the previous "URL Encoded", and everything is working now! It is strange though. I do not remember ever changing those settings. Well, the important thing is that it's working now. Kudos to you! 👏👏

Mmm. Maybe it's because I'm paying IFTTT the bare minimum when they accepted voluntary pricing? 😄 Attached is the screenshot from the Network Resource Editor. Anything off you see in there?

Yes, I have other network resources besides IFTTT. Pushover, for one, which is working fine. It is as if IFTTT is refusing to let my ISY reach its server.

I've followed your instruction, but mine still doesn't work. In the Resource Response window that pops up upon testing, all I see is N/A.

The webhooks that I created under the Network Resources tab seem to have stopped working. Is anyone else experiencing the same problem?

Factory-resetting these dimmer switches is a real pain. You need fine-toothed tweezers to be able to pull out that set button. Even then, it requires fine motor skills. Really bad design from engineering viewpoint. Is there an easier way?

Yes, there is "options" button at the bottom, but it doesn't reveal a "beep" setting for a dimmer switch. I'll upgrade to v.5 and see if it makes a difference.

Is that from Firmware v.5? My admin console looks nothing like that. Mine is missing the Beep option altogether.

I've linked a Dual Band SwitchLinc Dimmer Switch v.45, and after being linked, it beeps when manually controlled. Before being linked to Isy, that wasn't how it behaved and there was definitely no beep. How do you get rid of the beeping sound?

Thanks. The conditional statement "If" operates differently than I expected. In all the other programming languages that I've known, the entire "then" block is executed regardless of whether the "if" condition remains true throughout the execution. I'll keep that in mind.

I have the program that's supposed to turn on exterior lights when a motion sensor is triggered. But sometimes I'd find the lights stay on for hours long after there has been no motion outside. If Status 'Exterior Sensor' is On Then Set 'Exterior Lights' Fast On Wait 5 minutes Set 'Exterior Lights' Off Else No Action Looking at the log file, the only clue to the problem is that the motion sensor was triggered for a second time within the 5-minute period for the lights to be kept on. Can that second motion trigger somehow have thrown off this program and made the lights stay on for the rest of the night?

So what is the consensus here on the fate of serial PLM? Will they be back once the supply chain constraint is eased? Or is Smart Home pulling the plug due to low demand for the Insteon ecosystem altogether?

Thanks for the suggestion. (Now, this is a question that I would have created another thread to ask.) Is there an easy way to "recycle" lines from a previous program? It's such a chore to individually select a device and weave them into a program. It'd be much easier if you could copy & paste from a previous program, as I'll have to here to create three separate programs to turn them on at a give time of the day.

Got it. But I thought the issues were distinct - one about the "From-Then" schedule and the other about commands not running - although the two issues both arose from the same program. That's why I created separate threads intentionally, for posterity's sake, so people who want to look up a particular issue will land at the right thread. Didn't think they were crossovers. Anyways, I'll keep in mind that it's better to minimize the number of threads in this community.

Thanks. Didn't realize the raw text search was case-sensitive. Yes, it worked with the correct case.