Bumbershoot

I see three different IP addresses that you've used in your last few posts: 192.168.0.228; 192.168.86.46; 192.168.0.29. If you've got the right IP address, you should be able to SSH (ssh pi@192.168.0.228 for example) into that address and see if NodeLink is indeed running. It should look something like this after you run this command: ps aux | grep Node pi@raspberrypi:~ $ ps aux | grep Node root 598 1.3 6.4 247164 61240 ? Sl Oct29 23:50 dotnet /home/pi/node/NodeLink.dll pi 2929 2.8 6.4 252160 60640 ? Ssl 10:13 0:21 /home/pi/dotnet/dotnet /home/pi/node/NodeLink.dll pi 3163 0.0 0.0 7348 532 pts/0 S+ 10:26 0:00 grep --color=auto Node pi@raspberrypi:~ $ If it's not running, you won't get anything on that IP address:port

Excellent! Glad to hear it!

Nope, I didn't. This appeared with Polyglot version 2.2.5_1. That said, there's another Polyglot update available this morning: 2.2.5_3.

FYI -- I discovered something interesting this morning that might save some folks a little time: I installed my new Polisy PRO in the same cabinet as my ISY, as that's where most of my hardwired networked gear goes. In fact, I set my ISY directly on top of the Polisy. I began to notice issues with my previously rock solid Z-Wave devices, specifically, communication errors. After a bit of fussing around, I powered off and removed my Polisy from the cabinet, and Z-Wave began acting reliably again. I replaced the Polisy without the screw-in antenna, and the Z-Wave issues returned, though maybe not as bad as before. Removing it from the cabinet entirely and placing it elsewhere caused my Z-Wave devices to begin operating normally. Polisy now has a new home...

Okay, it appears that the new version of Polyglot is indeed running, but apparently not on port 3000, but on the default https port of 443. ' https://polisy' gets me in. 'https://polisy:3000' produces nothing here. The "Settings" page indicates this.

This is from the polyglot log after a reboot: 2019-10-29 06:09:57 [polyglot] info: Starting Polyglot.... 2019-10-29 06:09:57 [polyglot] info: Settings: Polyglot Version 2.2.5 2019-10-29 06:09:57 [polyglot] info: Settings: Retrieved config from database 2019-10-29 06:09:57 [polyglot] info: Running in Polisy mode 2019-10-29 06:09:57 [polyglot] info: Settings: Retrieved config overrides from .env and updated database 2019-10-29 06:09:57 [polyglot] info: Aedes MQTT Broker Service: Started on port 1883 2019-10-29 06:09:57 [polyglot] info: MQTT Client Service: Started 2019-10-29 06:09:57 [polyglot] info: HTTPS Interface Service: Started - Address: 0.0.0.0 Port: 443 2019-10-29 06:09:58 [polyglot] info: MQTTS: polyglot authenticated successfully. 2019-10-29 06:09:58 [polyglot] info: MQTTS: Client Connected: 2019-10-29 06:09:58 [polyglot] info: ISY: Got Version 5.0.16 2019-10-29 06:11:59 [polyglot] info: Caught SIGTERM/SIGINT Shutting down. 2019-10-29 06:12:59 [polyglot] info: Starting Polyglot.... 2019-10-29 06:12:59 [polyglot] info: Settings: Polyglot Version 2.2.5 2019-10-29 06:12:59 [polyglot] info: Settings: Retrieved config from database 2019-10-29 06:12:59 [polyglot] info: Running in Polisy mode 2019-10-29 06:12:59 [polyglot] info: Settings: Retrieved config overrides from .env and updated database 2019-10-29 06:12:59 [polyglot] info: Aedes MQTT Broker Service: Started on port 1883 2019-10-29 06:13:00 [polyglot] info: MQTT Client Service: Started 2019-10-29 06:13:00 [polyglot] info: HTTPS Interface Service: Started - Address: 0.0.0.0 Port: 443 2019-10-29 06:13:00 [polyglot] info: MQTTS: polyglot authenticated successfully. 2019-10-29 06:13:00 [polyglot] info: MQTTS: Client Connected: 2019-10-29 06:13:00 [polyglot] info: ISY: Got Version 5.0.16 2019-10-29 06:25:12 [polyglot] info: Caught SIGTERM/SIGINT Shutting down. 2019-10-29 06:29:08 [polyglot] info: Starting Polyglot.... 2019-10-29 06:29:08 [polyglot] info: Settings: Polyglot Version 2.2.5 2019-10-29 06:29:08 [polyglot] info: Settings: Retrieved config from database 2019-10-29 06:29:08 [polyglot] info: Running in Polisy mode 2019-10-29 06:29:08 [polyglot] info: Settings: Retrieved config overrides from .env and updated database 2019-10-29 06:29:08 [polyglot] info: Aedes MQTT Broker Service: Started on port 1883 2019-10-29 06:29:09 [polyglot] info: MQTT Client Service: Started 2019-10-29 06:29:09 [polyglot] info: HTTPS Interface Service: Started - Address: 0.0.0.0 Port: 443 2019-10-29 06:29:09 [polyglot] info: MQTTS: polyglot authenticated successfully. 2019-10-29 06:29:09 [polyglot] info: MQTTS: Client Connected: 2019-10-29 06:29:10 [polyglot] info: ISY: Got Version 5.0.16 Still, nothing on port 3000.

