Xathros

Hi smokegrub- Open the admin console using the applet on your desktop. After it opens, minimize the console screen. You should find the smaller ISY Finder screen hiding behind the console. Click the Add button and filling the URL for your ISY using the external IP address or DynDNS address. -Xathros

Check to see if the lights are OFF first and if they are NOT leave them alone. If Control 'Gathering Room / Motion' is switched On And From Sunset + 6 minutes To Sunrise + 6 minutes (next day) And Status 'Gathering Room / Floor Lamp' is Off Then Set 'Gathering Room / Floor Lamp' Fast On Wait 45 seconds Set 'Gathering Room / Floor Lamp' Off Else - No Actions - (To add one, press 'Action') Note the MS is coupled directly to the module via X10 but it causes the responding lamp to come ON very slowly and I don't like it so I hit it with a 'Fast On' immediately and it beats out the ramp up with an almost immediate full brightness. The ISY is fast if you don't call another programme first. I like the slow ramp off though. Larry- I don't think this program will work as expected. Lets assume that the lights are off to begin with and someone trips the motion sensor. The program will run the then and turn on the light which will instantly re-trigger the program since there is a status change in the lamp. This time it will run false and the timer will never time out and the lights remain on. Subsequent triggers of the sensor will have no effect as the light is now already on and the program will continue to evaluate as false. -Xathros EDIT: Here is a way that should work: If Control 'Gathering Room / Motion' is switched On And From Sunset + 6 minutes To Sunrise + 6 minutes (next day) And Status 'Gathering Room / Floor Lamp' is Off Then Run Program MotionTimer (Then Path) Else - No Actions - (To add one, press 'Action') Program: MotionTimer If Control 'Gathering Room / Floor Lamp' is not Switched On Then Set 'Gathering Room / Floor Lamp' Fast On Wait 45 seconds Set 'Gathering Room / Floor Lamp' Off Else This way, the motion sensor will only trigger the lights if they are not already on and the status change of the lights will not terminate the timer. In addition, if the MS turned the lights on and you want to cancel the timer and keep them on, simply switch the lights on again from the local control. Hope this helps. -Xath

Over the years, I have learned to not rely on consumer grade routers for DNS resolution. Any time I can specify a "real" DNS server in a devices network configuration, I have had better, more stable results. -Xathros

Hi DAlba- You need two programs for this. First: f Control ‘Device A’ is switched On Then Run Program Flasher (If Path) Else Program: Flasher (Disabled) if Status Device B is Off Then Repeat 2 times Set ‘Device B’ Fast On Wait 1 Seconds Set ‘Device B’ Fast Off Wait 1 Seconds Else Repeat 2 times Set ‘Device B’ Fast Off Wait 1 Seconds Set ‘Device B’ Fast On Wait 1 Seconds Very important: Make sure the flasher program is disabled! -Xathros

mdcastle- As far as the Insteon remote from the car: Insteon RF is very range limited. I have a Remotelinc2 in my car and an access point in my garage and find that it won't communicate once I get about 10' outside of my garage. The phone with Mobilinc is a much better solution. -Xathros

My guess is that your ISY is configured for DHCP and is using your router for DNS. I would try setting the ISY for a static address outside of your DHCP range and specify the DNS as 8.8.8.8 -Xathros Sent from my iPhone using Tapatalk

I think there may be some additional functionality if using the Mobilinc Connect service. -Xathros Sent from my iPhone using Tapatalk

pinkfish- I would start with a reboot of the PLM and ISY if you haven't already. Unplug the PLM from power and unplug the ISY power supply. Plut the PLM back in, wait about 10 seconds then plug the ISY power back in. Wait a minute and try to connect again. -Xathros

Big517- Any place a value is critical, regardless of state or integer, setting the init value is a good idea for just that reason. -Xathros

Hi Gary- There was another thread here a week or two back regarding building an Insteon beacon out of Triggerlinc for just this purpose. Once my schedule settles down a bit, I am going to pursue that route and see how it works out. -Xathros

