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.

I did some more diligent testing with one group of 3 insteon dimmers (two controlling load, one as secondary) controlled by a scene that syncs them all. The states of entities in the HA console do not change when I manually change switches and I see no events when listening to isy994_control in HA. Also i just discovered that in the ISY console the manually activated devices are not changing the status in the ISY console either. If I use the HA console to call an ISY scene, then all the ISY devices in that scene reflect their states correctly in HA. And have the right status in the ISY console too. I seen no events when listening to isy994_control in HS. The only events i am seeing in isy994_control are ones from my nodes servers. In the ISY event viewer. I see no on/off device events. unless i have forgotten how to use the event viewer - i have it set to level 3. --edits-- if i query the device in ISY console (say a light that shows as off that is actually on) then the ISY console shows correct status, but HA still shows as off. --edit2-- i just did a full restore PLM, that fixed it. I hate PLMs

I will have to keep digging HA just doesn’t even receive the device notification on the bus when devices are manually controlled. I will take a look at the beta integration. do I have to uninstall the built-in integration first?

I don’t see the events when I manually control the device, I wonder if it’s because I am on the latest ISY RC.... thanks for checking, I appreciate it.

You are right, I forgot that (I made my KPLs and automation over 5 years ago). Late last night I found the trick of using the HA.switch program folders, works really well. I use my ABCD buttons for four mutually exclusive scenes (so only A or B or C or D can be on at any one time) and using the variables trick meant I could replicate in HA. What’s great is how the intersection of the power of both systems is.

I see the KPL secondary buttons now appear as sensors, does this mean thus issue is now solved? I was disappointed the A B C D buttons don’t appear as switches in home assistant, any Idea why?

Another question, I can’t get state changes on Insteon devices to show in home assistant. I monitored isy994_control in the dev tools listener on HA. I see events from node servers but not from any Insteon devices. Any ideas?

Yes. I had got it working and was confused on my new HA node why it wasn't. In the 10 million things I did and forgot to write down i think at one point yes i made the filter before i added anything and i recall doing the yaml at one point. Will go play. I managed to get both ISY Zwave and new hass openzwave method all working together on the same z-wave network, not sure if thats best way to go or just have one unit do z-wave .... any opinions (I have waay more insteon than z-wave so the ISY isn't going anywhere and i don't like the amoun haas charges for alexa integration, the ISY integration has always worked really well) . Thanks for taking the time to think through the filtering, appreciate it. (oh BTW i kind of like some of my nodeservers make it through to HAAS too...)

Hi, i am new to HASS, just got the ISY integration working, trying to use the 'ignore string' to filter out devices in the ISY. For now trying to filter zwave devices. I have tried ZW {ZW} and {"ZW"} but none of these seems to filter out devices with ZW in their names. Any ideas what i am doing wrong?

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