IndyUDIuser

When I discovered the pole lamp was no longer responding to the bedroom wall switch, the first think I did was try to link the wall switch to the appliance module. The linking beeped successfully, but the lamp still did not turn on/off with the wall switch. So next I did a factory reset on the appliance module and then manually linked it to the wall switch. Just like I've done for years. This got the wall switch working correctly again with the pole lamp. Then I had to remove it from Admin Console and re-link it to Admin Console in order to fix the broken Bedroom Lights scene so Alexa would turn the lamp off again. Anyways, everything is back to working the way it has for many years. Going back to the beginning of my post, why would simply adding a device (or devices) to an existing scene (All Lights) in EISY cause existing links in the devices to be wiped out? I just used "Add to scene". It never said anything about wiping out existing links between devices. Annoying to say the least. And the "New modules" dialog box thing is a bug that I've been having since v6.0.0. I have to reboot EISY to clear it out. I'm currently on v6.0.5. Oh, and here's another nit to pick... When I click Start Linking in console, the Linking In Progress dialog box appears, as well as a small timer dialog box. NEITHER ONE can be cancelled (if I change my mind for instance). The red X in the corner doesn't close either box (which UI standards usually require). But that flaw has been around for years, so never mind. LOL Thank you all of you for your comments. I'll try to remember this as yet another foible in Insteon programming (which often seems like a Jenga game).

Reboot got rid of the "New Insteon Devices" false dialog.

Oh, and now when I start up Admin Console I get a pop-up box titled "New Insteon Devices" and shows me the address for an 2635-222 On/Off Module. Sure enough it is the pole lamp's module. Every time I open Admin Console this dialog appear, and all I can do is close it. This module has been in use for years and worked perfectly until the changes described earlier. This is reminiscent of problems on several devices I was having before I upgraded to v6.0.5. Now it's happening again. Ugh. I'll reboot EISY and see if this goes away.

IDK. This is first time I've added so many things to a scene. But how is the EISY wiping out existing links within and between the modules? Makes no sense.

