MrBill

@mvgossman and @tmorse305 two thoughts: 1) did you remember to say "Alexa, Discover devices" after adding it to the portal? 2) yesterday I had a really long delay waiting for a new scene to show up in the "routines". The scene showed up under "scenes" in the devices section immediately but wasn't accessible from routines for a long time. I'm not sure if the fix was A) waiting or b) Force quitting the Alexa app and restarting it. I would have assumed it was B, but someone on another social media platform was complaining yesterday about delays with respect to routines. (Interestingly, I noticed yesterday while troubleshooting my problem that "routines" don't even show up in the web interface from a computer browser at https://alexa.amazon.com which also surprised me because I tend to like the full browser Alexa interface better than the Alexa app).

Open a ticket with UDI... support@universal-devices.com I suspect the portal flips back an forth might need manual intervention on UDI's side.

WOW... I just tried this... I didn't realize contact sensor or a motion sensor options existed and behaved differently than what I was doing already. THANK YOU.

How do you use an ISY variable as a trigger in routine? Bottom line I don't think you can, but if you can teach me I'd love to learn how to do this. ISY variables seem to be one way with Alexa. I have a number of them exposed to Alexa through the portal that I use for custom dimming levels (i.e. Alexa, set Bill's lamp to 50). As best I can tell tho you can do nothing in the other direction (i.e. having Alexa do something because of a value changed to <whatever> ).

The C shows for me. Follow the instructions in the first post of this thread:

Also remember that every time Java update installs an update that you need to repeat the process outlined there.

BTW... 883LM is only $10.25 @ amazon. ?

When I had V4.x firmware my ISY was up for about 8 months without being rebooted (I have a variable that counts uptime--I was sad to actually have to break the streak and start it). With V5.x i haven't been so lucky, this last time it had been running about a month and something went wonky with subscriptions and i ended up restarting it from the portal. I could never do an auto-reboot tho, anytime it restarts I have 17 wireless sensors that need to be opened and closed manually.

@Michel Kohanim I wondered that yesterday and typed it into google.... this is what I found: https://www.amazon.com/ISY-Optimized-Smart-Home-V3/dp/B076B3BWSD it seems to be part of the name of the Alexa skill, which makes sense as this is posted in the Alexa section of the forum.... but mobilinc is something else entirely... at least to me.

Actually, I just learned this in this thread. previously I've always used variables to trigger programs. I've already put this to use tho. I was on a state variable reduction kick anyway, so this helped get rid of another handful.

There is also a related bug I noticed. for background, I discovered this because i installed a new switch next to an existing, the new switch (both 2477D) new switch backlight was too bright, but then Ultimately I decided to adjust the old switch too. To see the bug: Adjust Switch B (new switch), go to adjust switch A and find it claims in the UI to be set to the level used for Switch B, (it's not) and to change switch A to that value, you actually need to change it to something else first then back to that value, or restart the admin console then set the second switch.

I actually use "Alexa, turn away mode off" But it only works if all exterior doors are closed, a specific interior door is open and was opened within the last 20 seconds, and a specific light that we hardly ever actually use was turned on in the last 20 seconds, and one more condition that I'll omit from here. Combination Lock per se.

Since the xbox is already on, just use what I wrote above, with the names changes appropriately... Alexa turn off Xbox in 60 minutes. Caveat: if he has access to Alexa, he can easily override. We could add minor complexity and make it a non-resettable timer.

You create variables in the admin console: For this purpose you will need a "state" variable. (be sure to click SAVE at the bottom of the page, or it won't actually be created). 2) You link that variable to Alexa via the portal. Which will let you set the time via Alexa. 3) this program will start anytime the value of the variable is above 0 and run until it drops the variable back to zero, at which time it will turn off the device: aaatest_delete - [ID 00E1][Parent 0001] If $lamp.timer > 0 Then Wait 1 minute $lamp.timer -= 1 Else Set 'LR Lamp 3#' Off turning the device ON isn't covered, and requires a second program. If the time you want to turn the device back off doesn't change, there are other approaches, but I'm not sure what your exact goals are. if you get specific we can help.

I just played with this: Created a state variable name "lamp.timer" via the portal added a spoke "lamp timer" (i used the default type of 'scene') (default 'off' value: 0) (default 'On' value: 23) "Alexa, Discover devices" "Alexa, Set lamp timer to 70" -- as expected the value of the variable changed to 70. "Alexa, turn on lamp timer" -- as expected the value of the variable changed to 23. "alexa, turn off lamp timer" -- as expected the value of the vaiable became zero. so @larryllix you're correct the timer can be created in this manner. the only caveat is with the default type "scene" the value can only be set 0 to 100.. I'm not sure if any of the other "types" (portal) would expand the value that can be set. if lamp.timer > 0 then Wait 1 min lamp.timer -= 1 else <whatever happens when the time runs out>

The word off might be getting in your way. We use this routinely with lamps where the meaning of the variable actually is a percent but we don't say the word percent when we talk to her. "Alexa, set lamp one to 50" works just fine.

There is a "find". Right click the "My Programs" folder. Does that help?

have you restarted or upgraded your ISY today?

I've been on v5.0.16C since 3days after it's release. My ISY was last restarted a week ago exactly, I just looked it was literally this time of day last Sunday.

Correct. my isy is connected to the portal and alexa is working as well. my isy has not been restarted today.

except my portal connection works fine. my isy wasn't rebooted today, someone else said the same in another thread. The pattern or common denominator seems to be restarted isy's aren't reconnecting. perhaps an undesired maintenance issue. Commenting this so that we can consciously group analyze this theory which might save time identifying the issue if it's true.

I probably should have made the above post in this thread instead. my theory is ISY's that have been restarted can't re-connect to the portal, but if the ISY was already connected before this morning it stayed connected.

This isn't scientific but I've been reading posts in several threads, the general summary might be that if your isy was connected to the portal before this morning there is no problem, but if the ISY was restarted (which is the last stepup of upgrade) the connection to portal can't be re-established. That's my guess, but most of the people that have stated problems it seems the common theme is "isy restarted" and "portal/alexa offline".

I just remembered there was a scheduled maintenance earlier this morning. ((Note the date in the title doesn't match the date in Friday's post.))

I just logged into the portal and accessed my ISY and turned the light next to me off and on. I had Alexa do the same thing. All working fine for me.