MrBill

@pyrorobert https://blueirissoftware.com/Forum/viewtopic.php?t=3092 https://blueirissoftware.com/forum/viewtopic.php?t=2986 https://blueirissoftware.com/forum/viewtopic.php?t=2802

Three possibilities... the On-level is actually changing, this is likely a program changing the on-level. The On-level is not actually changing but for some reason the admin console is displaying it as zero. In this case clear the java cache including installed applications and applets, remove any copie of start.jnlp or admin.jnlp that are laying around your filesystem, download a new copy of start.jnlp and double click it. When you're setting the on-level in the admin column you are not setting the value in dropdown and then Pressing the On_level button to the left of the dropdown.

you must delete the .state files as linked by @Geddy they are corrupt. the admin console is opening outside the visible window for some reason. I'm not certain you needed to change your MicroSD card, you might retry the old one after your get your admin console issue resolved. FYI, With a new unused MicroSD card installed, the firmware bootloader burned onto the ISY994 is only a partial firmware image and is very old at that, to be operational you MUST use Help > Manually Upgrade ISY and load a complete firmware file.

Reboot your ISY. If that doesn't solve it, clear your java cache including installed apps and applets. delete any files you have laying around named start.jnlp, download a fresh copy of start.jnlp. and run it. if your on a mac you may need admin.jnlp instead.

Internet Access Disabled on Help > About doesn't actually mean that internet access is disabled. In short it means something else entirely, and perhaps should be labeled "UPnP disabled". To be clear: Internet Access on Help > About should say disabled, unless you're trying to use UPnP to expose your ISY to the internet, which might have been something people were doing when the 994 was invented, but not a safe or best practice in 2023. On to your problem.... what happens when you log into the portal? does the green Online circle show? in the admin console, Configuration tab, Portals Sub tab does it show Online and Registered? back in the portal, Select Tool > Information > ISY Portal Access License... has your subscription expired?

@MarcusD My take at the moment is just start over. Get your eisy up to date and connected with a new PLM or newly factory reset PLM. once it's working, factory reset every device one by one and add them to the new installation. This thread is 6 days old, spinning wheels any longer is just nuts... you can be done with it in another few days.

interesting... i've not had to format new cards before. glad it worked.

you have non "plus" firmware, it doesn't exist. that's a soft upgrade, if it's still available it's pay the money and the feature unlocks next time you start the admin console. Sadly it's included in polisy and eisy. Plus adds to the total number of nodes and programs, as well as give you those two buttons.