A few days ago, I was checking my EISY's setup in Admin Console. (V6.0.5) I had a scene called "All Lights" that I set up years ago. I decided to update it by adding more light switches and lamp modules. I right-clicked a number of items and selected "Add to Scene" and selected All Lights. After saving the changes I tested the Scene by turning it on and off. All the lights around me were activated as expected. So far so good. Then awhile later I went to my kitchen and turned on one of the three wall switches. No response. I tried a second switch, and it was nonfunctional as well. The third switch (master switch connected to the load) worked OK. I had to re-link the two slave switches to the main switch again (in both directions). Later I went to my bedroom and turned on the light switch. A pole lamp on an appliance module formerly linked to the wall switch no longer worked. I had to link it to the switch again. When I told Alexa to turn off the lights, the pole lamp didn't react. I had to go to the "Bedroom Lights" scene in Admin Console and remove and then re-add that module to the scene again. My memory is faint, but I believe this is not the first time something like this has happened to me (I've been using EISY and Insteon for 25 years). It's very rare, but then I don't make changes to my Admin Console very often. I haven't checked all my other devices to see if anything else was messed up, yet. Why did the simple act of adding devices to a scene corrupt so many links, both in the devices themselves and in the EISY? Rather frustrating.

Oh wow, thanks for the tip about FInd/Replace. I have never used that before. Very useful feature for the next time I tweak a line of code but forget to CAREFULLY click "Update" and then "Save". And therefore don't notice the wrong variable has been plugged into the code.. I run into that problem every so often.

OK, I confess... I found a line in one of my sub-programs (one I have not been paying attention to until now) that was setting iCurrentDayOfMonth to zero. I had accidentally used the wrong variable name in that program and didn't notice it until now. I corrected that and now all of the variables seem to be setting correctly. I added code to the beginning of the master program to initialize all variables to zeros before calling all the sub-programs (just so I can see this happening). I eliminated some of the waits, although I still wait 1 second between each sub-program call. So far so good. I'll check this tomorrow to see if it is working in production as expected. FIngers crossed.

Ugh. Programs still aren't working as expected. I added more WAITs between every line of code in every program so I can try and see what it is doing to the variables, but that made it worse. I can see what appears to confirm my original post, in that the variable iCurrentDayOfMonth gets set correctly, then the INIT gets set, and the variable is ZEROED OUT. So I added another line to set the variable again (after copying it to the INIT) and that seems to work. To me this looks like a bug in the OS. But now all the WAITs I've been adding are causing other things to malfunction. Programs are running out of order. More variables are being set incorrectly. I'm thinking I may have to throw out all the individual programs I wrote and write just one large program that does all of the calculations in sequence as I expect. More debugging..... DATTM SetCurDayOfMonth - [ID 0078][Parent 0028] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then $iCurrentDayOfMonth = 0 Wait 2 seconds $iCurrentDayOfMonth Init To 0 Wait 2 seconds $iCurrentDayOfMonth = [Current Day of Month] Wait 2 seconds $iCurrentDayOfMonth Init To $iCurrentDayOfMonth Wait 2 seconds $iCurrentDayOfMonth = [Current Day of Month] Else - No Actions - (To add one, press 'Action')

I only learned about "INIT TO" in the last year. Setting the INIT value allows the ISY to reset variables to the desired values if the ISY reboots for some reason (i.e. power blip).

Well, the problem came back again after the program executed at midnight on schedule. The variable shows 0 while the INIT shows 14. I experimented with adding a couple of initializer statements (so I can watch the variables get flipped while the program is running) as well as WAIT statements between each line, thinking the executor is not running them in the sequence they are coded (or running too fast?) Then I removed the WAIT statements one by one, testing over and over to make sure the code still worked. The following code finally does what I expect when the THEN clause is executed. For now at least. DATTM SetCurDayOfMonth - [ID 0078][Parent 0028] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then $iCurrentDayOfMonth = 0 $iCurrentDayOfMonth Init To 0 Wait 3 seconds $iCurrentDayOfMonth = [Current Day of Month] $iCurrentDayOfMonth Init To $iCurrentDayOfMonth Else - No Actions - (To add one, press 'Action') Note that if I set the wait statement to 1 second, the program doesn't work for some reason. I don't see the variable or its INIT being changed. Change it back to 3 seconds and then I can see the values changing. Weird.

Thanks for the information. I have not looked at Plug-ins in a long time because I don't use them and haven't taken the time to learn about them. I'm just an Admin Console user, controlling Insteon devices in my home. I poked around in the PG3 interface and see two listed as "Purchased". I don't remember purchasing them or what they are for. Perhaps from years ago. Both are described as "Notification Node Server for Pushover and Telegram" with one labeled Beta and one Production. I'm guessing they have to do with sending notifications to my phone, so I'll leave them as-is. I'm a retired batch developer (C and Unix) so all this Polyglot/GitHub programming stuff is foreign to me. Will take time to learn. Wish there was a good old-fashioned hard-copy book on all this to follow. I waste too much time wandering around lost in the forum and wiki. LOL ;-)

I agree with oberkc. I upgraded to 6.0.5 a few days ago. After reboot the "Added" dialog went away. Today it came back. Rebooting again cleared it. Don't quite understand what is going on here.

I'm not aware of what plugin you are referring to. Can you explain further? Thanks.

I have an IOLinc 2450 v.41 that has been in operation for over 5 years. A few weeks or so ago I started getting this same error (and several others). I tried all kinds of things but it wouldn't stop. Upgraded to v6.0.5 and after a reboot or two it finally seems to have gone away. Must have been a bug in 6.0.0. Thanks.

I deleted the program, restarted the Admin Console, and then hand-typed the entire program again from scratch. This time it worked, both the variable and it's INIT value appear correct. Thank you IndyMike.

I feel your pain. I've been a ISY user for maybe 20+ years (ISY994i and now EISY). I've been having a few odd bugs with my EISY lately. No idea why they suddenly started happening. Removing the devices and re-linking them over and over didn't help. The error messages from admin console were bizarre and all but useless. I thought I had a couple of failed devices. So I started browsing the forum. I saw a notice from MIchel about a new version 6.0.5 released. No information on how to download and install it. So, as I do about once a year, I spent time searching through the wiki and the forum. A simple software update in any other software I've used in 40 years doesn't take hours to figure out -- it's usually a click or two -- 5 or 10 minutes max. Not here. Tried rebooting my EISY and all of a sudden it was updated to 6.0.5. I didn't even know it would do that. Then the admin console no longer worked. More time spent finding the link to download start.jnlp again. Why isn't there a prominent link at the top of the "Official News and Announcements" page to a page that gives all the information about how to download and install updates? Why has it always been this hard? I'll get off my soapbox for now. Thanks.

I've been having a similar error for at least a month. Plus other anomalies about a couple of devices not communicating (that had been working for years). I just rebooted my EISY and it installed v6.0.5. The problems seem to have gone away. I had to clear Java cache and download a new copy of start.jnlp to get admin console working again. Good luck.

Thank you! I found them by clicking the three lines, then Settings, then System. Next question: Near the bottom of the list I see "Upgrade status: Inactive". What does that mean? Below that is a button labeled "Upgrade packages". Do I use that to update everything to the latest versions? I also find an "Upgrade packages" button in the Admin Console under Configuration > System. I assume that performs the same function? Sorry for the simple questions. I've been using Insteon + EISY (previously ISY994i) for 20+ years. I just don't look at this matter but maybe every couple of years. I get rusty.

Michel K. sent out a new version announcement last month. How do I find what my current versions are? If I go to Help > About in the Admin Console all I can see is Firmware IOS v.6.0.0. I cannot find the other version numbers he describes anywhere (Michel I suggest when you send a release announcement you include a link to the installation instructions). I've spent the better part of an hour trying to find the other numbers in my system and browsing the forum for hints. Also, I cannot seem to find out how to upgrade the Firmware. I've done it in the past but cannot seem to remember how I did it. When I go to Configure > System the "Upgrade BIOS" button doesn't function (doesn't respond to clicks). I found a link to an old YouTube video describing the process but the video is way out of date and the screen images do not match my EISY Admin Console displays. Help! Copied from Michel's post: Hello All, I am happy to announce a set of updated software and OS for your eisy/polisy: OS v14.3p9 UDX - v4.4.0_6 IoX - v6.0.5_1 eisyui - v0.10.1

