elvisimprsntr

EKeypad and mobilinc

I have an IRTach which I use as a door stop. They don't store codes. I replaced them with www.thinkflood.com redeye units which have mobile apps and a rest API which you can tie into the ISY network resources. I'm ordering redeye pro unit as I write this from my home theater.

Venstar humidity problems are typically a combination of a bad AP or bad AP location, and the fact the humidity needs to be divided in half. Between that and the never ending non-field updatable firmware changes for the Insteon adapter drove me to Nest.

The the time it would take to remove it and install the standard switch/outlets, only to install it again somewhere else doesn't seem worth it to me. I'd rather install new stuff at a new house. I'd probably take my new ISY994i and give them my old 99i. Then point them to the a few sites or hand them the phone number to smarthome.com who will roll a truck.

My ISI994iProIR locked up 5 minutes ago.

A serial console?

I really can't recommend any if the Insteon thermostats. They are so last century and plagued with Insteon firmware problems. That is not a reflection on UDI. Thermostats are not one of SHs strong points. Drop some coin on a Nest and you will not be disappointed.

I use the Elk DB module with an IOLinc and IP camera with GPIO at my front door. When someone presses the doorbell. I turn on the light, close IOLinc relay which triggers the camera to send a picture to my phone. I don't have to get off the couch to see who it is. Usually it's a package delivery.

Humm. I've never had the problem you describe except old firmware and Elk module problems. I've read other people having problems with bad flash. You can check the about page which will report bad blocks.

1. The N/A is the expect response from the RedEye IR controller. I wasn't concerned about that. 2. The only -140xxx error in the the WB error which is also in the video. 3. The network resources actually perform their function correctly. The error message seem to be related to previous errors from power up and not specifically related to network resources, but only appear when you attempt to use the test function.

BACKGROUND I've been getting various error messages when I test network resources. It's not unique to 3.3.10 INFO I am logged in from Safari + Java 1.7.11 using port 80. I have been through the advanced network procedure for certificates. In order to repeat the problem I have to reboot the ISY and I do not always get the same set of error messages, but the certificate file error and the failed request always come up. QUESTION What can I do to help diagnose this problem or what am I doing incorrectly? Thanks, Elvis

Following up on an issue i first reported under 3.3.7, I am still getting NTP timeouts even after updating the NTP Server to time.nost.gov. Elvis Sun 2013/01/06 05:37:45 System -60006 Stopping retries/next cycle Sun 2013/01/06 11:38:03 System -60006 n/a Sun 2013/01/06 18:00:01 System -140005 Net Module Rule: 23 Sun 2013/01/06 18:00:01 System -140005 Net Module Rule: 23 Sun 2013/01/06 18:00:02 System -140005 Net Module Rule: 30 Sun 2013/01/06 20:38:28 System -60006 n/a Sun 2013/01/06 20:38:28 System -60006 Stopping retries/next cycle Mon 2013/01/07 00:00:01 System -140005 Net Module Rule: 25 Mon 2013/01/07 00:00:01 System -140005 Net Module Rule: 28 Mon 2013/01/07 00:00:02 System -140005 Net Module Rule: 30 Mon 2013/01/07 00:00:03 System -140005 Net Module Rule: 36 Mon 2013/01/07 00:00:03 System -140005 Net Module Rule: 39 Mon 2013/01/07 00:00:04 System -140005 Net Module Rule: 41 Mon 2013/01/07 02:38:38 System -60006 n/a Mon 2013/01/07 02:38:43 System -60006 n/a Mon 2013/01/07 02:38:48 System -60006 n/a Mon 2013/01/07 02:38:53 System -60006 n/a Mon 2013/01/07 02:38:58 System -60006 n/a Mon 2013/01/07 02:38:58 System -60006 Stopping retries/next cycle Mon 2013/01/07 05:00:01 System -140005 Net Module Rule: 24 Mon 2013/01/07 05:00:01 System -140005 Net Module Rule: 23 Mon 2013/01/07 05:00:02 System -140005 Net Module Rule: 30 Mon 2013/01/07 05:00:02 System -140005 Net Module Rule: 35 Mon 2013/01/07 05:00:03 System -140005 Net Module Rule: 34 Mon 2013/01/07 05:00:03 System -140005 Net Module Rule: 41 Mon 2013/01/07 18:00:00 System -140005 Net Module Rule: 23 Mon 2013/01/07 18:00:01 System -140005 Net Module Rule: 23 Mon 2013/01/07 18:00:01 System -140005 Net Module Rule: 30 Mon 2013/01/07 20:39:35 System -60006 Stopping retries/next cycle Mon 2013/01/07 22:00:38 System -5012 0

