Scottmichaelj

I made sure all the devices were deleted. I still get the error the skill is not enabled in the portal though when choosing Amazon Echo in the drop down. Is that normal? I did add my office lights for a quick test, it worked and I am able to have to set to specific brightness levels which is really nice, which was not available on the emulator.

So this morning I woke up and read your comment. I went back to the "beta" link and clicked it. I got the result that "Amazon Echo is now connected to your ISY" and then went back into the app and wa-la it showed the ISY in the connected home section. FINALLY! Not sure since it was there before via the beta why it disappeared and I had to click the weblink again. Whatever, time to play. Thanks everyone for the help and suggestions.

Argh The HUE emulator seemed less work than this "easier" way. I deleted everything and still only Insteon, Wink and SmartThings are shown in the connected home amazon app. You have anything under the "Requested Services" on the ISY Admin Portal page?

Yeah I am about to give up. I unlinked my account from Amazon via the portal, I made sure the skill was disabled in the app, then back in the portal it shows connected to my ISY and green. When I go back in and link my account it shows its linked to Amazon, but then when I go into the Amazon app I still don't see the connected home available. When selecting "Amazon Echo" in the portal I get an error "The ISY skill is not linked to your portal user profile. Please go to your echo app, enable the ISY skill, and link the skill with this user profile." however if I hit ok I can see my scenes and devices in the drop down lists. I added one device but nada. Tried unlinking and linking again, nada.

I dono it was strange that mine wouldnt connect until I switched the IP then it found the ISY. I changed it back to the original IP and it was fine. Did you look in the error log and see if anything shows up? My issue now is my connected home is not showing up even though I signed up before the beta. So I guess I have to wait until Amazon puts it back in the app.

Ruh roh kinda sounds like my issue. Change the IP and see if that fixes it. If so you can change back. That fixed my portal issue. Also check your settings to make sure you have HTTPS client settings set to TLS 1.2 and Strength of All. Also make sure you don't have any port forwarding rules to ISY and specifically port 8001. http://wiki.universal-devices.com/index.php?title=Main_Page#Network_Security

Yup I made that mistake before too. [emoji16]

Your double posting. I already responded to your same question here: Automatically turn off lights after no motion http://forum.universal-devices.com/index.php?/topic/17978-Automatically-turn-off-lights-after-no-motion

I changed my ISY from DHCP back to original static IP and the portal can connect to it. So as I suspect there is something that causes the portal not to see the ISY until the IP changes or refreshes.

I got my tags last week and I am working on a small project with them and my remote control system at the moment. Once that is complete then I will do a real world analysis of them. I do know I am not the only one with these, Larry uses them too and then there is this thread: http://forum.universal-devices.com/topic/17232-wireless-sensor-tags/?hl=%2Bwireless+%2Btags

When I have time I am going to change my ISY back to the original Static IP address to test. Not sure why I had to move from Static to DHCP to make it work. I honestly did NOTHING ELSE but change from static to DHCP and it worked. Thats why I think there is some type of weird bug here. I signed up for the "Connected Home" beta with Amazon a while back and as of yesterday it disappeared from my Amazon App. I saw Michel said the Beta was closed and its now fully open to everyone and "in the queue", so I assume thats why its gone and it will be added back soon.

If you want something simpler you could look into the Wireless Tags by CAO here -> http://wirelesstag.net Toss a small tile in the fridge and freezer and then using the API send yourself a notification when it hits the set point you want. It will also data log for you. Just another idea.

Duh, went over my head! Good one! Cleaver.

Lol what!? A digestive disease? Now I could get behind something like stupidity but not ingestion. It is interesting that people have this issue. I had everything setup correctly obviously, so just switching from static to dhcp fixed it? Why? Would changing the static IP to something different fix it to? I suspect some type of bug there.

Did exactly as you suggested and I stated in my post above and your absolutely correct this worked for me as well. Thanks for the help!

