Scyto

I was a bit slow on this release, sorry folks. For those of you using it I have updated the container to .net 5 and nodelink 11.x If you are using persistent volume please delete NodelLnk.dll and NodeLink.runtimeconfig.json from your persistent volume before starting the refreshed container. scyto/nodelink (docker.com)

When i add a 2852-222 leak sensor it asks me for a device name. The wet and heartbeat nodes get named with the name I give it (with the right suffix) The dry node is named '2D.5D.1B - dry' as an example. No biggie as one can rename, so just FYI.

Hi Michael, I am having no issue with the ISY. Was just looking for a running / aggregate change log doc - that's all. No problem if there isn't one, it's a nice to have rather than scrounging over many posts.

got it so the short and actual answer to my original questions was "No" I know I can read the multiple lists and massive threads, i am not a moron, I was asking for something specific and the answer "no" is ok and was the helpful answer not given.

Do you means the page in the forums with each update or some other page? (i tried finding a single page with all updates and a cumulative set of release notes). The forum pages don't give a single cumulative release note.

Thanks, i read that post and understood it, i have been on series 500 since the HW was in beta. My ask was is there a cumulative set of release notes. Have you seen one?

@danbutter the container works, i am using it, i am not sure what you are doing or what the issue is You did map the the docker directory right with r/w perms so this is stateful? So on first boot the container looks to see if it has nodelink, if it doesn't it downloads it. I don't know why that causes an exit on your machine, it shouldn't. On the next boot it will be like this in the logs (this is how i know your state is being thrown away). I suggest you use the docker run command and test that rather than use portainer, once you have it working as per my instructions then i suggest you migrate into portainer. Also if you want help that's what the github is for - file an issue there and I will respond much faster. date stream content 2020-09-25 06:16:12 stdout 2020-09-24 23:16:12 - GEM: No valid parameters setup for connection [gem1] 2020-09-25 06:16:12 stdout 2020-09-24 23:16:12 - Warning: Node definitions need updating in ISY, see NodeLink's Devices page 2020-09-25 06:16:08 stdout 2020-09-24 23:16:08 - ISY Node Server config detected (profile 2) 2020-09-25 06:16:08 stdout 2020-09-24 23:16:08 - ISY resolved to 192.168.1.97 (5.2.0) 2020-09-25 06:16:08 stdout 2020-09-24 23:16:08 - Web config server started (http://172.17.0.4:8090) 2020-09-25 06:16:08 stdout 2020-09-24 23:16:08 - Net Core Version: 3.0.0 2020-09-25 06:16:08 stdout 2020-09-24 23:16:08 - OS: Linux scyto-nodelink1 4.4.180+ #40850 SMP Wed Sep 2 17:03:14 CST 2020 x86_64 GNU/Linux 2020-09-25 06:16:08 stdout root@scyto-nodelink1:/# 2020-09-24 23:16:08 - ISY NodeLink Server v0.10.6 started 2020-09-25 06:16:06 stdout starting NodeLink 2020-09-25 06:16:06 stdout checking if NodeLink exists

i am upgrading from 5.0.16c is there a cumulative release notes anywhere?

Using vcgencmd measure_temp my pi zero measures about 23c (73f) with 40f outdoor temp. just connected via web and its reading 78f now I am using web and shows about 28% CPU usage. i havent measured heat on ttl board but never noticed it being hot, when it stops raining I can try and get a temp reading? thoughts: you have a voltage issue supplying too many volts? you have something hitting the CPU heavily and generating heat you generator is running because you live off grid and it’s putting lots of heat into that compartment (joke)