I don't get a web page on port 3000 after upgrading to the newest version (2.2.5_1): sudo pkg update && sudo pkg upgrade Password: Updating udi repository catalogue... Fetching meta.txz: 100% 820 B 0.8kB/s 00:01 Fetching packagesite.txz: 100% 45 KiB 45.8kB/s 00:01 Processing entries: 100% udi repository update completed. 156 packages processed. All repositories are up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Checking for upgrades (1 candidates): 100% Processing candidates (1 candidates): 100% The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: polyglot: 2.2.4_2 -> 2.2.5_1 Number of packages to be upgraded: 1 17 MiB to be downloaded. Proceed with this action? [y/N]: y [1/1] Fetching polyglot-2.2.5_1.txz: 100% 17 MiB 9.1MB/s 00:02 Checking integrity... done (0 conflicting) [1/1] Upgrading polyglot from 2.2.4_2 to 2.2.5_1... ===> Creating groups. Using existing group 'polyglot'. ===> Creating users Using existing user 'polyglot'. [1/1] Extracting polyglot-2.2.5_1: 100% Polyglot appears to be running, however: [admin@polisy ~]$ ps aux USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 11 393.9 0.0 0 64 - RNL 06:12 25:55.93 [idle] root 0 14.7 0.1 0 4640 - DLs 06:12 1:02.02 [kernel] mongodb 1001 0.3 1.2 821000 48500 - I 06:12 0:07.56 /usr/local/bin/mongod --logpath /var/db/mongodb/mongod.log --logappend --config /usr/local/etc/mongodb.conf --dbpath /var/db/mongodb - root 1 0.0 0.0 9556 980 - ILs 06:12 0:00.21 /sbin/init -- root 2 0.0 0.0 0 16 - DL 06:12 0:00.00 [crypto] root 3 0.0 0.0 0 16 - DL 06:12 0:00.00 [crypto returns 0] root 4 0.0 0.0 0 16 - DL 06:12 0:00.00 [crypto returns 1] root 5 0.0 0.0 0 16 - DL 06:12 0:00.00 [crypto returns 2] root 6 0.0 0.0 0 16 - DL 06:12 0:00.00 [crypto returns 3] root 7 0.0 0.0 0 32 - DL 06:12 0:00.00 [cam] root 8 0.0 0.0 0 16 - DL 06:12 0:00.00 [soaiod1] root 9 0.0 0.0 0 16 - DL 06:12 0:00.00 [soaiod2] root 10 0.0 0.0 0 16 - DL 06:12 0:00.00 [audit] root 12 0.0 0.0 0 320 - WL 06:12 0:02.44 [intr] root 13 0.0 0.0 0 48 - DL 06:12 0:00.01 [geom] root 14 0.0 0.0 0 160 - DL 06:12 0:01.59 [usb] root 15 0.0 0.0 0 16 - DL 06:12 0:00.00 [soaiod3] root 16 0.0 0.0 0 16 - DL 06:12 0:00.00 [soaiod4] root 17 0.0 0.0 0 160 - DL 06:12 0:00.39 [zfskern] root 18 0.0 0.0 0 16 - DL 06:12 0:00.00 [sctp_iterator] root 19 0.0 0.0 0 16 - DL 06:12 0:00.29 [pf purge] root 20 0.0 0.0 0 16 - DL 06:12 0:00.09 [rand_harvestq] root 21 0.0 0.0 0 48 - DL 06:12 0:00.15 [pagedaemon] root 22 0.0 0.0 0 16 - DL 06:12 0:00.00 [vmdaemon] root 23 0.0 0.0 0 48 - DL 06:12 0:00.09 [bufdaemon] root 24 0.0 0.0 0 16 - DL 06:12 0:00.02 [syncer] root 25 0.0 0.0 0 16 - DL 06:12 0:00.01 [vnlru] root 670 0.0 0.0 0 64 - DL 06:12 0:00.00 [ng_queue] root 701 0.0 0.1 11308 2612 - Is 06:12 0:00.00 dhclient: system.syslog (dhclient) root 704 0.0 0.1 11504 2692 - Is 06:12 0:00.00 dhclient: igb0 [priv] (dhclient) _dhcp 705 0.0 0.1 11672 2816 - ICs 06:12 0:00.00 dhclient: igb0 (dhclient) root 785 0.0 0.0 10552 1500 - Is 06:12 0:00.00 /sbin/devd root 824 0.0 0.1 10916 2160 - Is 06:12 0:00.00 /usr/sbin/rtsold -a root 865 0.0 0.1 11276 2620 - Ss 06:12 0:00.03 /usr/sbin/syslogd -s root 993 0.0 0.1 12292 3452 - Ss 06:12 0:00.26 /usr/local/sbin/powerd++ -a hadp -b hadp -n hadp polyglot 1009 0.0 0.1 10768 2188 - Is 06:12 0:00.00 daemon: /usr/local/bin/polyglot-v2-freebsd-x64[1010] (daemon) polyglot 1010 0.0 2.5 705696 103592 - S 06:12 0:07.75 /usr/local/bin/polyglot-v2-freebsd-x64 -w /var/polyglot root 1032 0.0 0.1 11108 2320 - Is 06:12 0:00.00 /usr/sbin/hcsecd -f /etc/bluetooth/hcsecd.conf ntpd 1062 0.0 0.5 18632 18712 - Ss 06:12 0:00.27 /usr/sbin/ntpd -p /var/db/ntp/ntpd.pid -c /etc/ntp.conf -f /var/db/ntp/ntpd.drift -g nobody 1069 0.0 0.1 10892 2196 - Is 06:12 0:00.00 /usr/sbin/sdpd -c /var/run/sdp -g nobody -u nobody root 1089 0.0 0.2 17596 7872 - Is 06:12 0:00.01 /usr/sbin/sshd root 1092 0.0 0.1 11268 2656 - Is 06:12 0:00.01 /usr/sbin/cron -s root 1135 0.0 0.2 17896 8380 - Is 06:13 0:00.07 sshd: admin [priv] (sshd) admin 1138 0.0 0.2 17900 8400 - S 06:13 0:00.02 sshd: admin@pts/0 (sshd) root 1134 0.0 0.1 10804 2380 u1 Is+ 06:12 0:00.01 /usr/libexec/getty 3wire.115200 ttyu1 admin 1139 0.0 0.1 12828 4064 0 Ss 06:13 0:00.04 -bash (bash) admin 1149 0.0 0.1 11548 3012 0 R+ 06:19 0:00.00 ps aux [admin@polisy ~]$

