drmacro

Not sure... I changed the hostname of the pi I am running node-red on. The rest of my network handled this just fine. But, the ISY would not allow connections from node-red. I rebooted the ISY, I power cycled the ISY, I flushed the arp tables on the pi (I guess the tables get flushed on the ISY on a reboot? power cycle?) No go. When I changed the name back...all was good. The pi node-red flow could now connect to the ISY. ?

Ok, that's what I suspected. Thanks. It appears that I'll be moving my motion sensor inputs (contact closures from motion sensors in the driveway) to the raspberry pi, since 5.0.13 lost the ability to update the device status in the ISY when the contacts are closed on my Aeotec Micro Switch G2 and Enerwave ZWN-RSM1. I'll sense them from the pi and push a state variable to the ISY.

I don't remember ever seeing two controller nodes. Question: Does a flow need a ISY websocket node and, say, a device node? Or is just a device node required?

I finally messed around with the install and remove of the isy module that the nodes were disabled and would not remove. Not sure what I did to get it in a state where it wasn't usable and could not be un-installed in node-red. In any case, I re-built the pi SD card, installed node-red from the pi repository, then updated it to the latest, then installed the isy module. (left ISY at 5.0.13) It now seems to be behaving and not throwing the "var" errors. I guess I'll build some flows and see if I break it again...

They do.

So, I suppose, I need to open up WireShark to see what is sent? Cuz, the IP, user name, and password are the same. Since I'm using the node-red-contrib-isy library I don't get to see the header...at least I don't think I do.

Also, with 5.0.13 it appears to be rejecting or having a problem with inbound websocket subcriptions? Is there something that needs to be configured or enabled now (compared to 4.6.2)?

Ok, so I upgraded the ISY to 5.0.13. Same error. ?

Someone please correct me if I misunderstand the ISY firmware status. I know there are versions later than 4.6.2, but, none are released. Being un-released, I would need to update by downloading and forcing an update.

(I left an "issue" on your github, if you want contact me there, I might be able to help out some.) Output of http://<<ISY IP address>>/rest/vars/get/1: <vars> <var type="1" id="1"> <init>0</init> <val>0</val> <ts>20180704 20:34:02</ts> </var> <var type="1" id="2"> <init>0</init> <val>44</val> <ts>20180705 13:25:36</ts> </var> <var type="1" id="3"> <init>0</init> <val>0</val> <ts>20180704 20:34:02</ts> </var> <var type="1" id="4"> <init>0</init> <val>0</val> <ts>20180704 20:34:02</ts> </var> <var type="1" id="5"> <init>0</init> <val>0</val> <ts>20180704 20:34:02</ts> </var> <var type="1" id="6"> <init>0</init> <val>0</val> <ts>20180708 22:00:01</ts> </var> <var type="1" id="7"> <init>0</init> <val>1</val> <ts>20180709 06:39:29</ts> </var> <var type="1" id="8"> <init>0</init> <val>1</val> <ts>20180709 06:39:29</ts> </var> </vars> Output of http://<<ISY IP address>>/rest/vars/get/2: <vars> <var type="2" id="1"> <init>0</init> <val>0</val> <ts>20180709 06:39:29</ts> </var> <var type="2" id="2"> <init>0</init> <val>0</val> <ts>20180704 20:34:02</ts> </var> <var type="2" id="3"> <init>0</init> <val>0</val> <ts>20180704 20:34:02</ts> </var> </vars> Hmm...it might be my in experience with node-red, but I have no node to add a "catch" to. The configuration node is there, but I see no way to add a catch. It also gets into a mode where it sees the error described and then attempts to reconnect every two seconds. So if there is a place to put the catch, it still doesn't stop the network traffic with the reconnects.

Interestingly, I removed the module after removing all nodes from my flow/s. And it still was attempting to connect to the controller and throwing the error. I found the an un-used controller node listed (it is apparently added magically by the install or the module...not sure) forced it to delete. Then I restarted and no more attempt to create a websocket. I currently have left the module out (while I tinker with GPIO input/control for other parts of this project), because it trying to re-connect every two seconds makes the debug tab unusable.

Well, deleting any/all ISY nodes does not make it go away and it still connects a web socket to the ISY944. The node red console window last few lines shows AFTER the flow is deployed. Note there are no ISY nodes, of any kind, in the flow. I poked around in the "Manage palette" and noticed that there is a way to disable nodes. But, it says the isy-controller is in use and won't allow it to be disabled. In the config tab of the dashboard sidebar, it shows the isy-controller on all flows and unused. So, it appears, isy-controller is there even though I'm not using it. Is this something I've done accidentally?

Yes, and the debug window from mine displays the exact same message. I'm not near the thing at the moment but, I can screen shot mine tomorrow.

In fact, after going through your video frame by frame, the same error message can be seen at 23:04. At first I wondered if this was just the ISY Websocket node, but, it happens for the web socket, device, and variables nodes. Yet, it still connects and gets/sets values/devices. It appears to be something with the return from the actual socket subscribe.

As you note, the link seems to be missing...but, I did find it on youtube. And I've watched it...twice, maybe more. I could have missed something though, the video is pretty small for old eyes. I'm am able to control devices, so it must be connected, right? The error doesn't seem to stop that, it just throw's that error each time it connects. I assume something is different in the payload string. I checked the firmware on the ISY944 and it is the same you have.