BACKGROUND I have been getting NTP retry errors and USSockets errors (which incidentally is not listed on the error codes wiki). Not sure what beta release these started showing up, but they were not present with the last official release. I can manually sync time without a problem. I am using "us.pool.ntp.org" as the NTP server. Tue 2013/01/01 00:00:01 System -140005 Net Module Rule: 25 Tue 2013/01/01 00:00:01 System -140005 Net Module Rule: 28 Tue 2013/01/01 00:00:02 System -140005 Net Module Rule: 30 Tue 2013/01/01 00:00:03 System -140005 Net Module Rule: 36 Tue 2013/01/01 00:00:03 System -140005 Net Module Rule: 39 Tue 2013/01/01 00:00:04 System -140005 Net Module Rule: 41 Tue 2013/01/01 00:46:17 System -60006 Stopping retries/next cycle Tue 2013/01/01 05:00:00 System -140005 Net Module Rule: 24 Tue 2013/01/01 05:00:01 System -140005 Net Module Rule: 23 Tue 2013/01/01 05:00:01 System -140005 Net Module Rule: 30 Tue 2013/01/01 05:00:02 System -140005 Net Module Rule: 35 Tue 2013/01/01 05:00:02 System -140005 Net Module Rule: 34 Tue 2013/01/01 05:00:03 System -140005 Net Module Rule: 41 Tue 2013/01/01 14:59:31 System -170001 [uDSockets] RSub:44 error:6 Tue 2013/01/01 14:59:36 System -170001 [uDSockets] RSub:44 error:6 Tue 2013/01/01 14:59:41 System -170001 [uDSockets] RSub:44 error:6 Tue 2013/01/01 14:59:46 System -5012 30 Tue 2013/01/01 18:00:01 System -140005 Net Module Rule: 23 Tue 2013/01/01 18:00:01 System -140005 Net Module Rule: 23 Tue 2013/01/01 18:00:02 System -140005 Net Module Rule: 30 Tue 2013/01/01 18:47:01 System -60006 Stopping retries/next cycle Wed 2013/01/02 00:00:01 System -140005 Net Module Rule: 25 Wed 2013/01/02 00:00:01 System -140005 Net Module Rule: 28 Wed 2013/01/02 00:00:02 System -140005 Net Module Rule: 30 Wed 2013/01/02 00:00:03 System -140005 Net Module Rule: 36 Wed 2013/01/02 00:00:03 System -140005 Net Module Rule: 39 Wed 2013/01/02 00:00:03 System -140005 Net Module Rule: 41 Wed 2013/01/02 05:00:00 System -140005 Net Module Rule: 24 Wed 2013/01/02 05:00:01 System -140005 Net Module Rule: 23 Wed 2013/01/02 05:00:01 System -140005 Net Module Rule: 30 Wed 2013/01/02 05:00:02 System -140005 Net Module Rule: 35 Wed 2013/01/02 05:00:03 System -140005 Net Module Rule: 34

I've been experiencing problems access the Elk and ISY using third party iOS apps Mobilinc and eKeypad since upgrading to this release. I've had to reboot my Elk XEP, which I almost never need to, and the ISY. Not sure what to make of it yet, but thought I would mention it in case someone else observes symptoms.

no issues upgrading from 3.3.4

Upgraded from 3.2.6. No problems, except the first time I brought up the admin console on my Mac, the console only listed a tstat control page. I replace my Insteon tstat with a Nest a long while ago and had already deleted my previous tstat devices. I did clear my cache after the upgrade and checked the box to remove installed applets, and yes I am running Java 1.7. I cleared cache one more time and have been unable to duplicate the problem since, I also checked the REST interface for the URLs I use in my setup. Just curious, what were the factors that led to removal of Brultech support from the original ISY99i? Thanks, Elvis

Joe, I looked at the trying to add hardware to my builder installed napco many years ago. i ripped out my POS nalco and installed an Elk M1 Gold and couldn't be happier. WIth the Elk you can add ISY integration and control, there are mobile apps that will allow control. The best part is I don't have to pay an installer/monitoring service any extortion fees for the privilege of access my Elk/ISY.

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