Xathros

I believe that simply displays the URL that you used to access the ISY. Use the new URL and thats what it should display. Thats how it works with my ISY's at least... -Xathros

As long as the new URL points to your router and your router forwards to the ISY, all you need to do is start using the new URL wherever you used the old one. You can add a new entry to the ISY finder using the new URL then remove the old entry. -Xathros

Anytime. Always happy to help. -Xathros

Excellent! I still have some concerns about your PLM given the history you have posted. Lets hope it holds up and that the upgrade solves the problems. -Xathros

I'm using Mobilinc to manage my ZWave stuff remotely. -Xathros

All modules can be transferred to the new 994. Simply send the UUIDs of both the Old and New ISY's to support and request the modules be transferred. -Xathros

Since you are calling your program directly, simply disable the program. This will prevent the time triggers from operating on their own and they will only be evaluated when you call it directly with Roomie. A disabled program still runs when directly called, it simply does not self-trigger. Hope this helps. -Xathros

Looks to me like you are seeing rain in the past 24hrs rather than what WB called Rain Today. -Xathros

Chris- You can't have ZWave and Zigbee both in the same ISY. Assuming you are pulling the Zigbee radio and installing the ZWave radio, 25' will likely work as long as you get the external antenna with the ZWave radio. You will likely need other ZWave devices to build up a mesh to expand from there. The AOTech repeaters seem to work and are an easy way to extend out the ZWave network. Some Stats also act as repeaters - not sure about yours. -Xathros

Neil- I'm thinking your PLM, as Michel indicated, is on it's way out. RX lit steady means unable to communicate with the PLM. -Xathros

2 modules and 4 scenes should do the trick. -Xathros Sent from my iPhone using Tapatalk

While I could switch 115VAC with the DinRelay, I opted to switch the low voltage side of the wall warts that power the ISY and other network components. This way, I was able to just mount the DinRelay on my backboard and not have to worry about exposed high voltages. The web switch is simply the DIN Relay packaged for switching 115VAC. @Teken, I'll have to check out the iPhone app and see if it works with the DinRelay too. Thanks for the tip! -Xathros

Select delete from the Primary node of the KPL not one of the sub nodes. -Xathros

As long as the KPL primary node is in a scene as controller with the FL Light node as responder then it should just work as you want. No program necessary. -Xathros

It certainly can. I have a program that runs daily just before midnight and among other things, shuts down my AV stuff in the living room. -Xathros Sent from my iPhone using Tapatalk

I am using the itach with several network resources to control my samsung tv and a blue ray player. I can post some details when i get home. -Xathros Sent from my iPhone using Tapatalk

Assuming that the Sonos has a line level input, you could use a RaspberryPi with Festival for TTS and plug the audio from the Pi into the Sonos. ISY could then send a network command to the Sonos to select the line in and follow that with a request to the Pi to speak your message, then another command to the Sonos to reselect the previous source. I do not yet own a Sonos so some assumptions have been made on my part as to the capabilities of the sonos and the ISY's ability to control it. For reference, here is a link to TTS on a Pi: http://elinux.org/RPi_Text_to_Speech_%28Speech_Synthesis%29 Hope this helps. -Xathros

On the Configuration / System tab at the bottom of the box titled "System". You are correct that this is not accessible with an iPad however. I have used RDC to connect to a machine at work to connect to my ISY and gain access to the admin console from my iPad on a few occasions. Kinda the long way around but it does work in a pinch. I also use the Digital Loggers DIN relay web switch similar to the WebSwitch that Teken linked to for some of my isy/network gear as well as for ISY control of a few local appliances. Well worth the price and in the few years I've been using it, it has never failed. I'm pretty sure that what Teken linked to is the same core device with a power cord and outlets attached. -Xathros

You are correct. If we were to use Control in this case, there would be an issue with the reopening of the door during an existing countdown delay. The use of Status in this case will take care of that scenario by aborting the countdown if the door reopens during the delay. Now just to be compete here, we could use Control as long as we look for both On and Off events as follows: If Control 'Door Sensor' is Switched Off and Control 'Door Sensor' is not Switched On Then Delay... Else Nothing... But Status is easier in this case. -Xathros

N/O and N/C are defined differently by different industries and intended uses. Sensors meant for Alarm systems seem to have the opposite meaning than normal relays and switches. A N/C push button is closed until pushed. A N/C window sensor is closed when the magnet is in proximity and open when the magnet moves away. It's all in the definition of "Normal"... -Xathros

As seen above, Quote seems to work. At least on my Mac using Firefox. @oberkc, don't worry about second guessing me. I often miss things and you have offed much good advice here as well. As I stated in my first reply, either status or control SHOULD work in this scenario assuming the perfect operation of the door sensor. The only reason I suggested using status over control was due to the possibility of a sensor bounce occurring during the opening of the door causing a false close control message and starting the countdown while the door is open. Since only Control Off would trigger the program, the sensor stabilizing in the On position would not abort the countdown and the light would be turned off while the door is open. Status in this case would correctly abort the run when the sensor finally stayed on the open position. I have had to deal with sensor bounce on one of my garage doors and have helped a few others here with similar issues so it is a known possibility. In this particular case, I don't see an issue with status failing to accomplish the stated goal as any sensor bounce would only be a very momentary issue filtered by the waits and in the end the status will be correct for open or closed door positions. -Xathros

To add to what LeeG said, in the event this does happen again, you can log into the Admin console and reboot the ISY. This should correct the situation assuming the PLM is still functional. -Xathros

Hi Teken- In this instance, I don't believe it matters. Either control or status will achieve the same result. Only difference is that when using Status, the program will trigger on both door open and close. On open, it will run the empty Else clause and have no effect. On close it will run Then and do what you want. With Control, it should only trigger on the door closing. If you get some sensor bounce when the door is moving near the sensor, control might cause a false "Closed" trigger when opening the door while status would correct itself once the door moves away from the sensor. I would stick with Status in this case. Hope this helps. -Xathros

Right click the program name in the lefthand pane and select "Copy to Clipboard" from the bottom of the popup menu. My programs are also recognizing user codes correctly and executing appropriately. -Xathros

8 months is within warranty. Pick up a spare and have Smarthome replace the failing one for a future spare. -Xathros