Programs stopped being triggered. Sensors need Writes according to one computer, but not to another

[Oakland Jeff]

We had some power brownouts recently, so I'm going to blame them for this...

BTW, I'm on Firmware 5.3.3, Windows 10, Chrome.

1. All my programs, which I can see via the Admin Console, have stopped being triggered by anything

Not by sensors, not by dusk/dawn... nothing. So far I've cleared the Java cache and as a result downloaded a new ISY Launcher, but they still do not run at all. They run when I manually start them from the console, but nothing external triggers them. Scenes in which sensors participate as controllers still fire. However, because my dusk/dawn program that adjusts the scenes does not fire when it's dusk anymore, all my motions turn the lights on to daytime settings.

2. One computer with Admin Console shows that almost all of my sensors need to Write updates, but another computer does not

My main system (Desktop, Windows 10) shows sensors needing writes. OK, so instead of bothering my wife to trigger the sensor so I can hit Write Updates to Device in the console, I thought I would install Java and the ISY Launcher on my laptop and just walk around and do it all myself. When I fired up the newly installed Console on the laptop (Windows 11), it didn't register any writes being required. What's up with that? I suspect, but am not sure, that it's my dusk/dawn program that adjusts all my scenes for night vs. day settings that cause the need for writes... but (a) I thought that wasn't supposed to be an issue for the last several releases, and (b) why would the two systems show different things? It's not like the desktop computer was responsible for causing the writes to be needed. As mentioned above, cleared Java Cache completely on my desktop but it's still showing writes needed.

Thanks in advance. I'm really pretty stumped here.

Cheers,

Jeff

[MrBill]

Help > About...  what is the firmware and UI version?

Try: unplug ISY, Unplug PLM, wait 30 seconds, plug in PLM, wait 30 seconds, is the light on the side of the PLM solid green?, Plug in ISY.

Try: different power supply for the ISY.... there were some supplied by UDI with ISY's that don't do well after brownouts. The Bluepower light comes on still, but functionality is effected.  You can try any power supply that outputs anywhere between 5 volt and 30 volts,center positive, 2mm barrel connector.

[Oakland Jeff]

Thanks MrBill, but no joy. Sensors are still not triggering programs.

BTW, Firmware and UI are both Insteon_UD994 v.5.3.3 (2021-03-07-20:51:27)

[lilyoyo1]

4 hours ago, Oakland Jeff said:

We had some power brownouts recently, so I'm going to blame them for this...

BTW, I'm on Firmware 5.3.3, Windows 10, Chrome.

1. All my programs, which I can see via the Admin Console, have stopped being triggered by anything

Not by sensors, not by dusk/dawn... nothing. So far I've cleared the Java cache and as a result downloaded a new ISY Launcher, but they still do not run at all. They run when I manually start them from the console, but nothing external triggers them. Scenes in which sensors participate as controllers still fire. However, because my dusk/dawn program that adjusts the scenes does not fire when it's dusk anymore, all my motions turn the lights on to daytime settings.

2. One computer with Admin Console shows that almost all of my sensors need to Write updates, but another computer does not

My main system (Desktop, Windows 10) shows sensors needing writes. OK, so instead of bothering my wife to trigger the sensor so I can hit Write Updates to Device in the console, I thought I would install Java and the ISY Launcher on my laptop and just walk around and do it all myself. When I fired up the newly installed Console on the laptop (Windows 11), it didn't register any writes being required. What's up with that? I suspect, but am not sure, that it's my dusk/dawn program that adjusts all my scenes for night vs. day settings that cause the need for writes... but (a) I thought that wasn't supposed to be an issue for the last several releases, and (b) why would the two systems show different things? It's not like the desktop computer was responsible for causing the writes to be needed. As mentioned above, cleared Java Cache completely on my desktop but it's still showing writes needed.

Thanks in advance. I'm really pretty stumped here.

Cheers,

Jeff

What sensors? The Isy supports many types

[Oakland Jeff]

Motion (both I and II) and door open/close

[MrBill]

42 minutes ago, Oakland Jeff said:

Motion (both I and II) and door open/close

What happens if you open the admin console and click a node on the main tab,  can you watch the status change there? 

 

 

[Oakland Jeff]

Wait, something's fishy here... 

OK, so to answer your question, no. My front door Open/Close Sensor (2843-2) is not showing any status at all... just blank.
And this is really sus... The device, an Open/Close Sensor (2843-2), is shown in the console as a TriggerLinc v.00 (2421) !

That said, my misbehaving motion sensors are listed as the correct type of device.

Edited November 15, 2021 by Oakland Jeff

[MrBill]

24 minutes ago, Oakland Jeff said:

Wait, something's fishy here... 

OK, so to answer your question, no. My front door Open/Close Sensor (2843-2) is not showing any status at all... just blank.
And this is really sus... The device, an Open/Close Sensor (2843-2), is shown in the console as a TriggerLinc v.00 (2421) !

That said, my misbehaving motion sensors are listed as the correct type of device.

Blank status means it hasn't received a status since the last time the ISY was rebooted.

2421 is a version of the open close sensor. All of mine show up as 2421's also... 2843 is probably more about packaging than model of sensor enclosed.

First the obvious question... are the batteries good?  Does the LED on the sensor flicker when you open/close the door?  Did you try different battery?   (sorry for the elementary question and it does seem odd that all batteries at once would be dead, but that would be my first thing to eliminite). 

[Oakland Jeff]

Yea, batteries all good on all my sensors. AND remember they are still triggering the scenes they are part of. The ISY just seems to be blind to them... they are not triggering programs and I'm not able to get status from them.

[Oakland Jeff]

Other bits of if info... Yes, I can control all the lights using the admin console. No, using my RemoteLinc 2 turns on the lights that it is in a scene with, but does NOT initiate the program that automatically turns the lights off after an hour.

[MrBill]

28 minutes ago, Oakland Jeff said:

Other bits of if info... Yes, I can control all the lights using the admin console. No, using my RemoteLinc 2 turns on the lights that it is in a scene with, but does NOT initiate the program that automatically turns the lights off after an hour.

This sounds like an Noise issue, something is keeping the Insteon signals from getting to the ISY.  There's a couple troubleshooting pages in the wiki...

• 6.18.3 INSTEON Signal / Noise Troubleshooting
• 6.18.4 INSTEON No Status Feedback From Devices

Others here are better at giving advice on this topic than I am, to be honest.

 

[Oakland Jeff]

6 minutes ago, MrBill said:

 

• 6.18.4 INSTEON No Status Feedback From Devices

 

Thank you MrBill, you put me on the right track!!! The first step on this page is to look at the PLM link table making sure that there isn't more than about 900 links. HA! I only had 6 links in mine!!! I restored my PLM (back to around 300 links) and it solved everything. Thank you!

[MrBill]

Glad restore PLM worked for you.

Two things to keep in mind.... 1) That maybe the PLM going bad, in other words keep your fingered crossed that it doesn't come back soon.

2) link counts have to be done when there is no other Insteon traffic or they won't be accurate.  the hardest thing to stop Is wireless signals (including heartbeat).  Because of this, link counts need to be done several times to prove accurate.