Sorry: mongo polyglot --eval "db.nodeservers.remove({'name': 'ISY Portal'})"

The full syntax at the command line might be this: mongo polyglot --eval "db.nodeservers.remove({'name': 'DarkSky'})" and: mongo polyglot --eval "db.nodeservers.remove({'name': 'SolarEdge'})" Worked for me... Additionally, the update/upgrade process worked just fine here. I'm up on the latest and greatest Polyglot, among other things: [admin@polisy ~]$ sudo pkg update && sudo pkg upgrade We trust you have received the usual lecture from the local System Administrator. It usually boils down to these three things: #1) Respect the privacy of others. #2) Think before you type. #3) With great power comes great responsibility. Password: Updating udi repository catalogue... pkg: Repository udi has a wrong packagesite, need to re-create database Fetching meta.txz: 100% 820 B 0.8kB/s 00:01 Fetching packagesite.txz: 100% 45 KiB 45.9kB/s 00:01 Processing entries: 100% udi repository update completed. 156 packages processed. All repositories are up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Checking for upgrades (9 candidates): 100% Processing candidates (9 candidates): 100% The following 9 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: sudo: 1.8.27_1 -> 1.8.28p1 python37: 3.7.4 -> 3.7.5 python27: 2.7.16_1 -> 2.7.17 py37-setuptools: 41.2.0 -> 41.4.0 polyglot: 2.2.1_2 -> 2.2.4_2 pciids: 20190725 -> 20191012 isc-dhcp44-client: 4.4.1 -> 4.4.1_1 ca_root_nss: 3.46.1 -> 3.47 boost-libs: 1.71.0_1 -> 1.71.0_2 Number of packages to be upgraded: 9 The process will require 16 MiB more space. 59 MiB to be downloaded. Proceed with this action? [y/N]: y [1/9] Fetching sudo-1.8.28p1.txz: 100% 675 KiB 690.9kB/s 00:01 [2/9] Fetching python37-3.7.5.txz: 100% 16 MiB 16.6MB/s 00:01 [3/9] Fetching python27-2.7.17.txz: 100% 11 MiB 11.3MB/s 00:01 [4/9] Fetching py37-setuptools-41.4.0.txz: 100% 504 KiB 516.0kB/s 00:01 [5/9] Fetching polyglot-2.2.4_2.txz: 100% 17 MiB 9.1MB/s 00:02 [6/9] Fetching pciids-20191012.txz: 100% 206 KiB 211.1kB/s 00:01 [7/9] Fetching isc-dhcp44-client-4.4.1_1.txz: 100% 948 KiB 971.1kB/s 00:01 [8/9] Fetching ca_root_nss-3.47.txz: 100% 287 KiB 293.6kB/s 00:01 [9/9] Fetching boost-libs-1.71.0_2.txz: 100% 12 MiB 13.0MB/s 00:01 Checking integrity... done (0 conflicting) [1/9] Upgrading boost-libs from 1.71.0_1 to 1.71.0_2... [1/9] Extracting boost-libs-1.71.0_2: 100% [2/9] Upgrading python37 from 3.7.4 to 3.7.5... [2/9] Extracting python37-3.7.5: 100% [3/9] Upgrading sudo from 1.8.27_1 to 1.8.28p1... [3/9] Extracting sudo-1.8.28p1: 100% [4/9] Upgrading python27 from 2.7.16_1 to 2.7.17... [4/9] Extracting python27-2.7.17: 100% [5/9] Upgrading py37-setuptools from 41.2.0 to 41.4.0... [5/9] Extracting py37-setuptools-41.4.0: 100% [6/9] Upgrading polyglot from 2.2.1_2 to 2.2.4_2... ===> Creating groups. Using existing group 'polyglot'. ===> Creating users Using existing user 'polyglot'. [6/9] Extracting polyglot-2.2.4_2: 100% [7/9] Upgrading pciids from 20190725 to 20191012... [7/9] Extracting pciids-20191012: 100% [8/9] Upgrading isc-dhcp44-client from 4.4.1 to 4.4.1_1... [8/9] Extracting isc-dhcp44-client-4.4.1_1: 100% [9/9] Upgrading ca_root_nss from 3.46.1 to 3.47... [9/9] Extracting ca_root_nss-3.47: 100%

