io_guy

I don't use polyglot or the portal so I don't know. The point of the location node was to use something like locative or tasker to send an http message when they get near the house. The node would then send the status in the ISY. I haven't done much with it since I'm not a real fan of location tracking based automation.

That log file shows all the zone values being written to the ISY properly. Try deleting the nodes from the ISY and re-installing them. If that doesn't work it's a UDI problem.

You didn't enable either debug. We need to see what's coming from the DSC and what's going to the ISY.

A log file wouldn't hurt, debug level on DSC tab and System Config.

No it should be install.sh now.

Don't think it will currently work. NodeLink tries to find the node profile number (in the ISY) on startup. So both instances would try to use the same slot in the ISY and overwrite each others data.

Nope, my previous login says it doesn't exist when I try a reset.

Trying to login to the portal and/or developer portal and/or my.isy after about 6 months. None work and all tell me they don't recognize the various usernames (so I can't reset anything). Did I miss something?

This is polisy: https://www.pcengines.ch/apu2e4.htm

Yes

Can you PM me your config.xml?

Bug Report - Polisy does not respect secondary DNS servers. My primary was down and Polisy did not use the secondary.

You started manually by running mono NodeLink.exe The new command is dotnet NodeLink.dll For the error, I need the rest of the log. If you want to remove mono you could run sudo apt remove --purge --auto-remove mono-runtime

Polisy is waiting for UDI. They are creating required packages to run NodeLink. I run it successfully but I enable the regular BSD repo and install the required packages.

I mean why would you use a RPi image instead of just plain Debian VM. Or just run it on the Windows box straight.

No idea why you'd install a Pi image on Windows instead of just standard Debian. Can't help with the service startup, I use rc.local. I need the actual NodeLink log to work on your NLS issue.

I did netcore-runtime-3.0 instead of aspnetcore-runtime-3.0 I have no idea what VM RPi debian is but it's most likely the issue. Pi is ARM, Windows is x64, a VM cannot emulate a different architecture. Mono didn't care about arch, but Net Core does.

So I just installed a fresh Debian in a VM on Windows. Did the install as above (except I installed netcore-runtime-3.0=3.0.0-1, not netcore-runtime-3.0=3.0.0-1). NodeLink started up without issue.

It's no longer install-core it's http://automationshack/Files/install.sh I doubt the script will work as it's meant for a Raspberry Pi. It will install the wrong .NET Runtime (built for ARM) To use Debian download: http://automationshack/Files/NodeLink.dll http://automationshack/Files/NodeLink.runtimeconfig.json For the core runtime follow this: https://dotnet.microsoft.com/download/linux-package-manager/runtime-3.0.0 or download the binary: https://download.visualstudio.microsoft.com/download/pr/a5ff9cbb-d558-49d1-9fd2-410cb1c8b095/a940644f4133b81446cb3733a620983a/dotnet-runtime-3.0.0-linux-x64.tar.gz

v0.10.5 released.

v0.10.4 released.

Might be time for a new router. Or just use an ARP scanner on your phone (I use Net Analyzer for Android). Dunno why Polisy doesn't just give a UDP broadcast packet. There's about a million software packages that could pick that up.

The whole point of local APIs (and some people will only do local exclusively for that reason) is so that there is no dependence on your internet connection. Yes, you could do it in the cloud, but if the API is local I'd highly recommend a local solution for the nodeserver. For both internet independence and speed.

That's not cloud. The API to the EVL is a local API; using a cloud based nodeserver for a local connection defeats the whole point.

v0.10.3 released.