Bumbershoot

You can use IFTTT with either the UDI portal or the MobiLinc portal. IFTTT isn't the issue. It's simply that the ISY cannot simultaneously connect to both the MobiLinc portal and the UDI portal. You'll need to choose a portal service. Either portal appears to be very full featured, very well supported, and I doubt you'll go wrong with either. Looking forward, the UDI portal should support some cloud based nodeservers in the near future, if those are of interest to you. I don't know what plans are forthcoming for the MobiLinc portal. IMHO, we have something akin to an embarrassment of riches in the portal department... Very nice choices. I use MobiLinc and Agave (on my iOS devices) connecting to the UDI portal and they work just fine. I also use IFTTT from the UDI portal to make some things happen in my ISY. I believe the same can be said for the MobiLinc portal. To explicitly answer your question, you can indeed use IFTTT and a remote mobile connection to your ISY -- through a portal service. I my case, I connect with MobiLinc or Agave to the UDI portal when I want to use my iPhone to interact with my ISY. I do not open a hole in my firewall to connect my mobile device to my ISY, or create a VPN tunnel. My interactions with IFTTT occur at the UDI portal. I think you can do precisely the same thing using the MobiLinc portal, maybe even more -- I don't know as I haven't used it. You just need to pick a portal, and that might take a bit more research on your part. I can't/won't recommend one over the other.

The ISY can only connect to one portal at a time, either the MobiLinc portal or the UDI portal. One or the other. Unless I'm misreading, it appears that your ISY is actually connected to the MobiLinc portal, not the UDI portal, which is likely the cause of the issue.

Okay, good. You might post a question in the Polyglot forum. The developers might have a idea as to what's going on. You probably want to post a snippet of the logs where the error appears, as well.

I can't think of anything that would bork a restore of the ISY in that fashion, unless, possibly the ISY firmware version and the AC version you're using are different. Please check. I'd forget about Polyglot for the time being, shutting it off until I had a good restore of my ISY, and my ISY was running properly. One step at a time...

I don't know. If you have any extended ASCII characters in your ISY username or password, you might be hung up with the browser decoding them incorrectly. Otherwise, I'd post this issue in the Polyglot forum and see if any of the developers has an idea. Hurray! Good luck!

Just a thought: you're using the correct IP address for the ISY? You also might review the contents of the Polyglot log file to see if there's any indication of what the problem is.

