bwp91/homebridge-wemo

Homebridge plugin to integrate Wemo devices into HomeKit.

Hey 👋

For more information about me, please visit my sponsor page.

homebridge-wemo's Issues

Wemo CoffeeMaker Implementation

Hello,

Thank you for your work on this plugin! I have a Wemo CoffeeMaker among other Wemo devices. I understand it is not supported by this plugin. However, my Homebridge log is filled with "[Wemo] [CoffeeMaker] [urn:Belkin:device:CoffeeMaker:1] is unsupported but feel free to create a GitHub issue." Is it possible to disable this from being logged?

Ignored Devices

In the new version I don't see a way to ignore devices. In the previous version I ignored all newer Wemos that are HK compatible out of the box. I would like to do that again but don't see how to do it. Thanks.

WeMo BridgeWemoWARNING[192.168.1.96] connection error: could not find correct port for device.

What issue do you have? Please be as thorough and explicit as possible.

This error keeps on showing in the log and it involves in different wemo devices

Details of your setup.

• Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?

Hoobs

• Which version of Homebridge/HOOBS do you have?

4.1.22

• Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.

Hoobs Box

• Which version of this plugin (homebridge-wemo) do you have? Has the issue started since upgrading from a previous version?

4.7.0

• Which Wemo devices do you have that are causing issues? Please include product models if applicable.

Wemo 3-way switch
Wemo Light switch
Wemo Light Dimmer switch

Please paste any relevant logs below.

2/15/2022, 6:52:54 PMWeMo BridgeWemoWARNING[192.168.1.141] connection error: could not find correct port for device.
2/15/2022, 6:54:43 PMWeMo BridgeWemoWARNING[192.168.1.141] connection error: could not find correct port for device.
2/15/2022, 6:54:46 PMWeMo BridgeWemoWARNING[192.168.1.30] connection error: could not find correct port for device.
2/15/2022, 6:59:16 PMWeMo BridgeWemoWARNING[192.168.1.30] connection error: could not find correct port for device.
2/15/2022, 7:04:52 PMWeMo BridgeWemoWARNING[192.168.1.30] connection error: could not find correct port for device.
2/15/2022, 7:05:12 PMWeMo BridgeWemoWARNING[192.168.1.195] connection error: could not find correct port for device.
2/15/2022, 7:09:20 PMWeMo BridgeWemoWARNING[192.168.1.30] connection error: could not find correct port for device.
2/15/2022, 7:12:23 PMWeMo BridgeWemoWARNING[192.168.1.176] connection error: could not find correct port for device.
2/15/2022, 7:12:40 PMWeMo BridgeWemoWARNING[192.168.1.30] connection error: could not find correct port for device.
2/15/2022, 7:13:16 PMWeMo BridgeWemoWARNING[192.168.1.30] connection error: could not find correct port for device.
2/15/2022, 7:14:05 PMWeMo BridgeWemoWARNING[192.168.1.176] connection error: could not find correct port for device.
2/15/2022, 7:14:05 PMWeMo BridgeWemoWARNING[192.168.1.176] connection error: could not find correct port for device.
2/15/2022, 7:14:08 PMWeMo BridgeWemoWARNING[192.168.1.30] connection error: could not find correct port for device.
2/15/2022, 7:14:08 PMWeMo BridgeWemoWARNING[192.168.1.30] connection error: could not find correct port for device.
2/15/2022, 7:18:44 PMWeMo BridgeWemoWARNING[192.168.1.176] connection error: could not find correct port for device.
2/15/2022, 7:18:44 PMWeMo BridgeWemoWARNING[192.168.1.81] connection error: could not find correct port for device.
2/15/2022, 7:18:47 PMWeMo BridgeWemoWARNING[192.168.1.30] connection error: could not find correct port for device.
2/15/2022, 7:20:22 PMWeMo BridgeWemoWARNING[192.168.1.195] connection error: could not find correct port for device.
2/15/2022, 7:22:23 PMWeMo BridgeERROR[WeMo Bridge 8C36@On] The write handler for the characteristic 'On' on the accessory 'Laundry Lights Wemo Smart Light Switch 3-Way' was slow to respond!
2/15/2022, 7:22:29 PMWeMo BridgeERROR[WeMo Bridge 8C36@On] The write handler for the characteristic 'On' on the accessory 'Laundry Lights Wemo Smart Light Switch 3-Way' didn't respond at all!. Please check that you properly call the callback!
2/15/2022, 7:22:29 PMWeMo BridgeWemoWARNING[Laundry Lights Wemo Smart Light Switch 3-Way] sending update failed as a connection timeout occurred.
2/15/2022, 7:22:37 PMWeMo BridgeERROR[WeMo Bridge 8C36@On] The write handler for the characteristic 'On' on the accessory 'Laundry Lights Wemo Smart Light Switch 3-Way' was slow to respond!
2/15/2022, 7:22:43 PMWeMo BridgeERROR[WeMo Bridge 8C36@On] The write handler for the characteristic 'On' on the accessory 'Laundry Lights Wemo Smart Light Switch 3-Way' didn't respond at all!. Please check that you properly call the callback!
2/15/2022, 7:22:43 PMWeMo BridgeWemoWARNING[Laundry Lights Wemo Smart Light Switch 3-Way] sending update failed as a connection timeout occurred.
2/15/2022, 7:24:49 PMWeMo BridgeWemoWARNING[192.168.1.30] connection error: could not find correct port for device.
2/15/2022, 7:24:49 PMWeMo BridgeWemoWARNING[192.168.1.30] connection error: could not find correct port for device.
2/15/2022, 7:26:17 PMWeMo BridgeWemoWARNING[192.168.1.30] connection error: could not find correct port for device.
2/15/2022, 7:26:17 PMWeMo BridgeWemoWARNING[192.168.1.30] connection error: could not find correct port for device.
2/15/2022, 7:26:26 PMWeMo BridgeWemoWARNING[192.168.1.26] connection error: could not find correct port for device.
2/15/2022, 7:26:31 PMWeMo BridgeWemoWARNING[192.168.1.30] connection error: could not find correct port for device.
2/15/2022, 7:26:32 PMWeMo BridgeWemoWARNING[192.168.1.30] connection error: could not find correct port for device.
2/15/2022, 7:26:39 PMWeMo BridgeWemoWARNING[192.168.1.195] connection error: could not find correct port for device.
2/15/2022, 7:34:11 PMWeMo BridgeWemoWARNING[192.168.1.30] connection error: could not find correct port for device.
2/15/2022, 7:34:11 PMWeMo BridgeWemoWARNING[192.168.1.30] connection error: could not find correct port for device.
2/15/2022, 7:43:58 PMWeMo BridgeWemoWARNING[192.168.1.141] connection error: could not find correct port for device.
2/15/2022, 7:44:08 PMWeMo BridgeWemoWARNING[192.168.1.30] connection error: could not find correct port for device.
2/15/2022, 7:50:03 PMWeMo BridgeERROR[WeMo Bridge 8C36@On] The write handler for the characteristic 'On' on the accessory 'Laundry Lights Wemo Smart Light Switch 3-Way' was slow to respond!

Wemo Maker must be triggered as accessory in Homebridge before it works in Apple Home

What issue do you have? Please be as thorough and explicit as possible.

My Wemo Maker appears as not responding in Apple Home. However it works fine as an accessory in Homebridge. In fact, once I use it once as an accessory, in this case to open/close my garage door it then works fine in Apple Home and the not responding message disappears from there.

Details of your setup.

• Do you use Homebridge (with config-ui?) or HOOBS?
  Homebridge with config-ui

• Which version of Homebridge/HOOBS do you have?
  v.1.4.0

• Which version of this plugin (homebridge-wemo) do you have? Has the issue started since upgrading from a previous version?
  homebridge-wemo v4.5.4

• Which Wemo devices do you have that are causing issues? Please include product models if applicable.
  Wemo Maker
  WeMo_WW_2.00.11423.PVT-OWRT-Maker
  Hardware version v1

Please paste any relevant logs below.

There is nothing in the logs other than it starts successfully.

[25/01/2022, 13:35:23] Homebridge v1.4.0 (HAP v0.10.0) (Homebridge 1688) is running on port 51305.
[25/01/2022, 13:35:24] [Wemo] [Garage] initialising with options {"logging":"standard"}.
[25/01/2022, 13:35:24] [Wemo] [Garage] initialised with s/n 221444S0000200 and ip/port 192.168.1.5:49153
[25/01/2022, 13:35:24] [Wemo] [Garage] http has been established.
[25/01/2022, 13:35:25] [Wemo] ✓ Setup complete. Join the plugin's Discord community! https://discord.gg/cMGhNtZ3tW
[25/01/2022, 13:37:31] [Wemo] [Garage] current state [on].
[25/01/2022, 13:38:04] [Wemo] [Garage] current state [off].
[25/01/2022, 13:38:17] [Wemo] [Garage] current state [on].

