Bumbershoot

I'm not exactly sure what you're asking, but this program turns on my external lights 30 minutes prior to sunset, and shuts them off 5 minutes prior to sunrise the next day. ExternalLightingOn - [ID 0002][Parent 000A] If From Sunset - 30 minutes To Sunrise - 5 minutes (next day) Then Set 'Scenes / scnExternalLights' On Else Set 'Scenes / scnExternalLights' Off Turns house external lighting on 30 minutes prior to sunset every day. Lights go off at sunrise.

Sorry, I have a different system alarm system, so you might have better luck asking the same question on the NodeLink forum.

This will need a Raspberry PI and NodeLink, and you have to be running the 5.x.x series of firmware on your ISY.

I believe so. It's like a cloud backup/restore of the Insteon hub.

Who knows if UDI has the time/resources to manage something like this. IMHO there's probably not much point in creating videos until the 5.x.x firmware series reaches a production release (the 4.x.x series must be nearing EOL, so no point in spending time there), and the AC has been rewritten in HTML5. Otherwise, there might be a short shelf life for the videos. There are some very nice Polyglot setup videos available here.

There is a requirement that you upgrade your ISY firmware to the the current BETA to use this module. It won't work on the 4.x.x series firmware.

It is now, and it's located at: https://polyglot.isy.io/ It's limited to devices that have cloud based APIs: https://polyglot.isy.io/store Devices currently available are: Nest thermostats, Ecobee thermostats, Honeywell Total Connect thermostats, Ambient weather stations, WeatherFlow weather stations (there are also two WeatherFlow nodeservers that can be entirely local) and Solar Edge solar panels. It requires and active UDI Portal account, I believe. There are several other good candidates for inclusion to Polyglot cloud, notably CAO Wireless Tags, among others. For folks who don't want to maintain another CPU and have devices with cloud based APIs, this should be perfect.

Terrific, that sounds like a significant feature. If this were a horse race, I'd bet that we're in for another lap around the Beta track. @Blackbird, there you go. It very much sounds to me that UDI considers 5.0.14 to be stable, though not entirely feature complete (if you're not investing in Z-Wave, however, it may well be). Also, I don't see any promises made here that the migration process will be made entirely automatic or painless (given the endless configurability of the environments that the ISY can control, is it even reasonable to expect that?) I certainly didn't find the migration to be onerous. YMMV.

At this point, it seems the the 5.x.x series of firmware is essentially feature complete and stable, as it has been over a few iterations now (which in my mind is what a Beta should be). There are still migration issues that seem to need a bit of work (mostly to do with program conversion), as well as idiosyncrasies with devices that need working through. For me (and to be fair, I'm not terribly risk averse -- I always maintain a current backup of my ISY) the multiple benefits of nodeservers made the pain and frustration of migration worthwhile. They have changed the game for the ISY, and multi-channel Z-Wave devices haven't hurt any, either. If you decide you don't like pain/cost of the upgrade, restore your old firmware and backup. The only thing lost is some time/hair follicles. If you decide to upgrade, you may have some migration issues. You will, however, have a much expanded universe of devices (Polyglot, NodeLink, Z-Wave multi-channel and some Insteon) available to you, as well as some nice programming features. I'd be surprised if you see stability issues with the base platform, as not many are reported here.

I don't think "Status" will do it. I think you need to use "Control" in the IF stanza of your program.

If your MSII is powered by battery, then I believe they don't communicate with the ISY unless they're woken up by motion or by a button press. My understanding is that there is a short period after the sensor detects motion that you can use to connect to the device and query it. If the device is powered by USB, then you can query it anytime. MSIIQuery - [ID 00FF][Parent 00DF] If '4A.54.E8.1 Motion' is switched On Then Set '4A.54.E8.1 Motion' Query Else - No Actions - (To add one, press 'Action')

Insteon will replace a hub that has died, however, even past warranty. That's not much, but it's more than they're doing with dead PLMs. https://www.insteon.com/support-knowledgebase/2015/10/20/migrating-to-a-new-insteon-hub

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.