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.

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

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)

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

Thanks for all your help! I upgraded from 5.3.0 to 5.3.3 and after I cleared out all the queued writes, everything has been working just great! I've proceeded to update all the rest of my program-only motion activated suites to the new-for-me Scene plus programmatic Scene Adjust. Very happy with the product and with the super helpful community (looking at you all!) always ready to pitch in. Cheers, Jeff

I wanted less latency with my motion sensor triggered scenes (from program execution), so I'm experimenting with the technique (outlined by others) of creating a scene with the motion sensor and the switch, and using Adjust Scene to change the on level based on time of day, and setting it to Ignore if I have manually hit the switch (that is, if I manually adjust the switch, I don't want the MS triggered scene setting to reassert itself until I turn the light off or the light programmatically times out) Anyway, It seems that the motion sensors are in a constant state of trying to write updates as a result, and I fear the result is that I'm actually getting more latency and light failures because of network traffic. My old programmatic way of doing this never had these problems. So, what am I doing wrong that causes these writes to not be written to the motion sensors? I've just converted 3 of my motions to use this technique and already my console is very unhappy... Here are the relevant programs in my suite Master Bath Adjust for Time - [ID 0059][Parent 002F] If Program 'It's Dark Outside' is True Then In 'Master Bedroom / Master Bath Recessed' Set 'Master Bedroom / ~Master Bath Recessed' To 8% in 2.0 seconds In 'Master Bedroom / ~Master Bath-Sensor' Set 'Master Bedroom / ~Master Bath Recessed' To 8% in 2.0 seconds, No retries Else In 'Master Bedroom / Master Bath Recessed' Set 'Master Bedroom / ~Master Bath Recessed' To 40% in 2.0 seconds In 'Master Bedroom / ~Master Bath-Sensor' Set 'Master Bedroom / ~Master Bath Recessed' To ignore I adjust the overall scene so when I ask google to turn on the light it does so correctly for the time of day, and you can see that during the day, I want the scene to ignore the motion sensor's control of the switch. Then use this one for when I've touched a switch and want to disable the motion sensor for that reason... Master Bath Ignore Sensors - [ID 005A][Parent 002F] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then In 'Master Bedroom / ~Master Bath-Sensor' Set 'Master Bedroom / ~Master Bath Recessed' To ignore Else - No Actions - (To add one, press 'Action') Finally here is the program that uses all these... invoked whenever I touch the switch: Master Bath Switch Use - [ID 0041][Parent 002F] If ( 'Master Bedroom / ~Master Bath Recessed' is switched On Or 'Master Bedroom / ~Master Bath Recessed' is switched Fast On Or 'Master Bedroom / ~Master Bath Recessed' is switched Fade Up Or 'Master Bedroom / ~Master Bath Recessed' is switched Fade Down Or 'Master Bedroom / ~Master Bath Recessed' is switched Fade Stop Or 'Master Bedroom / ~Master Bath Recessed' is switched Brighten Or 'Master Bedroom / ~Master Bath Recessed' is switched Dim ) And 'Master Bedroom / ~Master Bath Recessed' is not switched Off And 'Master Bedroom / ~Master Bath Recessed' is not switched Fast Off Then Run Program 'Master Bath Ignore Sensors' (Then Path) Disable Program 'Master Bath Motion Detect' Else Stop program 'Master Bath Off Timers' Enable Program 'Master Bath Motion Detect' Run Program 'Master Bath Adjust for Time' (If) Anyway, maybe more info than required but It probably can't hurt. Thanks so much for your help! Cheers, Jeff

Like many I have a motion sensor that I only want to work during certain hours. I currently use a program that decides whether to turn on the light or not, but I'd love to reduce the small lag that this requires before the light triggers. I've just found examples of people using a time of day program that alters the scene between the light being an "Ignore" or an "Insteon" setting. This would be great, but I seem to recall that this writes to the device EPROM and over time "uses it up" such that it can no longer be written to. So, two part question: 1) Does this new (to me anyway) 5.x "Ignore" setting strategy somehow avoid writing to the EPROM? 2) Even if still writes to EPROM, what's the current thinking about EPROM degradation over time as a result of twice daily writes? Thanks, Jeff

Thanks lilyoyo1, that link was super helpful and I'm clearly not good with the Search syntax because I frustratingly couldn't find it myself!

OK, cool, motion detectors don't listen or respond. But then just to be super clear, there is no need and no benefit to setting all my Motion Detectors to "Ignore" in scenes? I was thinking that doing so might somehow reduce traffic or something.