Hi Everyone Sorry for the delay i had some serious issues with networking on the pi 4 and on pi zero. Turns out raspbian doesn't seem to like the DHCP packets from the Windows 2019 DHCP server i have, so at the end of the lease period it would drop leases on both wifi and LAN - took me 2 weeks to figure that out. I switched mid project from pi 4 (which was fully installed in the enclosure) to pi zero mainly a) to troubleshoot the network issue and b)its smaller, puts out less heat and i just wanted excuse to get one. so far it runs about 40% CPU so seems up to the job - i purchased the zero with the GPIO header already installed. I also installed a real-time clock on the pi, no real reason than i could Oh an i fitted a grommet to seal the box - not sure if that was a wise idea for something that generates hit, but i live in Seattle and need to keep out damp and mold. Another reason to stick with the pi zero. Great news, you can take an SD card straight out of a working pi4 and stick it in a zero and it works! I also took the suggestion of the project owner and put metal and nylon braid around my serial cables - which is fun, looks neat but may be unnecessary - also i learnt if you do that and use shrink tube only use a little or it affects the radius the cable can turn. I had to remove about 1 to 2 cm of my heat shrink. I would advise against putting the braid of TTL serial cable from the gpio pins unless you have interference, it just makes the cable difficult to manage (hence the glue gun glue in the pictures). Thanks to @johnstonsean for the OP and tips and H/W recommendations - they really helped. This post contains my chosen parts list FWIW, my next post will be random assorted photos. Pi Zero W header https://www.amazon.com/gp/product/B07B8MMD3V/ref=ppx_yo_dt_b_asin_title_o05_s00?ie=UTF8&psc=1 Pi Zero case - make sticking inside enclosure easy with command strips https://www.amazon.com/gp/product/B075FLGWJL/ref=ppx_yo_dt_b_asin_title_o04_s00?ie=UTF8&psc=1 Enclosure, i like this one better, its door had no issues https://www.amazon.com/gp/product/B07PK8K8S2/ref=ppx_yo_dt_b_asin_title_o07_s00?ie=UTF8&psc=1 Cable Gland https://www.amazon.com/gp/product/B077R1RT2T/ref=ppx_yo_dt_b_asin_title_o07_s01?ie=UTF8&psc=1 Real-time HW Clock https://www.amazon.com/gp/product/B00ZOXWHK4/ref=ppx_yo_dt_b_asin_title_o09_s00?ie=UTF8&psc=1 Cable i modded for connecting to Nexus https://www.amazon.com/gp/product/B07VF887KN/ref=ppx_yo_dt_b_asin_title_o08_s01?ie=UTF8&psc=1 (make sure to cut off the right end - the two ends are different!) Nylon braid https://www.amazon.com/gp/product/B071WF5K2X/ref=ppx_yo_dt_b_asin_title_o08_s01?ie=UTF8&psc=1 Metal braid https://www.amazon.com/gp/product/B01HE0PDG4/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 Motorcycle USB power https://www.amazon.com/gp/product/B01DYE54LI/ref=ppx_yo_dt_b_asin_title_o08_s01?ie=UTF8&psc=1 RS232 connector https://www.amazon.com/gp/product/B07437GS66/ref=ppx_yo_dt_b_asin_title_o08_s01?ie=UTF8&psc=1 Serial port module https://www.amazon.com/gp/product/B01JYNHNW6/ref=ppx_od_dt_b_asin_title_s01?ie=UTF8&psc=1 @agoltz hope this helps, YMMV, i tended to buy from amazon as seller and i haven't listed shrink tube as i way over bought for other projects I have some pastic cable clips coming, last part will be to use those on cables outside the case, might use one inside the case too.

Thanks for the info! i decided to have a go at this even though i only have a lowly nexus controller. I have a pi4, genmon installed, and cables loopback tested and all ready to go. Just waiting on an enclosure, the one recommend in this post seems to now have a defect that means door wont close once opened fully without manually squeezing and wiggling one of the hinge pins each time - same on two units. I have an alternate coming. how did folks attach their enclosures - 3m tape or magnets? did you clip the ends of the motorcycle power supply to the batter or properly uncrew bolts and push on to threaded screw?

Just getting back upto speed with the last year or so of ISY developments. Will many of the node servers only be available in polisy (i.e. you have to to buy the hardware), or does polyglot also get all of them, a store etc too?

With the release of v10 i have updated my NodeLink docker containers. The tag supports Linux (amd64, ARMv7 and ARMv8) and Windows (amd64). For Linux: docker run --name=NodeLink -v $PWD$:/NodeLink -v /etc/localtime:/etc/localtime:rw -p 8090:8090 scyto/nodelink For Windows: docker run --name=NodeLink -v $PWD$:C:\NodeLink -v /etc/localtime:/etc/localtime:rw -p 8090:8090 scyto/nodelink Where $PWD$ is the path to where you want files on the host, this will allow you to reuse the files you have or bootstrap the creation of new ones for more details see https://hub.docker.com/r/scyto/nodelink

Just finding this, haven't been around for a while. How have you found this in the cold / heat - I am in seattle so we don't go much below freezing or over 100f very often.

what happened to the button in the install doc (see below and compare with mine above)? Did it intentionally dissapear? It was there one moment today and not the next...

