elvisimprsntr

Just curious why the brultech support had to be removed.

in my case i work in my garage for long periods of time with the door open, so i have a program that only sends me a text message when motion is detect with the door open and alarm armed (arms automatically at night)

ML Connect uses the installed ISY module to create a continuous connection to ML servers. When you configure ML(HD,Pro,etc.) to access your ISY through ML servers it is not making a connect directly to your ISY. Since the ISY has no knowledge of your IP cameras ML Connect cannot connect to them thru their servers. That being said, there are ways to remotely access your IP cameras from an external network. 1. You can configure your router to forward various external ports to each of your internal network IP cameras. Make sure you enable password access to your cameras to prevent unauthorized access. Most IP cameras do not support encryption, thus authentication will be plain text over the internet which makes your system vulnerable. If your cameras do support encryption obviously use it. This should be possible with any consumer router. (Medium) 2. If you have a router the open source firmware at http://www.dd-wrt.com supports, you can flash your router with a version of their firmware that support VPN server. Then you can set up an encrypted VPN connection to your home network and access ANY IP based device on your network, not just the ISY and IP cameras, without setting port forwarding. (Advanced) In both examples, you will probably want either a static IP address from your ISP ($$$) or you can configure DDNS in your router and use for a free DDNS service from http://www.no-ip.com. This will provide a hostname that will resolve to your routers external IP address and will automatically get updated when your ISP changes your assigned IP address. If you happen to have your own registered domain name you can use your domain name for the DDNS service for a minimal change thru no-ip.com (Medium) PM me if you want how to's for either.

The Elk is a high end commercial quality security system which you can install and program yourself. If you add the Ethernet interface and you can remotely access the security system via a web interface or using iOS handheld devices using third party apps. If you add the ISY the two can communication between one another so you can controls lights based on security system events (e.g. garage door opens, turn on exterior lights at night). You can also control the security system from the ISY with the addition of an add on plugin for the ISY. See this post for links to the third party apps. viewtopic.php?f=42&t=6983 I have the Elk programmed to send me text messages if security system goes off which avoids having to pay a monthly fee, but I have read that you can have a professional monitoring service hooked up to the Elk. The ISY also allow you to create time and events based lighting changes without having a separate computer running 24/7. How you split the security/lighting programs between the two is up to you. In my case all security event driven (e.g. turn on exterior lights when garage door is opened when its dark outside) programs I have programmed in my Elk since those I am less likely to tweak. Time driven events (e.g turn on kitchen light at dawn). The ISY also has the ability to interface with energy monitors, thermostats, drape controllers, etc. I started with the Elk and ISY and slowly added lighting modules over time as I carefully thought about what lights i wanted to control. I can control my security and lighting from anywhere in the world and even at 35000 ft and don’t have to pay a monthly fee or go through some third party server to do so. The only word of caution is you have to have some patience with the Insteon lighting modules. It takes a little common sense and and tweaking to get it working perfectly. Most of the problems come from electrical interference from wall transformers which tend to operate at similar frequencies the wired Insteon communication operates at.

My AP is on the same circuit breaker as my PLM, I have a v2.2 stat adapter, and the device and AP are in the same room when I am trying to program it. For lack of anything else to do, I plugged the battery in while holding down the set button on the motion sensor to see if I could reset the MS. I then tried to write updates to the MS and the ISY "believed" its had successfully completed the writes and changed the icons from the pending write icons. I did a compare of the ISY vs. the device links and noticed the links did not write to the motion sensor. I performed the same comparison on a different motion sensor (newer revision) and it looks like the writes were successful in that device. The older module MS is v1.1. Even with the link comparison failure, the device works otherwise. it detects motion, turns on the scene, etc. Looks like I will be returning a motion sensor and suspect AP (different problem) back to SH for exchange. Thanks, Elvis

BACKGROUND I am having problems linking new motion sensors and triggerlincs in 3.1.17. if my memory serves me correctly these devices are not writable. unfortunately when removing and re-adding and existing device the ISY tries to write to the device until it claims it failed to write to the device and yes the devices were in linking mode. When i try to select the dvice in the menu and try writing updates to the device, the ISY appears to go through the process of writing to the device and does not display an error dialog box although the exclamation point is still on the device. this is odd as i also recently added a new motion sensor for the first time which seems to have been added successfully. when I reboot the ISY the icons in the device list change from the exclamation point to the symbol for pending writes. I can add the device to control a scene and have verified that it actually works. Unfortunately, the pending writes symbol is still persistent and when I try to change ANY links and scenes for ANY device, even scenes that do not contain the troublesome devices, the ISY tries to write to those devices again and prompts me with an error message. Any thoughts?