I have a scene for a three-way switch with switches at either end of a hall, and a motion sensor on one end of it. Both switches in the scene are controllers and responders for obvious reasons... either switch can turn on the light and both switches must reflect the current status. The motion sensor is in reality a controller only, but when I click on it in the device tree outside of the scene, the little membership tree on the far right tells me it's both a controller AND a responder to the scene. Why? And what is the best way to make it just a controller only? I'm on 5.3. Thanks, Jeff

In 5.3 Scenes, what is the difference between Insteon, Command, Default, Ignore actions? My hope was that Default would trigger the base settings of the device (i.e. those ON settings of the device as it exists in the tree outside of the scene) so that I wouldn't have to reproduce them inside the scene specification. It doesn't seem to be working that way though. And when it does act like it is sort of working, it seems to take a LONG TIME to trigger the desired device changes. Is the Default action just creating a longer execution path to what I used to specify directly in the scene settings? Is what I thought going to be an efficiency actually bogging down my device response time? Anyway, I haven't been able to find a clear explanation for what the new Insteon, Command, Default, Ignore actions are in scenes, nor all of their follow-on parameters, nor the pros/cons of selecting any of them over the others. Any pointers/help would be greatly appreciated! Thanks, Jeff

Yes, what Screw Loose Dan said... it's is much simpler and does not require any programming at all... just to add your scene to the portal, but have the portal tell Google to treat the scene as as a light. This is what I do, and it works perfectly. The only additional thing you need to do is that for your non-load controllers/responders, like the A B C D buttons on a KPL that may be part of the scene... you have to explicitly configure the scene to turn those On using the INSTEON menu pick in the scene member configuration panel. The load/controlling device can usually be left at Default in the menu pick. This is all with the 5.3 firmware, btw.

Xathros, that is a pretty crafty! I like the idea of bumping the backlight level of all the wall switches on the way to the bathroom. I will probably do that too. My boss is sensitive to light when she is sleeping too. Cheers, Jeff

builderb, yes, that's exactly the kind of functional solution I was hoping for - setting the on level to the current level - but searched through all the options in 4.2.18 and didn't see that capability. Is it really coming in 5.x? oberkc, yes, I know, that's how it's all currently implemented... all programmatic. However it's flakey... but I think that is mostly because I've been using the X10 motions (because they are so nice and small and I had them already from my legacy setup). They missed a lot. With the recent Smarthome sale, I got a ton of Insteon motions to replace them, and so now I have the opportunity to put them in scenes. In addition to much higher reliability, I was just hoping to eliminate the slight program delay. Until 5.x comes along, I'm too am leaning toward trading off the instant response for all the functionality of a fully programmatic solution. Cheers, Jeff

Glad this is resolved for the OP. My goal is so similar to the OP's that I thought it best to add on instead of start a new thread. Simple Goal: Use a scene for instant on with a motion sensor, however give precedence to local control of the switch. Have an auto off program because I'm lazy. Scenario: At night, have the bathroom motion turn on the lights at 30%. If I need to actually see something, like the new scratch my cat gave me that woke me up, use the switch to brighten to whatever I need... 50%, 80%, or 100%. Result: Works great, however, as soon as I move, the MS triggers the scene again and resets the light back to 30% Solution: Set the motion to send an On only after the maximum timeout (2 hours I think, which is long enough). This solution kills my motion sensing auto turn off program, and I have to rely only on my failsafe fixed time turn-off program. This is sort of acceptable. Result: Great, now I can move freely, treat my wound and go back to bed. However... sometime before the 2 hour MS timeout has expired, the cat scratches me again and I head back to the bathroom. Because the MS is still sleeping, it does not turn on the light. So here the compromises start to add up and tip the scale against this approach. Solution: Ask the forum for other ideas Thanks in advance, Jeff

LeeG, you're the man! Thanks so much, everything is now working as expected! Cheers, Jeff