OK, how do I paste code into a forum post and keep the indenting? For some reason it appears to be all shoved to the left and indenting is lost. If I post the same clipboard into Notepad the code appears indented. Thanks for any tip you can provide.

I have this program that I am trying to use to set an integer variable to the current day of the month. When I run the THEN clause the INIT value is correct but the variable iCurrentDayOfMonth is set to zero. This doesn't make sense. I expect them both to be the same. I have a couple of other similar programs using different variables and they work fine. What is going on? TIA DATTM SetCurDayOfMonth - [ID 0047][Parent 0028] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then $iCurrentDayOfMonth = [Current Day of Month] $iCurrentDayOfMonth Init To $iCurrentDayOfMonth Else - No Actions - (To add one, press 'Action') Whereas these programs work fine. Both the variables and its INIT values are correct all the time: DATTM SetCurHH - [ID 006D][Parent 0028] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Repeat 23 times $iCurrentHH = [Current Hour] $iCurrentHH Init To $iCurrentHH Run Program 'DATTM SetCurMM' (Then Path) Wait 1 hour Else - No Actions - (To add one, press 'Action') DATTM SetCurMM - [ID 006E][Parent 0028] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Repeat 59 times $iCurrentMM = [Current Minute] $iCurrentMM Init To $iCurrentMM Wait 1 minute Else - No Actions - (To add one, press 'Action') EISY running version 6.0.0.

I upgraded from an ISY994i to Eisy about a year ago. Didn't notice any difference in performance. Several weeks ago my Eisy stopped running programs and responding to Alexa commands. I went to check it and the box was very hot. I spent a few hours rebooting and trying to debug. It did notice an update was available, which restored its functionality (and now requires me to log on to Admin Console with my portal ID and passwords, which takes twice as long). I don't really know what "locked up" in the Eisy but it was very hot, and I fear it may have shortened its lifespan. In the last 2 weeks I've had wierd problems occur with an IOLinc that has been working for years suddenly getting communication errors. I moved it closer to the PLM (on the same power strip actually) and then it worked fine. I moved it back to its original location (15 feet away) and it failed again. Like I said, it has been working for years without an issue. Nothing else has been changed in that room. My PLM is over 10 years old and everything else in the house is working fine.

Sorry, forgot to post the previous version: DEHUM Toggle - [ID 0062][Parent 0057] If From Last Run Time for 'DEHUM Toggle' + 30 minutes For 30 minutes Then $sDehumidifierOn = 1 $sDehumidifierOn Init To $sDehumidifierOn Else $sDehumidifierOn = 0 $sDehumidifierOn Init To $sDehumidifierOn A separate program turns the dehumidifier on or off based on the value of $sDehumidifierOn.

I'm a long-time ISY Admin Console user struggling with the "From Last Run Time" statement. This is the first time I've tried using it. I'm trying to create a simple program that sets a variable to 1 for half an hour and then 0 for the next half hour. Repeat every hour all day. I've tried different variations of the following code but it doesn't behave I think it would. Or I don't know how this works in plain English. The current version (below) turns on for 30 minutes and then off for 60 minutes. DEHUM Toggle - [ID 0062][Parent 0057] If From Last Run Time for 'DEHUM Toggle' + 1 hour For 30 minutes Then $sDehumidifierOn = 1 $sDehumidifierOn Init To $sDehumidifierOn Else $sDehumidifierOn = 0 $sDehumidifierOn Init To $sDehumidifierOn A previous version, shown below, sets the variable to 1 and just leaves it that way forever. I can see from the status log that the program runs every hour, but never sets the variable to 0. Can anybody please explain the thinking on how this "From Last Run TIme" is supposed to work? In the past I had just hard coded all the half hour intervals, but I thought I could come up with something shorter and more succinct. Alas it is fighting me. No combination of times in the command seems to work. (For those that are curious, I like to run my dehumidifier for just half of every hour so that it has time to defrost between runs.) Thanks in advance!

That PDF shows the module I was wishing for, but I don't seem to find that for sale anywhere on Google. I wonder if/when they plan to release it? Knock on wood my current PLM keeps working until then.