Xathros

Hi, I have found the low batt notifications to be quite unreliable on these motion sensors. The major issue with these is that they will only turn on the low batt node once and if that event is missed, there won't be another sent. That said, there a a few approaches to this. First you will need to configure one or more custom notifications that can ben sent when a low batt condition is detected. Then a program like the following is the simplest: If Control 'Basement / Shop / Shop Motion / Shop Motion-Low Bat' is switched On Then Repeat Every 12 hours Resource 'NOTIFY - UTLITY - Basement Motion - Low Battery' Else - No Actions - (To add one, press 'Action') In that example, I am using network resources to send a prowl notification to my iPhone. You could just as easily sent a text or email message instead (and not need the network module to do that). This will notify every 12 hrs once a low batt event has been detected but as I said above, if that event is missed, this won't be of any value. Another approach would be to set countdown timers that reset each time there is motion detected and send a notification whenever a counter reaches zero. Start the counters with a high enough value that under normal conditions they will not reach zero unless the battery quits and they stop sending motion events. This works fairly well in higher traffic areas, will be rock solid reliable but does delay the notification until the counter expires. Hope this helps. -Xathros

If you are on Lion or Mtn Lion, you should install Java 1.7.25 from Oracle. UDI has been recommending that users uninstall the 1.6 branch of Java on the MAC but software update keeps putting it back and it hasn't caused me any grief so I just left well enough alone with that. -Xathros

Another remote possibility is that NTP is updating the ISY's clock and skipping the trigger time. This would assume that the ISY clockis drifting enough in a 24hr period and that NTP is updating around the same time that your program should trigger. You could disable NTP for a day or two and see how much clock drift you see. Then maybe change the frequency of updates in an attempt to avoid the mindnigt-ish update. -Xathros

The downgrade recommendation was one I had made a month or two ago to another user that was swapping a 99i for a 994. I remember Michel saying that there had been some database changes and that if you wanted to go back to the 3.3.10 FW from the 4.x betas, you should restore a 3.3.10 backup after the downgrade. This lead me to believe that the safest upgrade path on a new 994 from a 3.3.10 99i would be to start with the 994 at 3.3.10, restore the 99i backup then upgrade the 994 to 4.x from there. This may have been unnecessary. Michel- could you comment on this? -Xathros

Could you test one of the four that didn't work in a location where one of the others worked and see if you get different results? It could just be marginal communications to the locations where the four failed. -Xathros

The From ... To is also a trigger and triggers twice - Once at the From time and again at the To time. If the only condition was the From...To, then the program would trigger and run true at the From time and trigger and run false at the To time. As LeeG posted the program, the program will always run false at sunrise time regardless of the nightlight status. And besides, the very first program the OP posted would still turn the light off at Sunrise based on it's else clause. -Xathros

I don't think that would be a problem here. The if will reevaluate false at sunrise during the 10 minute wait and the light will not be turned back on. Looks fine to me as LeeG has it. -Xathros

Perfect. The filterlinc should be helping in this case. -Xathros

dstanley- Normally, the filterlinc is used to prevent noise or attenuation caused by a device like a UPS from reaching the powerline. Filtering the PLM eliminates the PLM's ability to communicate on the powerline. If the UPS is used for the ISY and other network gear, plug the UPS into the filtered outlet on the filterlinc and the PLM into the Passthru outlet on the filterlinc. This will isolate the USP from the line and allow the PLM direct access to the line. A few users here have purposely filtered the PLM to force it to communicate over RF instead of the powerline. While this may help in some situations, I believe that this will make things worse on many older Insteon networks where there are few if any dual band devices. This would also require a 2413S dual band PLM to work in this configuration. -Xathros

derw- Correct depends on a clearer definition of exactly what you want to accomplish. That will do what you stated but if at 8:31 you were to turn on button B, only the button would light because it is no longer 8:30. The only time this will work is when the B button is already on when the time becomes 8:30. A more common scenario might be: If Time is from 8:30pm to 10:30pm same day and Status KPL-B is on Then Set backroom light On Set dining room ceiling light on This way you can turn on those lights during the time window if needed rather than just at 8:30 if the button is already on. Again, it really depends on what you want to accomplish. oberkc- I believe that only the primary node on a KPL dimmer can have a status of >0% & <100% while the secondary nodes are all either On or Off. -Xathros

Try setting a static IP address for your ISY and use 8.8.8.8 for the DNS server address. Check Tools / Error Log and see if there is anything there to indicate what the failure is. -Xathros

That was why I suggested a proximity sensor mounted above the bay. I was just looking at a few at Mouser Electronics. For around $110 you can get an ultrasonic proximity sensor with a 20-150cm range and a NC or NO Transistor output that could be used to trigger an IOLinc or any other TTL input. I figure it could be mounted in/on the ceiling in the center of the bay and adjusted to watch for the vehicle roof. Optical Proximity sensors are cheaper but would likely be affected by the condition of the vehicle's roof (clean, dirty, wet, snow etc). Another option though somewhat expensive is medium range RFID. This would require an RFID antenna/reader in the garage and an active RFID tag on each vehicle. Might be able to use existing EZPass/FastPay Toll tags as in place of additional tags but for a multi car garage, this would require multiple expensive directional readers. There has to be a cheap way to detect a car sitting in the bay magnetically using the same technology used to detect cars waiting at a stop light but I haven't figured out the right search phrase for that yet... -Xathros

