jerlands

I'm also running v5.0.2 and created a couple simple programs to see if if sunrise to sunset had any impact and for me it operated as I would expect. New Program - [ID 00E9][Parent 00CC] If From Sunrise To Sunset (same day) Then $s.Test = 1 Else $s.Test = 0 New Program_B - [ID 00EA][Parent 00CC] If $s.Test is 0 Then Set 'Light Media Room' On Else Set 'Light Media Room' Off I'm still thinking you have some other program that's changing the variable "Light." I'd bet if you were to change the variable name it would run properly also. One of the reasons I think you have conflicting programs is your logic in assigning the variable. In my way of thinking I see 1=true and 0=false and I'm guessing at sometime you created a different program assigning "Light" values using the same logic. Jon...

How do you know the variable is changing back to 0? Do you have other programs that are reacting to the change? Also, do you happen to have an Integer variable named the same i.e., Light? Jon...

You can search your programs for $Light (right click programs > "Find/Replace") Jon...

The only way for this program to change the variable $Light = 0 is for the program to trigger while true and run the Then clause. You need to adjust the time from sunset to something where you can watch it change to false (run Else or $Light = 1) and then observe if the program turns true or something else is changing it. Jon...

What does the program status read.. true or false? (right click on "My Programs" > Status Icons > Detailed) I'm assuming the conditions are for (same day) The only thing I see is that when naming variables it helps to develop a convention that designates State or Integer e.g., $sLight for State and $iLight for Integer. Jon...

I just logged on without issue and tested Echo which is working. Jon...

From what I can tell your comms look good.. Hops Left=2, Hops Left=3 are good. Hops are the number of times the message gets retransmitted before reaching it's destination either from the device to PLM or from PLM to device. If the motion sensor "turns on" that message gets sent and if received by the PLM directly you'll see Hops Left=3 but if it has to be retransmitted by another device then the Hops count is reduced by 1 so you'll see Hops Left=2... anyway.. I don't see a problem showing up. Things that can cause communications issues are signal suckers and noise makers on the powerline. Some LED/CFL bulbs cause these problems while a UPS can dampen the powerline signal so if you happen to see any correlation with misfirings and an event like a light being on you might look into it. Also, most I believe turn the LED off to conserve battery life so what your seeing in the motion sensor's flashing light may be normal but I imagine it flashes when receiving or sending messages. Maybe someone else can see something in your trace. Jon...

"Motion (Deck)-Sensor is On" is likely the problem if it's status changes before wait completes (1 minute.) You can observe this by setting the status icons to detailed (right click on "My Programs" > "Status Icons" > Detailed.) If "Motion (Deck)-Sensor is On" changes status the conditions are re-evaluated and if they are false then wait stops and Else is run. The way around this would be to set a State variable with "Motion (Deck)-Sensor is On" and use that as a condition Also, you can copy your programs into a message by right clicking on the program and select "copy to clipboard" at very bottom. Jon...

This will help in communications test. The Event Viewer trace will show number of "hops" required for communication to and from devices. If you go to Tools in the top menu bar then to Diagnostics you'll see Event Viewer on top. Open it and on the bottom you'll see a "Clear" button then the text "level" followed by selections. Choose (3 Device Communications Events) Jon...

Open Event Viewer (Tools > Diagnostics ) to level 3, clear and then test your motion detectors and micro switches, copy to clipboard (notepad looking icon) then post results. Jon...

Jon...

It's working better for me but I think we're limited to 3 word naming. I'd like to be able to name "family room fan" and "family room fan light" but only "family room fan" is recognized. Jon...

You can paste your program into your reply by selecting the program, right click and copy to clipboard (bottom option) the either paste directly into reply or use code quotes (select angle brackets in toolbar <>) Jon...

Failed to add device, reason 3 <<-- Reason 3 = lack of communication 37 10 77 <<-- Are you certain this is the right address? How did you go about adding it? New Insteon Device or Advanced Options? Jon...

You may have to resort to removing devices and re-linking... How many devices do you have and how many links are in the PLM? Jon...

If I understand correctly you will only show an E2 if the device has been added to a scene as a controller. Otherwise your device links table will show A2 for responder. Jon...

Night Ramp Rate Program: If 10pm-Sunrise (next day) Then In Scene MS-Sensor Set Switchlinc 30% (On Level) In Scene Switchlinc Set Switchlinc 30% (On Level) <<--- Try adding this line... In Scene MS-Sensor Set Switchlinc 4.5 Sec (Ramp Rate) In Scene Switchlinc Set Switchlinc 4.5 Sec (Ramp Rate)<<--- Try adding this line... Else In Scene MS-Sensor Set Switchlinc 100% (On Level) In Scene Switchlinc Set Switchlinc 100% (On Level) <<--- Try adding this line... In Scene MS-Sensor Set Switchlinc 0.1 Sec (Ramp Rate) In Scene Switchlinc Set Switchlinc 0.1 Sec (Ramp Rate) <<--- Try adding this line... Jon...

"Refresh Devices" doesn't work any longer... you need to log into Portal and select Amazon Echo from Tools. Jon...

Yes, you might as well give it a try Instructions in the wiki... FR command Jon...

To factory reset devices it's best to refer to owners manual because this procedure can vary slightly depending on version. Jon...

Your devices appear linked in some fashion.. I'd factory reset both, issue "restore device" on outletlinc and then attempt to re-link switchlinc. Jon..

Another thread with additional info specific to "Connect Exception." Jon...

Have a look at this thread... typically it seems the issue is related to failing PLM.. Edit: likely you'll need to contact support for help with this. Jon...

What exactly is the issue you're having? The lack of E2 record isn't necessarily an indication of missing PLM record or otherwise a problem. E2 is a link record for a controller whereas A2 is a link record for a responder. Jon...

I believe "restore device" will rebuild PLM link records. You might try and check... Jon...