Vwas

UPDATE: With the EISY 6.0.0 migration, Admin console logins were migrated to use your portal credentials. I assumed that this applied to PG3 logins as well. My PG3 login appears to have RETAINED its original credentials (i.e. my pre EISY 6.0.0. admin console login credentials). I was finally able to successfully log into PG3 by using my old Admin console username and password. I'm not sure whether something may have gone awry in my particular EISY during the 6.0.0 upgrade, or whether others may find themselves in a similar situation? It may be helpful if others could give this a try and report their findings back here. It would be nice to know whether my situation may be an outlier, or whether it's a known condition that's already been reported elsewhere and I hadn't seen it. Or maybe I've discovered something that can save others some time and aggravation in the future....

It's running 6.0.0. I am using my portal credentials to successfully log into the admin console, but they're not working for PG3 login. Tried the admin/admin suggestion, but that doesn't work either.

Also, I was unsure as to whether it was more appropriate to post this under Polyglot PG3 or EISY. I apologize if I posted this in the wrong place. Thanks again.

I haven't attempted to log into Polyglot 3x for a while. When I attempted to do so tonight, I received the following response: I'll confess that I'm far from being an EISY power user, and I tend to use the beast in a similar manner as the ISY 994i that it replaced. I attempted to log into PG3 through the Admin console, using the Plugins>Launch Polyglot V3 (PG3) dropdown menu with the same username and password that I use to log into the admin console. This had always worked for me previously, but it appears that something has changed. I haven't been actively browsing the forum much recently, but I am aware that the Admin Console is in the process of being gradually replaced by a browser based utility. Not sure if this might be responsible for the difficulties I'm having here? Anyone have any ideas or suggestions as to what I may be doing wrong here and how to get past this? Thanks in advance to all, for any advice and assistance that you may be able to provide me with...

Well, it turns out that two totally unrelated events happened concurrently, and falsely led me to believe that a firmware update had gone bad and caused my EISY to lose its Insteon control capabilities. In the end, the root cause of my problems turned out to be a failed PLM. It appears that my PLM likely failed as a result of my repeatedly switching each of the circuit breakers in my breaker panel on and off. I was attempting to identify all of the loads connected to each circuit in the panel, in preparation for installing a whole house energy monitor on the circuits with the largest loads. Presumably, a transient was created on the power line when one of the breakers was switched OFF and it damaged the PLM. I'm unsure as to whether my power cycling activities had also unknowingly kicked off a pending firmware update due to an EISY reboot, or if UD had coincidentally pushed out an update to my EISY in the midst of my circuit mapping activities. When I returned from the basement, I noticed that there were firmware update and EISY restart notifications from UD Mobile on my phone. I also noticed that none of my timer initiated lighting scenes had turned on when scheduled. I tried to turn on the same lighting manually through UD mobile and the admin console and also found them both to be non responsive. Naturally, my first inclination was to presume that this non-functionality was somehow related to the firmware update. My bigger fear was that I might have also unknowingly corrupted the firmware update by killing the power to the EISY in the midst of it. So I submitted a support ticket, Michel promptly responded, and we quickly determined that the EISY firmware and UI versions had both successfully been upgraded to 6.0.0. We also found that my PLM was non responsive. I'd purchased a new USB PLM when I migrated from ISY to EISY last December. USB PLMs are currently out of stock on the Insteon web site and aren't due back until sometime in November. Fortunately, the serial PLM that I'd been using with my ISY is still functional and had only been in service for about a year. So, I ordered a serial PLM adapter kit from UD to get things back up and running, and it arrived today. I did a factory reset on the serial PLM and connected it to the EISY earlier this evening. After doing a Restore PLM, I'm happy to report that all is back to normal and my EISY is able to properly control all of my Insteon devices once again. Thanks to Michel and the rest of the UD team for walking me through the debug and getting me up and running again!

Great advice, and I wish the fix was that easy. Unfortunately the "Insteon Support" box is checked. I finally navigated around my way around the main UDI web site and figured out how to submit a support ticket. When we hopefully get things fixed, I'll post the solution here in case anyone else runs into the same situation. Thanks again.

I was doing some electrical work earlier today, and the circuit that my EISY is powered from was power cycled in the process. When I flipped the breaker back on, I heard a few notification tones on my phone and assumed it was the result of my EISY rebooting. When I checked my phone later, I saw a message from UDMobile stating that an upgrade had completed, along with a notification that another upgrade was available. And as nightfall approached, I noticed that none of my indoor and outdoor timed lighting had turned on as it should. I pulled up the admin console and received a warning about available updates that were required. I also noticed that I couldn't manually turn any lighting on or off. I've had my EISY about 9 months and had not upgraded any of its firmware since I acquired it. In my case all lighting control is 100% Insteon based. After having owned an ISY for 10 years previous, and realizing that 5.9.1 had been available for some time, I was also a bit surprised that the EISY had apparently taken the liberty to do an upgrade on its own without my requesting or initiating it. And after reading the release notes that the upgrade note referred to, it sounded as if it may have only partially installed all of the updates that were required. So, I opted to dive in and upgrade all packages. After repeated upgrade attempts in the hope that they would correct the problems I continue to have, It looks as if this took me from version 5.8.4 to 5.9.1, and then finally to 6.0.0. But in spite of all these upgrades, unfortunately my EISY is no longer humming along and quietly doing its thing every day as it had been for the past 9 months or so. The admin console does appear to be fully functional, and time of day clock is correct. If I check the Programs/Summary tab, all of my programs appear to running according to schedule, but none of the scheduled Insteon ON/OFF actions appear to be occurring under program control as they should be. When I first start the admin console a few different error messages appear (see attached). And any time I attempt to manually issue an Insteon ON/OFF command a "Request Failed" error message pops up and the controlled item fails to respond. I assume the same thing is happening behind the scenes when a program attempts to turn something on or off. I'd greatly appreciate it if anyone else has any ideas of what else needs to be done to bring my EISY back to life. I've heard many others speak very positively about the quality of UDI's support and I'm confident we'll be able to correct this situation in short order once its referred to the right people. In my own case, my past experience with UDI and my ISY has been so good that I've never had a need to create and submit a support ticket. If someone could kindly advise me as to how to go about doing so, I'd greatly appreciate that as well. Thanks in advance for your assistance.