It's possible that Polyglot would respawn after it's killed, but it's not likely. My suspicion is that you're doing something wrong. First of all, did you try to stop or delete the Blue Iris nodeserver from the Polyglot Dashboard? That's your first move, and it might be all that you need to do to solve the immediate problem (after restarting Poylglot, of course, but you can do that from the Polyglot web page as well). https://<your.polyglot.ip.here>:3000/dashboard This should be all you need to do. _~_~_~_~_~_~ For information only below - should not be necessary and use at your own risk _~_~_~_~_~_~_~ If you've tried that and for some reason it doesn't work, and the 'kill' options also don't work, you might read on below. Again, I don't know anything about how you installed Polyglot, so I'm guessing. I'm fairly confident that: sudo apt-get remove polyglot-v2 won't do anything, as Polyglot isn't in the software repositories that 'apt' looks at. I don't know if Polyglot will start again or not, which again depends on how you installed it (and if you've managed to achieve that, then you likely know how to do everything below). I'm very much hoping that you did NOT install Polyglot as user 'root', or using root permissions, in which case nothing below will work as written. Are you deleting the hidden Polyglot directory where the nodeservers, and their configurations actually reside? Normally, the node servers install themselves into a hidden directory. From the home directory of the user account that you installed Polyglot under (on my machine, it's user 'pi' in the '/home/pi' directory), issue the command: ls -altF You should see something like below, with a directory called '.polylgot/' -- the period before the name is important, that's what makes it, and it's child sub-directories and files, hidden. pi@raspberrypi:~ $ ls -altF total 240 drwxr-xr-x 31 pi pi 4096 Nov 3 05:10 ./ -rw------- 1 pi pi 33401 Nov 3 05:10 .bash_history -rw------- 1 pi pi 3953 Oct 1 12:25 .xsession-errors -rw------- 1 pi pi 56 Oct 1 12:25 .Xauthority drwxr-xr-x 2 pi pi 4096 Sep 8 03:43 Nodelink/ drwxr-xr-x 2 pi pi 4096 Aug 28 22:42 WeatherFlow/ -rw------- 1 pi pi 3953 Aug 24 06:28 .xsession-errors.old -rw-r--r-- 1 pi pi 66 Aug 14 06:19 .selected_editor drwxr-xr-x 5 pi pi 4096 Jul 20 05:51 .polyglot/ <-- this is the hidden sub-directory --> drwxr-xr-x 3 pi pi 4096 Jul 18 16:25 oldconffiles/ drwxr-xr-x 2 pi pi 4096 Jul 17 05:42 polyglot/ Issue this command: cd .polyglot then 'ls -altF' again, and you should see something like this: pi@raspberrypi:~/.polyglot $ ls -altF total 28 drwxr-xr-x 2 pi pi 4096 Nov 3 06:25 log/ drwxr-xr-x 31 pi pi 4096 Nov 3 05:10 ../ drwxr-xr-x 7 pi pi 4096 Sep 16 14:21 nodeservers/ drwxr-xr-x 5 pi pi 4096 Jul 20 05:51 ./ drwxr-xr-x 3 pi pi 4096 Jan 1 2018 ssl/ -rw-r--r-- 1 pi pi 21 Dec 22 2017 .env_not_used -rw------- 1 pi pi 191 Dec 22 2017 .nest_auth Issue this: cd nodeservers and you'll see something like this (and importantly, the files are owned by user 'pi' not user 'root' if you installed Polyglot correctly): pi@raspberrypi:~/.polyglot/nodeservers $ ls -altF total 28 drwxr-xr-x 8 pi pi 4096 Oct 29 05:47 Camera/ drwxr-xr-x 6 pi pi 4096 Oct 8 15:30 Nest2/ drwxr-xr-x 7 pi pi 4096 Sep 16 14:21 ./ drwxr-xr-x 5 pi pi 4096 Aug 28 22:34 LiFX/ drwxr-xr-x 7 pi pi 4096 Jul 27 06:21 WirelessTag/ drwxr-xr-x 5 pi pi 4096 Jul 20 05:51 ../ drwxr-xr-x 5 pi pi 4096 Jul 20 05:15 Sonos/ From here, navigate to the directory containing the Blue Iris nodeserver, and making certain that you're actually in the correct sub-directory by issuing the command: pwd once you get there. You should see something similar to this: pi@raspberrypi:~/.polyglot/nodeservers/Nest2 $ pwd /home/pi/.polyglot/nodeservers/Nest2 If you're certain that you're in the correct sub-directory, then you can delete the files in that directory by issuing this command (but be careful you DO NOT 'sudo' this command, as it's the destroyer of worlds if you're in the wrong place...? rm -rf * This should wipe out all the files in the particular sub-directory your in, which ought to take care of the offending nodeserver. Restart Polyglot and you should have control of you ISY back, if indeed this is the problem. Good luck!

I have no idea how you installed Polyglot, but you could log into your RPi and run this: sudo systemctl stop polyglot-v2 or, if that does nothing, you might try this: sudo killall -9 polyglot/polyglot-v2-linux-armv7 If that doesn't work, then you can grep the process ID of your polyglot instance: ps aux | grep polyglot-v2 That'll return a process number that you can then kill. It should look something like this: pi@raspberrypi:~ $ ps aux | grep polyglot-v2 pi 4710 2.5 10.1 193452 96428 ? Ssl 06:25 12:23 /home/pi/polyglot/polyglot-v2-linux-armv7 pi 8445 0.0 0.0 4376 564 pts/0 S+ 14:27 0:00 grep --color=auto polyglot-v2 Process ID 4710 is the process on my box, so if I wanted to kill this by ID #, I would use this syntax: sudo kill -9 4710 The -9 flag clobbers the process, so you won't have a clean shutdown, but I don't think it matters.

Me too, along with the WeatherFlow node server, which invokes another instance of Mono. No problems

Have a look here. I use a Mac and it works perfectly.

That is certainly possible. The only hitch might be that the smart bulbs don't remember their brightness/hue values across power cycles, and it might take them a few seconds to a few minutes reconnect with their controller and change to the desired levels. The smart bulbs that I'm familiar with (Insteon, LiFX and Hue) all return to their previous brightness/hue values with power is cycled, so those should work. Hue, Z-Wave, LiFX, Insteon, etc., all use different wireless technologies, so put some thought into how close your porch is to your controller, or how robust your mesh/wi-fi coverage is in that area.

Yes they do, but only with the 3rd generation or E series thermostats.

I'll take a whack at this: The best way I know of to use a Nest thermostat with the ISY, you have to run the Nest2 polyglot node server, which makes the Nest a fully functional member of the ISY universe. MobiLinc is more problematic, as the current version of MobiLinc doesn't support node servers. I believe Wes has indicated that he's embarking on a MobiLinc rewrite that will at least include some support for Polyglot node servers, but beyond that I have no information. In the attached screenshot, you can see what the Nest thermostat looks like in MobiLinc, but none of the states or values are actionable. No worries for me, as most of the things I wish to change are changed automatically using ISY programs. For the rare time I want to use an app to change something on my Nest, I simply use the very acceptable Nest app (iOS, in my case) to make the change. The second screen shot displays how the thermostat appears in the AC. EDIT: Additionally, it's very simple to install the Nest skill into Alexa and control the thermostat by voice.

In the "Configuration | System" tab, I set the value for my "Http Port" as 80 (it might default to this, I don't recall). See screenshot. I use the ISY Launcher to select http, as described in this thread.

Wow! I just did a test on my 4GHz i7 4 core iMac, and got these load/startup times (over local 5GHz wireless): http - Admin Console - 15 seconds http - Program tab - 20 seconds https - Admin Console - 90 seconds https - Program tab - 30 seconds Interestingly, the last step in loading the Admin Console ("Refreshing Status") just takes a couple of seconds over http. I haven't added any Insteon or Z-Wave devices in quite a while. All my newer devices have been handled by either the Polyglot, Nodelink or WeatherFlow node servers. I don't know if that reduces the startup load on the ISY or not. I'm running the 5.0.13D firmware.

I haven't seen this mentioned here, but I'm using Notify Me (an Echo skill) to enunciate the status of various items in my HA setup. I use it to announce when various household members cross a geofence, when a program starts supplemental irrigation on hot days, to enunciate the status of my security system when I issue Alexa the "goodnight" command; basically to vocalize things we're interested in. This relieves me from having to look at something -- a phone, a light, smartwatch, etc. -- to know the status of things.

Not that I'm aware of, but admittedly, I'm still on my original PLM from 2015 so I've never swapped mine out. I understand that you might not want to issue a "Delete PLM" command, as you'll get a new PLM with no links at all when you eventually do the "Restore PLM".

Have a look here.

If you're trying to update to the latest released software for your ISY, you might have a look here. The "Enable Internet Access" menu item is irrelevant to that process.

From the Wiki: Enable/Disable Internet Access In order to achieve remote/internet access, you will need to setup your router for port forwarding. Port forwarding allows the ISY’s port to be seen over the internet. The controller default setting is with internet access disabled. If you would like to enable internet access to the controller select this option. It is reversible and you will be presented with the Disable Internet Access menu option. For a list of supported routers, please see the Supported Remote Access Routers page. If you do not have one of the routers listed above, please contact us and we’ll walk you through setting up your router (port forwarding) manually. Unless you're port forwarding, you shouldn't need to enable this (and I'm pretty sure it's not recommended). You ISY can get out to the Internet (evidenced by your ISY's ability to use your local network to sync the clock) but the Internet can't get in to your ISY.

I concur -- I've got two Polyglot nodeservers involved (Nest2 and LiFX, with the ISY acting as the intermediary), and I get notifications (a couple of lights change colors) within a second or two of "Person" detection as well. That happens prior to getting notification on my Apple Watch. I'm pleased with the performance of these nodeservers.

Mine flip between plausible and implausible values seemingly randomly (meaning I haven't discerned a pattern). I can't rely on that value at this point, so I'm sticking to my CAO Wireless Tags for temperature/humidity. I don't really need great precision, but I need a device that will wake up when it's queried (without an external event) and provide a relatively good value.

Hi Bruce, It looks to me like you're on the right track When/if you're comfortable, you might think about deploying a Polyglot server for your Hue and MagicHome lights (along with a number of other technologies). Polyglot is looming large in the ISY's future as a tool to integrate disparate technologies under the control of the ISY. Polyglot requires beta ISY firmware currently, but it looks to be an important part of the next stable firmware release. The reason I mention this is that running Polyglot may be easier than creating the necessary network resources required to have your ISY control your Hue and MagicHome lights (though Alexa skills may allow you to navigate around the ISY for this). Good luck!

I only have these things powered by battery, so they might act differently under USB power. The only way I've managed to get the "CLITEMP" and "LUMIN" values to change for these devices is to programmatically query the device upon a motion status change (the "DON" event in the ISY event viewer, I believe). Then it seems to work (and you can see the values arriving in the ISY event viewer). MS Master Bath Query - [ID 0101][Parent 0004] If 'Master Bath.1 Motion' is switched On Then Set 'Master Bath.1 Motion' Query Else - No Actions - (To add one, press 'Action') Getting the temperature calibrated properly is a bit of black magic that I haven't mastered, but this seems to update the "CLITEMP" and "LUMIN" values for me. Issuing a query without an a corresponding "DON" event doesn't seem to produce anything on battery power, as I assume the device is asleep. EDIT: I forgot to add that the "CLITEMP" values returned are occasionally way out of bounds. I've gotten values such as 139.9°F for my master bathroom. ?

I have mine running off of battery power. I haven't watched the temperature value change, but it seems to. I suspect it only sends an update to the AC when they're activated by motion, though I don't actually know. If I find some time I'll write a program to notify me of status changes as well as temperature changes. If I do that, I'll report back here. I'd think if you wanted to use them for more-or-less real-time updates, you'd have to run them off of USB power. Hopefully, they'd act like the Aeotec Multisensors that I have on USB power in my garage.