@io_guy Not sure if it supposed to be there? I saw it when it was set to the default of profile 1? I installed ISY portal on 1 (thats what it chose after i had removed all my nodes for everything)

for ubuntu start here https://docs.docker.com/install/linux/docker-ce/ubuntu/ and obvioulsy try out on a machine that is not you production home theater machine not sure what you run on the box for home media but look at https://hub.docker.com/r/emby/embyserver and https://hub.docker.com/r/plexinc/pms-docker - though that last one is probably a little scary looking, start with simpler container first like the nodelink one (assuming my container works - lol)

@ulrick65 All great questions, I started using docker on my synology NAS because a)they provide a UI (i am old school windows server person and like UI) and b)because when you run custom apps via SSH on a synology their support people get pissy (understandably). So this was a way to run apps as discrete units that don't affect the OS. What did i learn (in no real order): the synology UI misses so many docker features.... that it is awesome that upgrades to the underlying OS don't change what happens in the docker - no pissing about with multiple python or perl versions on the host OS that cause conflicts etc because each app is in its own container with all needed dependencies that while this seems inefficient most containers are tiny and that really you only trade one management overhead for another (managing docker vs managing inter-relationship of apps running natively on the host) - so for example if you blow away the host so long as you kept the state you mapped into the container - you just repull the container image, map in your backed up state and boom you have the app running again (even if you moved from debian to windows).. ...ability to user docker desktop on windows to run linux.amd64 containers on windows - freaking awesome. Uses hyperv but is turnkey) by default you hide docker container apps behined a virtual NAT so only the port you want exposed to your LAN is exposed If the app needs root in the container you can avoid having that app run on the host as root (YMMV as some apps need host root access and need to be run as privileged) the ability to use github, docker hub and docker hub autobuilds to auto build new version of the container when i change the config in github OR the underlying base image gets updated (still need to manually pull the image to update the container locally) note this doesn't work when doing multi-arch builds (like the one 'tag (aka image)' i have that supports 3 linux archs and now windows - just figiured that out!) ability to user docker desktop on windows to run linux containers on windows - freaking awesome ability to use thinsg like portainer to manage across hosts with a UI - what can i say i like UI - but setting up can be complexy Linux (and thus docker) has too many ways to do the same one thing - so this is a rathole project like HA here is my set of containers on my synology - let me know if you have more questions (note most of that CPU and RAM usage is not from docker but from a windows server VM i run on the synology VMM app.) (influxdb, grafana and unifipoller - oops not running - pull data from unifi network system and display pretty graphs; nginx is my secure reverse proxy for inbound ingress to my network,' portainer and agent are for managing with portainer and playing with things like docker swarm) Next-up maybe a polyglot container pre-loaded with a bunch of polyglot stuff, havent looked at polyglot since early v1 betas so need to refresh my knowledge - heck hadn't done anything to my ISY in maybe a year until the last firmware)

If you have docker running you might want to look at my image https://github.com/scyto/NodeLink or look at the dockerfile.linux and shell script to see how I installed it.

I created a docker for this thanks as always @io_guy for the breadcrumb trails. If you don't already know docker this is probably not for you. My full set of tags is as follows: scyto/nodelink:latest - dotNet 3.0.0 Core and nodelinkv10.x (linux/amd64 & arm32v7 & arm64 and windows/amd64) Linux Version For linux use the following command to run the container - replace $pwd% with path to your host mapped files as required (where nodelink will store its config).. docker run --name=NodeLink -v $PWD$:/NodeLink -p 8090:8090 scyto/nodelink Windows Version For windows use the following command to run the container -replace $pwd% with path to your host mapped files as required docker run --name=NodeLink -v $PWD$:C:\NodeLink -p 8090:8090 scyto/nodelink:latest Let me know if you find issues. You can bug them on the dev github branch. Dockerhub page here https://github.com/scyto/NodeLink/tree/Dev

locks seem to be working after setteling down after a couple of tries (remote lock / unlock / query features) I had a couple of light switches that were working now not seen at all, weird. will troubleshoot and now heal the network --edit -- and i spoke to soon, the schlage BE deadbolt is unresponsive; a couple of my jasco wall switches are unresponisve. I have attached log incase it helps, don't have more time tonight to look at this I wish UDI had a vendor database to allow for better identification of the device in UI' also the multistream support still leaves a lot to be desired as grouping is still imperfect. ISY-Events-Log.v5.0.13A__Mon 2018.07.16 19.59.13.txt

