MrBill

eisy is local just like the ISY. does it need to communicate with the internet ever? yes for updates, but not for day to day operation. Generally that true for Polyglot running on eisy too, but some node servers do require access to the internet if they are contacting a cloud based device.

If you got that, I think you need to replace your microSD card, that a sign.. so are the "mysterious" offline events you're experiencing. Make certain you have a good backup.. and don't delete any old backups at this point until you're back to stable again. Order a 32gb MicroSD from your favorite retailer, watch for the A1 certification. Any size below 32gb is fine, but not above. The most econmically priced tho will likly be 32gb. Install it in the ISY, the built-in bootloader is not a full version of ISY firmware, so the first step once you've replaced the card and get back into firmware is to reload the firmware via "manually upgrade ISY"... after the restart from that then you can restore your backup.

I assume it's still there on eisy... on Polisy you need to know the url to get there: http://IP.OF.THE.ISY:8080/WEB/udajax.htm basically the IP with :8080/WEB/udajax.htm appended. I read this page in the wiki, which is what I think you're trying to do, but I don't understand it either.

This came up in another thread recently (linked post and the next)... Wait with nothing following doesn't turn the flag green.

if you think you have firmware corruption... doubtful.. just reload 5.3.4 over your current 5.3.4. I don't think factory reset is going to help you get beyond this issue.. likely either your PLM is on the way out or you have a corrupt SD card in the ISY.

You likely didn't need to restore the backup when this happened the first time. As for today, if you're still unable to logon via the admin console what are the lights on the front of the ISY doing? https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs/Lights

Upgrading from v4 to v5 isn't too difficult... read this post from yesterday. I forgot to mention in that one, the first thing to check when your logging into version 5 the first time is help > about to insure that the UI and firmware versions match. if they don't do not pass go, solve that problem. The second thing to do one your firmware and UI versions match is to check Programs tab, Summary sub-tab and look for the color yellow... if you find any that program needs manual updates (probably from use of "adjust scene") 5.3.4 is here. If you have a 300 series z-wave board (z-wave version 4.81.00) then you need 5.0.16C instead.

did you try restarting the admin console?

I'd add that program I linked in the other thread... then you can use aaaa1test - [ID 01F9][Parent 0001] If $sISY.MMDD is 3.15 Or $sISY.MMDD is 6.15 Or $sISY.MMDD is 9.15 Then Set 'Coffee#' On Else Set 'Coffee#' Off

Aha... and the line right above the screen shot contains the magic: I had forgotten about that since I don't use it....

I'm not sure where you got that screenshot, I can't find the schedule interface with the date like that anywhere. Now that your on 5 tho, you can add the program i linked above to give you the date variables you're looking for.

check Help > About are your firmware and UI version numbers the same?

the biggest issue with migrating v4 to v5 is programs that use "adjust scene" require manual intervention. Another caveat is you need to know what programs (if any) must be disabled, because disabled programs will be enabled. In addition to a standard ISY backup I also recommend backing up your programs in text format. Right click the root folder of the program tree (often named "My Programs") then right click it and select "Copy Folder to Clipboard" (near the bottom of the list). then open any text editor that won't add formatting (windows Notepad is dandy) and paste then Save As. You now have a reference copy of your programs if you need to look back after upgrade. With those things in mind, as @larryllix points out, upgrading isn't difficult anymore.

I have the most luck with New Insteon Device and leave the drop down on auto detect device type. Have to watch out for 0 / D and B / 8 in the device address tho because they are easy to confuse because of the font used on the label. The Start linking method avoids those issues, but I have trouble getting especially battery devices to link using this method. You mentioned many programs have "out of memory"... typically that indicates mis-matched firmware and UI.. Help > About the firmware and UI must match exactly. I missed that no one had addressed that fact after your first post above, and this might prevent you from being able to add devices.

i use the program in the post linked by @kclenden This keep variables up to date or triggering (state variable) or filtering (integer variable) for Day of Week, Day of Month, Month of year, Weak of Month, and month/day in mm.dd format.

the guide to blinking lights is here: https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs/Lights If red and blue are flashing simultaneously the ISY is unable to reach your network. Perhaps a bad cable or the router might need a reboot. Also note: plug the PLM in first, and give it 20 or 30 seconds. It must be online before the ISY. The PLM connects to port A.

Tool > Diagnostics > PLM Info/status is the only place you will see the PLM. When you try to re-add the device are you using Link Management > Start linking or Link Management > New Insteon Device? If the latter are you leaving the "device type" dropdown on Auto Detect? If you haven't tried the "start linking" method please try that. Also can you bring the device so that it's next to the PLM when you add it? Finally have you tried factory resetting the battery devices? That's a lot of questions, sorry, some perhaps you've already answered.. I'm just trying to get you back in business.

I usually protect the timer by linking 2 programs... Program1 If Condition that might change then run program2 (then) Program2 if (none) then disable program 1 do whatever wait whatever do somemore enable Program 1

that's quite normal. all devices actually have an extra digit, for simple devices it's always 1, for multi-node devices each (such as the motion detector) each node with have a different 7th digit. The first step to debugging this should be from the admin console can you operate the flagpole light via the buttons on the device page? Second question, can you open the dusk.dawn node of the device tree and see the node status during the day and after dark correctly? My bet is one or the other device isn't working correctly.

Sorry, now that you mention that... I do remember that from page 1 of this thread, the thread got pulled a different direction tho, or at least it did in my mind.... I see you're still on v4.9 so I'm not certain if this is helpful, it's been a long time since i was on V4: Have you tried right clicking one of the nodes that is showing up and group devices? Also if you click the top folder in the device tree (usually name "Network") and look at the table in the right pane, does that only show two nodes? (I have found devices that didn't seem to exist with group/ungroup in the past.. not sure how they hide) I did just re-read the thread from the top, it's unclear to me if you tried: Delete device from ISY, Factory reset Device, Re-add device to ISY. Which method are you using to add the device? If using "New Insteon Device" are you leaving the device drop-down on "auto detect".

Disclaimer: I don't have z-wave. What I bolded above is exactly what would have happened on the 994 if the devices in the if statement were insteon. This suggests to me that your analysis is correct and the newer firmware corrects a bug that exists in the 994 firmware. It's hard to test this theory unless you have an extra identical switch or are willing to move the device back to the 994, however to test this theory, create an integer variable $iTest then create a program with the IF being just the AND portion that you removed, and make the THEN simply wait 5 minutes after the wait increment $iTest. Test both on 994 and eisy and observe the green flag on the running program to determine when the program is waiting and when it terminated because of a change in state.

I should have included the disclaimer that I was just comparing text in messages on the forum and don't actually have the node server.🙃 glad you got it working tho...

I knew you had tongue in cheek on the cost, but I did want to point out that the single subscription does cover multiple devices.

Did you include token.txt on the path? if so, then don't...

There is a node server called virtual that lets you change a variable into a device node. Scene's don't actually have an on/off status which is why you can't check it via a program.