Config (I tried to setup as Garage door and didn't resolve issue)
{
"name": "Wemo",
"mode": "auto",
"debug": false,
"discoveryInterval": 60,
"upnpInterval": 600,
"disableUPNP": true,
"makerTypes": [
{
"label": "Garage",
"makerType": "garageDoor",
"makerTimer": 10
}
],
"platform": "Wemo"
},

Ignored Devices function is gone

I used to use the Ignored devices function but now it is gone so is there another way to disable devices as I found this feature was useful to me but I can't speak for other users

• Is your feature request related to a problem? Please describe.

• Any particular Wemo devices that this relates to?

• Anything else?

Wemo plugs and switches reseting themselves

I'm not sure this issue is specific to this plugin or just a issue with wemo devices in general i have lots of wemo devices and some plug that are usually on most of the time reset and turn off in the middle of the night also some times the light switches i have will reset just after they turn on. I only though of this may be causing it because i used to have my wemo devices in home assistant as well until i realized a lot of devices in my home would reset every minute or so, like they were getting to many requests from each platform for what ever reason but every couple of nights i have the same devices shut off overnight I'm guessing because they have reset themselves

Remove HomeKit Native Accessory

What issue do you have? Please be as thorough and explicit as possible.

I connected my Wemo Outlet to HomeKit and set it as a purifier type and it works. The problem is that both the outlet and purifier are visible on HomeKit.

Config File:

{
    "name": "Wemo",
    "mode": "auto",
    "wemoOutlets": [
        {
            "label": "Wemo Air Purifier",
            "serialNumber": "M1BAB133D73106",
            "showAs": "purifier",
            "manualIP": "<removed>"
        }
    ],
    "platform": "Wemo"
}

Details of your setup.

• Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
  Homebridge UI-X

• Which version of Homebridge/HOOBS do you have?
  v1.3.4

• Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
  Raspberry Pi

• Which version of this plugin (homebridge-wemo) do you have? Has the issue started since upgrading from a previous version?
  v4.1.4

• Which Wemo devices do you have that are causing issues? Please include product models if applicable.
  Wemo smart plug 2nd generation

Please paste any relevant logs below.

Belkin Wemo platform plugin error

So I tried following process for my devices namely; wemo switches, cree bulbs on Hue bridge and MyQ garage door opener.

It was not loading and giving some errors so I bought an app called homebridge from the apple store and used it. It successfully did the initial install but is not good enough to configure it fully. In that process it probably have installed its own version and now I have multiple wemo platform installs as well as config.json. I tried to copy a config.json which I checked on jsonlint.com and shows no error. Still I get the following. Can someone help?

[6/3/2017, 2:20:34 AM] Warning: skipping plugin found at '/usr/lib/node_modules/homebridge-platform-wemo' since we already loaded the same plugin from '/usr/local/lib/node_modules/homebridge-platform-wemo'.
[6/3/2017, 2:20:34 AM] Loaded plugin: homebridge-gpio
[6/3/2017, 2:20:34 AM] Registering accessory 'homebridge-gpio.GPIO'
[6/3/2017, 2:20:34 AM] ---
[6/3/2017, 2:20:34 AM] Loaded plugin: homebridge-gpio-relay
[6/3/2017, 2:20:34 AM] Registering accessory 'homebridge-gpio-relay.relay'
[6/3/2017, 2:20:34 AM] ---
[6/3/2017, 2:20:34 AM] Loaded plugin: homebridge-gpio-shutter
[6/3/2017, 2:20:34 AM] Registering accessory 'homebridge-gpio-shutter.shutter'
[6/3/2017, 2:20:34 AM] ---
[6/3/2017, 2:20:34 AM] Loaded plugin: homebridge-harmonyhub
[6/3/2017, 2:20:35 AM] Registering platform 'homebridge-harmonyhub.HarmonyHub'
[6/3/2017, 2:20:35 AM] ---
[6/3/2017, 2:20:36 AM] Loaded plugin: homebridge-people
[6/3/2017, 2:20:36 AM] Registering accessory 'homebridge-people.people'
[6/3/2017, 2:20:36 AM] ---
[6/3/2017, 2:20:37 AM] Loaded plugin: homebridge-platform-wemo
[6/3/2017, 2:20:37 AM] Registering platform 'homebridge-platform-wemo.BelkinWeMo'
[6/3/2017, 2:20:37 AM] ---
[6/3/2017, 2:20:37 AM] Loaded plugin: homebridge-rcswitch-gpiomem
[6/3/2017, 2:20:37 AM] Registering accessory 'homebridge-rcswitch-gpiomem.RcSwitch'
[6/3/2017, 2:20:37 AM] ---
[6/3/2017, 2:20:37 AM] Loaded plugin: homebridge-suncalc
[6/3/2017, 2:20:37 AM] Registering accessory 'homebridge-suncalc.Suncalc'
[6/3/2017, 2:20:37 AM] ---
[6/3/2017, 2:20:37 AM] Loaded plugin: homebridge-telldus
[6/3/2017, 2:20:37 AM] Registering platform 'homebridge-telldus.Telldus'
[6/3/2017, 2:20:37 AM] ---
[6/3/2017, 2:20:37 AM] Loaded plugin: homebridge-wol
[6/3/2017, 2:20:37 AM] Registering accessory 'homebridge-wol.Computer'
[6/3/2017, 2:20:37 AM] ---
[6/3/2017, 2:20:38 AM] Loaded plugin: homebridge-hue
[6/3/2017, 2:20:38 AM] Registering platform 'homebridge-hue.Hue'
[6/3/2017, 2:20:38 AM] ---
[6/3/2017, 2:20:38 AM] Loaded plugin: homebridge-liftmaster2
[6/3/2017, 2:20:38 AM] Registering platform 'homebridge-liftmaster2.LiftMaster2'
[6/3/2017, 2:20:38 AM] ---
[6/3/2017, 2:20:39 AM] Loaded plugin: homebridge-myq
[6/3/2017, 2:20:39 AM] Registering platform 'homebridge-myq.MyQ'
[6/3/2017, 2:20:39 AM] ---
[6/3/2017, 2:20:39 AM] Loaded config.json with 0 accessories and 3 platforms.
[6/3/2017, 2:20:39 AM] ---
[6/3/2017, 2:20:39 AM] Loading 3 platforms...
/usr/local/lib/node_modules/homebridge/lib/api.js:122
throw new Error("The requested platform '" + name + "' was not registered by any plugin.");
^

Error: The requested platform 'BelkinWemo' was not registered by any plugin.
at API.platform (/usr/local/lib/node_modules/homebridge/lib/api.js:122:13)
at Server._loadPlatforms (/usr/local/lib/node_modules/homebridge/lib/server.js:284:45)
at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:80:36)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:40:10)
at Object. (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Function.Module.runMain (module.js:441:10)
at startup (node.js:134:18)
at node.js:962:3

======

My config.json is:

{
"bridge": {
"name": "Homebridge",
"username": "CD:22:3D:E3:CE:52",
"port": 51826,
"pin": "031-45-505"
},

"platforms": [
{
"platform": "BelkinWemo",
"name": "WeMo Platform",
"Expected_Accessories": "2"
},
{
"platform": "PhilipsHue",
"name": "PHue",
"lights": true
},
{
"platform": "LiftMaster2",
"username": "[email protected]",
"password": "password"
}]

}

location for config.json
pi@mypi:~/.homebridge $ locate config.json
/boot/os_config.json
/home/pi/.homebridge/config.json
/home/pi/Downloads/config.json.txt
/root/.homebridge/config.json
/root/.homebridge/config.json.old
/root/homebridge/node-v4.3.2-linux-armv6l/lib/node_modules/npm/node_modules/node-gyp/gyp/buildbot/commit_queue/cq_config.json
/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/buildbot/commit_queue/cq_config.json
/usr/local/lib/node_modules/homebridge-gpio/sample-config.json
/usr/local/lib/node_modules/homebridge-gpio-relay/sample-config.json
/usr/local/lib/node_modules/homebridge-telldus/config.json
/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/buildbot/commit_queue/cq_config.json

Error running homebridge-wemo

Hi, I'm really new to all of node.js and npm, yesterday I had an issue with another homebridge plugin (but this worked fine) so I updated my node and npm versions and now i'm having trouble with this plugin, the error code is attached below, please help. Thank you

any help is greatly appreciated! thank you.

Homebridge-wemo errors.pdf

Existing Wemo Plugs on Reboot of Homebridge Error

What issue do you have? Please be as thorough and explicit as possible.

I have existing plugs, if those plugs are offline and Homebridge is restarted, the plugin attempts to reconnect (which is awesome), but when the plugs are brought back online, the plugin does not find them until the bridge is restarted.
This DOES NOT happen if I unplug and replug the unit in while Homebridge is running.

It appears that perhaps the IP address is not known for the system to attempt reconnect if the device is offline when Homebridge is first booted up.

Details of your setup.

• Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
  Homebridge UI-X

• Which version of Homebridge/HOOBS do you have?
  1.3.4

• Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
  Raspberry Pi 4
  Node.js = 14.17.4
  NPM = 6.14.14

• Which version of this plugin (homebridge-wemo) do you have? Has the issue started since upgrading from a previous version?
  Version is 4.0.0 and appears to be an issue with the NEW plugin I do not remember seeing this with the old plugin.

• Which Wemo devices do you have that are causing issues? Please include product models if applicable.
  Wemo Mini : Model F7C063 (4 of them, and they all fail)

Please paste any relevant logs below.

Errors are "[device name] awaiting (re)connection and will retry in 30s."

Home app changes freeze homebridge and/or homebridge-wemo plugin

What issue do you have? Please be as thorough and explicit as possible.

After initial discovery of wemos and display in the Homekit Home app, any subsequent change to a device, such as placing it in a specific room name, causes all logging (and apparently activity) in homebridge and/or the plugin to freeze. Simultaneousley, all bridge accessories disappear from the Home app. Restarting homebridge successfully rediscovers all wemos and the bridge with its accessories reappear in Homekit.

Details of your setup.

• Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?

I'm running a freshly installed Homebridge UI-X on MacOS 10.14.6 (Mojave). There is ONLY the homebridge-wemo plugin installed.

• Which version of this plugin (homebridge-wemo) do you have? Has the issue started since upgrading from a previous version?

homebridge-config-ui-x v4.41.5
homebridge-wemo v4.5.1
node -v -> v16.13.1
npm -v -> 8.1.2

My previous system, running MUCH older versions of both homebridge and homebridge-wemo ran for 3 or 4 years without any issues until yesterday for the same wemos. All wemo devices are exactly the same as before moving to the newer version and all work perfectly with the Belkin app. These are: 1 Wemo Link with 5 bulbs + 2 Wemo Smart Plugs.

No iOS versions have changed.

• Which Wemo devices do you have that are causing issues? Please include product models if applicable.

The issue appears to be coming from the Home app / Homekit... but "homebridge-wemo" is the ONLY plugin.

Please paste any relevant logs below.

I have turned on all logging I can find, including running "homebridge -D" in a shell. I can find no apparently relevant messages, since whatever Home app action (particularly setting up rooms) causes the log activity to stop and all bridge hub wemos to disappear.

Since I can find no good info in the log, I randomly change some settings for the plugin, such as increasing timeouts and and temporarily disabling UPnP. The Mac is on wired ethernet, so I forced binding to "en0". Nothing changed with any of these different settings. One thing I find in these settings that I do not understand is "UPNP Callback IP/Port" of 192.168.1.13:2021. There is no such IP address on my network, and the field is read-only, so I can't change it.

It's a good, solid, and fast network.

For what it's worth, below is an example of what comes out when I restart homebridge (in the UI) after losing all entries in the Home app. Logging is turned on for the plugin.

[0;37m[12/27/2021, 5:18:48 PM] �[0m�[0;36m[Homebridge UI]�[0m Changes to config.json saved.
�[0;37m[12/27/2021, 5:18:48 PM] �[0m�[0;36m[Homebridge UI]�[0m [homebridge-wemo] Terminating child process...
�[0;37m[12/27/2021, 5:18:48 PM] �[0m�[0;36m[Homebridge UI]�[0m [homebridge-wemo] Child process ended
�[0;37m[12/27/2021, 5:18:51 PM] �[0m�[0;36m[Homebridge UI]�[0m Homebridge restart request received
�[0;37m[12/27/2021, 5:18:51 PM] �[0m�[0;36m[Homebridge UI]�[0m UI / Bridge settings have not changed; only restarting Homebridge process
�[0;37m[12/27/2021, 5:18:51 PM] �[0m�[0;36m[Homebridge UI]�[0m Sending SIGTERM to Homebridge
�[37m[12/27/2021, 5:18:51 PM] �[39mGot SIGTERM, shutting down Homebridge...
�[37m[12/27/2021, 5:18:51 PM] �[39m�[36m[Wemo]�[39m SSDP client gracefully stopped.
�[37m[12/27/2021, 5:18:51 PM] �[39m�[36m[Wemo]�[39m Listener server gracefully closed.
�[37m[12/27/2021, 5:18:56 PM]�[0m �[36m[HB Supervisor]�[0m Homebridge Process Ended. Code: 143, Signal: null
�[37m[12/27/2021, 5:19:01 PM]�[0m �[36m[HB Supervisor]�[0m Restarting Homebridge...
�[37m[12/27/2021, 5:19:01 PM]�[0m �[36m[HB Supervisor]�[0m Starting Homebridge with extra flags: -I
�[37m[12/27/2021, 5:19:01 PM]�[0m �[36m[HB Supervisor]�[0m Started Homebridge v1.3.8 with PID: 7959
�[37m[12/27/2021, 5:19:01 PM] �[39mLoaded config.json with 0 accessories and 2 platforms.
�[37m[12/27/2021, 5:19:01 PM] �[39mLoaded 5 cached accessories from cachedAccessories.
�[37m[12/27/2021, 5:19:01 PM] �[39m---
�[37m[12/27/2021, 5:19:02 PM] �[39mLoaded plugin: [email protected]
�[37m[12/27/2021, 5:19:02 PM] �[39mRegistering platform 'homebridge-config-ui-x.config'
�[37m[12/27/2021, 5:19:02 PM] �[39m---
�[37m[12/27/2021, 5:19:02 PM] �[39mLoaded plugin: [email protected]
�[37m[12/27/2021, 5:19:02 PM] �[39mRegistering platform 'homebridge-wemo.Wemo'
�[37m[12/27/2021, 5:19:02 PM] �[39m---
�[37m[12/27/2021, 5:19:02 PM] �[39mLoading 2 platforms...
�[37m[12/27/2021, 5:19:02 PM] �[39m�[36m[Config]�[39m Initializing config platform...
�[37m[12/27/2021, 5:19:02 PM] �[39m�[36m[Config]�[39m Running in Service Mode
�[37m[12/27/2021, 5:19:02 PM] �[39m�[36m[Wemo]�[39m Initializing Wemo platform...
�[37m[12/27/2021, 5:19:02 PM] �[39m�[36m[Wemo]�[39m Initialising plugin v4.5.1 | Node v16.13.1 | HB v1.3.8...
�[37m[12/27/2021, 5:19:02 PM] �[39m�[36m[Wemo]�[39m Plugin initialised. Setting up accessories....
Setup Payload:
X-HM://0023OA632ZDE8
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
�[30m�[47m                       �[49m�[39m
�[30m�[47m    ┌────────────┐     �[49m�[39m
�[30m�[47m    │ 123-45-678 │     �[49m�[39m
�[30m�[47m    └────────────┘     �[49m�[39m
�[30m�[47m                       �[49m�[39m
�[37m[12/27/2021, 5:19:02 PM] �[39mHomebridge v1.3.8 (HAP v0.9.7) (Homebridge AE01) is running on port 51012.
�[37m[12/27/2021, 5:19:02 PM] �[39m�[36m[Wemo]�[39m Listener server port [62753].
�[37m[12/27/2021, 5:19:02 PM] �[39m�[36m[Wemo]�[39m [Bedroom Switch] initialising with options {"logging":"debug","showAs":"outlet"}.
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Bedroom Switch] initialised with s/n 221510K110065A and ip/port 192.168.1.192:49153
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Bedroom Switch] http has been established.
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Bedroom Switch] [urn:Belkin:service:basicevent:1] initial subscription for service.
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Bedroom Switch] upnp has been established.
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Living Room Switch] initialising with options {"logging":"debug","showAs":"outlet"}.
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Living Room Switch] initialised with s/n 221451K11003D2 and ip/port 192.168.1.191:49153
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Living Room Switch] http has been established.
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Living Room Switch] [urn:Belkin:service:basicevent:1] initial subscription for service.
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Living Room Switch] upnp has been established.
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Bedroom Switch] receiving update [BinaryState: 0].
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Bedroom Switch] current state [off].
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Gooseneck] initialising with options {"adaptiveLightingShift":0,"brightnessStep":1,"logging":"debug","transitionTime":0}.
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Gooseneck] initialised with s/n 94103EF6BF427ED0 and ip/port 192.168.1.190:49153.
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Bedroom Light] initialising with options {"adaptiveLightingShift":0,"brightnessStep":1,"logging":"debug","transitionTime":0}.
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Bedroom Light] initialised with s/n 1640616639 and ip/port 192.168.1.190:49153.
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Living Room Light] initialising with options {"adaptiveLightingShift":0,"brightnessStep":1,"logging":"debug","transitionTime":0}.
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Living Room Light] initialised with s/n 1640616723 and ip/port 192.168.1.190:49153.
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [WeMo Link] initialised with s/n 231450B01001A4 and ip/port 192.168.1.190:49153
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [WeMo Link] http has been established.
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [WeMo Link] [urn:Belkin:service:basicevent:1] initial subscription for service.
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [WeMo Link] [urn:Belkin:service:bridge:1] initial subscription for service.
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [WeMo Link] upnp has been established.
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Bedroom Switch] incoming notification:
<e:propertyset xmlns:e="urn:schemas-upnp-org:event-1-0">
<e:property>
<BinaryState>0</BinaryState>
</e:property>
</e:propertyset>
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Bedroom Switch] receiving update [BinaryState: 0].
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Living Room Switch] incoming notification:
<e:propertyset xmlns:e="urn:schemas-upnp-org:event-1-0">
<e:property>
<BinaryState>0</BinaryState>
</e:property>
</e:propertyset>
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Living Room Switch] receiving update [BinaryState: 0].
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Living Room Switch] current state [off].
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [WeMo Link] incoming notification:
<e:propertyset xmlns:e="urn:schemas-upnp-org:event-1-0">
<e:property>
<BinaryState>0</BinaryState>
</e:property>
</e:propertyset>
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [WeMo Link] incoming notification:
<e:propertyset xmlns:e="urn:schemas-upnp-org:event-1-0">
<e:property>
<TimeSyncRequest>0</TimeSyncRequest>
</e:property>
</e:propertyset>
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [WeMo Link] incoming notification:
<e:propertyset xmlns:e="urn:schemas-upnp-org:event-1-0">
<e:property>
<StatusChange></StatusChange>
</e:property>
<e:property>
<SubDeviceFWUpdateStatus></SubDeviceFWUpdateStatus>
</e:property>
</e:propertyset>
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [WeMo Link] incoming notification:
<e:propertyset xmlns:e="urn:schemas-upnp-org:event-1-0">
<e:property>
<TimeZoneNotification>005</TimeZoneNotification>
</e:property>
</e:propertyset>
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Living Room Switch] receiving update [BinaryState: 0].
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Gooseneck] current state [off].
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Gooseneck] current brightness [100%].
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Bedroom Light] current state [off].
�[37m[12/27/2021, 5:19:03 PM] �[39m�[36m[Wemo]�[39m [Bedroom Light] current brightness [100%].
�[37m[12/27/2021, 5:19:04 PM] �[39m�[36m[Wemo]�[39m [Living Room Light] current state [on].
�[37m[12/27/2021, 5:19:04 PM] �[39m�[36m[Wemo]�[39m [Living Room Light] current brightness [100%].
�[37m[12/27/2021, 5:19:04 PM] �[39m�[36m[Wemo]�[39m ✓ Setup complete. Interested in sponsoring this plugin? https://github.com/sponsors/bwp91
�[0;37m[12/27/2021, 5:34:09 PM] �[0m�[0;36m[Homebridge UI]�[0m [homebridge-wemo] Terminating child process...
�[0;37m[12/27/2021, 5:34:09 PM] �[0m�[0;36m[Homebridge UI]�[0m [homebridge-wemo] Child process ended

wemo motion sensor

Hi,
could you please add wemo motion sensor to this plugin?
the wemo platform crashed more often than this plugin due to wemo lost connection

3-way switch issues

What issue do you have? Please be as thorough and explicit as possible.

When using Siri to turn on the light that is a 3-way Wemo switch the switch will toggle twice in very short succession, causing the light not to turn on/off. You can hear it switch toggle twice when this occurs and sometimes the switch will show as being on/off in Homebridge even though the light is not on/off. You then need to toggle the light on/off again to get it back in sync with what Homebridge and HomeKit think the light status is. Sometimes this needs to be done multiple times.

Details of your setup.

• Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
  Homebridge UI

• Which version of Homebridge/HOOBS do you have?
  Homebridge 1.4

• Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
  Synology APK
  Node.js v16.13.2
  NPM v6.14.15

• Which version of this plugin (homebridge-wemo) do you have? Has the issue started since upgrading from a previous version?

homebridge-wemo v4.7.2

• Which Wemo devices do you have that are causing issues? Please include product models if applicable.

WeMo_WW_2.00.11563.PVT-OWRT-LIGHTV2
Lightswitch v3

Please paste any relevant logs below.

Cant find Wemo Switches on Pi

I have two home bridge servers, both on Wired LAN (same LAN) one is a MAC one is a Pi 3 (Im trying to migrate to the PI from the iMAC).

I have a Wemo Switch and a Wemo insight switch, on the MAC it discovers the devices no problems, on the Pi it can't find the devices. All other accessories and platforms have no issues.

iMAC

"[9/15/2016, 12:15:01 PM] [Living Room Speakers] Initializing Sonos accessory...
[9/15/2016, 12:15:01 PM] [Kitchen Speakers] Initializing Sonos accessory...
[9/15/2016, 12:15:01 PM] [Kitchen Fan] Initializing WeMo accessory...
[9/15/2016, 12:15:01 PM] [Kitchen Fan] Searching for WeMo device with exact name 'Kitchen Fan'...
[9/15/2016, 12:15:01 PM] [outside lights] Initializing WeMo accessory...
[9/15/2016, 12:15:01 PM] [outside lights] Searching for WeMo device with exact name 'outside lights'...
[9/15/2016, 12:15:01 PM] [Kitchen Fan] Found 'Kitchen Fan' device at 192.168.1.227
[9/15/2016, 12:15:01 PM] [Living Room Speakers] Found a playable coordinator device at 192.168.1.189 in zone 'Living Room' for accessory 'Living Room Speakers' in accessory room 'Living Room'
[9/15/2016, 12:15:02 PM] [Harmony Hub] Fetching Logitech Harmony activities...
[9/15/2016, 12:15:02 PM] [outside lights] Found 'outside lights' device at 192.168.1.173
[9/15/2016, 12:15:02 PM] [Harmony Hub] Fetching Logitech Harmony activities...
"

Pi on the same network,

[9/15/2016, 11:17:35 AM] [Kitchen Fan] Error finding device 'Kitchen Fan': WeMoSearchTimeoutError
[9/15/2016, 11:17:35 AM] [Kitchen Fan] Continuing search for WeMo device with exact name 'Kitchen Fan'...
[9/15/2016, 11:17:35 AM] [outside lights] Error finding device 'outside lights': WeMoSearchTimeoutError
[9/15/2016, 11:17:35 AM] [outside lights] Continuing search for WeMo device with exact name 'outside lights'...
[9/15/2016, 11:17:40 AM] [Kitchen Fan] Error finding device 'Kitchen Fan': WeMoSearchTimeoutError
[9/15/2016, 11:17:40 AM] [Kitchen Fan] Continuing search for WeMo device with exact name 'Kitchen Fan'...
[9/15/2016, 11:17:40 AM] [outside lights] Error finding device 'outside lights': WeMoSearchTimeoutError
[9/15/2016, 11:17:40 AM] [outside lights] Continuing search for WeMo device with exact name 'outside lights'...
[9/15/2016, 11:17:45 AM] [Kitchen Fan] Error finding device 'Kitchen Fan': WeMoSearchTimeoutError
[9/15/2016, 11:17:45 AM] [Kitchen Fan] Continuing search for WeMo device with exact name 'Kitchen Fan'...
[9/15/2016, 11:17:45 AM] [outside lights] Error finding device 'outside lights': WeMoSearchTimeoutError
[9/15/2016, 11:17:45 AM] [outside lights] Continuing search for WeMo device with exact name 'outside lights'.

Siri in iOS 13 responds "that feature is not available..." when trying to turn on/off a wemo outlet

After I installed iOS 13 recently, I noticed that I can no longer use Siri to turn on/off my Wemo outlets. She responds with phrases like:

"Hmm, that feature is not available for the <outlet name>"
"Hmm, the <outlet name> does not support that action"

I have tried specifying the outlets using a large variety of ways. The only thing that works is if I specify "turn on/off the <room name>". That is only useful when there's only 1 device in that room though.

I talked to Apple about this and they said to make sure my WeMo app is up to date (which it is). The outlet firmware is up to date as well. Perhaps there's some new device communication protocol? I just checked and I've got [email protected], which appears to be current...

TypeError: Cannot read property 'device' of undefined

Just started getting this today:

Mar 13 19:18:35 raspberrypi homebridge[321]: events.js:141
Mar 13 19:18:35 raspberrypi homebridge[321]: throw er; // Unhandled 'error' event
Mar 13 19:18:35 raspberrypi homebridge[321]: ^
Mar 13 19:18:35 raspberrypi homebridge[321]: TypeError: Cannot read property 'device' of undefined
Mar 13 19:18:35 raspberrypi homebridge[321]: at /usr/local/lib/node_modules/homebridge-wemo/node_modules/wemo/wemo.js:28:31
Mar 13 19:18:35 raspberrypi homebridge[321]: at Parser. (/usr/local/lib/node_modules/homebridge-wemo/node_modules/wemo/node_modules/xml2js/lib/xml 2js.js:483:18)
Mar 13 19:18:35 raspberrypi homebridge[321]: at emitOne (events.js:77:13)
Mar 13 19:18:35 raspberrypi homebridge[321]: at Parser.emit (events.js:169:7)
Mar 13 19:18:35 raspberrypi homebridge[321]: at Object.onclosetag (/usr/local/lib/node_modules/homebridge-wemo/node_modules/wemo/node_modules/xml2js/lib/xml2 js.js:444:26)
Mar 13 19:18:35 raspberrypi homebridge[321]: at emit (/usr/local/lib/node_modules/homebridge-wemo/node_modules/wemo/node_modules/xml2js/node_modules/sax/lib/ sax.js:639:35)
Mar 13 19:18:35 raspberrypi homebridge[321]: at emitNode (/usr/local/lib/node_modules/homebridge-wemo/node_modules/wemo/node_modules/xml2js/node_modules/sax/ lib/sax.js:644:5)
Mar 13 19:18:35 raspberrypi homebridge[321]: at closeTag (/usr/local/lib/node_modules/homebridge-wemo/node_modules/wemo/node_modules/xml2js/node_modules/sax/ lib/sax.js:903:7)
Mar 13 19:18:35 raspberrypi homebridge[321]: at Object.write (/usr/local/lib/node_modules/homebridge-wemo/node_modules/wemo/node_modules/xml2js/node_modules/ sax/lib/sax.js:1436:13)
Mar 13 19:18:35 raspberrypi homebridge[321]: at Parser.exports.Parser.Parser.parseString (/usr/local/lib/node_modules/homebridge-wemo/node_modules/wemo/node_ modules/xml2js/lib/xml2js.js:502:31)
Mar 13 19:18:35 raspberrypi homebridge[321]: at Parser.parseString (/usr/local/lib/node_modules/homebridge-wemo/node_modules/wemo/node_modules/xml2js/lib/xml 2js.js:7:59)
Mar 13 19:18:35 raspberrypi homebridge[321]: at Object.exports.parseString (/usr/local/lib/node_modules/homebridge-wemo/node_modules/wemo/node_modules/xml2js /lib/xml2js.js:534:19)
Mar 13 19:18:35 raspberrypi homebridge[321]: at Request._callback (/usr/local/lib/node_modules/homebridge-wemo/node_modules/wemo/wemo.js:26:12)
Mar 13 19:18:35 raspberrypi homebridge[321]: at Request.self.callback (/usr/local/lib/node_modules/homebridge-wemo/node_modules/request/request.js:198:22)
Mar 13 19:18:35 raspberrypi homebridge[321]: at emitTwo (events.js:87:13)
Mar 13 19:18:35 raspberrypi homebridge[321]: at Request.emit (events.js:172:7)

New red plug symbol suddenly appeared

Since the last Eve app update to vers. 5.4.3 suddenly I see a red plug symbol in the "Power off/on" line. Eve support says it is a warning symbol there is no plug in the Belkin Wemo Insight Switch. But it was and is plugged for years. Eve support says also take the plug out, wait a minute and set it in would help. But it don´t.

To make it clear. Everything works as usual. No problems with the combination Homebridge / wemo plugin / Eve app. Only the red plug symbol appears which give no sense.

Homebridge: 1.4.0
homebridge-wemo: v4.7.1
iOS: 15.3.1

Unupdateable switches

Hi Ive found a issue not with the plugin as such but i have a couple of wemo switches that i just opened recenly so the firmware is ancient before the move to cloud service for wemo, so i cant get them to connect to the wemo app or update the firmware for them, it sets up the switch and names it but it never shows up in the app so i tried manually adding it to this plugin and although it adds it its named "plugin light switch device" and the second one i added gets named the same thing so only one shows in homekit at once and when homebridge resets any changes that i make to it gets reverted back to what it was originally, im guessing this is because there is no cloud aspect to it, any chance there is something i could do so it doesnt reset it to a new device every time homebridge resets?

Wemo Devices work in Homebridge but show as "No Response" in Home App

I don't believe this is a plugin issue but here is my problem. I am running the latest homebridge and wemo plugin version on a raspberry pi. Everything looks good in homebridge. I can turn on/off my 3 devices. When I add the devices to the home app, they seem ok for a few minutes and then I get the dreaded "No Response" on all devices. I've tried resetting all the devices, the raspberry pi, and my iPhone 12. I've removed the devices from the app then re-added them and I get the same behavior. I don't know what else to do. Also, the devices work correctly in the wemo app. The 3 wemo devices are all homekit compatible but since I don't have a homekit hub (ipad, apple tv), I am using the homebridge app as my hub.

Info: Plugin does not recognize node.js version

I am running Node.js version v16.13.1

Homebridge-wemo plugin shows this in logs:
The plugin "homebridge-wemo" requires Node.js version of ^14.18.3 || ^16.13.2 which does not satisfy the current Node.js version of v16.13.1. You may need to upgrade your installation of Node.js

Not sure if this would cause issues at some point.

Plugin crashes Homebridge

Occasionally (every few hours or every couple of days) the wemo plugin crashes Homebridge with the following output:

/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:11
throw new Error("This callback function has already been called by someone else; it can only be called one time.");
^

Error: This callback function has already been called by someone else; it can only be called one time.
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:11:13
at WeMoAccessory. (/usr/local/lib/node_modules/homebridge-wemo/index.js:77:7)
at /usr/local/lib/node_modules/homebridge-wemo/node_modules/wemo/wemo.js:110:5
at ClientRequest. (/usr/local/lib/node_modules/homebridge-wemo/node_modules/wemo/wemo.js:99:4)
at emitOne (events.js:77:13)
at ClientRequest.emit (events.js:169:7)
at Socket.socketCloseListener (_http_client.js:240:9)
at emitOne (events.js:82:20)
at Socket.emit (events.js:169:7)
at TCP._onclose (net.js:469:12)

Wemo BridgeWARNUNG unhandled rejection: Error: Request failed with status code 500

What issue do you have? Please be as thorough and explicit as possible.

Since latest update I'm receiving following Warning
16.8.2021, 07:16:56Wemo Bridge WARNUNG unhandled rejection: Error: Request failed with status code 500

Details of your setup.

• Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
  Hoobs

• Which version of Homebridge/HOOBS do you have?
  Hoobs 4.0.100

• Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
  Raspberry 4.8
  Node 14.17.5
  Homebridge Version 1.3.4

• Which version of this plugin (homebridge-wemo) do you have? Has the issue started since upgrading from a previous version?

4.1.1

• Which Wemo devices do you have that are causing issues? Please include product models if applicable.
  I can't tell which of my WEMOs causing this WARNING, as it don't say exactly what the issue is

Please paste any relevant logs below.

16.8.2021, 19:18:47wemobridge stopping
16.8.2021, 19:18:52Wemo Bridge starting
16.8.2021, 19:18:55Wemo BridgeLoaded plugin 'homebridge-wemo'
16.8.2021, 19:18:55Wemo BridgeLoading 1 platforms...
16.8.2021, 19:18:55Wemo BridgeWemoInitialising plugin v4.1.1 | Node v14.17.5 | HB v1.3.4 | HOOBS v4...
16.8.2021, 19:18:55Wemo BridgeWemoPlugin initialised. Setting up accessories....
16.8.2021, 19:18:55Wemo BridgeBridge is running on port 51836.
16.8.2021, 19:18:55Wemo BridgeWemo[Blumensäule WZ Wemo] initialising with options {"logging":"standard","showAs":"outlet"}.
16.8.2021, 19:18:55Wemo BridgeWemo[Blumensäule WZ Wemo] initialised with s/n 221403K1101830 and ip/port 192.168.0.113:49153
16.8.2021, 19:18:55Wemo BridgeWemo[Blumensäule WZ Wemo] http has been established.
16.8.2021, 19:18:55Wemo BridgeWemo[Blumensäule WZ Wemo] upnp has been established.
16.8.2021, 19:18:55Wemo BridgeWemo[Gartenlicht Garage Wemo] initialising with options {"logging":"standard","showAs":"outlet"}.
16.8.2021, 19:18:55Wemo BridgeWemo[Gartenlicht Garage Wemo] initialised with s/n 221304K11000AD and ip/port 192.168.0.105:49153
16.8.2021, 19:18:55Wemo BridgeWemo[Gartenlicht Garage Wemo] http has been established.
16.8.2021, 19:18:55Wemo BridgeWemo[Gartenlicht Garage Wemo] upnp has been established.
16.8.2021, 19:18:55Wemo BridgeWemo[Blumensäule WZ Wemo] current state [off].
16.8.2021, 19:18:55Wemo BridgeWemo[Gartenlicht Garage Wemo] current state [off].
16.8.2021, 19:18:55Wemo BridgeWemo[OG Yoga Zimmer Ambiente] initialising with options {"adaptiveLightingShift":0,"brightnessStep":1,"logging":"standard","transitionTime":0}.
16.8.2021, 19:18:55Wemo BridgeWemo[OG Yoga Zimmer Ambiente] initialised with s/n 94103EF6BF427018 and ip/port 192.168.0.173:49153.
16.8.2021, 19:18:55Wemo BridgeWemo[Terrasse] initialising with options {"adaptiveLightingShift":0,"brightnessStep":1,"logging":"standard","transitionTime":0}.
16.8.2021, 19:18:55Wemo BridgeWemo[Terrasse] initialised with s/n 94103EF6BF42D754 and ip/port 192.168.0.173:49153.
16.8.2021, 19:18:55Wemo BridgeWemo[UG Katzentreppe] initialising with options {"adaptiveLightingShift":0,"brightnessStep":1,"logging":"standard","transitionTime":0}.
16.8.2021, 19:18:55Wemo BridgeWemo[UG Katzentreppe] initialised with s/n 94103EF6BF42E807 and ip/port 192.168.0.173:49153.
16.8.2021, 19:18:55Wemo BridgeWemo[WZ Stehlampe Leselicht] initialising with options {"adaptiveLightingShift":0,"brightnessStep":1,"logging":"standard","transitionTime":0}.
16.8.2021, 19:18:55Wemo BridgeWemo[WZ Stehlampe Leselicht] initialised with s/n 94103EA2B2789161 and ip/port 192.168.0.173:49153.
16.8.2021, 19:18:55Wemo BridgeWemo[EG Bistro] initialising with options {"adaptiveLightingShift":0,"brightnessStep":1,"logging":"standard","transitionTime":0}.
16.8.2021, 19:18:55Wemo BridgeWemo[EG Bistro] initialised with s/n 94103EA2B278BF75 and ip/port 192.168.0.173:49153.
16.8.2021, 19:18:55Wemo BridgeWemo[WeMo Link] initialised with s/n 231448B01004D8 and ip/port 192.168.0.173:49153
16.8.2021, 19:18:55Wemo BridgeWemo[WeMo Link] http has been established.
16.8.2021, 19:18:55Wemo BridgeWemo[WeMo Link] upnp has been established.
16.8.2021, 19:18:55Wemo BridgeWemo[OG Yoga Zimmer Ambiente] initialising with options {"adaptiveLightingShift":0,"brightnessStep":1,"logging":"standard","transitionTime":0}.
16.8.2021, 19:18:55Wemo BridgeWemo[OG Yoga Zimmer Ambiente] initialised with s/n 94103EF6BF427018 and ip/port 192.168.0.173:49153.
16.8.2021, 19:18:55Wemo BridgeWemo[Terrasse] initialising with options {"adaptiveLightingShift":0,"brightnessStep":1,"logging":"standard","transitionTime":0}.
16.8.2021, 19:18:55Wemo BridgeWemo[Terrasse] initialised with s/n 94103EF6BF42D754 and ip/port 192.168.0.173:49153.
16.8.2021, 19:18:55Wemo BridgeWemo[UG Katzentreppe] initialising with options {"adaptiveLightingShift":0,"brightnessStep":1,"logging":"standard","transitionTime":0}.
16.8.2021, 19:18:55Wemo BridgeWemo[UG Katzentreppe] initialised with s/n 94103EF6BF42E807 and ip/port 192.168.0.173:49153.
16.8.2021, 19:18:55Wemo BridgeWemo[WZ Stehlampe Leselicht] initialising with options {"adaptiveLightingShift":0,"brightnessStep":1,"logging":"standard","transitionTime":0}.
16.8.2021, 19:18:55Wemo BridgeWemo[WZ Stehlampe Leselicht] initialised with s/n 94103EA2B2789161 and ip/port 192.168.0.173:49153.
16.8.2021, 19:18:55Wemo BridgeWemo[EG Bistro] initialising with options {"adaptiveLightingShift":0,"brightnessStep":1,"logging":"standard","transitionTime":0}.
16.8.2021, 19:18:55Wemo BridgeWemo[EG Bistro] initialised with s/n 94103EA2B278BF75 and ip/port 192.168.0.173:49153.
16.8.2021, 19:18:55Wemo BridgeWemo[WeMo Link] initialised with s/n 231448B01004D8 and ip/port 192.168.0.173:49153
16.8.2021, 19:18:55Wemo BridgeWemo[WeMo Link] http has been established.
16.8.2021, 19:18:55Wemo BridgeWemo[WeMo Link] upnp has been established.
16.8.2021, 19:18:56Wemo BridgeWemo[OG Yoga Zimmer Ambiente] current brightness [15%].
16.8.2021, 19:18:56Wemo BridgeWemo[Terrasse] current state [off].
16.8.2021, 19:18:56Wemo BridgeWemo[Terrasse] current brightness [11%].
16.8.2021, 19:18:56Wemo BridgeWemo[UG Katzentreppe] current state [off].
16.8.2021, 19:18:56Wemo BridgeWemo[UG Katzentreppe] current brightness [100%].
16.8.2021, 19:18:56Wemo BridgeWemo[WZ Stehlampe Leselicht] current state [off].
16.8.2021, 19:18:56Wemo BridgeWemo[WZ Stehlampe Leselicht] current brightness [100%].
16.8.2021, 19:18:57Wemo BridgeWemo[EG Bistro] current state [off].
16.8.2021, 19:18:57Wemo BridgeWemo[EG Bistro] current brightness [100%].
16.8.2021, 19:18:57Wemo BridgeWemo[OG Yoga Zimmer Ambiente] current state [off].
16.8.2021, 19:18:57Wemo BridgeWemo[OG Yoga Zimmer Ambiente] current brightness [15%].
16.8.2021, 19:18:57Wemo BridgeWemo✓ Setup complete. Thanks for using this plugin, I hope you find it helpful!
16.8.2021, 19:18:57Wemo BridgeWemo[Terrasse] current state [off].
16.8.2021, 19:18:57Wemo BridgeWemo[Terrasse] current brightness [11%].
16.8.2021, 19:18:57Wemo BridgeWemo[UG Katzentreppe] current state [off].
16.8.2021, 19:18:57Wemo BridgeWemo[UG Katzentreppe] current brightness [100%].
16.8.2021, 19:18:58Wemo BridgeWemo[WZ Stehlampe Leselicht] current state [off].
16.8.2021, 19:18:58Wemo BridgeWemo[WZ Stehlampe Leselicht] current brightness [100%].
16.8.2021, 19:18:58Wemo BridgeWemo[EG Bistro] current state [off].
16.8.2021, 19:18:58Wemo BridgeWemo[EG Bistro] current brightness [100%].
16.8.2021, 19:19:00Wemo BridgeWARNUNGunhandled rejection: Error: Request failed with status code 500
16.8.2021, 19:19:01Wemo BridgeWARNUNGunhandled rejection: Error: Request failed with status code 500

WeMoSearchTimeoutError

I can't get home bridge to recognize my old wemo. Here is the error I get:

[1/29/2019, 5:02:17 AM] [the front] Continuing search for WeMo device with exact name 'the front'...
[1/29/2019, 5:02:22 AM] [the front] Error finding device 'the front': WeMoSearchTimeoutError

Here is my config file:

{
"bridge": {
"name": "Homebridge",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},
"description": "This is an example configuration file. You can use this as a template for creating your own configuration file containing devices you actually own.",
"accessories": [
{
"accessory": "WeMo",
"description": "the front",
"name": "the front",
"ip": "192.168.1.165"
}
],
"platforms": [
{
"name": "Config",
"port": 8080,
"auth": "form",
"theme": "blue",
"tempUnits": "f",
"platform": "config"
},
{
"platform": "BelkinWeMo",
"name": "WeMo Platform",
"timeout": "25"
}
]
}

Let me know if more info is required. I have these 2 plugins installed:

WeMo Platform plugin for homebridge - Blubs, Switches and Insight Switches Supported
homebridge-platform-wemo v1.3.8

wemo plugin for homebridge:
homebridge-wemo v0.0.2

I can ping the Demo in question.

Terminal stopped being able to find WeMos

my WeMo switches are successfully connected to my ipod touch with the app. On my mac, the terminal goes on forever saying this:

[Monitor] Error finding device 'M': WeMoSearchTimeoutError
[Monitor] Continuing search for WeMo device with exact name 'M'...

I have tried changing the name in the app and the config.json but it won't work. Please, somebody help!

Pull details from different subnet

I have two Homebridge installs with one for my home and the second for an apartment that is on a different VLAN/subnet from the main house. The plugin sees the Wemo devices on my network immediately but when I install the plugin on the apartment homebridge it doesn't since it is on a different subnet. From the apartment VLAN I'm able to communicate with the items on the main network so there isn't a connectivity issue.

What I'm looking for is the ability to have the plugin poll the other network.

eg: Main 10.10.0.1/24, Apt 10.10.1.1/24
Apt HB Wemo plugin scan 10.10.0.1/24 for devices.

I know I'm a very small corner case, but it sure would be nice to be able to specify the network to scan for devices.

pywemo virtual device error message

Log repeatedly reports reports

[Wemo] [pywemo virtual device] [urn:Belkin:device:switch:1] is unsupported but feel free to create a GitHub issue.

Details of your setup.

(1) Homebridge UI-X

• Which version of Homebridge/HOOBS do you have?
  1.3.4

• Which platform do you run Homebridge/HOOBS on
  Raspberry Pi
  Node.js Version | v14.17.5
  Npm v6.14.14

• Which version of this plugin (homebridge-wemo) do you have? Has the issue started since upgrading from a previous version?
  Move from old version 3.x to v4.1.3 and now have this

Which Wemo devices do you have that are causing issues? Please include product models if applicable.
4 first edition UK sockets
1 Wemo Maker

[Wemo] [pywemo virtual device] [urn:Belkin:device:switch:1] is unsupported but feel free to create a GitHub issue.

Cannot read config file properly

Error: Parse error on line 14:
... "WeMo", "name": 'Test', "descript
----------------------^
Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'undefined'

Crockpot - receiving update failed

[02/06/2022, 21:17:14] [Homebridge UI] Homebridge log truncated by admin.
[02/06/2022, 21:17:23] [Wemo] [Slow Cooker] receiving update failed as Invalid value passed at default.externalModeUpdate (file:///usr/local/lib/node_modules/homebridge-wemo/lib/device/crockpot.js:350:17).

No more power consumption bars in the Eve app

Hi.

Yesterday I switched to to the new home base "homebridge-wemo". I processed the shift from "homebridge-platform-wemo" exactly according to the instructions in your readme. And everything worked fine. No problems. I thought.

My "homebridge-wemo" config:
{
"name": "Belkin WeMo",
"mode": "auto",
"wemoInsights": [
{
"label": "Waschmaschine",
"serialNumber": "xxx",
"wattDiff": 2,
"timeDiff": 30
}
],
"platform": "Wemo"
}

I only add the "label"-line to the new config.

Problem:
Since then I see no more power consumption bars in the Eve app. The line hangs at 0 watts.

But the washing machine is definitely in use.

What I´ve done:

• today updated to homebridge-wemo v4.1.0
• take the Wemo Insight Switch out the power outlet, wait 20 sec. and plug it in again

Any ideas what I could do?

NO QR code for Wemo Bridge

What issue do you have? Please be as thorough and explicit as possible.

I was having issues with the latest version of your Wemo Plugin due to my Hoobs version being 4.0. (I was getting an error saying that the plugin may be unstable due to the version of Hoobs I was running.)

I updated to Hoobs v. 4.1.21 (Homebridge Version 1.3.9), uninstalled the Wemo Bridge and Plugin, cleared the cache of the Hoobs, rebooted my Hoobs and reinstalled the Wemo Bridge and Plug-in. However, when I went to the bridge, I did not have a QR code to scan for Homekit under pairing. (Prior to this, I had a QR code for this bridge.) All of my other bridges have QR codes in the same location.

Furthermore, as soon as the Wemo Bridge was installed (even though I could not link it to my Homekit), I started getting the following error for all of my other bridges:

WARNING unhandled rejection: SyntaxError: Unexpected token u in JSON at position 0

I have since uninstalled the Wemo Bridge and Plug-in due to this error and the instability they were creating with my other bridges.

I would love to fix this, as I was very happy using the Wemo bridge until recently.

Details of your setup.

• Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?

HOOBS

• Which version of Homebridge/HOOBS do you have?

Hoobs 4.1.21

• Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.

Hoobs Box
Node Version 16.13.1

• Which version of this plugin (homebridge-wemo) do you have? Has the issue started since upgrading from a previous version?

The latest version (v. 4.5.3) // Yes.

• Which Wemo devices do you have that are causing issues? Please include product models if applicable.

Two switches, two outlets

Please paste any relevant logs below.

1/6/2022, 1:33:37 PMPlatform Orbit BridgeWARNINGunhandled rejection: SyntaxError: Unexpected token u in JSON at position 0
1/6/2022, 1:33:37 PMAugust Smart Locks BridgeWARNINGunhandled rejection: SyntaxError: Unexpected token u in JSON at position 0
1/6/2022, 1:33:37 PMRing BridgeWARNINGunhandled rejection: SyntaxError: Unexpected token u in JSON at position 0

No consumption data since update to iOS / ATV OS 15.4.1

No consumption data shown or visible since update of all iPhones to iOS 15.4.1 and ATVs to 15.4.1. Just a flat line. Nothing changed on Homebridge or in config file. Homebridge and plugin up to date.

Another Apple side issue besides geolocations that no longer work? Have to wait for iOS 15.4.2?

wemo crockpot

Finally upgraded from the old wemo-platform

the crockpot is no longer working correctly, often showing no reponse. only the "warm" mode see to be set correctly.

[02/03/2022, 20:48:16] [Wemo] [Slow Cooker] initialised with s/n 221515S0000358 and ip/port 192.168.0.160:49153
[02/03/2022, 20:48:16] [Wemo] [Slow Cooker] http has been established.
[02/03/2022, 20:48:16] [Wemo] [Slow Cooker] upnp has been established.
[02/03/2022, 20:49:38] [Wemo] [HeaterA] current temperature [21°C].
[02/03/2022, 20:49:40] [Wemo] [HeaterA] current temperature [22°C].
[02/03/2022, 20:49:49] [Wemo] [undefined] BinaryState could not be processed as accessory.control.receiveDeviceUpdate is not a function at connectionHTTP.receiveDeviceUpdate (/usr/local/lib/node_modules/homebridge-wemo/lib/connection/http.js:111:33).
[02/03/2022, 20:49:53] [Wemo] [undefined] BinaryState could not be processed as accessory.control.receiveDeviceUpdate is not a function at connectionHTTP.receiveDeviceUpdate (/usr/local/lib/node_modules/homebridge-wemo/lib/connection/http.js:111:33).
[02/03/2022, 20:49:55] [Wemo] [HeaterA] current temperature [21°C].
[02/03/2022, 20:49:56] [Wemo] [undefined] BinaryState could not be processed as accessory.control.receiveDeviceUpdate is not a function at connectionHTTP.receiveDeviceUpdate (/usr/local/lib/node_modules/homebridge-wemo/lib/connection/http.js:111:33).
[02/03/2022, 20:49:57] [Wemo] [HeaterA] current temperature [22°C].
[02/03/2022, 20:50:00] [Wemo] [HeaterA] current temperature [21°C].
[02/03/2022, 20:50:03] [Wemo] [HeaterA] current temperature [22°C].
[02/03/2022, 20:50:06] [Wemo] [HeaterA] current temperature [21°C].
[02/03/2022, 20:50:16] [Wemo] [Slow Cooker] current mode [warm].
[02/03/2022, 20:50:26] [Wemo] [undefined] BinaryState could not be processed as accessory.control.receiveDeviceUpdate is not a function at connectionHTTP.receiveDeviceUpdate (/usr/local/lib/node_modules/homebridge-wemo/lib/connection/http.js:111:33).
[02/03/2022, 20:50:46] [Wemo] [Slow Cooker] current mode [off].
[02/03/2022, 20:50:50] [Wemo] [Slow Cooker] current timer [0:00].
[02/03/2022, 20:50:50] [Wemo] [Slow Cooker] current mode [warm].
[02/03/2022, 20:50:51] [Wemo] [undefined] BinaryState could not be processed as accessory.control.receiveDeviceUpdate is not a function at connectionHTTP.receiveDeviceUpdate (/usr/local/lib/node_modules/homebridge-wemo/lib/connection/http.js:111:33).
[02/03/2022, 20:50:53] [Wemo] [Slow Cooker] current mode [low].
[02/03/2022, 20:50:53] [Wemo] [undefined] BinaryState could not be processed as accessory.control.receiveDeviceUpdate is not a function at connectionHTTP.receiveDeviceUpdate (/usr/local/lib/node_modules/homebridge-wemo/lib/connection/http.js:111:33).
[02/03/2022, 20:50:53] [Wemo] [Slow Cooker] current timer [3:00].
[02/03/2022, 20:50:54] [Wemo] [undefined] BinaryState could not be processed as accessory.control.receiveDeviceUpdate is not a function at connectionHTTP.receiveDeviceUpdate (/usr/local/lib/node_modules/homebridge-wemo/lib/connection/http.js:111:33).
[02/03/2022, 20:51:01] [Wemo] [Slow Cooker] current mode [high].
[02/03/2022, 20:51:02] [Wemo] [undefined] BinaryState could not be processed as accessory.control.receiveDeviceUpdate is not a function at connectionHTTP.receiveDeviceUpdate (/usr/local/lib/node_modules/homebridge-wemo/lib/connection/http.js:111:33).
[02/03/2022, 20:51:13] [Wemo] [Slow Cooker] current timer [0:00].
[02/03/2022, 20:51:13] [Wemo] [Slow Cooker] current mode [off].
[02/03/2022, 20:51:13] [Wemo] [undefined] BinaryState could not be processed as accessory.control.receiveDeviceUpdate is not a function at connectionHTTP.receiveDeviceUpdate (/usr/local/lib/node_modules/homebridge-wemo/lib/connection/http.js:111:33).
[02/03/2022, 20:51:25] [Wemo] [undefined] BinaryState could not be processed as accessory.control.receiveDeviceUpdate is not a function at connectionHTTP.receiveDeviceUpdate (/usr/local/lib/node_modules/homebridge-wemo/lib/connection/http.js:111:33).
[02/03/2022, 20:51:28] [Wemo] [undefined] BinaryState could not be processed as accessory.control.receiveDeviceUpdate is not a function at connectionHTTP.receiveDeviceUpdate (/usr/local/lib/node_modules/homebridge-wemo/lib/connection/http.js:111:33).
[02/03/2022, 20:51:32] [Wemo] [undefined] BinaryState could not be processed as accessory.control.receiveDeviceUpdate is not a function at connectionHTTP.receiveDeviceUpdate (/usr/local/lib/node_modules/homebridge-wemo/lib/connection/http.js:111:33).

Can’t Dim Wemo bulbs

What issue do you have? Please be as thorough and explicit as possible.

Was working fine but recent update seems to have stopes ability to dim bulbs (still works in wemo app) and can turn them on and off.

Details of your setup.

• Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
  Homebridge UI-X

• Which version of Homebridge/HOOBS do you have?
  V1.3.9

• Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
  RPi
  Node 16.13.1

• Which version of this plugin (homebridge-wemo) do you have? Has the issue started since upgrading from a previous version?
  V4.5.3

• Which Wemo devices do you have that are causing issues? Please include product models if applicable.

Wemo bulbs

Please paste any relevant logs below.

Motion Sensor

Hi and Thaks for developing this pluging. I have a question about how does motion sensor works with homebridge.

My main question is if motion sensor sends information when detects triggering motion to homebridge plugin or if homebridge plugin is scanning sensor´s activity periodically.

It is coz i want to develop my own motion sensors, and it seems that wemo works with upnp and soap.

Thank you for your atention. Best Regards

High CPU on macOS

What issue do you have? Please be as thorough and explicit as possible.

With homebridge-wemo installed, process homebridge runs at 100% CPU.

With it disabled, process homebridge idles at < 1% CPU.

Details of your setup.

• Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?

• Which version of Homebridge/HOOBS do you have?

HomeBridge 1.3.8

• Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.

macOS Mojave - Mac mini server. Node 16.13.1, Npm 8.1.2.

• Which version of this plugin (homebridge-wemo) do you have? Has the issue started since upgrading from a previous version?

I previously used homebridge-wemo-platform. Now on 4.4.0 of homebridge-wemo.

• Which Wemo devices do you have that are causing issues? Please include product models if applicable.

Can't Make Outlet Show As Air Purifier

What issue do you have? Please be as thorough and explicit as possible.

I am using the "outlet" options section as with the old version and trying to turn my outlets into air purifiers. The log shows the "ShowAs" is still "outlet" even though the options say Air Purifier.

Details of your setup.

• Do you use Homebridge (with config-ui?) or HOOBS?

Homebridge

• Which version of Homebridge/HOOBS do you have?

1.3.4

• Which version of this plugin (homebridge-wemo) do you have? Has the issue started since upgrading from a previous version?

3.4.1. I just moved over from the old plugin, which worked fine.

• Which Wemo devices do you have that are causing issues? Please include product models if applicable.

Wemo outlet, v1 and v2

Please paste any relevant logs below.

What’s the reason behind the name change?

What’s the reason behind the name change? Is there functionality that the old plugin couldn’t provide due to its name, or a limitation in that plugin that required moving to a plugin with a new name?

According to the notice on the homebridge-platform-wemo page the process of moving to the new plugin requires a decent amount of effort from the end users:

If you are already using homebridge-platform-wemo you should consider moving to homebridge-wemo. You will need to reconfigure your HomeKit accessories from scratch - including their names, rooms, scenes and automations.

… but there’s no explanation about the reasons that prompted the name change which requires this effort from the end users.

A name change is entirely within your rights as an uncompensated developer and maintainer of this plugin, but that change does lead to a not insignificant amount of work for all the users of this plugin if they want to stay current, so it’d be useful to have some insight into the reasons that led to the change.

Wemo Coffee Maker implementation?

Is it a possibility to add a coffeemaker to this?

exception while setting power state

[Coperta] Setting power state on the 'Coperta' to 1
[Coperta] Error setting power state to 1 on the 'Coperta'
[Coperta] WARNING: setBinaryState called its callback more than once! Discarding the second one.
[Coperta] Error setting power state to 1 on the 'Coperta'
/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:11
      throw new Error("This callback function has already been called by someo
Error: This callback function has already been called by someone else; it can only be called one time.
    at /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:11:13
    at WeMoAccessory.<anonymous> (/usr/lib/node_modules/homebridge-legacy-plugins/accessories/WeMo.js:107:7)
    at /usr/lib/node_modules/homebridge-legacy-plugins/node_modules/wemo/wemo.js:127:5
    at ClientRequest.<anonymous> (/usr/lib/node_modules/homebridge-legacy-plugins/node_modules/wemo/wemo.js:99:4)
    at ClientRequest.emit (events.js:107:17)
    at Socket.socketCloseListener (_http_client.js:247:9)
    at Socket.emit (events.js:129:20)
    at TCP.close (net.js:485:12)

Anything problematic with Npm Version v8.1.1?

After update to NPM version 8.1.1 the log looks like this:

[23/10/2021, 16:20:27] Loaded plugin: [email protected]
[23/10/2021, 16:20:27] Registering platform 'homebridge-wemo.Wemo'

[23/10/2021, 16:20:27] [Belkin WeMo] Initializing Wemo platform...
[23/10/2021, 16:20:27] [Belkin WeMo] Initialising plugin v4.2.5 | Node v14.18.1 | HB v1.3.5...

[23/10/2021, 16:20:27] [Belkin WeMo] Plugin initialised. Setting up accessories....

[23/10/2021, 16:20:27] [Belkin WeMo] [Gästezimmer Leselampe] initialising with options {"logging":"standard","showAs":"outlet"}.
[23/10/2021, 16:20:27] [Belkin WeMo] [Gästezimmer Leselampe] initialised with s/n 221313K11012CC and ip/port 192.168.87.25:49153
[23/10/2021, 16:20:27] [Belkin WeMo] [Gästezimmer Leselampe] http has been established.
[23/10/2021, 16:20:27] [Belkin WeMo] [Gästezimmer Leselampe] upnp has been established.
[23/10/2021, 16:20:27] [Belkin WeMo] [Gästezimmer Leselampe] current state [off].

[23/10/2021, 16:21:30] [Belkin WeMo] The following devices have still not been initially found: [Waschmaschine].
[23/10/2021, 16:22:20] [Homebridge UI] [homebridge-wemo] Terminating child process...
[23/10/2021, 16:22:20] [Homebridge UI] [homebridge-wemo] Child process ended
[23/10/2021, 16:23:00] [Belkin WeMo] The following devices have still not been initially found: [Waschmaschine].

[23/10/2021, 16:24:28] [Belkin WeMo] [Waschmaschine] initialising with options {"logging":"standard","showAs":"outlet","timeDiff":30,"wattDiff":2}.
[23/10/2021, 16:24:28] [Belkin WeMo] [Waschmaschine] initialised with s/n 221540K12002B3 and ip/port 192.168.87.26:49153
[23/10/2021, 16:24:28] [Belkin WeMo] [Waschmaschine] http has been established.
[23/10/2021, 16:24:28] [Belkin WeMo] [Waschmaschine] upnp has been established.
[23/10/2021, 16:24:28] [Belkin WeMo] [Waschmaschine] current state [on].
[23/10/2021, 16:24:30] [Belkin WeMo] [Waschmaschine] current outlet-in-use [yes].
[23/10/2021, 16:24:30] [Belkin WeMo] [Waschmaschine] current consumption [21W].

[23/10/2021, 16:26:44] [Belkin WeMo] [Waschmaschine] current consumption [125W].

[23/10/2021, 16:28:53] [Belkin WeMo] [Waschmaschine] upnp error (will be re-attempted) [connect EHOSTUNREACH 192.168.87.26:49153].
[23/10/2021, 16:28:56] [Belkin WeMo] [Waschmaschine] http error (will be re-attempted).
[23/10/2021, 16:28:56] [Belkin WeMo] [Waschmaschine] upnp error (will be re-attempted) [connect EHOSTUNREACH 192.168.87.26:49153].

Config:
{
"name": "Belkin WeMo",
"mode": "auto",
"debug": false,
"wemoInsights": [
{
"label": "Waschmaschine",
"serialNumber": "221540K12002B3",
"wattDiff": 2,
"timeDiff": 30
}
],
"platform": "Wemo"
}

Wemo beta results

Well it worked great for about 30 minutes.

I did see some odd results in Home+ app. Said: Error. Communication to dehumidifier failed Value is lower than minium.

But; it still turned on/off even with error. Home app and Eve both worked fine no error.

Now 30 mins later;

Not working;

Logs

[8/5/2021, 9:53:19 AM] [Wemo] [Dehumidifier] requestDeviceUpdate() error:  at Object.<anonymous> (/usr/local/lib/node_modules/homebridge-wemo/node_modules/p-queue/dist/index.js:8:22).
[8/5/2021, 9:53:28 AM] [Wemo] [Dehumidifier] could not update from internal change as  at Object.<anonymous> (/usr/local/lib/node_modules/homebridge-wemo/node_modules/p-queue/dist/index.js:8:22).

And i just tried it again in home app and it works again.

[8/5/2021, 9:57:10 AM] [Wemo] [Dehumidifier] current state [purifying].

WEMO Link Error Message

Hello and thank you so much for this incredible work. I have been semi-successful getting the platform to recognize the Insight Switches I have but when it gets to the WEMO Link - it throws an error no matter how many bulbs i have connected. (I have 8).

I have reset all of the bulbs as well as the Link and reconnected and renamed everything but the error persists. I was wondering if anyone could point me in the right direction?

All bulbs are running the latest firmware (83) and the Wemo Link's firmware is WeMo_WW_2.00.10062.PVT-OWRT-Link

Here's where i'm at:

TV:.homebridge TV$ homebridge
Loaded plugin: homebridge-nest
Registering platform 'homebridge-nest.Nest'
//---
Loaded plugin: homebridge-platform-wemo
Registering platform 'homebridge-platform-wemo.BelkinWeMo'
//---
Loaded config.json with 0 accessories and 2 platforms.
//---
Loading 2 platforms...
Initializing Nest platform...
Fetching Nest devices.
[WeMo Platform] Initializing BelkinWeMo platform...
[WeMo Platform] Wemo Platform Plugin Loaded
[WeMo Platform] Fetching the Wemo Accessories, expecting 10 and will wait 20 seconds to find them.
[WeMo Platform] Found: Landscaping, type: insight
[WeMo Platform] Landscaping is false
[WeMo Platform] Discovered 1 accessories of 10
[WeMo Platform] Found: Washer, type: insight
[WeMo Platform] Washer is false
[WeMo Platform] Discovered 2 accessories of 10
[WeMo Platform] Landscaping binaryState: 1
[WeMo Platform] Washer binaryState: 8
[WeMo Platform] Landscaping binaryState: 1
[WeMo Platform] Washer binaryState: 8
[WeMo Platform] Found: WeMo Link, type: bridge
[WeMo Platform] Found endDevice: Living Room 2, id: 94103EF6BF4312F5
events.js:141
throw er; // Unhandled 'error' event
^

TypeError: Cannot read property '10006' of undefined
at new WemoAccessory (/usr/local/lib/node_modules/homebridge-platform-wemo/index.js:107:38)
at /usr/local/lib/node_modules/homebridge-platform-wemo/index.js:53:23
at /usr/local/lib/node_modules/homebridge-platform-wemo/node_modules/wemo-client/client.js:147:7
at Parser. (/usr/local/lib/node_modules/homebridge-platform-wemo/node_modules/xml2js/lib/xml2js.js:483:18)
at emitOne (events.js:77:13)
at Parser.emit (events.js:169:7)
at Object.onclosetag (/usr/local/lib/node_modules/homebridge-platform-wemo/node_modules/xml2js/lib/xml2js.js:444:26)
at emit (/usr/local/lib/node_modules/homebridge-platform-wemo/node_modules/sax/lib/sax.js:639:35)
at emitNode (/usr/local/lib/node_modules/homebridge-platform-wemo/node_modules/sax/lib/sax.js:644:5)
at closeTag (/usr/local/lib/node_modules/homebridge-platform-wemo/node_modules/sax/lib/sax.js:903:7)
at Object.write (/usr/local/lib/node_modules/homebridge-platform-wemo/node_modules/sax/lib/sax.js:1436:13)
at Parser.exports.Parser.Parser.parseString (/usr/local/lib/node_modules/homebridge-platform-wemo/node_modules/xml2js/lib/xml2js.js:502:31)
at Parser.parseString (/usr/local/lib/node_modules/homebridge-platform-wemo/node_modules/xml2js/lib/xml2js.js:7:59)
at Object.exports.parseString (/usr/local/lib/node_modules/homebridge-platform-wemo/node_modules/xml2js/lib/xml2js.js:534:19)
at parseResponse (/usr/local/lib/node_modules/homebridge-platform-wemo/node_modules/wemo-client/client.js:137:12)
at /usr/local/lib/node_modules/homebridge-platform-wemo/node_modules/wemo-client/client.js:97:5

Wemo Maker - GarageDoor

Hello,

I've two issues with my fresh Homebridge setup on Raspberry Pi with Wemo Maker as garage door opener.

1. The log shows an error: "[Wemo] Config entry [makerTypes] has an invalid entry which will be ignored" - how to solve this?
2. Garagedoor is seen as switch, not as GarageDoor, although "MakerType" is set as "gagageDoor" - how to solve this?

Details of your setup.

• Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
  1 - Homebridge UI-X

• Which version of Homebridge/HOOBS do you have?
  Homebridge v1.5.0

• Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
  Raspberry Pi
  Node.js v16.16.0

• Which version of this plugin (homebridge-wemo) do you have? Has the issue started since upgrading from a previous version?
  v5.0.3

• Which Wemo devices do you have that are causing issues? Please include product models if applicable.
  Wemo Maker - to use as Garagedoor opener

Please paste any relevant logs below.

[13/07/2022, 09:23:00] [HB Supervisor] Started Homebridge v1.5.0 with PID: 1004
[13/07/2022, 09:23:02] Loaded config.json with 0 accessories and 2 platforms.
[13/07/2022, 09:23:03] Loaded 1 cached accessories from cachedAccessories.
[13/07/2022, 09:23:03] ---
[13/07/2022, 09:23:04] Loaded plugin: [email protected]
[13/07/2022, 09:23:04] Registering platform 'homebridge-wemo.Wemo'
[13/07/2022, 09:23:04] ---
[13/07/2022, 09:23:04] Loading 2 platforms...
[13/07/2022, 09:23:04] [Wemo] Initializing Wemo platform...
[13/07/2022, 09:23:04] [Wemo] Initialising plugin v5.0.3 | System linux | Node v16.16.0 | HB v1.5.0 | HAPNodeJS v0.10.2...
[13/07/2022, 09:23:04] [Wemo] Config entry [makerTypes] has an invalid entry which will be ignored.
[13/07/2022, 09:23:04] [Wemo] Plugin initialised. Setting up accessories....
Setup Payload:
X-HM://0023XZG0WP4WQ
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
                       
    ┌────────────┐     
    │ 286-41-504 │     
    └────────────┘     
                       
[13/07/2022, 09:23:04] Homebridge v1.5.0 (HAP v0.10.2) (Homebridge 3C21) is running on port 51124.
[13/07/2022, 09:23:04] [Wemo] [Garagedoor] initialising with options {"logging":"standard"}.
[13/07/2022, 09:23:04] [Wemo] [Garagedoor] initialised with s/n 221615S000006F and ip/port 192.168.0.251:49153
[13/07/2022, 09:23:04] [Wemo] [Garagedoor] http has been established.
[13/07/2022, 09:23:04] [Wemo] [Garagedoor] upnp has been established.
[13/07/2022, 09:23:06] [Wemo] ✓ Setup complete. This plugin currently has a 5☆ rating on HOOBS! http://bit.ly/hbwemo-review

My Config:
"platforms": [
{
"name": "Config",
"port": 8581,
"platform": "config"
},
{
"name": "Wemo",
"mode": "auto",
"makerTypes": [
{
"label": "Garagedoor",
"makerType": "garageDoor",
"serialnumber": "221615S000006F",
"makerTimer": 15
}
],
"platform": "Wemo"
}
]

Reinstall of everything Plugin not finding devices and being stopped by Homebridge

What issue do you have? Please be as thorough and explicit as possible.

I just reinstalled everything including node js on a mac mini.

so far all other plugins working great.

Wemo plugin not finding any devices. All on same subnet. Prior installation it did work.

Last lines in logs are:
[4/11/2022, 9:24:44 AM] [Homebridge UI] [homebridge-wemo] Terminating child process...
[4/11/2022, 9:24:44 AM] [Homebridge UI] [homebridge-wemo] Child process ended

Details of your setup.

• Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
  Homebrige

• Which version of Homebridge/HOOBS do you have?

homebridege v1.4.0

• Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.

macos Mojave
Node v16.14.0

• Which version of this plugin (homebridge-wemo) do you have? Has the issue started since upgrading from a previous version?
  homebridge-wemo v4.7.2
  I tried homebridge-wemo v4.7.1 and same issues

• Which Wemo devices do you have that are causing issues? Please include product models if applicable.

All Wemo devices Light switchs and smart plugs

Please paste any relevant logs below.

[4/11/2022, 9:24:10 AM] [Wemo] Listener server port [49358].
[4/11/2022, 9:24:12 AM] [Wemo] ✓ Setup complete. Want to see this plugin in your own language? Let me know!
[4/11/2022, 9:24:44 AM] [Homebridge UI] [homebridge-wemo] Terminating child process...
[4/11/2022, 9:24:44 AM] [Homebridge UI] [homebridge-wemo] Child process ended

Creating 2 WeMo switches in iOS Home app but I only have 1

Hi, I have 1 WeMo switch that I am using this plugin for but there are 2 WeMo switches showing in the iOS Home app. One of the switches works but the other one shows that it is unreachable. Is there a way to get rid of the one that doesn't work?

Edit: I switched to the homebridge-platform-wemo package and no longer have this problem.

Continual WeMoSearchTimeoutErrors when outlet unplugged

If I unplug a smart outlet, the log fills up with tons of these errors:

[1/26/2020, 7:38:27 PM] [Spare Room Air Conditioner] Error finding device 'Spare Room AC': WeMoSearchTimeoutError
[1/26/2020, 7:38:27 PM] [Spare Room Air Conditioner] Continuing search for WeMo device with exact name 'Spare Room AC'...

Is there a way to quiet this error in the log other than taking the device out of the config?

Updates

Just general feedback. Incredibly annoying y'all feel like you have to have cut a new release every few days. Not necessary. And your node requirements aren't necessary either.

No devices shown after reboot

What issue do you have? Please be as thorough and explicit as possible.

I Wasn't able to access to my devices. After several tries (including reboot the service, and the hoobs as well) I decided to use the clear cache function.
Now after restarting the whole thing, I can't see any of my devices, and wemo isn't discovering the devices even with mode=auto

Details of your setup.

• Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
  Hoobs

• Which version of Homebridge/HOOBS do you have?
  4.1.17

• Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
  RPi 4 on Node 16.13.1 and HB-Version 1.3.6

• Which version of this plugin (homebridge-wemo) do you have? Has the issue started since upgrading from a previous version?
  4.3.0
  I'm not sure abaout the time when this issue shows up for the first time

• Which Wemo devices do you have that are causing issues? Please include product models if applicable.
  all of my devices are affected:
  2 Outlets
  5 Lightbulbs

Please paste any relevant logs below.

7.12.2021, 16:51:31Wemo BridgeConfiguration change
7.12.2021, 16:51:31wemobridge stopping
7.12.2021, 16:51:32Wemo BridgeWemoSSDP client gracefully stopped.
7.12.2021, 16:51:32Wemo BridgeWemoListener server gracefully closed.
7.12.2021, 16:51:37Wemo Bridge starting
7.12.2021, 16:51:40Wemo BridgeLoaded plugin 'homebridge-wemo'
7.12.2021, 16:51:40Wemo BridgeLoading 1 platforms...
7.12.2021, 16:51:40Wemo BridgeWemoInitialising plugin v4.3.0 | Node v16.13.1 | HB v1.3.6 | HOOBS v4...
7.12.2021, 16:51:40Wemo BridgeWemoPlugin initialised. Setting up accessories....
7.12.2021, 16:51:40Wemo BridgeWemodiscovering all IPs from interface lo
7.12.2021, 16:51:40Wemo BridgeWemodiscovering all IPs from interface wlan0
7.12.2021, 16:51:40Wemo BridgeWemoWill use interface wlan0
7.12.2021, 16:51:40Wemo BridgeWemoListener server port [44927].
7.12.2021, 16:51:40Wemo BridgeWemoSSDP listening: { address: 'http://192.168.0.158:46745', interface: '192.168.0.158' }
7.12.2021, 16:51:40Wemo BridgeWemoAttempting to send an M-SEARCH request
7.12.2021, 16:51:40Wemo BridgeWemoSending a message to 239.255.255.250:1900
7.12.2021, 16:51:40Wemo BridgeBridge is running on port 51836.
7.12.2021, 16:51:40Wemo BridgeWemoSent M-SEARCH request: {
  message: 'M-SEARCH * HTTP/1.1\r\n' +
    'HOST: 239.255.255.250:1900\r\n' +
    'ST: urn:Belkin:service:basicevent:1\r\n' +
    'MAN: "ssdp:discover"\r\n' +
    'MX: 3\r\n' +
    '\r\n',
  id: '64057c5a597d19e7'
}
7.12.2021, 16:51:42Wemo BridgeWemo✓ Setup complete. Want to see this plugin in your own language? Let me know!
7.12.2021, 16:52:10Wemo BridgeWemoAttempting to send an M-SEARCH request
7.12.2021, 16:52:10Wemo BridgeWemoSending a message to 239.255.255.250:1900
7.12.2021, 16:52:10Wemo BridgeWemoSent M-SEARCH request: {
  message: 'M-SEARCH * HTTP/1.1\r\n' +
    'HOST: 239.255.255.250:1900\r\n' +
    'ST: urn:Belkin:service:basicevent:1\r\n' +
    'MAN: "ssdp:discover"\r\n' +
    'MX: 3\r\n' +
    '\r\n',
  id: 'ca5acd0ad39ca291'
}

[Eero] Connection Issues, Could not Find Port

What issue do you have? Please be as thorough and explicit as possible.

Homebridge Logs continually show error that there is a connection error, Could not find the correct port to the device. This seems to cause lag when trying to use via the Home App

Details of your setup.

• Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
  Homebridge UI-X

• Which version of Homebridge/HOOBS do you have?
  v1.3.5

• Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
  Running on Linux Ubuntu Box.
  Node.js Version v14.18.1
  NPM v6.14.15

• Which version of this plugin (homebridge-wemo) do you have? Has the issue started since upgrading from a previous version?
  homebridge-wemo v4.2.6

• Which Wemo devices do you have that are causing issues? Please include product models if applicable.
  I have multiple light switches, dimmers and mini plugs.

Please paste any relevant logs below.

wemo plugin can't update or remove

Hi,
the plugin sudden can't remove or update.

screen shot : https://www.dropbox.com/s/drs7m9ksmngiv3v/Screen%20Shot%202021-08-03%20at%2011.36.12%20pm.png?dl=0

Details of your setup.

Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
HOOBS

Which version of Homebridge/HOOBS do you have?
3.3.3

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
hoobs hub

Which version of this plugin (homebridge-wemo) do you have? Has the issue started since upgrading from a previous version?
Version is 3.1.0 , it happened last update

Which Wemo devices do you have that are causing issues?
all wemo plugs are still working, but just can't update this wemo plugin anymore. i try to remove this manually, the hoobs then will not restart.