tomjmul / node-red-contrib-fake-wemo Goto Github PK

Any reason not to work with the author of the other node to fix that rather than add a new node?

Firstly thanks for fixing the install error, installed fine... Works fine but if i check my error log I am getting about 5 errors per second with the following:
[2019/3/6 11:40:10 Pool Pump:713] Unknown wemo request
[2019/3/6 11:40:10 Pool Pump:713] Unknown wemo request
[2019/3/6 11:40:10 Pool Pump:713] Unknown wemo request
[2019/3/6 11:40:10 Pool Pump:713] Unknown wemo request
[2019/3/6 11:40:10 Pool Pump:713] Unknown wemo request
[2019/3/6 11:40:10 Pool Pump:713] Unknown wemo request

Any ideas?

Sorry, I'm not an expert, I got this on a fresh nodered install :

npm WARN deprecated [email protected]: Use uuid module instead

> [email protected] install /home/pi/.node-red/node_modules/epoll
> node-gyp rebuild

make: Entering directory '/home/pi/.node-red/node_modules/epoll/build'
  CXX(target) Release/obj.target/epoll/src/epoll.o
In file included from ../node_modules/nan/nan.h:192:0,
                 from ../src/epoll.cc:15:
../node_modules/nan/nan_maybe_43_inl.h: In function ‘Nan::Maybe<bool> Nan::ForceSet(v8::Local<v8::Object>, v8::Local<v8::Value>, v8::Local<v8::Value>, v8::PropertyAttribute)’:
../node_modules/nan/nan_maybe_43_inl.h:112:15: error: ‘class v8::Object’ has no member named ‘ForceSet’
   return obj->ForceSet(isolate->GetCurrentContext(), key, value, attribs);
               ^~~~~~~~
In file included from ../src/epoll.cc:15:0:
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’:
../node_modules/nan/nan.h:835:60: warning: ‘v8::Local<v8:...

In moment all my existing nodes don't work anymore and new added nodes were not found from Alexa-app.

Alexa- app is showing "server doesn't respond" for every existing node.

Hi again, When i use the alexa app on an android phone to switch the node on, it shows on for a couple of seconds then status reverts back to off....If I look at the node in node-red I see that the node has a green on status and the node is actually on... to turn the node off I have to click "on" again on the app and very quickly click it to turn off again. I have not restarted node-red so this is not initial state. If i use voice to turn on the node.... the app display show that the switch is off....even though its actually on.