MrBill

something else is wrong, the external URL makes no difference to the portal. The portal doesn't initiate the connection, the ISY makes an outbound connection. check the Configuration > Portals tab of the Admin console and/or reboot the ISY and/or the local router.

Thanks! I just switched to 16..... this looks awesome... I can read the tree on main even with its funky magenta text ?

The funny part, is I knew exactly what the problem was when I saw your post, but didn't know the font size setting actually existed. I like bigger too and left mine turned up and i tested the problem.

you can go higher, try 1024 and BTW when java updates you have to do it again.... so a few months ago was older than the last java update... i bet your back at default.

You have your font size turned up. the value can't fit in a box that's fixed size. (the font size control in the admin console is on File > Themes) I just cranked mine up to see and yes that's what happens.

Have you tried increasing the memory of the Java Workspace?

The short answer is make them BOTH CONTROLLER's. Why because you want them both to control the scene, and any controller is automatically also a responder. There are reason's you may want a responder only, but in general make everything a controller. A case where I use responder is at my front door, I have an 8 button keypad where 4 of the buttons are radio style buttons for Off/reset, Bright, Night, Late Night. there are 4 scene's and one of those buttons is a controller for each scene, but it's also a responder in the other 3 scenes. These are used to override the mode of the outside lighting. If we are in night mode by time and I press bright, I need the light to turn off behind the Night button as it shifts mode, so the "night" button included as a 'responder' in the "bright" scene. Generally tho when it's just 2 or 3 switches controlling the same load, you want them all to be controllers. and yes have the program turn the scene on. Edit to add: I also create a scene for literally everything and always use the scene for control, that way I don't have to stop and think which I want a device or scene. My system started with lots of 8-button controllers tho before I ever knew ISY's existed. I make extensive use of button's and scenes, so it's just handy for me to make a scene for even the odd 1:1 switch that only controls it's own load.

Not the OP.. but I'll look at see how many I still have. Back around 1998/99 the leviton rep was sending me 72 free to install on the lighting in the office of an important Leviton customer. the rep thought he ordered 6 boxes of 12 = 72, he actually ordered 6 cases of 12 boxes of 12 or 864. By the time we called to say gee we got 11 times too many his boss had already signed off on the credit memo, the rep came and took like 3 boxes so had freebies for other customers having issues, told us to keep the rest in case we needed them....

out of curiosity do you know if Leviton 6287 is useful for Insteon's spectrum? I have a box of them, just not sure how many are left I sold some on ebay like 15+ years ago.

I'm not sure if you're experiencing the same problem I had recently, the symptom was you would click the launcher and then briefly see the Java logo it would vanish and nothing else would happen. The solution to that was: 1) uninstall java completely 2) navigate to C:\Users\<username>\AppData\Local\Sun\ and delete the entire folder named Java 3) reinstall java

Have you tried rebooting the ISY??.... it may vanish at that point, or after it's back up delete may work correctly.

@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.