io_guy

Those are Polyglot errors. Ecobee's servers are a mess right now. When I remove the app it never works the first time, don't know what they're doing over there.

I use an Aube RC840T-240 hanging off the side of my electrical panel. It can be controlled by any dry contact relay (such as an IOLinc) since it has a built-in 24V transformer to power it's contactor.

Just an FYI, Next version of NodeLink will be a "breaking" change. I'll be moving to .NET 5 (which comes out in 3 weeks) and I've modified all the NodeDef files to allow for dynamic changing of units. It will be similar to the move to .NET Core 3 where it didn't auto upgrade. I'll stick with .NET 5 for a long time so this should be the last of the painful updates. I'll also be adding a couple new devices: - Weatherbit - Hayward Omnilogic pool controller - MyQ

I was curious why you moved off the Synology. Makes sense.

Get it running on the Pi and then just copy over the config.xml file. No need to change anything on the ISY with the exception of the new IP address for the Node Server.

Reboot NodeLink, you should get a pin. I don't for additional pins on a single program run because Ecobee's shi**y servers like to spit our random errors sometimes and NodeLink would be disconnecting way more if I believed what the servers say. In the next version I'll add a manual pin request, it looks like Ecobee's servers are worse than ever.

Any chance this could be added? Homeseer has this feature and it's been great for upping reliability. I couldn't care less if my dimmers add as insecure and as insecure they have a much easier time pairing and meshing with various other devices.

Is there a way to include a device that supports S0/S2 as insecure?

It's an Ecobee server issue, you need to re-add it with them. The Polyglot guys are having the same issue.

I use Insteon only for light switches/dimmers, have about 40. I need to pick up a couple more switches but am debating moving to Z-wave for all replacements. I don't want anything fancy so the GE Enbrighten fits the bill. No flashy features and looks very similar to the Insteon. It's also very shallow and auto detects line/load wiring. I like the Inovelli but I'm don't want a frankenstein house where every switch looks different. Main reasons for the slow transition is I hate PLMs and having limited controller options.

Agreed. Every other controller I've used allows me to disable S0. If you choose that option on the ISY then the "secure" device just never enrolls.

There's no benefit of plus with the ISY anyway. Every one of my devices are plus and they had to be within a couple feet to pair. Pretty sure NWI doesn't work.

I had two 469s that we're bulletproof with my old 300. I had a GE plug-in outlet next to each for beaming. It was almost 100% reliable. Once I switched to the 500 they were unusable. I then purchased 4 ZW+ range extenders to replace the plug-ins which made everything but the locks ZW+. At that point they were about 80% reliable. I've since moved and my new locks are the 469ZP. These work much better with the 500.

I've always had NWI enabled with my 500. I doubt it actually works because I've always had to bring the devices to within a couple feet. And I do have 2 range extenders which are the first things I pair.

I can't find this anywhere. Can you elaborate?

I have the system working on 5.1.0 but very poorly. Every secure device had to be brought within 3' of the ISY. In comparison Homeseer required zero moving around (50' and a wall were no problem). 2 LS100 leak sensors just give "1010", other 2 work fine. Communication is crazy slow. I have a Z-Wave wall switch that triggers a Z-Wave plug-in switch (programs, not association). After hitting the wall switch it takes about 6-8 seconds for the plug-in to turn on, in Homeseer this is about 0.5 seconds.

v0.10.6 released.

Yep, the install script assumes you used the old install script, meaning you're running NodeLink from rc.local. You did a custom systemd startup so the old .exe would keep running.

The Nodes match the thermostat, can't be changed later. Delete the nodes and let them redo in the ISY. I'd love to change all the devices to support dynamic switching of units but it'd break everyone's current setups.

You need to enable the option "Include 653 (Ready to Force Arm) in 650 (Ready)" As for the Venstar timeout, it's common. Increase the timeout in the Venstar NodeLink tab.

I can't help if you don't post a verbose log. I need to see what data is coming into NodeLink.

Yes, it's under NDA so I can't share the info. I use a Pi3 but have also played with a Pi1 and a Pi4, any will run NodeLink easy. Standard Raspbian Buster.

Try the ISY upgrade before wiping your Pi, based on the log this looks like an ISY issue.

Just a heads up. Finally getting around to setting up automation in my new place. Swimming pool will be in mid July. I've been in contact with Hayward pool products who have given me access to their Omnilogic API. Will add it to NodeLink once I get it installed.