Xathros

Excellent! And as always, Happy to help. Yes - sorta. https will do the trick assuming you have either enabled Internet access in the ISY or set up the proper port forwarding in your router but the IP address will need to be your external IP assigned by your ISP. Visit http://www.whatismyip.com to find your external IP address. It should also be available in your routers admin console if you know where to look. I wouldn't remove Java if you want to access the admin console since it is 100% dependent on the Java VM. -Xathros

Clear your java cache (All 3 check boxes!). Then try http:///admin/admin.jnlp Remember to substiture your ISY's IP address. You will want to save this file somewhere (Desktop or Applications folder) Double click the file you just downloaded. It will download the applet to cache and then you WILL get the "Cannot create shortcut" message. Click OK and the ISY finder and Console should come up. -Xathros

Very strange. Unable to create shortcut happends after the applet is downloaded to java cache and verified. It should just launch into the console after you click OK on that message. What URL are you using to access the console ? -Xathros

Here's a few answers: A) You currently must manually set up your user codes using the door lock itself Yes, you can detect which code was entered using programs, and therefore can do a variety of things based on that including logging (notifications), turning on lights, adjusting thermostat, arm/disarm Elk, etc. C) Not currently, but we will be adding more detailed support as we go along. D) For Schlage locks it actually "unsecures" the lock meaning someone still has to manually unlock it. For Yale, this will actually "throw the bolt" as they say, meaning the door will actually lock/unlock. E) Yes, but there would be no distinguishing whether the door is locked/unlocked manually from inside vs automatically, or by code, or by key outside, etc. If there is a way to detect this, then we would likely add this feature in a future build. Thanks Chris. Good answers. Could you clarify on answer E. If the ISY can detect the state change from Secured to Unsecured and there was no code entered, wouldn't that indicate manual lock operation? Thanks again. -Xathros

A Nexia/Zwave enabled lockset is required - the Nexia Home bridge and service is NOT I'm told. I don't know yet how much control the ISY will give me over the lockset. I can't wait to find out. Maybe Michel will chime in here. Can we: A) Manage User codes. Log which code was used when. C) Enable/Disable Vacation mode D) Lock/Unlock - This I'm pretty sure we can do. E) Log when the door is Locked/Unlocked manually by the inside lock knob. -Xathros

You need a lock that is Nexia enabled, but you DO NOT need the Nexia monthly service. Correct. The lockset they sent me was of the non-Nexia variety. Very pretty keypad but no radio From what I've seen online, I think they look the same except for the model# and the Nexia info on the box. I'll know better in a few days. I suspect someone at the warehouse just picked the wrong item. -Xathros

I'm running 3.3.8. So what is the issue? Thanks for your help! Unfortunately, no. You should however upgrade to 3.3.10 (The official release) but that I'm afraid is not the issue with the temp updates. So, now we are down to communication issues or link record issues. Is this stat on battery power or powered by the line somehow? Run an event viewer level 3 trace showing a few setpoint changes from the admin console as well as a few from the stat. If you can change the temp in the vicinity of the stat (Hair dryer, open garage door etc) and capture that traffic, I'm sure that would be helpful as well. Post the trace. -Xathros

jmed999- That other thread occurred before I became enlightened with the above knowledge otherwise I would have offered it back then! -Xathros

Well, my Schlage lockset arrived Sat morning and very soon after, I discovered they shipped the Non Nexia version. 3 more days till the right one arrives... -Xathros

Just in case- I ran into this over the weekend. Apple very nicely changed the default action for opening .jnlp files. For me, they wanted to open with my text editor. Cute. I always wondered what was in that file... Anyway, simply do a Get Info on the admin.jnlp file (Cmd-I) and change Open With to Java Webstart. Select change all. That should fix it. HTH -Xathros

