Home Automation Domotica Forum Europe, Bwired Forum

I found out what the problem is, otmonitor requires the origin header to be set. Weirdly enough it doesn't matter what you set it to as long as it's not empty. This .js code works fine: var socket = new ws(node.path, { origin: "localhost" }); And the result in the command line is as follow...

I'm building a solution where I am using Node-Red, a flow-based programming tool for wiring together hardware devices to talk to a number of sensors and to otmonitor. Node-Red offers a way to connect to websockets but for some reason it does not connect to otmonitor. Node-Red is based on node.js and...