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

ISY does track X10 status but not based on query but rather by remembering the last command heard. Depending on powerline and module manual control, this status may not be accurate. -Xathros

Right click it and select "Write Updates to Device" Wait for the writes to take place then test again. -Xathros

You must have the older 2412S PLM like me. Yes. It provides 12V to the ISY. The newer Dualband 2413S does not. -Xathros

Hi All- I just tested on all of my KPL's and this works exactly as the Wiki describes for me on MAC OS X 10.8/Java 1.7.13 Click KPL Node in Tree, Click "Buttons Toggle Mode" button, Select a Button from the Popup, Click "Toggle On/Off" button. -Xathros EDIT: My KPL's are v.36, v.40 and v.41

Exactly!. -Xathros

Drew- From that, it doesn't look like the ISY is connected to the network. Check the ethernet cable between the ISY and Airport/Switch. Are there any lights on the ISY's ethernet port when the cable is connected? Michel- See: https://discussions.apple.com/thread/4427603?start=0&tstart=0 Re: AirPort Utility on Lion/Mountain Lion -Xathros

I have run 25' with no problems. I don't think I'd want to push it any further than that though. My Current install is 1.5' -Xathros

I don't think re-flashing 3.3.10 on top of 3.3.10 would have any downside. I considered doing it myself last week but realizing there was not difference from when it was called RC7, I just removed "Beta RC7" from my signature instead... There have been many posts from people whose ISY's did not reboot after a firmware upgrade and required a power cycle. I would be surprised if it needed anything more than that. Mine has never done that but I don't use UPNP or DHCP for my ISY so that may have saved me from this issue. My ISY has only locked up twice that I can recall (once last week) but I attribute both to PLM problems. -Xathros

Other than the fact that the ISY will respond to a ping sent from a computer or other network device. -Xathros

kstock- Relay, Yes - It is a responder type device. Sensor, No - It is a controller only device. It cannot be turned on/off via a command. It Sends On/Off commands to responders/ISY PLM. -Xathros