So if I understand you right, you deleted the port forwarding and changed the ISY IP from static to DHCP? Once that was done assume your rebooted the router the powered back the ISY which obtained a dhcp ip then you added that to your reserve list and then added new port forwarding rule to it so you could use mobilinc? Is that correct?

I have been going through trying to setup my amazon echo to the protal without any luck. After having such a bad last week I really shouldnt be messing with this but I guess I am a gluten for punishment. I setup my account on my.isy.io and entered my ISY UDID. On the ISY side I selected Manage Modules and can see the Portal tab. Under the portal tab it shows the portal offline with a red flag but registered. When on the portal website the ISY is not found. I made sure I can access the ISY from outside my network via the IP and the port, which I can but I get the security warning. In my router I have the port being forwarded to the ISY internal IP address. I have all router firewalls turned off temporarily along with my windows firewalls. I went into the network security http://isy.universal-devices.com/994i/dashboard.jnlp and set my HTTPS Client Settings to Protocol TLS 1.0 Strength ALL and Verify Checked. For HTTPS Server Settings I have protocol on TLS 1.2 Strength Low and Verify is not checked. I do not have anything in CA, Server or Client Certificates. All my network settings and ports are right and I even have port forwarding setup in my router (I also tried to delete it as well). But for whatever reason I can not get the portal to see my ISY. Anyone have any ideas? Do I need a SSL cert? EDIT I am using v4.3.26 firmware and the UI and Firmware match. Here is some of my ISY Error log: Sun 2016/01/24 02:58:13 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 02:58:43 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 02:59:13 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 02:59:43 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:00:13 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:00:43 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:01:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:01:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:02:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:02:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:03:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:03:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:04:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:04:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:05:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:05:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:06:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:06:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:07:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:07:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:08:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:08:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:09:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:09:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:10:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:10:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:11:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:11:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:12:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:12:27 PM System -170001 [TCP-Conn] -1/-140002, Portal-SECR Sun 2016/01/24 03:12:27 PM System -170001 [TCP-Conn] -1/-140002, Portal-SECA

There has been a lot of questions asked about Honeywell Thermostats and their ability to be controlled via the ISY, so I thought I would take some time to help clear up some questions. To be clear as of this post Honeywell has not released any of the APIs for local control. Many people including myself, have tried tirelessly to get Honeywell even to respond to our emails and phone calls, to no avail. The only solution for now is to use IFTTT via the Honeywell Total Comfort Connect channel. Unfortunately I do not have a list of actual model numbers of thermostats this affects however I do know IFTTT will work with all "Redlink" thermostats, which includes Prestige IAQ, Prestige 2.0, WiFi 9000, RTH9580WF WiFi, VisionPro, VisionPro WiFi, RTH8580WF WiFi, FocusPro WiFi, and the RTH6580WF WiFi. There is a separate Honeywell portal for the Honeywell Lyric which may have APIs released for it later. The Honeywell Lyric looks like it will be another channel in IFTTT. IFTTT also provides access for Honeywell Single Zone Thermostats and the Honeywell evoHome, both separately from the thermostats I have listed. A good rule of thumb is, if your thermostat can be controlled via the My Total Connect webpage or has Redlink you can use IFTTT. Now I would like to address some of the Pros and Cons of using the Honeywell IFTTT channel to control your thermostat since you cannot directly control it with the ISY. Pros: -You can control your thermostat using Amazon Echo and IFTTT -There is total control of setting the heat and cool points for your thermostats -You can control multiple thermostats in your system - upstairs, downstairs, basement, etc -The response time for changes are quick, usually within a minute Cons: -Limited Control. There are only 4 options, "Set temperature to permanent hold", "Set temperature for a period of time", "Resume Program Schedule" and "Set fan on or auto" -You cannot TURN ON or OFF your system. Yes you read that right! The system MUST BE ON before you can control your heat/cool temperature. You also cannot turn your system from Heat to Cool or vise versa. So no going from Heat at 74 to AC to 68. -No local APIs have been released, so all control is via the Honeywell TCC web portal or via IFTTT If I get feedback I will add a list of specific thermostats models for others to this post so it's on the first post for people to find. I welcome all feedback and any additional information. The more info we have the better. I hope this helps clear things up a bit on the Honeywell side. I know IO_GUY has recently teased a screenshot of the ISY and Honeywell data. What I know right now is this integration will be purely a web scrape, and not a 100% solution. It may change at anytime based on if Honeywell makes changes to the site which may break it permanently. I don't even know if IO_GUY will be able to release it so while its fantastic he is working on it I wouldn't consider this a solution over a local API based thermostat over the Venter T7900 or the like. IO_GUY has a great program that works with local APIs for Venstar. So if you live in an area where maybe you rely on the thermostat for making sure your pipes don't freeze I would not suggest using anything that a web scrape or a cloud based thermostats like NEST either as those have negatives as well. There is also the Vera Edge controller with a Honeywell Thermostat plugin available. Please be aware this too uses the Honeywell TCC website and scrapes the data. So again my previous warnings apply. UPDATE 01/23/16: Honeywell TCC was just added to NodeLink. It requires ISY V5 firmware and currently just sends the data to the ISY, control from the ISY will come in a later release. http://forum.universal-devices.com/topic/17228-nodelink-latest-version-v031/ Resources: Compatible thermostats and their details can be found via pdf here: http://www.forwardthinking.honeywell.com/related_links/thermostats/03-00005.pdf IFTTT Honeywell Total Comfort Connect Channel Screenshot Update 01/26/16: Today the Honeywell Total Connect iPhone app was updated. See screenshot for details.