BACKGROUND I have a number of programs that trigger on various zones and combinations of other zones. Unfortunately there seems to be a significant difference between how programs trigger between the Elk and ISY. For example: I have an Elk program that monitors garage motion, door position and alarm status. WHEN ZONE GARAGE MOTION BECOMES NOT SECURE AND GARAGE DOOR IS NOT SECURE AND GARAGE (AREA 4) ARMED STATE = ARMED THEN SEND EMAIL MESSAGE THEN TURN GARAGE RECORD ON FOR 2 SECONDS There is a subtile timing delay that I am taking advantage of in this case to avoid sending me message and recording video every time I come home from work and open my garage door. Because the light built in to the garage door opener turns on when immediately when the motor starts, this triggers the IP camera motion detection. at this moment in time the garage door has not physically moved and the garage door is still secured, thus will not send me a message or record video. This also eliminates sending me a message if something falls in the garage or the camera pans the garage while the garage door is closed. The program in the elk is primarily used for when I forget to close the garage door at night (a frequent occurrence when I drive home from the pub) after the Elk automatically arms itself every night after a certain time. The big difference here is in the Elk WHEN... BECOMES is a state change (edge) trigger. the other conditions are current state (level) checks. In the Elk the first conditional check is ALWAYS an edge trigger and all subsequent conditionals ate level checks. There is no other way to program the Elk. Here is the problem with implementing the same program in the ISY. Here is what I created. If ( Elk Zone 'Garage Motion' is Violated And Elk Zone 'Garage Door' is Violated ) And ( Elk Area 'Garage' 'Armed State' is Armed Away Or Elk Area 'Garage' 'Armed State' is Armed Stay ) Then Set Elk Output 'Garage Record' On for 2 Seconds Else - No Actions - (To add one, press 'Action') This similar program implemented in the ISY will trigger every time I open my garage door when the house is armed. This is because I believe the ISY IF conditional checks are LEVEL and not EDGE triggered. QUESTION Are ALL the ISY conditionals LEVEL triggered? Is there a different way for me to accomplish the same outcome? Or is there a possibility for a future enhancement to the ISY conditionals checks? Thanks in advance.

Michel, I don't have any baby monitors, but I share common walls (Townhouse) with new neighbors that might. I'll have to ask. TStat adapter is v2.2. PLM is v85. RF APs are 1.0

BACKGROUND I've been experiencing problems with stale values for my TStat (v2.2 adapter). I had moved my RF APs to address problems with a TriggerLinc. Then I starting noticing the TStat was not reporting changes and longer query times. I eventually had move my APs back to their original locations, deleted and re-added my TStat to get it working as expected again. I had already deleted and re-added my TStat under a prior release per release notice instructions. During this time my RF motion sensors continued to work normally. Not exactly sure what to make of it.

Michel, I have been unable to reproduce the problem, but I had been doing electrical work turing off various circuits while re-wiring some electrical boxes. All circuits were on during the time the ISY locked up and the times are correct.

BACKGROUND I have a few programs that use network resources to sent http get commands to an IR blaster to change the channel on my whole house video distribution set up. Unfortunately the ISY locked up trying to send those commands. The ISY would not respond to ping requests and the admin console would not come up. I have to power cycle the ISY. ERROR LOG Tue 2011/12/27 18:00:01 System -140005 Net Module Rule: 23 Tue 2011/12/27 18:00:01 System -140005 Net Module Rule: 23 Tue 2011/12/27 18:00:02 System -140005 Net Module Rule: 30 Wed 2011/12/28 00:00:00 System -140005 Net Module Rule: 25 Should have been followed with Rule: 28 Should have been followed with Rule: 30 Wed 2011/12/28 03:16:59 System -170001 UDQ:Queue Full: ELK Wed 2011/12/28 03:16:59 System -170001 UDQ: Queue(s) Full, message ignored Wed 2011/12/28 03:16:51 System -5 Start Wed 2011/12/28 03:16:53 System -170001 [Network] Established Wed 2011/12/28 03:19:10 System -170001 [uDSockets] RSub:31 error:6

I keep getting errors that the ELK WSDK PDF is currupted. http://www.universal-devices.com/develo ... DK-ELK.pdf

Attached are some shell scripts, resulting XML responses, and logs of the wget communication. I added comments in the elk/isy_interrogate.log files where I noted discrepancies. UPDATE I fixed a bash script bug for the elk rest command to disarm the system. the resulting output indicated the command was successful, but the ISY did not disarm the Elk. I also changed the bash scripts to prompt the user for unique settings so you can run them at your facility. I also have a question what "ae type" is in the area status output. <?xml version="1.0" encoding="UTF-8"?> And where do I find the elkArmType definition or enumeration? rest.zip Archive.zip

