2473 OutletLinc is ON but ISY says it's OFF

[slcasner]

I have a 2473 OutletLinc with a table lamp plugged in.   The past two mornings I have discovered the lamp to be ON when I don't expect it  to be.  When I look at the status of that device in the ISY Administrative Console (v4.6.2, firmare v4.9.0) it shows the current status as OFF.  The linked controller, a 6-button keypad, also did not have its button lit and the ISY indicated that the button was OFF.  On the context menu for the 2473 device, I selected Diagnostics - Query Insteon Engine, but that did not correct the status.  

If I click the OFF button in the admin console the lamp turns off, and I can toggle the lamp on and off as much as I want.  When I toggle it ON, then the current status is correctly displayed as ON.

This problem arose after the circuit breaker for that device was off for 48 hours as part of testing my home solar PV system.  Can Insteon devices lose some configuration in that period of time?  I tried Restore Device from the context menu after I first discovered the problem yesterday, but then the lamp was on again this morning.  I know about the Load Sensing feature of the 2473, but the load in this case is just a standard incandescent bulb which shouldn't do anything funny.  And if the 2473 was sensing a load change and deciding to turn on, shouldn't the ISY see that and update the current state?

[MrBill]

what kind of light bulb is it?  If the answer is LED, try a standard incandescent light bulb.  if that works try different LED bulbs until you find one that doesn't cause the effect.  Phillips Warm Glow bulbs typically work very well with Insteon devices, available at Home Depot.

Another thing you can try is to factory reset the device, then do Restore Device again.

Also  your Admin console and firmware version should match at v4.9.0.  If you're using windows,  I'd suggest installing The Launcher from the thread linked below (just read the first post, not the whole thread).  It's a newer method of launching the admin console that grabs a matched version of the admin console.   I do not think the mismatch has anything to do with your lamp module problem, there's not much difference between 4.6.2 and 4.9.0 but you should always be in the habit of firmware and UI versions are exactly equal, it will make a difference if and when you load Version 5.x

 

[slcasner]

Thanks for your reply.  I meant to state in my post that the lamp has a standard incandescent 3-way bulb installed.

I have been using the ISY994 Administrative Console launcher 4.6.2 that I installed in 2017 even though I have updated the firmware since then. ("Why change something if it's not broke?") To access the ISY Launcher and the Dashboard I fetched the new start.jnlp which did start up the ISI Launcher and deposit an alias on my Desktop.  However, that alias refuses to execute on my MacBook because I am still running macOS 10.14 as I have some 32-bit software that I need to run.  I have verified that if I dig down to the actual ISY Launcher binary I can run that just fine.  I looked at the Info.plist file and I see nothing there that would restrict to macOS 10.15, so I can't see how that restriction is imposed.  This launcher is also less convenient because I have to select my ISY in the list of one and use the context menu to select Admin Console, whereas I can just click the 4.6.2 desktop icon and the Admin Console starts up, ready for me to log in. 

I already fetched https://isy.universal-devices.com/994i/4.9.0/admin.jnlp and when I ran it I did get version 4.9.0 of the UI, but it did not install a new alias on the desktop nor a new app in the Java cache.  Perhaps that is because I disregarded the instruction to clear the Java cache since I did not want to lose the 4.6.2 version of the app that was working with a desktop alias. 

[MrBill]

12 hours ago, slcasner said:

Thanks for your reply.  I meant to state in my post that the lamp has a standard incandescent 3-way bulb installed.

Try Factory Reset then Restore Device again. Page 9

14 hours ago, MrBill said:

If you're using windows

I did preface that with "If you're using windows", Launcher doesn't seem to play well on Mac's.

With the admin console it's always important to use the version matched to the Firmware. 

[smokegrub]

"I already fetched https://isy.universal-devices.com/994i/4.9.0/admin.jnlp and when I ran it I did get version 4.9.0 of the UI, but it did not install a new alias on the desktop nor a new app in the Java cache.  Perhaps that is because I disregarded the instruction to clear the Java cache since I did not want to lose the 4.6.2 version of the app that was working with a desktop alias. "

I use a Mac (Mojave) and the alias appears on my desktop however I cannot access the Launcher using that alias. I get the message:

"You can’t use this version of the application “ISY Launcher” with this version of macOS.

You have macOS 10.14.6. The application requires macOS 10.15 or later."

Fortunately, I can place the start.jnlp file on the desktop and access the Launcher through it by double-clicking on it.

[slcasner]

@MrBillThanks, it seems to be behaving itself now.

@smokegrubWhat you report is exactly what I saw.  As I mentioned, if I dig down to the actual "ISY Launcher.app/Contents/MacOS/ISY Launcher" binary I can run that just fine.  I looked at the app's Info.plist file and I see nothing there that would restrict to macOS 10.15, so I don't know how that restriction is imposed.  I'm not a Mac guru.  I have also used the start.jnlp file as you did, but that keeps putting an invalid alias on the desktop.

[smokegrub]

Yes, the alias is invalid. I have "lived" with this anomaly for a few months. From my experience, the workaround is solid.

Best wishes. 

Edited July 23, 2021 by smokegrub
Typos