elvisimprsntr

Just a wild guess, but have you tried replacing the spaces with %20 UPDATE: I tried using %20 and it did not work.

If you really want to get fancy you can add separate scene for each fan speed and adjust the single keypad button brightness for each fan speed.

I recommend staying away from the Insteon thermostats. Not one of Smarthome's better products. Poor adapters, RF signal, poor features, etc. Has nothing to do with the ISY controllers, which are excellent. Drop some coin on some Nest thermostats and don't look back, assuming they are compatible with your HVAC. No integration with the ISY since it's not a public API, but it's not really necessary given the features of the Nest. If you really want to control the Nest, the Cloud API has been reverse engineered.

I'm in the wait and see mode. Lets see if they survive past their initial round of funding. In my humble opinion HA is about making lives easier and convenience. A touch screen device located on a book shelf or permanently mounted on a wall means i need multiple units located throughout the home. Living room, theater, kitchen, one on every floor, etc. raises the entry cost barrier, complexity, and means I have to get up off the couch to use it. I prefer a mobile touch device which is always within reach and can be used in any room. As I have commented on other forums, the next 2 years we will see a lots of companies putting an ARM CPU in a pretty box with wifi and HA control. Most will charge a monthly recurring extortion fee for the privilege of controlling ones home, if not initially, eventually when they can't turn a profit or their investors force them to. So what will you be left with when 99% of these companies go bankrupt after they bleed their KS funds dry? A door stop and hopefully some devices you can reuse with some other HA controller. There are two basic criteria I use for any new piece of technology I introduce in my home. One, can it be controlled via my mobile device? Two, is their a recurring extortion fee?

The folks at cocoontech did a live chat on Friday. http://cocoontech.com/forums/index.php? ... i-(Almond+)---02/22/2013

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.