jimmywarting / wemo-client

JavaScript client library for controlling and subscribing to Wemo Devices
MIT License
132 stars 40 forks source link

Examples crash with Error: addMembership EHOSTUNREACH #46

Open m-altmeyer opened 7 years ago

m-altmeyer commented 7 years ago

First of all thank you so much for this great work! I just bought an Insight switch and wanted to try out your API but was not able to get the examples running. I tried 'insight.js' but always got the following error when calling wemo.discover(...):

Error: addMembership EHOSTUNREACH
    at exports._errnoException (util.js:1026:11)
    at Socket.addMembership (dgram.js:508:11)
    at addMembership ([***]\wemo-test\node_modules\node
-ssdp\lib\index.js:177:19)
    at Socket.onSocketListening ([***]\wemo-test\node_m
odules\node-ssdp\lib\index.js:173:5)
    at emitNone (events.js:91:20)
    at Socket.emit (events.js:185:7)
    at startListening (dgram.js:121:10)
    at dgram.js:228:7
    at _combinedTickCallback (internal/process/next_tick.js:77:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

The insight switch is in the same network as the PC running the example. Moreover I am able to control the switch using the official Wemo App. Do you have any idea what might cause this issue?

Thank you so much and all the best, Max

timonreinhard commented 7 years ago

Seems related to node-ssdp. Which OS are you running?

m-altmeyer commented 7 years ago

I am running on Windows 10

timonreinhard commented 7 years ago

Can you please try upgrading node-ssdp to the latest 2.9.0 (e.g. by bumping the version in package.json and then running npm update)? If that still doesn't help, I suppose you create an issue for node-ssdp.

m-altmeyer commented 7 years ago

Thank you for your fast reply. I updated to 2.9.0 but still get the same error. I'll raise an issue at node-ssdp and I think this one can be closed.

timonreinhard commented 7 years ago

Requires diversario/node-ssdp#66

jeffrey-cochran commented 7 years ago

If you're on Windows, you'll almost certainly need to install IIS. I had the same issue, and this fixed it. You can find a brief guide on installing it here.

Tip of the hat to Fullstack React authors, whose book I remembered saying something to this effect.