Bumbershoot

I just looked at one of my new Switchlincs, and the date value is 4118, which I believe means the 41st week of 2018. I'll be yours (0713) is the 7th week of 2013.

You're doing it properly. This is an improvement, as you're UI and firmware versions will always stay in sync.

For information, here is the file size of the downloaded 5.0.14 firmware zip file on my Mac: 6,544,325 bytes Don't unzip the file prior to installing it, or you'll get that same error. Otherwise, a search of the forums for this: "Upgrade Failed :Failed uploading file (reported written size is invalid)" generally seems to indicate that you may have some sort of firewall/AV/network issue. Others before you who have gotten this error submitted a support ticket, and that may be a good option here: support@universal-devices.com

Try to change the setting in your ISY Configuration | System tab, as per the screenshot.

You also might consider putting a two or three second wait between each notification.

A test of the Kidde alarms don't; those tests just activate as normal alarms, meaning that the smoke bridge "Status" value switches to "On". ISY programs that are looking at the smoke bridge "Status" value will run as intended during a test of the Kidde alarms. I don't recall if the the First Alert sensor sends an actual test value or not -- it's been a while since I installed this. If I have a chance, I'll see if I can test for this, but don't hold your breath for it (family in the house for a while...)

No, low battery alarms are not. A press of the "Test" button on any of the alarms propagates through to the ISY, as does an actual alarm, but nothing else.

I'm sorry, but I can't help you with that question. My Kidde alarms are smoke only, and my CO alarms are separate. That's something I'll fix eventually, likely by integrate both alarms into my Elk system, but for now, this works well for the smoke alarms.

In reading the comments on this forum, I'd be in agreement with you on this if it wasn't for the very good luck I've had with my Nest thermostat and the Nest2 Polyglot nodeserver. This combo has been rock solid for me for quite a while now. I'm sure there are many faults people can find with this setup (the cloud based API for one), but I haven't otherwise had any issues with the functionality. Due to the cloud based API, I only have my ISY manipulate the Nest for exceptions to normal HVAC activities (such as stopping the cooling when doors/windows are left open, that sort of thing). Normal operations are handled by the Nest, not the ISY, and it's working very reliably. BTW, thanks to @xKing for the nodeserver! I'm curious about the UDI portal based Nest nodeserver that's currently in development, as it'll remove one mode of failure (RPi) from the equation.

Amazon has Insteon on sale today as well, FWIW.

Have a look/listen here. https://www.thedigitalmediazone.com/2018/10/18/whats-going-on-with-insteon/

You could always create a program to turn the lights on and off at specific times, then put it into a folder and set the properties of that folder to enable the programs within to only run between certain dates. Test Programs - [ID 00A7][Parent 0001] Folder Conditions for 'Test Programs' If From 5:30:00PM on 2018/04/01 To 5:30:00PM on 2018/09/30 Then Allow the programs in this folder to run. I actually don't know if this is available in the 4.x.x series firmware, but it's pretty foolproof if it is.

I guess that depends. Scenes are awfully useful, and fast. On the other hand, ISY programs consume no links in your PLM. If you're pushing the limits on your PLM, then use a program. I use scenes when I want things to happen immediately. When I don't care so much, I use a program.

I'd insert a 2 second wait between turning each device on. This ensures that there won't be any communication collisions and the ISY rapidly tries to turn on multiple devices. I do this every evening as I turn down the sentinel LEDs for a bunch SwitchLinc Dimmers, and the reverse in the morning. I never seem to have trouble with them. Or, you could just put all these devices into a scene, and turn the scene on.

Nope, it's written in Java, so it's portable across operating systems. There are no OS specific AC binaries.

I'm not entirely certain what the UDI portal costs, but I believe it was $49.00 for the first two years, and $12.00 a year to renew. Check with sales@universal-devices.com. I know there's a boat load of functionality included, as it includes/replaces the networking module in the ISY. For me, it's very well worth it. IFTTT/Alexa/Google Home connectivity is included, and MobiLinc works just fine with it.

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