MrBill

Interesting... I've never really paid much attention to the date codes, except involving fanlinc's where I was having issue at one point. a date code of 1921 will certainly be ambiguous soon!

Something has definitely changed in the cloud. I make all of my spoken's pretty unique and she's questioning me a lot about what I mean..... for like the past 2 weeks, maybe 3

@Teken So this thread made me go look at the full version of the manual. which makes no mention of the jumper block. and then I had to walk around an inspect most of my 2843-222's which are version 1.b date code 3815. the user manual doesn't mention the jumper block, although in the picture I can see where it was on the board, by the 38th week of 2015 it is just unused holes on the board. Checking the admin console, all of my have the closed node, but I've never used that and wonder in what conditions it becomes useful? Extra credit: I just ordered some 2342's during the sale and had them on my desk to link today.... the date codes seem reversed v2.0 1921.... i wonder why? especially since after the 19th week of 2021 that will become confusing.....

The theory all sounds great, except I can tell you first hand about two specific problems I've had in the past (my system is all Insteon and large i don't know how many devices anymore but over 100, none more than a few years old at that time, and all DUAL-BAND, with zero z-wave): Case 1: I used to have a deep fryer in the kitchen that got used once a week for taco shells and chips, for the one hour per week it was plugged in most Insteon didn't work. Some items coming from the PLM would ultimately execute very late as soon as the plugged was pulled for the deep fryer. This is a 110v counter top deep fryer, on a kitchen counter receptacle circuit that has NO Insteon device on the circuit. The deep fryer didn't even have to be turned on, just simply plugged in and Insteon would be dead in the water. We just lived with that problem since it was only an hour per week. Eventually that deep fryer kicked the bucket, it's replacement and Insteon very happy co-exist together. Case 2: After a storm most Insteon didn't work, but the weird part was some did. At first I was sick to my stomach because I thought I was going to have to replace 50+ devices. In the end I started playing with circuit breakers-- the first goal was to figure out if it was all devices on one phase and the other phase was fine, but it wasn't one phase or the other. Eventually I turned off breakers in big groups then further narrowed it down to one when one breaker labeled "Furnace Blower" was turned off my entire Insteon system worked perfectly. The kicker was I then tested heating and Air Conditioning... everything checked out and worked, but with that breaker turned on my Insteon system was essentially dead in the water. It suddenly dawned on me.... the attic fan was also on that circuit. I remember because it was actually hard to find the attic fan breaker when I installed it's Insteon switch, no breakers were labeled attic fan, no breaker seemed to turn the circuit off, of course I skipped "furnace blower" because why would it be that circuit? Well during the initial install I finally just decided to "trip" the breaker so I could install the Insteon switch so went up and created a dead short so the breaker would trip...haha it was the furnace breaker, but stupid me didn't add it to the label at that time. So I installed a 2466SW to control the attic fan. I decided it need to be that switch because its advertised by smarthome as being "better" for motors and florescent lights than 2477S. Anyway to wrap up this long story the 2466SW sustained storm damage, it was generating noise that brought down most of the Insteon dual band system... once I popped that single switch out and replaced it with a 2477S that I had on hand my entire system was back up and running. Moral of the Story.... you have to get rid of noise makers and signal suckers follow the standard troubleshooting steps, and no you can't assume the radio portion of insteon will take over and heal the network in the event of line noise.

I spoke too soon becuase I was thinking of the networking module being much like the cron interface and it's not. This is very doable still tho. The ISY's networking module just needs to call a URL on the pi that runs a script via http, the Pi script would run shutdown on the pi. If you need help making that happen I'm going to let someone else take over my idea and help you out. I could get it done but it doesn't role off my fingers like I bet it will for someone else. the steps: 1) create a pi script that can be called via the pi's webserver that contains a single command to run shutdown. 2) create network resource on ISY that runs the pi script 3) create an ISY program that runs network resource, waits, turns off plug.

if you have the network module on the ISY you could go in reverse. the ISY program calls a network resource that SSH's to the pi and runs shutdown, then waits, then shuts off the plug.

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.