hyounker, Michel- If after the support session, the DD-WRT router still appears to be at fault, try this: Log into the router, go to the Administration tab and make a backup of the router. Save the nvram.bin file where you can find it again in a few minutes. After the backup, also from the administration tab, reset the router to factory defaults. Power cycle the router. Log back into the router (default user/pass is either root/admin or admin/admin), go to Administration and restore your backup. Power cycle the router again and restest. -Xathros

Yes. Depending on the age of the 994, you may need an enclosure as well. Newer 994s have a knockout large enough for an RJ-45 Jack right next to Port A on the back. If your 994 does not have that knockout, you will need to replace the enclosure. The zwave dongle actually lives at the other end of a 10' cable that plugs into an RJ-45 at that knockout. (At least in the Alpha form.) -Xathros

I don't think I was having any trouble until 4.0.1. The console was staying accurate and my programs were executing properly for me until then. This is with a Venstar/Insteon Adapter. -Xathros

jmed999- 2 things. First, what firmware are you running on the ISY? If 4.0.1, the temp is not being updated in the ISY without a query. Mobilinc and the admin console are in agreement with each other. I suspect the temp has just not updated in the ISY. Second, why all those programs just to send the temp? You can send the temp in a customized email using variable substitution with: sys.node.AA BB CC 1.ST where AA BB CC is the address of your thermostat. Then just one program like: If Time is sunrise Then Send notification “Current Temp†Here is the string I use in an email customization: Current Temperature is ${sys.node.11 B2 7 1.ST} My Venstar address is: 11.B2.07 I had to drop the 0 from 07 to make it work. You can get status from any node in this way. Also some other useful stuff. See this section of the Wiki: http://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Custom_Email_Substitution_Variables -Xathros

No Problem and I have confirmed that when the IOLinc is queried via program the false trigger does NOT occur. -Xathros

The procedure is as follows: Upgrade the 99i to the latest firmware for the 99i (3.3.10) if you haven't already. Backup the 99i Since you have the network module, copy any files that you have placed in the 99i's webserver as these are not backed up by the above backup. If you haven't touched the webserver at all then don't worry about this. Your Network Resource Rules ARE in the backup. Don't worry about them. Make a note of the uuid of the 99i from Help/About, make a note of any addon modules (Network Resources Module etc) that you have purchased that you want transferred to the 994i. Make a note of your SMTP settings for notifications as you may need to enter these into the 994 after restore. Unplug the PLM from power, disconnect the 99i and replace with the 994i. Plug the PLM back in, wait 5-10 seconds then power up the 994i. Log into the 994i admin console and Upgrade the 994's firmware to 3.3.10 if not already there. You can skip the backup step here when prompted as there is nothing configured that needs to be backed up from the 994i. Once upgraded to 3.3.10, log into the 994i and restore the backup from the 99i If you had a static IP address set in your 99, you should be prompted about setting that address in the 994 or leaving the 994 configured for DHCP. - Your choice. NOTE A: If you have port forwards all set up in your router, restore your static address and nothing in the router should need to change. NOTE B: If your static address is provided by your router using MAC reservation, you will need to edit that reservation in your router to use the 994's MAC/UUID instead of the 99's You will need to reset your custom username and password if you have changed them from the default (recommended) Email support@universal-devices.com with the old uuid, new uuid and list of purchased addon modules that you want transferred to the 994i. Support has been very responsive on these requests. Once that has been done, you can replace any files that were on the 99i's web server. Double check your location settings, NTP server settings and correct if necessary. Now, make a backup of the 994i with your configuration and save this one. That should do it! Hope this helps. -Xathros EDITED 3/8/13 to add additional detail.

Yep. Last run/finish are same as the last time I queried the IOLinc sensor node. for the one I'm playing with. For the other door, it was time the door was closed this morning until I queried it just now. I think I've run into this before too and just never took the time to research exactly what was happening. So it's quite possible it's behaved this way all along and I'm just now noticing. I don't have a 3am query set up so I can't say if that would trigger my notifications or not. Michel- Is this the intended behavior? Everything I've learned here so far would seem to indicate not. Shouldn't the status have to change to trigger that condition? -Xathros

