Bizywk

Thanks lilyoyo1. We're still holding our cards where they are for now. If I could find a supply of Motion Sensors to replace the one that just went bad, that would be great. My wife didn't see the value in the home automation system when I proposed the project, but lately she's sure been hinting that trying to live without the one bad sensor is difficult. I spoiled her.

I see where you're coming from, and I think you have a very reasonable response given the apparent slow motion demise of the Insteon brand. I have been grappling with the same decision myself for several months now. However, its hard to argue, even with the current product line neglect, that Insteon isn't still superior to every other competing product line out there in terms of reliability, flexibility, scalability and performance. I have a large home installation with a substantial time and money investment in Insteon that I REALLY don't want to replace.

I've been searching for a replacement Insteon Motion II sensor since late last year and can't find them anywere. Out of frustration, I contacted Insteon directly to see if I could get the necessary repair part for my home system. They informed me that beyond the long time supply chain issues that has had most Insteon parts in very short supply for an extended period of time, that at some point they decided to permanently discontinued making the Motion II sensor with no alternate to choose from. As a community, we need to figure out a solution to the original posters question: Is there a viable Alternative to the now discontinued Insteon Motion Sensor II?

Ooops. I failed to answer your age question. Unsure - 3y maybe?

I was hoping to avoid a trouble ticket, but I think you're right, and there is probably no other alternative. I'm starting to wonder if the issue here really isn't my operator error - except that all other ISY functions appear to work very well and no one else on this forum board seems to be having trouble getting State values to work properly. I'm just at a loss to find the issue. I'll probably file a trouble ticket later tonight unless I can strike gold on this forum tonight. Thanks for your help though! I appreciate it!

The only way I can get the State or Integer values to change is a manual change on the Variables Table screen which would then be immediately reflected accurately in the "Last Updated" box with the correct date and time of the manual change. I just manually updated the State Value. The attached is a screen grab (#5) shows the updated value matched against the current time in the upper left corner. Just for giggles, after that screen grab, I then right-click/Run Then and right-click Run Else on both programs. All four attempts are conspicuously absent from my log - screen grab #6 attached.

Sorry to bother you all with this, but I've read the Wiki and scanned the forum boards and can't seem to find my problem. Hoping someone smarter than I can point to my error. I've had my ISY994i/IR Pro exclusively in combination with Insteon devices for a few years now and have been very happy with they system. Now that I have a little more time available, I'm trying to get a little more refined with conditional programming, but having trouble with the simple task of getting either Integers or State values to react. They stay unchanged after many attempts to prove that I can adjust their values via test programs. I found one other forum chat with exactly the same symptoms, but ultimately realized his test program was disabled. Here's where I am at: 1. Created both a new Integer and a State value with the following settings: initial:0, Value:0, Prec:0 and saved. They are the only Integer and State value containers I have. I want to prove can change their values via programs. 2. Created Test Program 1: Named Test1_StateValue If: No conditions Then: $State_1 += 1 Else: $State_1 +=10 3. Created Test Program 2: Named Test2_IntegerValue (Same settings except used $Int_1 for both Then and Else statements with same value settings. 4. Attempted multiple tries manipulating the values using Test Programs 1 and 2 (right click/Run Then, and right click/Run Else, for both) Each time, I checked for a change in the variables table of the UI and found unchanged zero values after each attempt. 5. Refresh Values and Reload from the Variables Table Screen was tried repeatedly after each test iteration to ensure I'm not looking at old static data. 5. Changed Test Program 1 to: $State_1 = 1 Else: $State_1 =10 , as well as also using the same values in Test Program 2 (adjusting the action for $INT container of course) Tested both sets of Run Then and Run Else commands but still get no value changes or Last Changed updates. I restarted my ISY and tried the full testing procedure again. I upgraded the ISY firmware from v5.0.13 to Insteon_UD994 v.5.30. (dtd 2020-10-01) and tried all the above testing again from scratch with no joy. I have tried periodically Refreshing and Reloading from the Variables Table screen. I've tried testing after changing the prec value to no avail. I verified that my test programs were enabled. I tested an unrelated program and it worked as expected proving that the issue isn't affecting all program executions. I checked all other existing live programs to ensure they had no links to any INT or STATE value containers. I can manually change the value in the Variables Table screen and that's the only thing that will change the Last Changed date. I'm at a loss. Any suggestions?

Great input. Thank you all. Disabling and re-enabling the Alexa App seems to have done the trick for me - at least for now. Alexa suddenly "Supports" my specific sensor again. I am able to again see and select my hidden door sensor. Strange how unpredictable this stuff can be.

I stepped up from an Insteon hub to a new ISY994i and I'm pretty happy with it. I then set up an Alexa routine to recognize that the master bathroom door closed (via insteon Hidden Door Sensor 2845-222) which then initiates a scene to turn on the lights at 30%, command Alexa to say good morning and have Alexa start playing a favorite iHeart radio station without having to utter a series of verbal commands when we're trying to wake up. It worked extremely well for a couple weeks but now today unexpectedly fails to execute the whole scene. The lights come on properly, but that's it. The problem doesn't seem to be with my ISY, but rather Alexa even though she executes part of the routine when the door close sensor is triggered. As I was fiddling around with it, I tried to delete the routine and re-create the routine from within the Alexa app but noticed that while the sensor is still in Alexa's list of devices (in her app), and she detects it when I delete it, re-add it and ask her to discover devices, the routine writing page says that it still can't see a single triggering device. I re-advertised it to Alexa a number of times from the UD ISY Portal, etc. In my research, I noticed that this sensor is not supported by Alexa anymore. ??? Alexa still uses it to trigger the scene part of the routine. 1.) Are there any tricks I can use to get alexa back to recognizing my existing door sensor and executing my full routine? I suppose I could rig the door with a second non-insteon sensor if I had to (Maybe ZWave), but the reviews on those sensors aren't fully encouraging and won't be hidden. 2.) Are there any better ways to use my ISY to directly command alexa to verbally greet and play a live radio station than to use a routine?