io_guy

For the me newer ZP locks just didn't play nice with the ISY. With a Z-Wave 300 ISY and non-ZP BE469 locks, I used a GE outlet next to each door and it worked 100% of the time. Once I moved to the Z-Wave 500 ISY the non-ZP locks were useless. They would only pair at 1' away from the ISY and would not communicate (directly or through repeaters). I updated the repeaters to 500-series (Aeotec) and it improved things but they were maybe 85% reliable going through the repeaters. Once I switched to a Z-Wave USB stick my issues went away since the locks now have no issue talking directly to the controller. Hopefully when the ISY moves to Polisy the BE469ZP issues will be resolved (stronger Z-Wave controller signal). I use a 700-series stick now and the locks talk directly without any issues.

Works fine here too. I suspect abril's issue is related to the number of node servers he has. Polyglot uses a separate connection for each node server and the ISY is quite limited on connections. In my opinion Polyglot should have used a common FIFO buffer for ISY communication to prevent this (which is what I did with NodeLink for that exact reason).

Sorry, I don't do Polyglot and NodeLink is now in maintenance only (no new devices). I've moved my system over to Home Assistant.

In my last house I had similar packet loss when my ISY was connected to a non-managed 5-port TP-Link switch that also had an Amcrest IP camera on it. It appeared that the ISY couldn't handle all the multicast traffic coming from the camera. Once I moved the camera over to my main managed switch, all was ok again.

Nope, I've given up with NodeLink on polisy, too much of a pain with the base polisy OS installation. My graphs are from EmonCMS, I have it installed on a Pi4 with NodeLink.

Latest versions require .NET 5 installed. Download http://automationshack.com/Files/NodeLink.cmd and put/run it in your NodeLink dir.

I do add devices still (just added a crude internet weather starter) and will be adding OmniLogic pool control and MyQ this spring. But I have to say that KLF200 API is pretty much the most complicated I have seen in a while. It can be done I just don't have the time to put into it these days.

What's your docker error? Plain install is harder than docker: wget https://packages.microsoft.com/config/debian/10/packages-microsoft-prod.deb -O packages-microsoft-prod.deb sudo dpkg -i packages-microsoft-prod.deb sudo apt update sudo apt install apt-transport-https sudo apt install dotnet-runtime-5.0 Then download NodeLink and run it. You can find the NodeLink links in the Pi install script. You'll want to setup NodeLink as a systems service (so it reboots on startup), there's a post on how to do that.

Nope. It's a Pi install script and the .NET version is specific.

v0.11.1 released.

Yep I can add it to the next version. Would be nice if the genmon author used a standard JSON format (and stopped changing it).

A "df -m" will tell you how much space you have and partition size.

No space on device seems to come up a lot...

And it's a local API. Ecobee's cloud servers are notoriously unreliable.

Correct

I had 0.10.X running but 0.11.X will need a new .NET 5 runtime that UDI wont be creating/supporting. I don't have a Polisy anymore so I'll call the answer, "No".

v0.11.0 released. See breaking changes here:

Starting with version 0.11.0, NodeLink will use .NET 5. This release is a breaking change since it requires a new .NET runtime. If you're running on a Pi, just run the install script and everything will update as required. Another breaking change is the NodeDef files for thermostats (Ecobee, Honeywell and Venstar). There were previously separate node definitions for F and C. There is now a single definition which will dynamically changes units based on settings. This will break the existing node in the ISY. After updating the node definition files in the ISY, if you have one of the following devices you'll want to try the below commands to switch the ISY's definition to the new one: * In the below commands "1" and "001" should be changed to the node server slot that NodeLink is installed on. Ecobee: http://ISY/rest/ns/1/nodes/n001_ecobee1/change/Ecobee?nls=140E Honeywell: http://ISY/rest/ns/1/nodes/n001_hwstat1/change/HonTCC?nls=140H Venstar: http://ISY/rest/ns/1/nodes/n001_ven1/change/Venstar?nls=140V

UDI have previously posted that a vertical mounting is preferred for the 500 series Z-Wave.

If you're buying the Wagos get the 221 series. The picture is the older 222 series. 221s are smaller and clear.

Hikvision DS-HD1. Way cheaper than a Doorbird, local ONVIF support, 16-24 VAC wiring (doorbell transformer).

I don't see energy consumption but scene control and LED notifications work.

I spoke with Chris, looks like there will be a way to avoid re-doing anything in the ISY, just need to send a rest command from your browser which I'll identify once I roll out the new version.

Not really, it's just a re-run of the install script, same as had to be done when it moved to Net Core 3. The part that's more breaking is the node def files. I've changed a number of them to allow for dynamic unit changes (no separate C and F devices). That may require the device to be reinstalled in the ISY. Going to talk to UDI before it happens to see if there's a clean way to avoid this.

The contacts on the Aube just need to be closed to enable it. Connect the two lines across a relay of the IOLinc.