arw01

Help about in the ISY admin console. When you are sending the commands out, do any of the led lights on the modules blink? Especially the plm.

Unless you add some tests for your motion sensor to time out, or go read about how to do up some timers, even if you have motion your lights will go out in 20 minutes period. And on the second question you can definitely have a program that looks at turning the lights off at 11:00 if the motion sensor is off. You will have to either close jumper 5 on the motion sensor and then make the changes in the ISY or by a bit of trial and error adjust the trim pot on the sensor to get about a 20 minute time out. Personally, I have not tackled the timer programming myself. I would love to see Universal-Devices give us a timer method in the programming.

Media_popcorn connected to the load it is controller of scene Media_popcorn_sc Media_popcorn_sl has no load it is controller of scene Media_popcorn_sc, Media_Popcorn Media_popcorn_sl is responder to the Media_popcorn_sc, and Media_Popcorn When I turn on Media_Popcorn_sl from the ISY the light does not come on When i turn on the media_popcorn_sl from the switch the light turns on Am I not understanding how this should work? Should I not expect to turn on a switch via isy NOT connected to the load and get it's linked one to respond to turn on the light

What does your error logs show around that time? Might want to run a level 3 log overnight too and export it to take a look at.

I have been thinking about this. I have a couple of the wireless modules that post the temperature to their servers and can be pulled down. Can the ISY be programmed to poll a website with some of the extension modules? Refresh this page to get the latest values for your TX-60 devices. Name Probe Device Hum Last Seen Batt Link Greenhouse 31.2 °F 30.2 °F 86% 12/18 10:19 PM OK 100 % Shop 64.5 °F 45.6 °F 64% 12/18 9:25 PM OK 100 %

For the wire, there are extremely flat wires about 2 sheets of paper thick that would be great for getting the sensor into the fridge. But as another member suggested, getting through the light wire might be an option if you can fish it properly.

My mix of devices are pretty varied by version, and I was concerned it would be a large burden to get all of the devices programmed if I did then in one scene only. To help with some strange communications issues, I have moved a couple access points around and ordered another one to fill in. I noticed some switches in the basement didn't tend to take their programming until I moved an access point while working on a RL2, and they magically stopped being so stubborn.

Thank you for the encouragement. Would you mind sharing your program so I can dissect it a bit?

Like a bed time button. Hit it twice fast so a fast off, I want to run a couple of scenes that turn off all the house lights. Wondering if I have the concept down here before I embark, or if there is a smart way to do it. since i cannot seem to have a scene be part of a scene I need two scenes: upstairs lights basement lights a program that looks for fast off on my kpl when it sees fast off it executes upstairs lights off it executes downstairs lights off Is that pretty much the gist of it?

I am in the same boat as you. However, I have a lot more programming experience in general. But still bending my head around some of the limitations I read here on the boards. I am surprised that Timers are not a native object to use on the ISY, seems like they would have been requested as a new feature a long time ago. Write it up, maybe some of your stuff will give me some ideas for my stuff.

Does WVS use modules or anything like that we can make up a little bit of code to use the rest commands and write that weather data into the ISY?

Would be interested in this as well. Been working for a few months to get a really great buy on a Davis system off of Ebay. I also have heard of the WVS linux program. It talks to a variety of weather stations at home and can upload the data into weatherbug's servers. It would be a work around for sure, we keep a number of computers up 24x7 around here, but native support would be my preference.

I happen to have both. The 2413SH is connected to the ISY. I think that the 2413SH is only needed when you first setup Houselinc, once it's up and running, it has never cared which of my two PLM's I use. I happen to have both PLM's connected, the 2413S to the HL, and 2413SH to the ISY when I was finally able to get the Remotelinc and the first motion sensor going. When I connected the second motion sensor, I had only the ISY plm connected. Yep, some strange stuff there, but it's up!

Got em just moments ago, both are added now.. Wierdness. I even unplugged the second PLM just in case that was the reason they linked up, and they are still received. I will unplug the 3rd access point and try them around the house again to make sure the other 2 access points and the ISY 2413SHplm pick them up. Then that third access point can go out to the shop or garage if it's in range, and I can use the remotelinc as the control of my dust collector as planned. Alan