If the rest/security interface as been depreciated, should it still be in the WSDK document? My ID and PW are correct and the syntax for the wget command I pulled off a forum and confirmed with the wget --help option. Here is the output for a successful command: root@Siri:~/SiriProxy# sh isy_living_off.sh --2011-12-01 07:32:54-- http://192.168.69.90/rest/nodes/19496/cmd/DOF Connecting to 192.168.69.90:80... connected. HTTP request sent, awaiting response... 401 OK Reusing existing connection to 192.168.69.90:80. HTTP request sent, awaiting response... 200 OK Length: 104 [text/xml] Saving to: `cmdresp.log' 100%[================================================================>] 104 --.-K/s in 0s 2011-12-01 07:32:54 (2.34 MB/s) - `cmdresp.log' saved [104/104] UPDATE I have tried a number of the Elk REST commands defined in the Elk WSDK document an I get mixed results on the responses. Some result in 404 errors, other result in 200 status with empty contents, a few result in 200 status will what appears to be appropriate contents. All REST commands I get the initial 401 message when I have confirmed I am using the correct ID/PW. Some of the Elk REST 404 errors appear to be documentation errors. I have also seen random slow response as another forum member has reported.

Not sure if I am doing something wrong, but the security REST interface seem to be returning 404 errors. Excerpt from my bash script. Same syntax works for other REST commands. wget -O security.log --user $USER --password $PASS ${ISYRESTURL}${ISYCMD} Output from command. --2011-11-30 07:15:45-- http://192.168.69.90/rest/security Connecting to 192.168.69.90:80... connected. HTTP request sent, awaiting response... 401 OK Reusing existing connection to 192.168.69.90:80. HTTP request sent, awaiting response... 404 OK 2011-11-30 07:15:45 ERROR 404: OK. The above command is listed in the WSDK http://www.universal-devices.com/develo ... Manual.pdf

only problem i have observed so far is upon first login after upgrading and clearing cache, the Insteon devices statuses are blank. I had to close my browser and log back in without clearing cache. UPDATE I have several program that use network resources that run at different times of the day. I do not have run at startup enabled for these programs. My network resource programs change the channel on my whole house video distribution system at various time of the day. In .12 only the program that should have run last based on the time of day would run. Now all of them run at start up in .13 Time User Code Message Fri 2011/11/25 20:18:34 System -5012 28 Fri 2011/11/25 20:19:51 System -5012 29 Fri 2011/11/25 20:22:51 System -170001 UDQ:Queue Full: ELK Fri 2011/11/25 20:22:51 System -170001 UDQ: Queue(s) Full, message ignored Fri 2011/11/25 20:22:41 System -5 Start Fri 2011/11/25 20:22:43 System -170001 [Network] Established Fri 2011/11/25 20:23:02 System -140005 Net Module Rule: 25 (CH 5) Fri 2011/11/25 20:23:03 System -140005 Net Module Rule: 28 (CH 8 ) Fri 2011/11/25 20:23:03 System -140005 Net Module Rule: 30 (Enter) Fri 2011/11/25 20:23:04 System -140005 Net Module Rule: 23 (CH 3) Fri 2011/11/25 20:23:04 System -140005 Net Module Rule: 23 (CH 3) Fri 2011/11/25 20:23:05 System -140005 Net Module Rule: 30 (Enter) Fri 2011/11/25 20:23:05 System -140005 Net Module Rule: 24 (CH 4) Fri 2011/11/25 20:23:06 System -140005 Net Module Rule: 23 (CH 3) Fri 2011/11/25 20:23:06 System -140005 Net Module Rule: 30 (Enter)

BACKGROUND My error log seems fairly clean, but do notice a few errors. I also observe the error log does not save the last entry. For example there should be a "System -140005 Net Module Rule: 30 " entry at 6::00:01 AM at the very end. Also noticed the first few events are out of order. Time User Code Message Tue 2011/11/22 05:27:55 System -170001 [uDSockets] RSub:32 error:6 Tue 2011/11/22 05:28:14 System -170001 UDQ:Queue Full: ELK Tue 2011/11/22 05:28:14 System -170001 UDQ: Queue(s) Full, message ignored Tue 2011/11/22 05:28:05 System -5 Start Tue 2011/11/22 05:28:07 System -170001 [Network] Established Tue 2011/11/22 05:28:24 System -140005 Net Module Rule: 25 Tue 2011/11/22 05:28:25 System -140005 Net Module Rule: 28 Tue 2011/11/22 05:28:25 System -140005 Net Module Rule: 30 Tue 2011/11/22 05:36:27 System -170001 [uDSockets] RSub:31 error:6 Tue 2011/11/22 05:36:32 System -170001 [uDSockets] RSub:31 error:6 Tue 2011/11/22 05:36:36 System -170001 [uDSockets] RSub:31 error:6 Tue 2011/11/22 05:36:41 System -170001 [uDSockets] RSub:31 error:6 Tue 2011/11/22 05:36:45 System -5012 26 Tue 2011/11/22 05:58:12 System -140005 CLI-WBug Tue 2011/11/22 06:00:00 System -140005 Net Module Rule: 24 Tue 2011/11/22 06:00:01 System -140005 Net Module Rule: 23

