Teken

Given the various Java environments will be deprecated at some *Sooner Than Later* point by almost everyone in the technology field. HTML5 will be the go forward interface for all of us down the road. As you noted their team is small and this impacts their ability to role out everything the end users want to see. I have no doubt UDI will offer a better method to interact with the (AC) Admin Console at some point. From my birds eye view they have too many things on their plate with competing goals and timelines . . . I'll state this again as I have in the past and that is the company find someone to help them launch a crowd funding campaign. This will be a multi purpose goal of hiring the talent to create a better user interface and mobile application. It will help fund and spur the development of the Polisy hardware platform so it can be the next generation Home Automation Controller - Sooner. Lastly, I honestly believe they need to hire someone to design and build them an auxiliary box with lots of analog & digital I/O's. This box would support the most common industrial and enterprise class contacts and sensors. There are so many existing vendors who are just sitting around to do OEM / ODM for other companies. They can build to spec or just re-badge their own field proven technology hardware - why recreate the wheel?? Lastly, having watched and interacted with Michel over the course of twelve years. The man has come a long way like myself where new ideas and technology is considered and integrated. It comes down to ROI, Time, and Resources . . . The man is like a Turtle, slow & steady - but always gets there! ??

Circle back and let us know how things work out . . .

Normally this problem is seen after a firmware upgrade from 4.XX to 5.XX where the client hasn't cleared the Java cache, and used the correct UI. Since you already cleared the cache, rebooted, and this wasn't a UI mismatch. Not sure what else you could try besides a ISY Restore - except recreate the program?!? Creating the program would most definitely take less time and waiting . . .

Welps, if you have a recent backup you can try a ISY Restore. Best to get into your most comfortable shorts and T-Shirt, cold beverage, rockin music, kick back that recliner . . . [emoji53] Sent from my iPhone using Tapatalk

When you select Help -> About do both U.I and firmware match 5.0.16C? [emoji848] Sent from my iPhone using Tapatalk

If you review the UDI WiKi confirm this isn’t due to a firewall / antivirus related issue. Sent from my iPhone using Tapatalk

Was this via direct connection and no switch? Have you tried using a switch where you can force it to negotiate at 10 /100? As a hell merry I would take the controller off site and connect to someone else network to see if there is any difference. If the off site network still can't ping, and connect to the controller it sounds like the NIC is given up the ghost! This assumes the controller is in fact still set to DHCP . . .

Please select the link I highlighted in red. Once this small applet has downloaded and installed it will provide you with the *Universal* Admin Console. Essentially this will download and install the correct Admin Console U.I. on to your desktop. Please keep in mind 4.7.5 was provided to resolve some security issues and thus even (IF) the UI shows 4.7.5 and the firmware is 4.7.3 this is OK. At this juncture it makes little sense toying around with the 4.XX firmware branch since you're on 4.6.2 . . . Please consider updating to the latest 5.0.16C RC (Release Candidate) for more features and security fixes:

Ideally, your son should be opening and closing the GDO via the built in exterior remote keypad. The next extra layer would be to have him carry a iBeacon on his key ring along with the cell phone. Incorporating the other elements you noted like geo location and these two physical access keys than the door could be opened. I'm probably the last person to ask because I don't feel Home Automation has a place with respect to true security of the largest door to your home. Insteon is integrated solely for awareness (Read Only) so the ISY Series Controller can offer myself and the family those creature comforts of turning on, off, lights and infrastructure resources. It has no access to open / close the door which is handled by my security alarm system which even then is restricted to time & schedule. And that is simply addressing the electrical aspect never mind the physical which is managed three locking solenoids and with a measure of force protection while away huge bollards to guard against a physical impact to the door.

In case you haven't tried the login to the right should be used.

Wait For It . . . [emoji1787] [emoji2357] [emoji2955] Sent from my iPhone using Tapatalk

The company has expressed that Z-Wave will come via an external dongle if and when the migration is public ready. I on the other hand would love to know if ZigBee falls in the same category for those using it for energy monitoring. As an aside I’ve been working with the Brultech team who are the makers of the best in class energy monitor called the Green Eye Monitor (GEM) and Dash Box (DB) as a Alpha / Beta Tester for more than ten years now. The long term plan is to create a GEM Node Server for Polyglot. Unfortunately there is no timeline or ETA given their limited resources and prior commitments on other development tasks. Regardless, I’ll continue to push for this to be completed so Energy Monitoring is easy and sexy! [emoji106][emoji1787][emoji110] Sent from my iPhone using Tapatalk

No, the company is transitioning all climate / weather features via Polyglot Node Servers. Those who purchased the Climate Module will be provided various levels of free ISY Portal subscriptions to lessen the pain. As of this writing there isn't a clean irrigation solution as of yet. Having said that there are no less than five weather related Node Servers offered by our amazing forum members. Members have really two options for hosting Polyglot: ISY Portal, Raspberry Pi or Polyisy The greatest benefit of the Node Server weather offerings is real time hyper local measurements which can be acted upon by the ISY Series Controller. Receiving weather data from stations which are dozen to hundred of miles at 30 minute intervals is less than ideal.

The USB is called the monitor port by UDI. Sent from my iPhone using Tapatalk

EOL email was sent out to all registered customers more than a month ago and also last week.

