Yann-Gaël Gautheron
Yann-Gaël Gautheron
Same problem here too... latest openzwave recompiled with gyp, but I don't know why OZW_Log.txt is showing good detections : 2015-03-22 22:31:18.650 Detail, Node027, Received: 0x01, 0x09, 0x00, 0x04, 0x00,...
I wonder if the message "rechecking" might be a clue...
A 25€ raspberry box and 5 watts is enough, i don't know why you want to use more power supply to handle a zwave daemon ?
2 options, maybe you can try to run a virtual box on your windows box to run the zwave daemon... or write your own/wait a windows node-openzwave support.
Does anyone found a solution on that ? I'm using ruby official code only because of this problem... and i don't like to code with ruby... :-/
Thank you very much for your answer, i'll try your libs !
I confirm : node-lifx is working properly.
> > Setting `keepAlive` to `false`, does not fix the issue. After some more debuging i figured out, that during the above scenario `this.#socket` is undefined when [`socket.disconnect`](https://github.com/redis/node-redis/blob/ac7d50c7313fe1158131e13b0e3b11d982697123/packages/client/lib/client/socket.ts#L230). Therefore the...
You mean faster than `Query.filter: Expression` ?