FWIW: The daily program update check is returning a '404' this morning. 2019-10-26 07:41:00 - Auto-Update: Error updating file: The remote server returned an error: (404) Not Found.

That's how I use a LIFX light to convey security status: the light itself is hidden over a piece of sculpture in a central part of the house. The color of the light conveys the status of my various portals. If we leave a door open, it gets noticed. It's very effective and unobtrusive.

Maybe you'll hear from him. Payment is an issue across the border (if you're in the US). It appears that PayPal might be a bit of a hassle for the recipient. It was easy for me, though. ?

I bought mine from a member here, so no. Sorry. Supplyhouse.com has them for a cost that's well below that of what I found on Amazon, or for what Costco sells Ecobee or Nest for. YMMV.

Both of your points are exactly how I'm using LIFX bulbs; for tuning lights in an art studio and sending security notifications. My house is full of wood, and colored lights just don't look that good.

Yep. NodeLink was just migrated to dotnet, so I’m not entirely certain that there aren’t some prerequisites, but I don’t think so. It runs like a champ on my RPi, along with Polyglot and a node.js server.

It uses NodeLink. If you're running an RPi (or soon, Polisy), then you can host an instance of NodeLink, which connects to the Venstar using the local API. The Venstar appears and acts as a fully native device in your ISY.