Not having noticed any issues with my garage door IOlincs, I decided to do a little testing this morning to see if I was having the same problems everyone else is reporting with them. So far I don't think I am but I'm not quite done with my tests yet. I did notice something that I think may be wrong and wanted to mention it and see what you all think. Right now the door is closed, Admin console shows sensor is off. This is correct. From the console, I query the sensor, the query returns Off as it should BUT my door closed notify program runs. If Status 'Garage / Garage Door IOLinks / GD- Dad Garage Door Sensor' is Off Then Resource 'NOTIFY - Dad Garage Door Closed' Else - No Actions - (To add one, press 'Action') The status of the sensor did NOT change due to the query yet this program fired. If I query again, the program fires again. Without the status changing. I don't think this program should notify unless the sensor status CHANGES from On to Off. Is this a bug or am I overlooking something? -Xathros

The only way would be to disable the normal 4am query and build your own scene with only the devices you want queried and a program to query that scene at 4am. -Xathros

oberkc- No. The announcement listed initial support for the few devices I have plus a few locksets. I certainly don't expect the alpha to support anything outside of what UDI says is there. -Xath EDIT: Actually, the Wiki mentioned it - not the announcement: http://wiki.universal-devices.com/index ... Wave_Alpha

I will attempt a reasonable distance test with the lockset once I get it. I don't have any zwave motion sensors yet and I'm not sure I will go that route anyway. Like you I am considering wired pet immune sensors instead. So far, I have an appliance module and a dimmer installed. My zwave dongle is in the basement near my network shelf at one end of the house just hanging from a nail in a ceiling beam. The dimmer is on the first floor maybe 25' away and works flawlessly. I have moved the appliance module from plug to plug on the first and second floors and it has not failed yet. Furthest is probably 45' with 2 sheetrocked walls and 2 hardwood floors between the module and the zwave dongle. At that location, the dimmer may have been acting as a repeater but I don't yet know how to tell. -Xathros

I am headed down this path this weekend with a Schlage lockset. I will let everyone know how it works out for me. -Xathros

Michel- Thanks. I feel much better now. Was worried I might have file system problems. -Xathros

I have been getting these in my error logs for the last few days. Should I be worried? What do I need to do to correct this? Wed 2013/02/20 12:25:50 AM System -110022 /CONF/880000.REC Wed 2013/02/20 12:25:50 AM System -110012 /CONF/880000.REC Wed 2013/02/20 12:25:50 AM System -110022 /CONF/910000.REC Wed 2013/02/20 12:25:50 AM System -110012 /CONF/910000.REC Wed 2013/02/20 12:25:52 AM System -110022 /CONF/910000.REC Wed 2013/02/20 12:25:52 AM System -110012 /CONF/910000.REC Wed 2013/02/20 12:25:53 AM System -110022 /CONF/880000.REC Wed 2013/02/20 12:25:53 AM System -110012 /CONF/880000.REC Wed 2013/02/20 05:38:38 AM System -110022 /CONF/880000.REC Wed 2013/02/20 05:38:38 AM System -110012 /CONF/880000.REC Wed 2013/02/20 05:38:38 AM System -110022 /CONF/910000.REC Wed 2013/02/20 05:38:38 AM System -110012 /CONF/910000.REC Wed 2013/02/20 05:38:40 AM System -110022 /CONF/910000.REC Wed 2013/02/20 05:38:40 AM System -110012 /CONF/910000.REC Wed 2013/02/20 05:38:41 AM System -110022 /CONF/880000.REC Wed 2013/02/20 05:38:41 AM System -110012 /CONF/880000.REC Thanks -Xathros

You could just pull air gap switches one or two at a time till the problem stops. That should help narrow down the problem device(s) -Xathros