No Venstar here. I have run houselinc with a second plm I have, just a plain 2413S and can confirm both the motion sensor links and the remote linc links up. I can see the traffic with the verbose logs by pressing a button on the remotelinc 2. Therefore I can accurately surmise there is at least SOME rf working around here. Took a walk around the house, see houselinc log below: 2012-12-16 08:50:59,546 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.02, Flag: CB (Hops: 2/3), C1: 13 (Light OFF), C2: 00 2012-12-16 08:50:59,765 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.02, Flag: CB (Hops: 2/3), C1: 13 (Light OFF), C2: 00 2012-12-16 08:52:48,859 [16] DEBUG - Rx: Std Msg, From: 14.1A.66, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 13 (Light OFF), C2: 01 2012-12-16 08:52:49,078 [16] DEBUG - Rx: Std Msg, From: 14.1A.66, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 13 (Light OFF), C2: 01 2012-12-16 08:52:54,812 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.01, Flag: C7 (Hops: 1/3), C1: 11 (Light ON), C2: 00 2012-12-16 08:52:54,968 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 11 (Light ON), C2: 00 2012-12-16 08:53:14,875 [16] DEBUG - Rx: Std Msg, From: 14.1A.66, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 11 (Light ON), C2: 01 2012-12-16 08:53:15,093 [16] DEBUG - Rx: Std Msg, From: 14.1A.66, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 11 (Light ON), C2: 01 2012-12-16 08:53:22,656 [11] DEBUG - Checking gateway communication... 2012-12-16 08:53:22,671 [11] DEBUG - Tx: Get PLM Config Flag 2012-12-16 08:53:22,671 [16] DEBUG - Rx: PLM Ack, 02 73 48 00 60 06 2012-12-16 08:54:04,796 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.02, Flag: C7 (Hops: 1/3), C1: 11 (Light ON), C2: 00 2012-12-16 08:54:05,015 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.02, Flag: C7 (Hops: 1/3), C1: 11 (Light ON), C2: 00 2012-12-16 08:54:16,375 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 13 (Light OFF), C2: 00 2012-12-16 08:54:16,593 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 13 (Light OFF), C2: 00 2012-12-16 08:54:25,312 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.04, Flag: C7 (Hops: 1/3), C1: 13 (Light OFF), C2: 00 2012-12-16 08:54:25,531 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.04, Flag: C7 (Hops: 1/3), C1: 13 (Light OFF), C2: 00 2012-12-16 08:54:33,515 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.03, Flag: C3 (Hops: 0/3), C1: 11 (Light ON), C2: 00 2012-12-16 08:54:33,640 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.03, Flag: C7 (Hops: 1/3), C1: 11 (Light ON), C2: 00 2012-12-16 08:54:41,265 [16] DEBUG - Rx: Std Msg, From: 14.1A.66, To: 00.00.01, Flag: C7 (Hops: 1/3), C1: 13 (Light OFF), C2: 01 2012-12-16 08:54:41,500 [16] DEBUG - Rx: Std Msg, From: 14.1A.66, To: 00.00.01, Flag: C7 (Hops: 1/3), C1: 13 (Light OFF), C2: 01 2012-12-16 08:54:53,656 [16] DEBUG - Rx: Std Msg, From: 14.1A.66, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 11 (Light ON), C2: 01 2012-12-16 08:54:53,937 [16] DEBUG - Rx: Std Msg, From: 14.1A.66, To: 00.00.01, Flag: C7 (Hops: 1/3), C1: 11 (Light ON), C2: 01 2012-12-16 08:55:09,750 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.05, Flag: C3 (Hops: 0/3), C1: 11 (Light ON), C2: 00 2012-12-16 08:55:09,890 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.05, Flag: C7 (Hops: 1/3), C1: 11 (Light ON), C2: 00

Three access points all in proper LED mode, and 2 dual band PLM's (one being used to test what's up with houselinc) Any other testing I can do there? I confirmed by watching each individual led, that when either the 2420M set button is pressed the access point(s) blink.

And a silly question. Does the remote linc 2 need to be linked to the access point first, or do they blindly relay every radio wave insteon command they get?

That is the part that is maddening. Been all over the house. Once when I had my tongue the correct way, the write failed after it got it going. The only other time it communicated was just as the rl2 timed out! Also having trouble with a motion sensor taking the write from the isy. I can watch the access point blink right when the RL2 goes into linking mode. Alan