There are no string variables yet. Version 5 may allow for this when it is released. The simple solution for now would be to send a message when the door is opened that includes the current time: If Control GD_IOLinc_Sensor is Switched On Then Send Notification To Content GarageDoorOpened For the custom notification: Garage door opened at: ${alert.time12}} on ${alert.date} Leave you "Still Open" reminders as they are. When V5 comes out, hopefully you will be able to modify the above to simply store the date/time in variables when the door is opened then use those variables in your reminder messages. It's been a while since I looked at apostolakisl's date programs and I don't remember if he tracks time as well as date. It may be possible that you could grab integer Hour and Minute from them to store in variables now but unless you have other uses for those programs, it's a lot of effort for this single use. -Xathros

Make sure you have upgraded the 99 to 3.3.10. Make a good backup. If you have the Pro module and have anything on the webserver, copy that out to a folder on your computer as that is not included in the ISY backup. Make a note of the ISY's UUID from Help/About as you will need this and the 994's UUID when requesting that any of your purchased modules get transferred to the 994. Shut down the old 99I and unplug the PLM. Connect the new 994 to the PLM. Power up the PLM, wait a few seconds then power up the 994. Login to the 994 and restore your backup from the 99i -Xathros

The hub is really a very basic device and is rather limited. If cost is not a factor, and you want full featured programmability and the capability to interface to other things like your cameras and such, then in my opinion, the ISY-994 is the way to go. Given a small install, you likely don't need to Pro module and can pick up the network module at a later date if/when you decide to integrate with external systems. -Xathros

WetCoastWillie- To simplify, you can combine your first 2 programs into one: Unocked Status If Status 'Front Door Lock' is Unlocked Then Set Scene 'Front Door Lock / Front Door Lock' On Else Set Scene 'Front Door Lock / Front Door Lock' Off Then, you can combine your second two programs into one: Door Locked If Control 'Master Bedroom KPD.H' is switched Off and Control 'Master Bedroom KPD.H' is NOT switched On Then Set 'Front Door Lock' Lock Else Set 'Front Door Lock' Unlock Note: you need the programs because Insteon/ZWave scenes do not yet work. If they did, having both the KPL Button and Lock set as controllers of a scene would have eliminated the need for all of the programs. -Xathros

/r/n is Carriage Return, Line Feed (n = newline). It terminates the string. -Xathros

Anytime. Happy to help. Also quite interested in how these tags work out for you. -Xathros

It will just add to the headers section - i think it's position is predetermined by HTTP rules and the ISY will just put it where it needs to go. I've never had to move one once added. -Xathros

Have you added an authorization header to the rule? -Xathros

OK. That sounds doable. Is your hangup with the ISY submitting the request or Tag issuing the /REST? -Xathros

jonnynt- Have you seen what LeeG has found Re IOLinc queries and duplicate responses? The IOLinc is queried twice - once for the relay and once for the sensor. In some cases, the ISY reads a duplicate response from the first query as a reply to the second. It's a timing issue and may be related to insteon messages taking multiple routes back to the PLM (Powerline and RF via dualband devices). Yes, I know the IOLinc is not dualband but it is possible for messages that originate on the power line to be retransmitted and received via access points and other dual band devices. Not sure that this is any help - just a possible explanation for your issue. -Xathros

Gary- To me, ping implies a 2 way transaction requiring a response. At the moment, the ISY network module is xmit only. Do you have a method in mind for receiving a reply? -Xathros

Sorry, this is not an answer to the main problem - but - With your mvars, why not add: $myMvar initTo $myMvar after each place you change the value of $myMvar. This way, you will survive the power cycle without data loss. This is what I do with all trackers and critical values. On the main topic, your ISY should be rock solid. I would investigate the possibility of a bad power supply powering the ISY or problems with the AC line powering the ISY's supply. -Xathros

This directly follows a system startup. Have you looked for "Query at restart" under the system config: -Xathros

Hi Ferdies- Without having better documentation on the fireplace itself, it's hard to know all of the possibilities. That said, it looks like an IR remote control. You could use an IRLinkTX (2411T) to learn the remote functions then the ISY would be able to issue commands in place of the IR Remote. -Xathros

Try 50%. ISY will not send changes to a device if it believe the value would be unchanged. ISY probably thinks the SL is at 100% already. -Xathros