Xathros

Yes. It has a very clean and simple Web UI for control and configuration that is easily driven via the ISY's network module. I have uploaded my set of DIN Relay resource rules for the new database already. In addition, they have an iOS app for the DIN Relay and their web power strip (same device built into a power strip). Not a very pretty app but it does work. Both of these devices can be configured to ping other devices and cycle a relay/outlet upon ping response failure. Handy for network devices that can hang on occasion. -Xathros

As oberkc pointed out above, Mobilinc reads the device/scene/program and variable configurations from the ISY and presents a mobile UI to access those. There is some Mobilinc specific configuration (at least on the iPhone/iPad) that can be done beyond what is configured in the ISY. For instance, you can set custom Icons, status and control names to thake the place of things like True/False,On/Off etc. In addition there is a Resource Manager in Mobilinc that allows some timer type automation managed by Mobilinc rather than ISY programs. I don't use this feature so can't tell you much more about it. There are other apps like iRule and Demopad that allow for much greater customization but these require you to build the interface from the UI elements to devices/scenes/programs on the ISY using the ISY's /REST interface via http network calls. These apps generally offer the ability to interface with things beyond the ISY such as cameras, AV equipment, and much more all at the expence of being much more difficult to deploy. Hope this helps. -Xathros

The DIN Relay is an ethernet controled "Web Switch". You use Network Resource rules to turn on/off/cycle the relays. -Xathros

Im still using the IOLinc sensors on the doors. I simply took control of the doors off the IOLinc relays. -Xathros Sent from my iPhone using Tapatalk

I too monitor motion sensors and other control events in the house to control occupied/vacant status and like Andy, take into consideration the visibility of our phones to prevent the house from sleeping if somebody is home. I had to build in an override that I can set from Mobilinc for those times when someone forgot their phone at home... -Xathros

dstanley- Is it the sensor or the relay that is showing out of sync? If the relay, this is normal as the relay is not a controller and does not sent status changes to the ISY. The ISY simply remembers the last thing it told the relay to do. If the relay is in a momentary mode, th ISY tells the relay to turn on to move the door. a short period later the relay turns itself off and there is no feedback to the ISY an the status remains on until the relay is either queried or commanded off by the ISY. If it's the sensor input that is not updating, that is a problem. I would do some testing by disconnecting the reed switch and opening/shorting the wires while running a level 3 event log on the ISY to see what traffic is captured. Has this been an issue since the PLM replacement? If so, maybe a restore device to rebuild the link table in the IOLinc is in order. -Xathros

Hi jspoon- I use both Mobilinc geofencing and the presence of our phones on the house wifi network. I have found that using only one of these can result in false arrivals or departures. The ISY itself is not capable of monitoring the WiFi for connected devices. For that, you will need something like a router running DD-WRT or Tomato firmware and a script to watch for connected devices and update state variables in the ISY via the /REST interface. There are some good threads on this forum about how to accomplish that part. To add to that, I have found that I need to time buffer disconnects as our phones often drop off the network then reattach a couple of minutes later. I logged these connects and disconnects for a while to build a profile by device type to determine the best wait time before I consider a device "gone" on average that worked out to 4 minutes. I do still get a false disconnect on occasion but maybe only once a week now. I have also found it valuable to have an extra variable for each device that gets set to 1 when both the WiFi and Geofence say the device is home and 0 when both say gone. This way I can act on the first indication that a device has arrived home and not on a reconnect after I'm already home. I hope this helps. I'm happy to provide additional details if needed. -Xathros

@johnnyt I'm glad I was able to point you at the DIN Relay. It is an excellent little device and I've been very happy with mine too. I recently moved control of my garage doors over to the DIN relay to avoid the possibility of an Insteon All-On event opening my doors when I'm away. -Xathros

In addition, I believe you need to query the Low Batt node of the motion sensor to clear the low batt status. -Xathros

Luke- It sounds to me like tyou have things configured correctly in terms of the scene setups. Instead of controling the fanlinc device directly with Mobilinc, control the scenes instead. This will keep the fan and KPL led's in sync. Since the Fanlinc is not a controller, there is no way for it to tell the KPL what to do when you control the fanlinc directly. The scene will do what you need. No programs necessary. Hope this helps. -Xathros

This is true. In such a case, the OP would need to consider that and reset the vars in the all off program if so desired. -Xathros

I see lots of Hops=3, Left=0 and Left=1. This indicates marginal comms from top to bottom of this trace. Lets do the extension cord test next. -Xathros

Nice catch! Yes - both the Open and Close should have read 0 instead of 1. Thanks. -Xathros

The noise referred to here is on the powerline not RF so physical distance is not necessarily going to help. Moving the PLM to a different circuit may help. This is what you need to test with an extension cord. Additionally, noise isn't the only possible problem. Signal attenuation is another major player with comm issues. Some devices have noise filtering capacitors across the line input that simply absorb Insteon and X10 signals. Such devices also should be isolated from the line with a filter. I do not know if the XPNR is suitable for this or not. -Xathros

Most Insteon devices have a PLM built in. The EZIO8SA does not and as a result require an external PLM connected. This is acceptable as this is a device and not a system controller like the ISY. -Xathros

JayM- Is the china cabinet lighting plugged into a power strip? If so, try going direct to the outlet. Many power strips have noise filters that kill insteon signals. -Xathros

Z-Wave has proven to be quite stable and reliable for me since the GenII board was installed. I'm very happy with the performance of the ISY with my Schlage ZWave locks. -Xathros

