ISYhbsh01

I might also add that if the program has run at startup enabled it will also run whenever the ISY is rebooted, whether manually or due to a power failure. Sent from my SPH-D710 using Tapatalk 2

Hi, Just my 2 cents: You should set program 2 to run at startup. Otherwise, if you ever have a power outage or you reboot the ISY for whatever reason program 1 will remain disabled & program 2 will never run on it's own, thus you won't get any more emails. Sent from my SPH-D710 using Tapatalk 2

Michel, Have you checked out the 2441ZTH yet? Does it have the same issues as the 2441TH as reported here http://forum.universal-devices.com/viewtopic.php?f=27&t=8745&hilit=2441TH or is it going to work as expected? Thanks.

Those devices were just now released. I don't think the current 3.2.6 firmware supports them. Michel, Can you give an estimated ETA on if & when it will be supported? I am really looking forward to use them as a relatively non-expensive temp/humidity sensor in each room and setup programs to report back to my venstar tstats thats actually controlling the HVAC. Sent from my SPH-D710 using Tapatalk 2

I checked out the website & they now support sending emails using the API key as an email address. This means that you don't have to bother with setting up network resources for each notification, you can just use the standard send notification from the ISY. Sent from my SPH-D710 using Tapatalk 2

You are right, DON has to be upper case. But cmd must be lower case. Thanks.

Ok I got it! It seems that it's case sensitive! The Insteon address must be all upper case while the commands must be in lower case. Am I correct? Perhaps this is self understood ABC for a programmer, which I am not...

I am using the browser & I am getting a http 404 error.

Thanks Lee & Michel, I learned a couple of things already now from you that I didn’t know before: 1. That I have to use the Insteon address & not the name of the device. 2. That I don’t actually type the <> brackets… (Did I mention that I have no clue about programming?) 3. That I have to add the 1 (or 2 as applicable) at the end of the address. 4. That while the admin console shows the address of the appliancelinc as 15.4E.0B the rest/nodes page showed the address as 15 4E B without the 0. (Though I don’t know if it makes a difference) 5. That I CAN and should use spaces to type the address, even though normally you don’t have spaces in a URL. Still I couldn’t get it to work. I tried both of the following for the appliancelinc, using http & https, with a forward slash at the end & without, with spaces & without, nothing worked. https://myipaddress/rest/status/15 4E 0B 1/ https://myipaddress/rest/status/15 4E B 1/ Thank you

Hi Michel, I read the ISY-WS-SDK-Manual, however it is written for developers & rightfully assumes that the reader already has programming knowledge. I am far from being a programmer so I did not find there an answer to my specific question what to put in the . As I understand, the ISY can be controlled by sending it REST commands, which can be sent to the ISY simply by typing it into a web browser. That’s all I am trying to do here. Once I know how to do this I believe there are many things that can be done from there, Like integrating it with IFTTT.com’s DropBox channel which can send URL’s, and probably much more. So here is my question: I got the following to work: https://myipaddress/rest/status. That was simple. Now if I want to check the status of a specific device for example an ApplianceLinc named “Dehumidifier†with an Insteon address of 15.4E.0B, can you tell how I would do it? Here is where I get stuck: https://myipaddress/rest/status/ If in order to answer that question you will first need to give me a lesson or two in programming for dummies, then just let me know & I will sadly resign to my fate that this is not for me… Thank you

Sorry for my ignorance. Can someone enlighten me how to use REST commands? Specifically when using . What do I put there, do I use the device name or address? And do I have to put it in those brackets? I got it to work when using the simple command like this: http://ipaddress/rest/nodes. But I have no clue how to work with specific nodes. Again sorry for my ignorance. I searched for a bit more info on REST commands on the wiki & forum and didn't find very much info for someone like me. Thanks Sent from my SPH-D710 using Tapatalk 2

You might want to make a separate program for the else part. Sent from my SPH-D710 using Tapatalk 2

Thanks. Sent from my SPH-D710 using Tapatalk 2

You can change it to whatever port number you want but you will need to add the port number after the ip address if not using the 80/443 default. For example if you change it to port #999 you would do like this to log in: Your_IP_address:999 Sent from my SPH-D710 using Tapatalk 2

So basically that means that with a thermostat there is no difference between using "if control" or "if status" is on/off in a program. Sent from my SPH-D710 using Tapatalk 2

Hi az1324, Can this work only locally? I tried to use this on my office computer, and entered in the IP address box the dynamic DNS URL I use to connect remotely & it doesn't work.

Thanks Lee, however I am referring specifically to thermostats where the “If control†does not work the same way it does with all other Insteon devices in the way you described it. See the posts above. Thanks.

I get it. So is there really any difference between using status & control when the condition is "if on/off"? Thanks. Sent from my SPH-D710 using Tapatalk 2

Hi Chris, When someone changes the setpoint manually at the thermostat the ISY obviously detects it & shows the change immediately, so shouldn't it be possible for the ISY to use it in a program somehow? Thanks again.

Hi Michel, That's the way it is with all Insteon devices. However, with the thermostats, when selecting “if control†I only get the “is/is not†“on/off†choices, (Which is not something that can be directly done locally. The only thing one can do locally is changing the setpoint or change the mode, none of which is available when using “if controlâ€), I don't get a choice of any changes in the setpoint (Which is what someone can change locally at the device, no one can actually force cool on at the device), and when the a/c goes on because the temperature in the room is higher than the setpoint the program is triggered. The main thermostat node is not even in the drop down list when using “if controlâ€. As a test I tried again the following program: If Control '14.67.0A - Cool Control' is switched On Then Send Notification to 'isy99@' Else - No Actions - (To add one, press 'Action') I then lowered the setpoint using the admin console so that the a/c should go on, and sure enough I got a notification. Am I missing something?

Hi, It seems that unlike all other insteon devices, when using the "if control" condition with the Venstar thermostats it will be triggered even when the change is not done manually at the thermostat. Is there a way to make a program to get a notification whenever someone makes a change manually at the thermostat? Sent from my SPH-D710 using Tapatalk 2

The Venstar T1800 & T1900 both support humidity & dehumidifier control and are Insteon controllable so they would be natively supported by the ISY. For the T1800 you would need to buy an additional humidity module for about $30 while the T1900 has the humidity module built in.

Thanks.

Thanks Michel & all, I will setup a static IP from within the ISY. I do use manual port forwarding not the UPnP. On a side issue, does changing the default port numbers from 80/443 to something else make it more secure against outside attackers since they won't find anything at the normal web server http/https ports?

Hi Michel, I had a power outage that lasted for about a minute on Saturday, and after that the ISY was unreachable. Both the Mem & Err LED’s were blinking & the error log was full of -100 error messages which means that it was unable to get an IP address from the router thru DHCP. (BTW the error code -100 is not listed in the Wiki). Normally my ISY is assigned a static IP from the router. After rebooting the ISY it went back to normal. According to the post below in another thread this should not have happened as of release 2.8.16 and above. http://forum.universal-devices.com/viewtopic.php?p=62802#p62802 Any thoughts on why this happened? And should I rather assign a static IP address in the ISY outside of the router’s DHCP range to avoid this problem In the future? Or is there something else wrong here & this should NEVER occur with 2.8.16 and above? By the way Michel, this is the first time I had any issues since you logged into my ISY & fixed my problems. Thanks.