The ISY Series Controller *Electronically* supports a maximum of 32 GB. Whether or not it can use all of that space to me doesn't matter. As much as installing a high quality class 10 and high endurance Micro SD card. Even in 2020 every maker struggles to offer robust and long term memory based storage due to the end of life write cycle. High Endurance memory offers the best in terms of repeated writes vs standard cards . . . This is why they are used exclusively in Dash Cams, Personal body cams, and Onboard NVR IP cameras.

The error message provided by the system is a misnomer when in fact it should indicate incorrect addressing. As you noted below when you transition from 4.XX to 5.XX the migration can and does cause errors. You need only correct all of the programs that have incorrect pointers, select save, or update the resource needed. Whether it be weather, hardware, network resource, email, some kind of state like a wait, repeat, etc. Once all of the impacted programs are corrected the system will operate normally. Insure you take a new back up once the system has been fully tested by completing local, remote, and scene tests.

No, you don’t need to do anything. [emoji106] Does your environment have a mix of Insteon & Z-Wave?!? [emoji848] Sent from my iPhone using Tapatalk

A UPS on the electrical circuit would have no baring on the AC operating or being accessible. That sounds more like a network related issue. Depending on the type of UPS it surely can impact the Isteon power line signal though. [emoji3516] Sent from my iPhone using Tapatalk

@gregkinney Tight Loop: Generally speaking anything that makes the controller receive or do something in a short period of time will cause a tight loop. Say create a program to count something every second that would be a tight loop. Now, if all you had is a single program doing that the system would be OK. When you have more than one you run into serious issues. What most people see are programs, scenes, network resources, are slow to react or at all. Another is when you log into the AC (Admin Console) and you will notice the system is slow to load or even at all. You can create another situation which is similar to a tight loop but not and this is by sending / receiving REST. If you ever review the error logs you may see lots of Queue Full messages. Remember the ISY Series Controller is essentially a small clock which has to share time (resources) to accomplish all the different things we ask of it. It also operates on the FIFO (First In First Out) principle. So what ever tasks it has been assigned to do is performed in order . . . Anything it can't do it places it in a virtual queue (back of the bus) until it can complete the same later. As noted early on the controller (generally speaking) doesn't really have a problem sending / doing outbound tasks. What really impacts the controller are / is anything that comes inbound to the controller which ties up lots of I/O and resources of the system. One key thing about any inbound REST call is you must insure you stagger the requests by several seconds otherwise you will have conditions where the controller appears bricked and sometimes self reboots. Short Version: Allow enough time between program activation, REST calls, and schedule folders to be disabled so there are more quiet times in the 24 hour period than active. Also, if you have any programs that make the Insteon network beep, blink, flash, use them sparingly. ie. You're asleep so anything that has to do with Home Remote should be disabled. Schedule the same folder to activate during your waking hours.

Any specific reason not to mount and install one of these eight button dedicated remotes?!? https://www.smarthome.com/collections/insteon-keypads/products/insteon-2342-222-mini-remote-8-scene If you wanted a hard line than a 8 button KPL with custom keys would be ideal held in one of the stands.

No worries . . . Also keep in mind you can place a schedule time for an entire folder to become active (true / false). Placing a condition on a parent folder allows you to manage program(s) in a global manner while also offering you an opportunity to kill a *Tight Loop* race condition. You'll really be happy to have conditioned folders when the controller is really locked up!

I can only suggest things I've done from past experience having seen the same: - Tight Loop: You may see this phrase bounced around in this forum once in awhile. Generally speaking it means not having programs or network calls whether they be inbound / outbound that happen in rapid succession or in short intervals. You can have a tight loop simply by telling the controller to execute a program 1~5 second. The same can be had where you send in bound REST calls to the controller. - Schedule: Always try to spread out program execution in longer intervals - Wait: Incorporating a wait statement is good practice to allow the controller to catch its breath. - Repeat: Use repeats when and where appropriate but use caution to not abuse this statement as it can lead to *Tight Loops*. - Disable: You can have a program disable another program to insure the system is idle when it should. - Folder Color: Once you activate the folder status indicator if you see what some of use term *Flutter*. Where you see the folder alternate from solid / half solid this is a really good indicator that programs resource is causing unexpected traffic / processing. - Pending Writes: Always insure all hardware is fully operational and no pending writes are in queue. If you're on 5.XX firmware there is a known bug were the Motion Sensor II will constantly try to write to this battery operated device if it has some kind of scene adjust involved. The band aid is to disable the battery write if you have the Pro controller.

If you have a lot of inbound network traffic to the controller this is one possible reason. This sort of problem will also happen when there are lots of overlapping programs completing tasks like blinking lights, beep, flash LED. Programs that have very short counting say less than 5 seconds. If you have any sort of pending writes this too can cause the same. Rebooting the controller is a band aid to a much larger problem as all you’re doing is flushing out the memory / network cache queue. Until it becomes full again and the system grinds to a halt. [emoji52] Sent from my iPhone using Tapatalk

This is a valid concern but I understood the OP simply wanted the original program structure to save time writing from scratch. [emoji2369] I would think any required changes to calling resources / hardware is something that would be tailored prior to deploying. [emoji848] Sent from my iPhone using Tapatalk