It's easy to do if you run NodeLink. You'll need a script on your RPi, a Network Resource on your ISY and NodeLink configured properly. I use this to have my ISY bounce Polyglot on occasion (both NodeLink and Polyglot run on the same RPi), amongst other things. I'd post an example but I'm away from home this week. EDIT: In NodeLink, you need to turn on the "Relay Server".

I bought a used Venstar Colortouch t7900, and along with a couple of remote sensors and Nodelink, it replaces my Nest 2 beautifully, and it interacts reliably with my ISY. The Venstar Skyport app/website are well designed and easy for the non-techie in the house to use. I use a node server for geofencing, but the Skyport app now supports that as well with a recent update.

Mine are all approx. 156k. Firmware version (I'm on 5.0.16) might make a difference, as well as how many devices, programs, nodeservers, etc. I don't have any from the 4.x.x series firmware.

I don't believe it is, at least in the nodeserver. I just use the Wireless Tag webpage to set an arming/disarming schedule, which is adequate for my needs. You may do it with a Network Resource or a Kumoapp, but I haven't taken the time to explore doing it.

Yes, they have. I had a power supply fail in a Hub that a relative owns. Smarthome acknowledged the issue, and sent a free replacement for this unit (I think there's a link somewhere on the Insteon or Smarthome forums that explains the replacement program for these Hubs).

I find it useful to document devices in my ISY as well, using the "Notes" function (right click on the device, and select "Notes" in the AC). Probably not a time saver, though...

I don't think Polisy is built on Linux, but on FreeBSD. There are many similarities, but also a great many differences. You're right that knowledgeable users, if UDI allows them permissions on the box, shouldn't be stymied long by the differences from Linux. Casual users, on the other hand, may not like it so much. I would expect this FreeBSD installation to be very lean, with a very limited 'sudo' permission set. I know that if I was responsible for supporting it, it would lean and locked.

I'm experiencing problems with Polyglot Cloud similar to those that occurred earlier in the week. I can't get PGC nodeservers to install, delete, restart, display logs, etc.

I believe that Ecobee and Ring have cloud based API's, so moving them local probably wouldn't solve much, other than giving you a degree of local control (and I believe you're stuck with PGC for Ring). It would mean that you have more things you have to maintain - though that may be a good thing for some folks. Personally, I don't mind offloading server management to UDI when/where it's reasonable. I intend to use Polisy for nodeservers that don't have a PGC installation.