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

That sounds more like a scene failure to me. A direct command failure usually results in a "Can't Communicate" popup in the admin console. -Xath

Hi. I've been lurking in the background watching this thread. This makes the most sense to me. Both the remove and re-add to get all the nodes and On=Wet/Off=Dry. -Xathros

Well, you could tell the program to set the Kitchen SWL On/Off rather than the scene. That would at least give you the built-in retries of a direct command. Probably best to solve the comm issues though. -Xathros

OK this makes more sense now. When operating a scene, the ISY does not verify that the SWL actually turned on/off and so does not retry in the event of a failure. When Operating the SWL with a direct command, the ISY expects a response and if it doesn't get one, it tries two more times before giving up and saying "Unable to communicate with...". You have marginal comms between the PLM and the SWL location based on your above description. It seems the MS and whatever dualband device it is communicating through have good comms to the SWL since it is able to operate the SWL as a scene controller. Run a level 3 event trace and turn on/off the swl (device) a few times from the Admin console. Lets see what we get for comms. -Xathros Edit: Hehe. LeeG beat me to it!

It's currently configured with a 5 minute timeout, sending both ON and OFF commands and set to do it all day, not just at night. I tried setting it to send ON only, but then the ELSE statement never ran.... I guess I could modify the program so it turns the scene on, waits 5 minutes, then turns the scene off all in the THEN statement and tell the motion detector to only send the ON commands. Might that work better? How does everyone else seem to do it? There are a number of variations. A) MS as controller of Scene On/Off with timeout. MS As controller of Scene On Only with a program to delay and turn off. C) MS not in a scene On Only with programs to watch for On and delay for off. A&B offer fast light response on motion but less control over when the light are enabled/disabled on motion. C offers the greatest flexibility but has an inherent 1 - 2 sec delay between detection and response. Now, back to your problem... Are you seeing the MS Status change in the admin console? I assume you are letting the MS timeout and turn off then moving to cause an On correct? -Xathros

How is the MS configured? Is it in occupancy mode? Is it sending On Only? What is the timeout delay? -Xathros