MrBill

I agree, and I would suggest body... i can't remember why I think this, but it seems like there is/was/might be a long standing bug around displaying variables in the subject line. Once it's working them move to putting it where you want it.

Excuse me, but this doesn't answer the question. Nor does it help people scrolling thru the forum in the near or distant future trying to figure out there own problem. I've seen people in this very forum later reply, "sorry I assumed since the unit had the lastest firmware because it was just shipped to me. I've also seen, I didn't know we had a 5.6.3 I thought it was 5.3.0. Look at the admin console Help > About and answer the question. Also verify that firmware and UI versions are identical. </rant off> this simply must be programs. I can't explain why they behave differently today than they used to without seeing your programs. Yours is also a one-off complaint.... meaning out of 1000's you're the only one reporting this problem, that fact also points to your programs. When a change or bug comes thru that effect the way things have worked for years... we hear about it from 100's of users and those of use who help people in the forum get tired of typing the same thing over and over again... that's not happening here. One person is complaining that on-level suddenly and magically gets changed somehow. Most of us are happy to help you figure it out, but you'll have to play the game too.

Does it work if you try the same variable in the body instead? (this will suggest if there's an issue with where it's used and opposed to not working at all.)

@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.

Actually insanely funny in my case.... I have some artwork (here is 30 second video clip is of 3 of the 5 pieces) that changes color via hue constantly 24 hours a day... it's even changing color when it's off. When I click on any day of history (such as yesterday) it produces a few hundred records getting us back to 11:59PM.... (i.e. 1 minute of history) then it pauses for awhile before it says "an error has occurred". I'd love someone to go searching thru my history.....

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?

I have something similar, I have most all dual band devices and have no issues with Insteon in the outbuilding.

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.

There was a period that both methods worked... without looking Feb was the release of variables as numbers, variables as sensors were deprecated at that time, but continues to work thru (without looking up the date) the HA May release. Both were covered in the release notes (and here). During the interval that both worked you should have seen a message in the updates section that "The isy994.set_variable service will be removed" and to "Update any automations or scripts that use this service to instead use the number.set_value service with a target entity ID of this device." This was an announced and planned change to better align with the methods of Home Assistant... tread numbers as numbers, rather than text value sensors. This was not a surprise for those that read the HA release notes or this forum. See Bullet point 5 in this post:

the If statement: If therm.setpt <= 9999 basically runs every time therm.setpt changes, and always resolves true. Therefor the variable is always up to date. Running Then manually should have no apparent effect unless you change the value of the variable manually first.

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.

Excellent usage and need. I actually have something similar, using a "scene" that sets a variable via alexa. Keep in mind that the portal "Alexa scene" can be configured to update a variable. "Alexa, set temp to 72" can set a state variable. (what's actually happening is the variable is being set to a percentage, but you can drop the word percent when talking to her. SO in essence you're naming a scene "temp", having it set a state variable to a percent but you can forget that it's a percent. Just be sure when writing your programs to throw out bad values. for example when my downstairs fireplace temp is changed via the method the only valid value in the ISY programs are 63 to 75... if someone accidentally or on purpose sets a larger or smaller value it just blinks a nearby lamp and doesn't actually change the set point. the method works for anything but keep in mind values are limited to 0 to 100, because you're actually telling her a percent but just not saying the word.

@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.