Perfect. You are 100% correct - I have three water leak detectors left to add back but for now I just "disabled" them in the ISY because they are a PITA to get to and not a high priority. With my luck this week one of those three will leak and well...lets hope not. I just dont have it in me today to take off covers and climb into the attic. Everything is back up and seems to be working well. Thanks for everyones help. Not sure if v5 was the issue or the one device that I had to airgap. I added it back ok and did a few queries and it looks fine. Getting 3 hops left each time etc so not sure what its problem was there. Again I dont have the energy to worry about it right now. Hope everyone has a great weekend and thanks again for the help.

Thanks this is better since I they seem to timeout doing the full store device. Will do, thanks for the reminder. I disabled the hard to reach locations so hopefully that helps "bypass" the other devices from trying to link to them. I dono if thats the case or not. I been able to add my four water leak sensors back and both motions. Still working on the hidden door sensors and going to see if I have energy left to climb into the attic and remove the plates of the fridge and dishwasher to add those back. They are not high priority and based on my last crappy week I wanted to just relax as much as possible this weekend.

So just "writing the update" is ok or do I have to do the "restore device"? I thought it was restore device since the PLM is new. Sorry if I am being a PITA.

So there are three battery leak sensors in VERY difficult places to get to. Can I skip them and do the rest of do I HAVE to put them in the group?

Yup your right already back up and running. Now for all my water leak detectors, motions etc, Can I add them individually or do I have to run around and put them all in linking mode? I just tried to put two in linking mode and by the time the ISY got to them it timed out because it cant communicated with the other battery devices (which I didnt put into linking mode). So do I have to gather all of them up and put them on a table, put them in linking mode then put them back when done? I thought if I did this then the links/hops would not be correct for the devices once I moved them and could cause communication issues for them. Am I right or wrong?

No it was you post 16 - pulling the airgap didnt cause the issue I think the issue was the device and airgapping it helped the ISY not get stuck in the loop restoring it. It was a good call I didnt even notice it. Got mesmerized by the scrolling screen and was more interested in the hops than device. Oh look something shiny...

So FINALLY I am getting somewhere! Lol I did the reset and then unplugged the ISY - started things back up and upon logging in its now appears to be restoring the PLM. My switches are beeping and I can see the status for each change in the admin console. Not sure why it was stuck but I kept the device Jon mentioned airgapped, maybe thats a bad device and was causing it to loop on the restore?