Bumbershoot

Nope, it's not running. Crash. You might try running NodeLink from the command line, and see if it sends any helpful output to the screen (I think you can just run the command that you see in output above): dotnet /home/pi/node/NodeLink.dll Other than that, I don't know how I can help with a seg fault.

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

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.

I'm using the 13 bit temp/humidity tags (5), along with the PIR KumoSensors (4) and Water/Moisture sensors (4). All work just fine with the ISY, either with Network Resources or through the nodeserver. BTW, if you're going to buy some of these things, then use this link: https://goo.gl/rXAGk9 @Jimbo, who maintains the Polyglot Wireless Tag nodeserver gets a discount on his purchases when this link is used. Whether you use the nodeserver or not, this is a way show him some support.

I have these in two freezers, one in the garage approx. 70' from the tag manager, and they work very well. I have others in the garden, maybe 150' from the tag manager. I have the tag manager stuck in a cabinet, so the range is likely impaired somewhat by it's location. I use the Wireless Tag nodeserver to put the data into my ISY, which vastly increases the usefulness of these little devices. I have about a dozen of them in my HA environment, using them to help manage irrigation, humidity levels, temperature, occupancy, even to know if anyone has been rooting around in my humidor.

This seems all good. Thanks again for all your excellent work! Looking foreward, I read the .NET Core 3.x is available on FreeBSD. If so, is it possible that NodeLink will have an install script on the Polisy?

The symlink to '/sbin' will have to be owned by 'root', won't it? Back in my sysadmin days, I did everything I could to keep other admins from using the 'root' account when it wasn't necessary. It probably doesn't matter that much on your average RPi, but maybe for consistency (Polyglot installs under the user account, not the 'root' account) the user account might be preferable? Do you know if 'dotnet' and it's supporting files will be included in the standard 'apt' repositories, going forward? I'm imagining that they will, which may make it somewhat more difficult for users to update the file(s) if they're located in a user directory.

Just an FYI: Interestingly, the config file in '/home/pi/node' was created with 'root' ownership/permissions. My usual practice is to keep things in user directories owned by that user, so I changed the ownership of '/home/pi/node/config.xlm' to user 'pi' to give my '/bin/systemctl' control file ('/etc/systemd/system/nodelink.service') permission to run. I could have also just eliminated the 'User=pi' line. [UNIT] Description=NodeLink Server Documentation=http://automationshack.com/nodelink.html Requires=network-online.target After=network-online.target [Service] Type=simple ExecStartPre=/bin/sleep 10 ExecStart=/home/pi/dotnet/dotnet /home/pi/node/NodeLink.dll Restart=always User=pi [Install] WantedBy=multi-user.target

Now that all my devices are working, I get this error in NodeLink related to my RainMachine when the "Enable Weather Node" checkbox is checked: 22019-09-29 07:42:00 - ISY NodeLink Server v0.10.0 started 2019-09-29 07:42:00 - OS: Linux raspberrypi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux 2019-09-29 07:42:00 - Web config server started (http://192.168.1.5:8090) 2019-09-29 07:42:01 - ISY resolved to 192.168.1.20 (5.0.15A) 2019-09-29 07:42:01 - ISY Node Server config detected (profile 2) 2019-09-29 07:42:04 - Relay Server: Started on port 2405 2019-09-29 07:42:06 - RainMachine: Poll Error - ValueType 'System.Double' cannot be null. [rain1] 2019-09-29 07:42:37 - RainMachine: Poll Error - ValueType 'System.Double' cannot be null. [rain1] 2019-09-29 07:43:07 - RainMachine: Poll Error - ValueType 'System.Double' cannot be null. [rain1] 2019-09-29 07:43:38 - RainMachine: Poll Error - ValueType 'System.Double' cannot be null. [rain1] I don't have a rain sensor attached to my RainMachine, so I suspect this should be normal/expected? This error goes away when the checkbox is unchecked.

Please disregard -- RainMachine is now working as intended on the new NodeLink. Thanks, and sorry for the problem. Network issue here...