Thanks for the quick reply guys. I tried the Scene Test and it said it Failed. Here are the details: Sat 01/05/2013 08:03:14 AM : [GRP-RX ] 02 61 28 13 00 06 Sat 01/05/2013 08:03:15 AM : [iNST-SRX ] 02 50 1E.62.F6 19.81.C4 E1 13 FF LTOFFRR(FF) Sat 01/05/2013 08:03:15 AM : [iNST-SRX ] 02 50 1E.62.F6 19.81.C4 E1 13 FF LTOFFRR(FF) Sat 01/05/2013 08:03:15 AM : [iNST-SRX ] 02 50 1E.62.F6 19.81.C4 E1 13 FF LTOFFRR(FF): Process Message: Ignored Sat 01/05/2013 08:03:15 AM : [iNST-SRX ] 02 50 1E.61.98 19.81.C4 E1 13 FF LTOFFRR(FF) Sat 01/05/2013 08:03:15 AM : [iNST-SRX ] 02 50 1E.61.98 19.81.C4 E1 13 FF LTOFFRR(FF) Sat 01/05/2013 08:03:15 AM : [iNST-SRX ] 02 50 1E.61.98 19.81.C4 E1 13 FF LTOFFRR(FF): Process Message: Ignored Sat 01/05/2013 08:03:16 AM : [iNST-SRX ] 02 50 1E.61.98 19.81.C4 E1 13 FF LTOFFRR(FF) Sat 01/05/2013 08:03:16 AM : [iNST-SRX ] 02 50 1E.61.98 19.81.C4 E1 13 FF LTOFFRR(FF) Sat 01/05/2013 08:03:16 AM : [iNST-SRX ] 02 50 1E.61.98 19.81.C4 E1 13 FF LTOFFRR(FF): Process Message: Ignored Sat 01/05/2013 08:03:16 AM : [iNST-SRX ] 02 50 1E.61.98 19.81.C4 E1 13 FF LTOFFRR(FF) Sat 01/05/2013 08:03:16 AM : [iNST-SRX ] 02 50 1E.61.98 19.81.C4 E1 13 FF LTOFFRR(FF) Sat 01/05/2013 08:03:16 AM : [iNST-SRX ] 02 50 1E.61.98 19.81.C4 E1 13 FF LTOFFRR(FF): Process Message: Ignored Sat 01/05/2013 08:03:16 AM : [CLEAN-UP-RPT] 02 58 06 Sat 01/05/2013 08:03:16 AM : [iNST-SRX ] 02 50 1E.61.98 19.81.C4 E1 13 FF LTOFFRR(FF) ----- Test Test Results ----- [Failed] Jeff's Room (1E 61 98 1) ----- Test Test Results ----- I also did a Show Device Links Table for the switch in the scene, and then a Compare. It showed 5 links in each table: 1 was Identical, and 4 were Record Mismatch. I don’t know what this means, or how to fix it, but it doesn’t sound good What should I do next? Thanks, Jeff

I have recently installed several SwitchLinc Dimmer 2-Wire v.41 (2474DWH). Some of them are already successfully in scenes. I am having trouble with one though… the office switch. In the admin console (v.3.2.6) I’ve linked the office switch to the ISY 99i. I have full control of it through the console. HOWEVER, when I add it to a scene, and turn the scene on and off, the office switch does not respond, although the admin console indicates that the switch is changing states. The switch still responds when I select it in the Network tree on the left and use the On/Off buttons, but not when I select the scene and use the scene’s On/Off buttons. I’ve got 56 devices including all manner of switches, keypads, remotes, motion detectors, and open/close sensors. I’ve got some pretty cool programs for many of these too. This is all to say that I’m not a noob, but I sure feel like one right now because of this crazy 2-wire switch that doesn’t want to play well within a scene! Any clues? This is driving me nuts! Thanks, Jeff

Rats, I was hoping there was a resolution to this... I have the exact same problem

Thanks Xathros!

I have a program that controls the bathroom light to make the place look lived in. I want it to repeat every 1.5 hours give or take while the condition of the parent "Away" folder is true. Is there any harm in using tail-recursion to achieve this? Will memory fill up or does the new call to the program kill the last running instance? Here is the pseudo-code: Program Content for "Away - Master Bath" If - no conditions Then Wait 90 minutes (Random) turn light on Wait 10 minutes (Random) turn light off Run Program "Away - Master Bath" (Then Path) Else - no actions I'm assuming that using a repeat is better, as follows, but I just wanted to understand mor fully how recursion works here. Program Content for "Away - Master Bath" If - no conditions Then Repeat Every 0 seconds Wait 90 minutes (Random) turn light on Wait 10 minutes (Random) turn light off Else - no actions Thanks in advance for any insight. OH, last question... is there a good way copy/paste code from the Admin interface? I had to type these examples in by hand. Just wondering. Cheers, Jeff