Hi Bob: Well, since you're the guy who wrote the plugin, I trust that it works exactly as intended. If not, I'll let you know otherwise... 😉 Thanks for providing the keys that finally unlocked this puzzle for me. While poking around in that "action" tab previously, I've only clicked on that arrow button once, to toggle between the option to assign numbers or my predefined TRUE and FALSE constants to the variables. I never realized until now that a few additional clicks would reveal additional dropdowns. Sure enough, the list of properties provided by my weather station plugin is hidden back there. And I'm also able to freely select any of them and assign them to the variable of my choice! Also for the record, here's the reason behind my wanting to create a running average filter for this data. Here's the solar radiation data that was logged on AWN for two consecutive days last week. Unless you're willing to tolerate lighting randomly turning on and off at one minute intervals, you really need something to smooth this data to make sense of it. Thankfully, your guidance will make short work of taming this beast! Thanks again! Thanks

Long time ISY user here who recently migrated to EISY. I’m currently running 5.8.4 and trying to take advantage of some of the added capabilities that EISY brings to the table. Thanks in advance to all for your insights and assistance. Is there any way that one can set variables in an IoX program to the property values returned by PG3 plugins? I’d like to calculate the running average of the solar radiation level measurements obtained from my Ambient weather station plugin. I’d be using this calculated value to determine whether or not to turn on supplemental indoor lighting on cloudy days. The running average is intended to smooth out the effects of passing clouds on measurement data, to reduce or prevent unnecessary turn on and turn offs. It would be a simple matter to calculate a running average of the last N measurement values returned by the plugin, if these values could somehow be directly stored into program variables. After poking around in the administrative console and the program content editor for a while, I couldn’t find a way to do this. It seems that any returned property values are only available for use in decision making as part of an if/then/else clause, rather than as part of any mathematical analysis/evaluation. Is this a fundamental limitation of how IoX interfaces with plugins? Can anyone provide any insight or ideas as to how I might be able to pass these returned values directly into a variable? Thanks again

See related post here. It appears to be a bug in the admin console.....

Now that you mention it, it seems like I also ran into this behavior with my old 994i many years ago. Coincidentally, I was tweaking a few of my lighting programs earlier today to fine tune the on timing based on the solar radiation reading that eisy pulls from my weather station. I use the time of day to establish a turn on window around the time of sunset, then fine tune lighting turn on events based on measured daylight level. That's when I realized that the sunset time shown in the console was off by an hour...

My "Night Detect" program is scheduled to run 15 minutes before sunset. Admin console shows sunset as 7:43, but next scheduled run for this program is shown as 6:28. That works out to 15 minutes ahead of 6:43, as expected. If this holds true (fingers crossed), it appears that eisy has its internal sense of sunrise and sunset times correct, it's only the admin console display that's out of whack...

Same problem with my eisy here in the Boston area (running version 5.8.4). Time of day appears to have adjusted correctly, it's only the sunrise and sunset times reported in the admin console that appear to be off. I have several lighting scenes that are scheduled relative to sunset time. Not sure if their run time will be similarly affected by this?, or if this is only a fluke in the admin console display. For reference, my Ambient Weather station is reporting sunset as 6:46 PM. The weather station has my exact longitude and latitude coordinates set, while the eisy has my location set to Boston. I'm actually about 30 miles west, I presume that's likely the reason for the slightly later sunset time reported by AWN. I'll check back in again around sunset to report whether my scene timings are similarly affected by this one hour shift...

Did you do a "Restore Modem" from your Admin Console after you connected the new PLM? You can't just plug in a new PLM, you need to restore the links between all of your existing Insteon devices and the new PLM. Your ISY maintains a local record of this information and will download this information to the new PLM once you initiate a Restore Modem command. You can also test your ISY's ability to communicate with the new PLM with the Diagnostics>PLM Info/Status command, that should return the Insteon address of your new PLM. If that doesn't work, there's an issue with the new PLM or the comms link between the ISY and the PLM....

Well, after all the head scratching we went through together over the past few days, once I resolved my admin console issues, I was thinking that maybe I should quit while I was ahead. In hindsight, for me at least, the 4.9.0 to 5.3.4 upgrade couldn't have been any easier.... With this 5.3.4 upgrade in place, doesn't this provide me with the ability to use UD Mobile with my ISY? I know it requires a portal account, wondering if it also requires a paid subscription? My wife has been complaining about "all this stuff in this house that only YOU know how to use" for quite some time now. And that started me thinking... As for me, I bought my first X10 devices to enable automated and remote control of lighting and appliances when I was still in engineering school back in the late 70s. I've also been an avid audio video enthusiast since the days when buying your first killer audio system was regarded as a right of passage upon entering the workforce after graduating college. I've also taken more than my share of abuse over the years with regard to "how difficult it is to sit down and watch TV in this house..." I have a network accessible Pioneer Elite AV receiver in my current system. Right now I'm thinking that the EISY will provide me the ability to achieve customized one touch integration of all AV system functionality, while allowing the less technically inclined folks in the family to access it through their familiar smart phone devices. Maybe I can finally manage to walk away from all of this chaos as a hero - while having some fun in the process... 😊 Thanks again to all of those that helped along the way