Bumbershoot

I have a hub set up in a relatives 2nd home, and it works just fine for that simple setup; they just want some lighting and HVAC control when they're not there, which the hub provides. It's basic, easy and it works, and all the setup/control can be done with the Insteon app on a mobile device. The hub has plenty of limitations, but if you're only looking for simple scheduling, and on/off and level control of devices, and on/off control of scenes, the hub should work. It works with Alexa and Google Assistant, though I can't speak to how well it works in that environment. It should be maintainable without relying too much on specialized knowledge, which I believe is the sole benefit of choosing it over the ISY.

Good find, I forgot about raspi-config. I assume that the time values that NodeLink provides to your ISY Data nodes are correct, and that you're off to the races...

Not normal. I think that NodeLink gets the time from the RPi, which should be set up to use NTP (Network Time Protocol, I believe) to set the time. You might be seeing time for the default location, which is Greenwich Mean Time, which is equal to the time in London, instead of your location. Run the 'date' command from the command line (it should look something like this): pi@raspberrypi:~ $ date Tue Jan 22 22:09:52 PST 2019 This tells me that I'm in Pacific Standard Time. If yours doesn't show EST, then you don't have the RPi configured correctly. I think this command will work to change the timezone for south Florida: sudo cp /usr/share/zoneinfo/America/New_York /etc/localtime You should see the time update correctly with the next time update in an hour or so. I think...

BTW, this did not produce the correct result. The reason for that is that you failed to capitalize the "L" in NodeLink, so the command only returned the process number for the command you just ran. FYI, case in Linux is IMPORTANT! An upper case "L" and a lower case "l" are completely different animals. It should look something like this: pi@raspberrypi:~ $ ps aux | grep NodeLink pi 8346 0.0 0.0 4376 572 pts/0 S+ 17:15 0:00 grep --color=auto NodeLink pi 32043 1.5 5.3 101436 50152 ? Ssl 03:43 12:50 /usr/bin/mono /home/pi/Nodelink/NodeLink.exe Anyway, glad you got it going. Cheers! ?

Don't thank me, thank io_guy, and maybe buy him a beer (link at the bottom). Your ISY is getting awesome!

Almost there! Have a look here.

Okay, the ISY address field needs to have the IP address of your ISY in it: 192.168.x.x The ISY username and password are what you use to log into the AC.

Yes, definately that ^^^^^

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.