from the wiki: Only Error light blinking: ISY cannot communicate with the SD Card. Please ensure: The micro SD Card (on the front) is seated properly. Unplug ISY, remove the rubber cap, using a sharp object, push the micro SD Card in so that it pops out. Push it back in so it clicks in. Apply power to ISY If reseating the micro SD Card does not work, you probably have a defective SD Card. Please consult Replacing/Formatting SD Card So your new card is bad or the wrong type, or not seated correctly. you need 32gb or less (look for the newer A1 rating for better wear, the ISY doesn't have the hardware for A2 to be effective). To be clear, the error light should NOT be blinking with a fresh card installed. Second, the first think you must do after a new card is installed in "help" -> "manually upgrade ISY" and load the full firmware file that you'd like to use. The burned in bootloader that fires up the ISY with a new SD card installed is NOT a full version of the firmware, and what's there is very out of date.

Turn off the far right two buttons on the admin console ribbon. ---> . this will make it so that only the device in the tree that you have selected will be written to. By default if the ISY is going to write it writes to all devices that have something in the queue. I'm not sure what you've got going on here. I've read those two paragraphs a dozen times and i'm just not getting it. I will say tho that if you delete the device from the ISY you should also factory reset the device before adding it back.

Do you have Insteon support checked on the configuration tab? Also read the migration instructions https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration

If you log into the portal there is a method to create a node server for occupancy (Select Tool > Occupancy Node Server), that appears in the Polyglot interface as "ISY Portal" It will always appear "Unmanaged" in the PG2/3 interface because it is not managed by Polyglot and it is using a slot, but managed by the ISY portal.

I was just about to write a post asking about that.. @landolfi it's in the "configuration" tab of the admin console.

Help > about what are both version numbers listed?

Literally everyone's time need will vary for one reason or another. Sometimes there are unforeseen glitches to be worked out. eisy does not have a speaker. PG2 never existed on eisy. PG2 is removed from Polisy when PG3x is installed. If you've installed PG3x on Polisy and are still seeing PG2 it sounds like you have not rebooted.

I can't imagine how either. If you Delete PLM you will literally be starting from scratch. Ground zero, nothing to restore anymore. At that point i would factory reset each device as you re-add them to the ISY. This action is non-reversible (with the exception of restoring a backup should work). You can factory reset a PLM, then "Restore Modem". Yes and no. Cloud works but it will be faster if you do it on the local LAN. Event Viewer is a Viewer, it doesn't write any files. If I didn't understand the question then please restate.

@MarcusD I'd try "Restore Device" individually on every single node. It's a pain and depending on the size of your system and number of scenes may take awhile. You can try intially on the devices you know have issues to prove that it's the solution. Then do them one at a time. The issue: Every device knows the Device ID of the PLM, and it likely effects many links in each device. When "Restore Modem" is selected after a PLM change occurs, the function checks the known value of the PLM (the BEFORE value) and compares that to the device ID of the currently connected PLM (the AFTER value). If those are the same Restore modem simply loads the links that ISY thinks should be in the modem back to the modem. On the other hand, when BEFORE and AFTER are different addresses, then Restore Modem first Updates the entire Link database for both PLM and Devices, replacing the BEFORE value with the AFTER value where ever needed. Then it writes all updated records to BOTH the PLM and all devices in the house. In this mode it can take a very long time. So long that in larger systems if your not expecting all the work the ISY must do that you might interrupt it saying this busy bar shouldn't be here... it's stuck. It's not stuck, in larger systems it could take hours. Add to that normal traffic on the Insteon network that creates collisions and errors. Problem being that once the address change run has been executed BEFORE and AFTER are now the same.... so the function will only run in the more simple mode. I think that some people have had success using yet another new PLM to change BEFORE and AFTER again. Better tho I think is just sitting at the admin console and doing "Restore Device" from the top of the device tree to the bottom. This ensures fresh links everywhere and minimizes the chance that normal life (a family member flipping a switch that initiates Insteon traffic) being collisons that cause errors. Doing one device at a time lets the network settle for at least 10-15 seconds while you're moving to the next device.

Devices talk back... Scenes don't. Send ON to a device, the device responds to the sender. Send ON to a Scene, responders turn on but don't generate traffic. Device: Scene: I think the original design consideration (way back almost 20 years ago) was that acknowledgement of signal received was the thing X10 users wanted the most, therefor device ACKnowledge receipt of a signal. However due to the relatively slow speed of wireline transmission it's not practical to do that for more than 1:1 communication. Consider I have a scene use as "downstairs-All Off"... it has 40+ responders, if all 40 responders had to acknowledge it would take way to long and jamb up the network.

tagging @shbatm on this discussion because it involves Home Assistant, even tho you've manually reproduced and indicated the issue is on the IOX/ISY side.

known issue. there's at least a dozen threads with the same question. You don't have bad space, it's a bug that's been around since Polisy was released.

No, but there is a thread for Zigbee Device support requests... Basic zigbee switches might work, but there will be many devices that must be "supported" before they work.

(disclaimer: I didn't carefully read everything said after I saw the issue, but I did skim it and didn't see anyone really pointing this out directly.) It's much easier to use 3 or 4 scene's, one each for Low, Medium, High and optionally one for off, although you can really do off with any of the first 3 scenes). Once you've converted to the multi-scene method, then your programs, Home Assistant, etc can all turn on or off the appropriate scene and the buttons will stay in synch, rather than using all the helper programs you have to update buttons status afterwards.

Since your original issue appears solved, you might want to start a new topic in the UD Mobile section of the forum for better exposure.

The admin console has program search available after right clicking a program name. it doesn't matter where in the tree you click from, the search will always start at the top of the tree. Its easier to use the various drop downs for objects such as variables/nodes/scenes. When using RAW text keep in mind case counts.

I wonder if @kclenden might get an email from this mention and hopefully log in. He’s the best at reading and interpreting logs and link issues of anyone that’s ever participated here.