I think this can be accomplished but it will take a series of 9 programs and 3 variables to make it happen. Something like this: Define 3 integer variables: i.Light1.Status i.Light2.Status i.Light3.Status Create 3 programs to monitor the controls for the 3 lights: Program: Light1Monitor If Control 'Light1' is Switched On and Control 'Light1' is not switched Off Then i.Light1.Status = 1 Else i.Light1.Status = 0 Duplicate the above and edit for Lights 2 and 3. Now, we need 3 more programs that monitor the sensor and turn on the lights when the door opens: If Control 'Door Sensor' is switched On and i.Light1.Status = 0 Then Set scene 'Light1' On Duplicate and edit for Lights 2 & 3 and Lastly, three more for turning off the lights when the door closes: If Control 'Door Sensor' is switched Off and i.Light1.Status = 0 Then Set scene 'Light1' Off Duplicate and edit for lights 2 & 3 Place all of these programs in one folder. That way if you want to disable the automatic lights, you can simply disable the folder with a false condition. Hope this helps. -Xathros EDITED: to correct variable values (Thanks oberkc!)

The 2413S PLM can be put behind a UPS as long as you provide an RF bridge over the UPS back to the powerline. This will cost you one hop on the insteon network but it does solve the problem of keeping the ISY operational during a power failure. That said, you may still have problems during an outage as the PLM will be unable to communicate with the rest of the insteon network that is without power and that can back things up with queued events. As for networked IO devices, I really like the RaspberryPi. Lots of capability and possibilities there. Many of the Pi packages come with descent enclosures. You may need to build your IO interface into a separate project box however. -Xathros

Anytime. Happy to help. -Xathros

Mike- Does the Low Battery node not clear with the first open/close or heartbeat after battery replacement? -Xathros

Both the KPL in the wall and the fanlinc should have uninterrupted power. Just cap the red wire from the KPL and power the fanlinc from the line in the KPL's box. You create a logical link between the KPL's and the fan/light nodes in the fanlinc to control both the light and the fan. Both KPL's can be scene controllers for the fan and light. -Xathros

How about this one program: If Status 'Basement Door.3 - Low Battery' is On And ( Time is 08:30:05AM Or Time is 10:30:10PM ) Then Send Notification to 'Eric text' content 'Basement Door Low Battery' Else This will alert you at 8:30 and 10:30 each day while the low battery node is on until you replace the battery. -Xathros

Run the event viewer at level 3 then select write updates to device on one of the problem devices. Post the event trace. -Xathros

Hi Peter- It depends what portion of my logging you are referring to. I run a syslog server on my Pi. I have the syslog from my DD-WRT router directed there, the Pi's own logs are there and I write to an ISY log on the Pi using network resources called by programs. Here is an excerpt from todays ISY log: ISY994i - SECRTY - Breezeway Entry Door Closed. ISY994i - MOTION - Living Room ISY994i - OCPNCY - Matt iPhone Online. ISY994i - OCPNCY - Jess iPhone Online. ISY994i - MOTION - Living Room ISY994i - MOTION - Living Room ISY994i - MOTION - Living Room ISY994i - MOTION - Living Room ISY994i - SECRTY - Breezeway Entry Door Opened. ISY994i - OCPNCY - Control Event Detected. ISY994i - SECRTY - Breezeway Entry Door Opened. ISY994i - OCPNCY - Control Event Detected. ISY994i - SECRTY - Breezeway Entry Door Closed. ISY994i - LIGTNG - Utility Room AutoOff. ISY994i - MOTION - Living Room ISY994i - MOTION - Living Room ISY994i - MOTION - Living Room ISY994i - MOTION - Living Room ISY994i - MOTION - Master Bed ISY994i - MOTION - Master Bed ISY994i - OCPNCY - Matt iPhone Online. ISY994i - OCPNCY - Jess iPhone Online. ISY994i - LIGTNG - Main Bath Off. ISY994i - OCPNCY - Matt iPhone Online. ISY994i - OCPNCY - Jess iPhone Online. ISY994i - PRXMTY - Jess' iPhone Disconnected. ISY994i - OCPNCY - Matt iPhone Online. ISY994i - PRXMTY - Matt's iPhone Disconnected. ISY994i - NETWRK - Internet Access Test Started. ISY994i - NETWRK - Internet Access Test Passed. ISY994i - PRXMTY - Matt's iPhone Connected. ISY994i - OCPNCY - Matt iPhone Online. ISY994i - PRXMTY - Lora's iPhone Connected. ISY994i - PRXMTY - Livvy's iPhone Connected. ISY994i - SECRTY - Breezeway Entry Access Code 3 - Livvy ISY994i - OCPNCY - Control Event Detected. ISY994i - SECRTY - Breezeway Entry Door Opened. ISY994i - OCPNCY - Control Event Detected. ISY994i - SECRTY - Breezeway Entry Door Closed. ISY994i - MOTION - Living Room The network resource for these is fairly simple: I had to create a Source, Filter and Destination in my syslog-ng config on the Pi to look for the ISY entries coming in via UDP from the ISY's IP address and to point them to an appropriately named log file. I also set up a cron job to rename and move the log files into the webserver's directory daily to make them available via the link at the bottom of my report.. The logging of control data as shown in the daily report is described in my first post. I'm simply incrementing integer variables as control events happen then dump those values into the report at the end of the day. Hope that answers the question. -Xathros EDIT: The log above normally contains a date/time stamp as well as the IP address of my ISY, I removed those before posting. Should have left the time stamp...