search

QNimbus / node-red-contrib-openhab-v2

MIT License
9 stars 3 forks source link

Connection Error #10

Closed bkmar1192 closed 3 years ago

bkmar1192 commented 5 years ago

I am periodically getting the following error (I think it started after upgrading to OpenHAB 2.4 but can't 100% confirm). The node will register events fine but every now and then I get the following error in the log and it delays the update.

type: Error: connection ended at IncomingMessage. (/Users/familymartin/.node-red/node_modules/@joeybaker/eventsource/lib/eventsource.js:133:28) at emitNone (events.js:111:20) at IncomingMessage.emit (events.js:208:7) at endReadableNT (_stream_readable.js:1064:12) at _combinedTickCallback (internal/process/next_tick.js:139:11) at process._tickCallback (internal/process/next_tick.js:181:9) }

QNimbus commented 5 years ago

I am experiencing the same issue after the 2.4 upgrade. I also get some occasional errors in the OpenHAB log with regard to SSE. (Server side events, which is what the eventsource library is for)

In the meantime I went back to 2.4M6 which was the build that was working flawlessly for me until I figure out what the issue is.

bkmar1192 commented 5 years ago

Can you give me pointers to going back to 2.4M6? Is it just:

sudo runtime/bin/update 2.4.0.M6

QNimbus commented 5 years ago

@bkmar1192 I am using Docker containers myself, so downgrading was as easy as specifying a different image to run as container.

I suggest you look through the official OpenHAB documentation (Community forum link) to find the right way to downgrade your OpenHAB instance for now.

I will try to figure out if I can resolve the issue by using a different EventSource library for my node-red nodes. Will try to keep you updated through this thread.