FYI, I relinked my APs and no longer observe the 170 humidity problem. Everything is being observed on my local WLAN. In my case i can duplicate the problem by simply manually query the tstat. 50% of the time the humidity is reported by the adapter as 170. (see previous post) All other values are reported correctly. Your Cool Setpoint is set to 85 degrees, right? (humidity reports 2 x Cool Setpoint) I believe this is a Venstar adapter bug that has been around ever since I first got mine 2 versions ago and they (Smarthome) still haven't fixed it. The good news is if you don't do manual queries it won't happen much.

Lee, I found the problem. I forgot I have some IR receiver lighting programs which I never use, one of which had a bug in it. Thanks, Elvis

Lee, I do not have any lighting programs in my ISY yet. All still reside in my Elk at the moment. I attached the toggle mode settings, on and ramp rate, and comm error log. Let me know if I am doing something wrong or can help troubleshoot. Elvis Archive.zip

Lee, OK I now see the scene vs the controller initial and ramp rates, and tweaked them to get it working, or so I thought..... For some reason now when I press the MOVIE button when all the lights are off, the responders in the MOVIE scene perform a FAST ON, then proceed to ramp off at the specified ramp rate. I added the MOVIE button as a responder to other scenes to make the illumination respond as appropriate. I attached my topology if this helps. P.S. Are the version numbers reported by the ISY supposed to match the version numbers physically on each device? topology.v3.1.12__Sun 2011.11.20 22.12.28.html.zip

BACKGROUND Sorry if this is a duplicate question, but I didn't come across anything recent. I added a 6 button Keypadlinc switch (2486S v5.5) which I am using secondary buttons for MOVIE and PARTY scene. For the MOVIE scene I want the theater lights to ramp up/down over 30 seconds like in a movie theater. When I add a button to the MOVIE scene the lights simply FAST ON/OFF even though I have the ramp rates set for the individual dimmer devices. The only way I could get it to work was to remove the button from the MOVIE scene and create separate programs to FADE UP/DOWN the MOVIE scene. QUESTIONS Is there a better way to do this or is this a limitation of either the KPL or ISY? Elvis

i installed the Elk module. everything seems to be working, including the voltage and zone status. I discovered that I had to export and import the lighting into the Elk, then tweak my Elk event and time based lighting rules since the indexes changed. My Elk lighting rules are working again. But now the Elk module is no longer reporting area status, zone status or voltages. I have tried rebooting my ISY the symptoms remain. I confirmed the Elk config settings. UPDATE I cleared java cache again even though I had cleared cache after upgrading to 3.1.12 and the Elk module. Now the Elk area/zone information is reflected in the admin console. elk.tiff

Everything is being observed on my local WLAN. In my case i can duplicate the problem by simply manually query the tstat. 50% of the time the humidity is reported by the adapter as 170. (see previous post) All other values are reported correctly.

I upgraded to 3.1.12 remotely without any problems. I did follow the instructions to remove and re-add my tstat per the release notes. When I did i observed that when editing my devices the changes would not take effect until I close my browser and logged back in. Perhaps this is because I was remotely connected. I am at back home now, so I will reports any similar behavior if I see it. I also upgraded to the v2.3 stat adapter late last week. Upon reboot (hard and soft) of the ISY the humidity is sometimes first reported at 170. A manual query of the tstat corrects the humidity. I can't imagine I have Insteon communication issues as my network as been stable for better than a year. Elvis UPDATE I can actually get the tstat to report 170 approx. 50% of the time when I manually query the stat. Thu 11/17/2011 14:47:11 : [ 14 66 F4 1] CLIHUM 53 Thu 11/17/2011 14:47:18 : [ 14 66 F4 1] CLIHUM 170 Thu 11/17/2011 14:47:28 : [ 14 66 F4 1] CLIHUM 53 Thu 11/17/2011 14:48:08 : [ 14 66 F4 1] CLIHUM 54 Thu 11/17/2011 14:48:08 : [ 14 66 F4 1] CLIHUM 170 Thu 11/17/2011 14:48:14 : [ 14 66 F4 1] CLIHUM 54