ScottAvery

With a program? Or you just connected all the devices in a scene as all controllers?

I have some of the older insteon models laying around. May use for pet related things, but I hate the surface mounted devices and would prefer to have a hardwired device in-wall for a cleaner look in the main living areas. I have a bunch of inline-lincs and micro-lincs that I could wire in behind to get a signal to the ISY, but I have not had time to research options for the hardwired device. The ones I see at big box stores have unwanted buttons for physical interaction. EDIT: checked my order history: got the last insteon detector at $22 on Amazon. $64 is a wee bit out of line, but it is out of production...

Good news, and that was probably the only way to resolve this, so kudos to UDI again.

Awesome. Wonder if the guy with sunrise issues forgot to set location.

Then that is a bigger problem. A simple timer should absolutely execute without error. How is your Zwave comms in general?

Why do you check if it is not On at all? Just turn it on at the time required. If it is already on, no harm, no foul. That extra status check forces you into multiple programs.

Going back to this previous post, It looks like you factory reset then added to a scene without restoring the PLM link. The ISY will not have status for the device in this case without querying. I would delete from ISY, reset, and re-add to ISY and scene.

I don't have this device so I can't tell you what the selections are, but the logic will probably be like this: If door sensor is open AND door sensor is not closed Then wait 10 minutes send email Else (nothing) This assumes you have hooked up the sensor and that this zwave device is not your only means of opening the door (thus eliminating the control from choices). If it is opened by any means the timer starts. If it closes before 10 minutes it will reevaluate and stop the timer.

Typically you will use " If Control [button ID] is switched On" to track a button press programmatically. Why are you opposed to using a scene? There will be a slight delay doing it with a program.

Room is optional when you fill it in. not used for anything yet. If you are indeed seeing a device on the amazon echo connection, then I am out of ideas. something must be disabled somewhere. Try adding more devices and scenes... You didn't use a reserved word for the spoken did you?

You have remote access to the web console through the portal if the portal account is active and approved. ISY Web Access, top option. My point is moot though, as he was able to select devices.

I notice you only stated you could control the device from the ISY. Can you control it from the portal? Is that what you mean by it is online and registered?

Yes, was quoting your statement for the OP's attention, in that case. We do agree that he needs to restore or all is for naught, really.

Can't post graphic, but it is on the Devices sub-tab of the alexa.amazon.com Smart Home tab. "Forget All" is at the bottom of the page if you have devices. Yours will be blank if you never found a device to begin with, so there won't be a forget option. Your account isn't connecting. if you had your account linked v1/v2 style it would find devices even without the skill enabled. V3 requires logging into UDI Portal(once) from the Alexa page after you enable the skill. It then tells you that you can close the page. Did that ever happen? The device you define in portal also needs to be in the right place, under connections / Amazon

Not a train enthusiast but I have considered building a decorative train as a permanent installation and was wondering if you have control of your system through your ISY?

Also, are you using UDI's portal or Mobilinc portal? The instructions you are being given are for UDI portal: my.isy.io -> connections -> amazon

Forgetting devices is done only through a web browser at alexa.amazon.com or echo.amazon.com. There is a difference between how v2 and v3 authenticate your user account. Are you successfully linking the accounts? I ultimately had to disable the v2 style linking because it was conflicting with v3 for me. If you have pop-up blocker on, you may not be getting all the way through the process of enabling the skills.

You disassemble the PLM for this? Always or just for the link count? Since you started with a concern about poor response, this seems like a critical flaw in the plan given that now the ISY will be oblivious to activity in the network. Restore should only put valid links in the table.

With your current design, the execution is inevitable once the program is executed. What you want is to have the evaluation occur at the time the random ends. If the folder option Oberkc suggested doesn't work, then another program (third in the case of your usage) should be executed at the expiration of the timer rather than executing the command directly. You could also, put the wait in the calling program instead, but a 3rd program would make more sense. Also disabled.

Your tests show that the problem is likely noise at the location of the device. I believe that the Icon predates the current Insteon Protocol so it may not have the most efficient comms to begin with. Your program design has a lot of simultaneous scene traffic that has no clean up. Is there a reason you do not want to put the device directly into the program and or add a wait and repeat? This is what others try to overcome comm challenges. What happens if you turn that one scene off 30 seconds later than the rest?

I've never bothered with announcements because I thought configuring a doorbell with multiple announcements would be too painful and emails are impractical. This would be infinitely more useful. Hopefully you can target a device for the announcement rather than send to all. I'd like to make decisions about where to direct it based on time (master bedroom at night, kitchen in day, etc.)

In which case I still recommend checking to make sure the devices are indeed pointing to the new PLM. Removing, resetting, and adding them back would be the quickest thing, but you can manually inspect the links as mentioned above.

I am wondering now if perhaps thermostats are secure devices that require special treatment in some way, like the morninglinc lock controller.

I can't see my console from here, so I can't give you the exact steps, but you can see link tables by right clicking the device in the admin console. Probably under the diagnostics menu when the right click context menu pops up. If you have done a restore they should be identical. Checking to see if it is orphaned from the PLM is a little more tedious - you have to find the common single link that all the other devices have, which will be the PLM link, and make sure your troublesome device also has that link. If not, that device has to be removed and re-added. As for intermittent failures to update status, note that even the hard wired Insteon thermostat model is wireless-only because it is powered by a 5-30v transformer in the furnace, not the power line. That means you could potentially just have a communications issue. Move a dual band device or two near it for a while to check that.

I always thought it was just for convenience that we ignored the on-device schedule, but this statement puts the nail in the coffin.