Bumbershoot

Okay, something might have not gone correctly with the script. If you can log back on to your RPi, and type the following command at the prompt to see if NodeLink is running: You should get output that looks like the following: pi@raspberrypi:~ $ ps aux | grep NodeLink pi 4693 0.0 0.0 4376 544 pts/0 S+ 14:52 0:00 grep --color=auto NodeLink pi 32043 1.5 5.7 101436 54348 ? Ssl 03:43 10:36 /usr/bin/mono /home/pi/Nodelink/NodeLink.exe The last line is the important one, that's what tells you that NodeLink has a process number and is indeed running.

That probably means that Nodelink isn't running on your RPi (possibly it never started). I don't know how the install script sets up Nodelink, but there's a good chance that it starts on boot. It might be easiest if you reboot your RPi. Do you know if Polyglot is set to start on boot? EDIT: I see in the very first post that Nodelink should start upon boot: "It updates the Pi, installs mono, downloads NodeLink and sets up the startup script."

Here's a short list of the changes I can think of: Nodeservers -- your ISY now can interact with a great many new devices natively (see Polyglot and Nodelink sections to this forum) Z-Wave multichannel devices -- much greater functionality with a much greater variety of devices Insteon Siren and Motion Sensor II compatibility Variable precision variables Ability to assign numeric device values to variables and vice versa Enhanced "adjust scene" functionality Other programming enhancements that I'm forgetting Version 5.x.x is the way to go!

Well, almost. You're already logged in to the terminal. What is being referred to is for you to login to Nodelink through your web browser. For Nodelink, I would point my web browser to: http://192.168.1.5:8090 For Polyglot: http://192.168.1.5:3000 Same machine, just different port numbers... Once you're logged into Nodelink with your browser, you can begin setting up your devices that Nodelink will talk to.

Port 3000 is unusual. That's the port that Polyglot uses. Maybe just leave the "Port" value blank and let it use the default, or specify port 22. That's probably the port that your RPi is listening to for SSH connections.

If you log onto your RPi from another computer using the 'ssh' command, then you're already at the terminal once you're logged in. If you have your RPi hooked up to a monitor, keyboard and mouse, and you're looking at a GUI when you log in, then you should be able to find the program named "terminal" somewhere on the box. Just run it, and you'll be presented with a command prompt in a terminal window. Alternatively, you might be able to switch to a command line terminal (full screen) by pressing and holding the ALT+CTRL+F2 (or substitute the F2 with F3 through F5) keys. Switch back to the GUI with ALT+CTRL+F1. I've been running Polyglot, Nodelike and Weatherflow node servers on my RPi for many months with no issues at all.

Same date as mine -- probably bought it at the holiday sale? I did.

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.