How about a Dakota Alert driveway sensor hung from above the car to detect when it is in the garage? Do these only detect a car moving past their fixed location or will they also detect a car parked over, or in this case, under the sensor? Otherwise, there are plenty of optical proximity sensors that could be mounted above the car and adjusted to detect the roof of the car. -Xathros

I assume you meant a "UPS with the PLM". In some cases you can. Several users here have placed their PLM's behind UPS/Filter combos effectivly isolating them from the powerline network. Then add Access points near by - one on each phase. This forces the PLM to use RF only. (requires 2413S PLM) As a result, for any non dual band powerline devices, you lose one hop out of the 3 to the PLM -> access point jump. If you have a solid network that may be OK but if things are marginal, losing a hop may worsen your reliability. This is certainly not the recommended setup but if you are prone to power problems, this might help. -Xathros

Hi propman07- Unfortunately, those type of fan controls do not work well with Insteon. The way we do this is to use a fan without the remote control and instead wire in a Fanlinc to manage the fan speed and light. This will give you the ability to operate the fan (Hi/Med/Lo/Off) as well as the Light (On/Off/Brighten/Dim) via Insteon commands from programs or linked controllers. The fanlinc DOES NOT manage fan direction. Direction is usually controlled by a switch on the fan itself. Some of the fans with integrated remotes can have the remote removed and replaced by the Fanlinc but you will lose control of the fan direction. -Xathros

I am afraid not. The ISY knows nothing about video at all. You might be able to do some control of the device from the ISY network module if the device has some kind of network accessible user interface but that would be about it. -Xathros

Hi pauliep- I'd be happy to. What kind of cams do you have and do you have the ISY network module installed? Here is the overview: In my Foscam PTZ cams, I have created between 3 and 6 saved positions per cam. Then in the ISY network modue, I have created a resource for each of those saved positions and named then appropriately (Garage cam to Dad's Door, Garage Cam to Mom's door etc.) Then with some simple programs, I can point the cams based on other events: Program: If Control 'Garage / Garage Door IOLinks / GD- Dad Garage Door Sensor' is Switched On Then Resource 'Syslog-SECRTY - Dad Garage Door Opened' Resource 'CAM-CRTL: GarageCam-Dads Door' Wait 1 minute Resource 'CAM-CRTL: GarageCam-Inside Door' Else I also have a few programs set up for my utility room cam to cycle through 6 positions. I have made one of these programs a favorite and associated it with my Utility Cam. This makes it easy to loop through the 6 positions by tapping the program favorite while watching the cam. These could be implemented for each cam but I haven't bothered to do this for my other cams yet. Program: Utility Cam Cycle (This is the Mobilinc fav) If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then $s.UtilityCamPosition += 1 $s.UtilityCamPosition Init To $s.UtilityCamPosition Else - No Actions - (To add one, press 'Action') Program: UtilityCamPos1 If $s.UtilityCamPosition is 1 Then Resource 'CAM-CRTL: BasementCamPosition1 - Stairs' Else - No Actions - (To add one, press 'Action') . . . Program UtilityCamPos5 If $s.UtilityCamPosition is 5 Then Resource 'CAM-CRTL: BasementCamPosition5 - Network Shelf' Else - No Actions - (To add one, press 'Action') Program UtilityCamReset If $s.UtilityCamPosition is 6 Then $s.UtilityCamPosition = 1 $s.UtilityCamPosition Init To $s.UtilityCamPosition Else - No Actions - (To add one, press 'Action') The $s.UtilityCamPosition mvar is a state variable. -Xathros

I think it would be easier to use the network module in the ISY to tell the PC to play a sound. I think there are a few threads on here where something very similar has been done. -Xathros

Or Mobilinc Connect. -Xathros

Like oberkc, I skipped answering this one as I am not familiar with the whole scope of the question. I do use a Harmony One so here is what I can offer: While the Harmony remotes *can* learn from other remotes, I don't think the ISY comes with a remote that you can train the harmony with. I could be wrong, I don't have the IR version of the ISY. I do remember a thread a while back where someone mentioned that the Harmony Programming Web Interface had a more functional profile for an ISY99i rather than the ISY994I (going from an aging memory here so It might be the other way around). You might try adding a ISY-99i instead and see if that populates with IR commands. I believe the IR section is identical in the 99 series and the 994 series ISYs. Another somewhat vague memory is that the ISY IR responds to Phillips Pronto codes. -Xathros

If the problem was the ISY, then it would affect all of the system that you use to access it. This is something local to that system/XP install. Besides, all of the UI is in code that lives external to the ISY so reinstalling the ISY would not change anything there. Not sure where to go from here. Are your video card drivers up to date? Maybe start the XP machine in "Safe Mode with Networking" and test. See if the problem goes away. If so, there is likely a driver or software conflict. -Xathros

Yes. I would think so. I have not played with subscriptions yet. Time for someone else to step in and pick this up from here. -Xathros

If the admin console is the only place you see this happen, then I suspect a broken Java install. Completely remove Java, restart the machine and reinstall Java from a fresh download of the current version. -Xathros

There is no "Scene Status" in the Insteon world so for status checking, you need to look directly to the devices. -Xathros

In both cases you are issuing direct commands to the microlinc. You need to address the scene that contains both the microlinc and KPL button via /Rest and the Console to get the results you desire. Use /rest/nodes/scenes to retrieve a scene list. Use the scene id in /rest/nodes//cmd/ -Xathros