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

Michel- Gotcha. That makes sense. I have to remember that there is more than one piece to this puzzle. Still wouldn't having NTP enabled cause DNS lookup errors / fail to connect errors in the log? Certainly the NTP stuff happens in the ISY rather than the console right? -Xathros

Michel- I think he is asking about setting up an ISY with no internet available. I was thinking disable NTP but not sure if there is anything else that should be done for a LAN only setup. I know the ISY calls home to check for firmware updates and module installs. Not sure how it ill behave when it can't make the connection back to UDI. -Xathros

Andy- For now, I have a program query the Venstar every 5 minutes. That should solve the problem till it gets fixed. -Xathros

I second this! I just did this last week when I meant "And" and said "Or" in an If statement. It kept the ISY so busy, it took a good minute to get to and disable the program so I could fix it. -Xathros

I believe failed comm during query leaves the status of the device unchanged but will pop up a "Could Not Communicate With ..." message on your next login to the admin console. I have had my 3am query disabled since I moved into this house 2 yrs ago. No problems with that (until this morning). I have generally decent comms within the house. Only one Togglinc that gives me trouble in my barn at the far end of a 300+' run. The two other devices in that barn report consistent 3/2 comms so when I get a chance, I will replace the weak togglinc. -Xathros

This morning I woke up to the house at 60F. I keep Venstar stat that controls my oil burner set at 60 and have a few programs that watch the temp as reported by the Venstar and turn on/off my pellet stove as necessary. When I logged into the admin console, it reported the temp as 69F. As soon as I hit query, the temp updated to show 60F and the pellet stove came on. After an hour or so, I looked again and the Venstar had come up to 65F but the admin console still showed 60F. The corrected again as soon as I hit query. Testing comms between the console and the Venstar shows consistent 3H/2L when adjusting setpoints via the console. I did a show device links table and compare: Attachment: Extra Record does not sound right to me? My plan is: Query Engine and Restore Device but figured I'd post here first just in case you want my to try something else first. -Xathros

First zwave related operational problem - maybe. I created a scene with a zwave appliance module as responder and a Togglinc as controller as shown below. If I turn the scene on/off from the console it works just fine. If I turn the scene on/off from the togglinc, the console shows the togglinc status change but does not tell the zwave module to turn on/off. If I run a scene test, it fails as below. Both the module and togglinc turn on for the test but the appliance module does not turn off untiol after the trest reports failed. I understand that the Insteon togglinc does not link to the zwave module but I assume ISY is supposed to pass on the message when both devices coexist in a scene. Am I misunderstanding? Do I need to use programs to track and manage the devices? -Xathros

Looks like some theme issues in 4.0.1 As soon as I added a Zwave device, the blue started to creep in. I think the finder came up blue before that. The Wiki seems to show the theme working so not sure if this is just a MAC thing. Here are some examples: I noticed the Add dialog for zwave devices has a MASSIVE font size during the add and only the bottom half of the Adding Device message was visible. No operational problems to report yet. -Xathros

Upgraded to 4.0.1 and installed zwave module without issue. Thanks. -Xathros EDIT: What/where exactly is the IP camera support mentioned? - Found it! - On the basic web interface.

I use Mobilinc HD and iRule. Looking into Demopad but I need to build a WindowsVM to operate their designer software and I haven't quite convinced myself that its worth the effort yet. -Xathros

Matt- With the exception of the Weatherbug module, I don't see where the ISY cares about C/F - It simply reports/Sets degrees. I'm working with a Venstar Thermostat. Dunno if that makes a difference here or not. -Xathros

Some of us here have installed low cost / low power linux devices like Pogoplug or Raspberry PI to get away from needing to run a PC all the time. I use a Pogoplug to run caiwc to interface my CAI Webcontrol board with the ISY. It also doubles as a Syslog , FTP and Web server. Next project is getting Siriproxy running on it. -Xathros

Awesome. Thats much cheaper than a new PLM or even return shipping for a warranty exchange. -Xathros

I assume you have tried another cable between the ISY and PLM. Does the PLM light do anything when plugged in and/or it's set button pressed ? -Xathros

I think there must be another program involved somewhere. -Xathros