MrBill

You could write a script for the RPI that does 2 things: 1) execute a REST API call to the ISY 2) then initiate the rPi shutdown sequence. The REST call could run an ISY programs 'then'.... example: /rest/programs/0032/runThen the isy program can be disabled, and doesn't need an 'if' or 'else', the 'then' body should "wait" the number of minutes (or seconds) that will take the rPi to reach the safe shutdown state plus some cushion time, after the wait, it should turn off the plug.

Another thread recently lead me to File > Themes > font size Since changing it to 15 I can actually read the funky magenta text easily. (hint: 14 breaks display of some selector boxes, skip that size).

I'm surprised it works. Try the instructions in this post to install the launcher on your desktop. It's the modern way of always opening the correct version of the Admin Console.

I periodically run the check for updates also and since they seem to appear frequently try to remember to check every week at least. I also run the check again after I apply the updates to make sure it returned to zero. At one point in history months ago, it didn't return to zero and the updates continued to mount and ultimately Michel ultimately had me sudo pkg update && sudo pkg upgrade sudo service udx restart I've often wondered about the contents of the updates and whether there needed to be a more pro-active method of making them obvious. I'm happy that @asbril asked. In the early days I was also rebooting polisy after applying any updates, however they were so frequent that I've stopped doing that, figuring it would tell me to restart if I really needed too. I must mention again tho that the non-persistent green boxes that you have to stare at the screen and wait for are quite annoying. I hope that its high on the list that those become persistent until dismissed.... at least the subset that say things like "Update Check complete. 1 package available for update. Click on the "System > Update Polisy" button to start."

I think @ronvond is refering to this notice: which does make me wonder what people without a UDI portal account are supposed to do....

There should be a factory "query all" program in your program tree that is already set to run daily at 3AM. On large systems this can take awhile and is best run when no one is moving about or turning things on and off during the query. (example in my house the query all takes almost 10 minutes.) that said the solution is probably not to have that run more often, nor to add a method to cause an auto reboot, the actual solution is most likely to find the root cause, which is most likely a noise problem. Is your system composed in Insteon, Z-wave or both? how many of each type device roughly? is it always the same devices and tasks with problems?

in current versions of the admin console the font size is File > Themes > Font Size. That said if you really mean you're still using a 99i you'll have to wait for someone else to answer... I have no idea, i wasn't a customer yet in the 99i days and have no idea what that version looked like.

There are several ways mobilinc can connect and some of it depends on versions and options of mobilinc. It does sound like the option you've chosen is compatible, however, its worth pointing out, that the product "mobilinc connect" is a competing portal. This is important because the ISY can only connect to one portal. Either UDI's or Mobilinc connect, not both. If you have subscribe to mobilinc connect, you will need to unsubscribe that in order to reconnect with UDI's portal. If you have not subscribed to mobilinc connect, and you have rebooted your ISY as suggested, and then checked the Configuration > Portals tab in the admin console as suggested above, then your best bet is to open a ticket with UDI support.... shoot an email to support@universal-devices.com. Be sure to include your UUID and a link to this thread to expedite things. UDI answers quickly even on weekends usually, but this being a holiday weekend may add a slight delay.

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.