I am having an issue with the Remotelinc-2 as well. Just won't pair. Got close a time or two AFTER it is basically timing out. I even put it ON the access point Sat 12/15/2012 08:35:29 PM : ---- Initializing the linked devices ---- Sat 12/15/2012 08:35:29 PM : ---- All Linked Devices are now initialized ---- Sat 12/15/2012 08:35:29 PM : ---- Add remaining devices ---- Sat 12/15/2012 08:35:29 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:35:29 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:35:38 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:35:38 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:35:48 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:35:48 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:35:52 PM : ---- All Remaining Device Added ---- Sat 12/15/2012 08:35:52 PM : [All ] Writing 0 bytes to devices Sat 12/15/2012 08:35:57 PM : ---- Initializing the linked devices ---- Sat 12/15/2012 08:35:57 PM : ---- All Linked Devices are now initialized ---- Sat 12/15/2012 08:35:57 PM : ---- Add remaining devices ---- Sat 12/15/2012 08:35:57 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:35:57 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:36:06 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:36:06 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:36:15 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:36:15 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:36:19 PM : ---- All Remaining Device Added ---- Sat 12/15/2012 08:36:19 PM : ---- Initializing the linked devices ---- Sat 12/15/2012 08:36:19 PM : ---- All Linked Devices are now initialized ---- Sat 12/15/2012 08:36:19 PM : ---- Add remaining devices ---- Sat 12/15/2012 08:36:19 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:36:19 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:36:19 PM : [All ] Writing 0 bytes to devices Sat 12/15/2012 08:36:28 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:36:28 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:36:37 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:36:37 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:36:41 PM : ---- All Remaining Device Added ---- Sat 12/15/2012 08:36:41 PM : [All ] Writing 0 bytes to devices Sat 12/15/2012 08:36:59 PM : ---- Initializing the linked devices ---- Sat 12/15/2012 08:36:59 PM : ---- All Linked Devices are now initialized ---- Sat 12/15/2012 08:36:59 PM : ---- Add remaining devices ---- Sat 12/15/2012 08:36:59 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:36:59 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:37:08 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:37:08 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:37:17 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:37:17 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:37:21 PM : ---- All Remaining Device Added ---- Sat 12/15/2012 08:37:21 PM : ---- Initializing the linked devices ---- Sat 12/15/2012 08:37:21 PM : ---- All Linked Devices are now initialized ---- Sat 12/15/2012 08:37:21 PM : ---- Add remaining devices ---- Sat 12/15/2012 08:37:21 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:37:21 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:37:21 PM : [All ] Writing 0 bytes to devices Sat 12/15/2012 08:37:30 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:37:30 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:37:39 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:37:39 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:37:43 PM : ---- All Remaining Device Added ---- Sat 12/15/2012 08:37:43 PM : ---- Initializing the linked devices ---- Sat 12/15/2012 08:37:43 PM : ---- All Linked Devices are now initialized ---- Sat 12/15/2012 08:37:43 PM : ---- Add remaining devices ---- Sat 12/15/2012 08:37:43 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:37:43 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:37:43 PM : [All ] Writing 0 bytes to devices Sat 12/15/2012 08:37:52 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:37:52 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:38:01 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:38:01 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:38:05 PM : ---- All Remaining Device Added ---- Sat 12/15/2012 08:38:05 PM : ---- Initializing the linked devices ---- Sat 12/15/2012 08:38:05 PM : ---- All Linked Devices are now initialized ---- Sat 12/15/2012 08:38:05 PM : ---- Add remaining devices ---- Sat 12/15/2012 08:38:05 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:38:05 PM : [All ] Writing 0 bytes to devices Sat 12/15/2012 08:38:05 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:38:14 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:38:14 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:38:23 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:38:23 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:38:27 PM : ---- All Remaining Device Added ---- Sat 12/15/2012 08:38:27 PM : [All ] Writing 0 bytes to devices Sat 12/15/2012 08:38:47 PM : ---- Initializing the linked devices ---- Sat 12/15/2012 08:38:47 PM : ---- All Linked Devices are now initialized ---- Sat 12/15/2012 08:38:47 PM : ---- Add remaining devices ---- Sat 12/15/2012 08:38:47 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:38:47 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:38:56 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:38:56 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:39:05 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:39:05 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:39:09 PM : ---- All Remaining Device Added ---- Sat 12/15/2012 08:39:09 PM : ---- Initializing the linked devices ---- Sat 12/15/2012 08:39:09 PM : ---- All Linked Devices are now initialized ---- Sat 12/15/2012 08:39:09 PM : ---- Add remaining devices ---- Sat 12/15/2012 08:39:09 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:39:09 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:39:09 PM : [All ] Writing 0 bytes to devices Sat 12/15/2012 08:39:18 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:39:18 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00)

Ever since seeing a high end system that pulled the drapes and dimmed the lights at a local stereo shop when you sat BACK on the couch, I have been thinking about this sofa sensor as well. However, i was thinking a triggerlinc would be a "unplugged" option to use for that.