Elapsed 00:00:11.113 : Loading Variables Elapsed 00:00:11.355 : Loading Node Definitions Elapsed 00:00:12.481 : Loading Nodes Elapsed 00:00:15.743 : Creating Widgets Elapsed 00:00:18.202 : Creating Widgets Complete Mon 07/16/2018 19:15:04 : Starting Subscription Mon 07/16/2018 19:15:05 : Completing initialization Mon 07/16/2018 19:15:08 : Refreshing Status Mon 07/16/2018 19:15:08 : Refreshing Views Mon 07/16/2018 19:15:52 : [ZWAVE-RESTORE ] Restoring Z-Wave dongle using backup created on 2018-07-15 14:01:23 Mon 07/16/2018 19:16:03 : [ZWAVE-RESTORE ]: In programming mode Mon 07/16/2018 19:16:08 : [ZWAVE-RESTORE ] Failed to Restore Z-Wave dongle using backup created on 2018-07-15 14:01:23 Mon 07/16/2018 19:16:57 : [ 28 93 E7 1] ST 0 (uom=100 prec=0) Mon 07/16/2018 19:16:57 : [ 24 E2 3 1] ST 0 (uom=100 prec=0) Mon 07/16/2018 19:16:57 : [ 2A 2F ED 1] ST 0 (uom=100 prec=0) Mon 07/16/2018 19:16:57 : [ ZW002_1] ERR 1 Mon 07/16/2018 19:16:57 : [ ZW003_1] ERR 1 Mon 07/16/2018 19:16:57 : [ ZW004_1] ERR 1 Mon 07/16/2018 19:16:57 : [ ZW006_1] ERR 1 Mon 07/16/2018 19:16:57 : [ ZW046_1] ERR 1 Mon 07/16/2018 19:16:57 : [ ZW034_1] ERR 1 Mon 07/16/2018 19:16:57 : [ ZW037_1] ERR 1 Mon 07/16/2018 19:16:57 : [ ZW042_1] ERR 1 Mon 07/16/2018 19:17:21 : [ZWAVE-RESTORE ] Restoring Z-Wave dongle using backup created on 2018-07-15 14:01:23 Mon 07/16/2018 19:17:25 : [ZWAVE-RESTORE ]: In programming mode Mon 07/16/2018 19:17:45 : [ZWAVE-RESTORE ] Z-Wave dongle successfully restored using backup created on 2018-07-15 14:01:23 Mon 07/16/2018 19:17:45 : [ZWAVE ] Setting our application node info Mon 07/16/2018 19:17:45 : Restarting the Z-Wave dongle Mon 07/16/2018 19:18:01 : [ ZW044_104] ST 100 (uom=78 prec=0) Mon 07/16/2018 19:18:01 : [ ZW044_104] DON 100 (uom=78 prec=0) Mon 07/16/2018 19:18:02 : [ ZW044_104] DON 100 (uom=78 prec=0) Mon 07/16/2018 19:18:13 : [ 2A 2F D1 1] ST 0 (uom=100 prec=0) Mon 07/16/2018 19:18:14 : [ ZW013_143] TPW 12825 (uom=33 prec=3) Mon 07/16/2018 19:19:24 : [ ZW044_104] ST 0 (uom=78 prec=0) Mon 07/16/2018 19:19:24 : [ ZW044_104] DOF 0 (uom=78 prec=0) Mon 07/16/2018 19:21:00 : [ZW-TX-FAILED] enc=Fail uid=14.0 cmd=0x62.01 DOOR_LOCK Mon 07/16/2018 19:21:05 : [ZW-TX-FAILED] enc=Fail uid=14.0 cmd=0x62.01 DOOR_LOCK Mon 07/16/2018 19:21:10 : [ZW-TX-FAILED] enc=Fail uid=14.0 cmd=0x62.01 DOOR_LOCK Mon 07/16/2018 19:21:10 : [ ZW014_1] ERR 1 Mon 07/16/2018 19:21:17 : [ ZW014_1] ERR 0

The second attempt at restore worked. the first looked like this.... (i have no idea why it was querying the devices as i turned query at restart off - those missing devices are known missing devices)

Am i missing a trick - this unit doesn't have a connection point for the external antenna - is that correct? I hope it has better range than the old internal which was not capable in my house...