@dadarkgtprince I pushed out an update to the Connect app, the switch driver, and the dimmer driver that may resolve some of those. Try updating the Connect app and any drivers you're using. Also, note that devices must be added through the Connect app, not manually.
1 Like
in my case, all the devices were added through the connect app. i just had to delete the old versions and then they worked. i'll go through that again though tonight to test and let you know
@YapFlapper Another day, another update... 
I changed how manual IP addresses are specified, and fixed an incorrect variable name.
For the devices in your log that are showing 'null' for hexIp and hexPort, are those devices that used to work and recently stopped? Did you manually set any IPs or ports in the driver page of any failing devices?
on the new Dimmer code, i'm getting the following error when trying to save it
Cannot invoke method hexStringToInt() on null object on line 67
weirdly enough, i'm NOT getting it on the switch driver
I did the same and added them all through the connect app. My ips were all reserved right after adding so no chg there.
So yes they were working and then stopped. I did nothing to the devices on their page at all. Not sure what changed.
There's a new version of the Connect app and accompanying drivers. Hopefully this will help out with some of the issues that have been coming up.
What's new:
- Ability to manually add devices through the Connect app -- give the app an IP address (like 192.160.0.15:12345) and it will try to discover the device at that address
- Updated method for manually setting address and port -- use device preferences rather than a device command
- Improved cleanup -- when uninstalling the Connect app, any child devices will be automatically removed
- Everything has an
importUrlnow, so updating in the future will be slightly easier - Miscellaneous bug fixes
1 Like
Cool. Do you think this will make it so the wemo mini switches can be seen? I had just ordered a couple of these thinking they would work like the others and was just a different firm factor. In my backyard these things are instantaneous and very reliable compared to zwave which despite repeaters has never been (the yard is small so nothing impressive but does have a lot of cement/rock).
Unfortunately ifttt can’t handle multiple virtual switch state changes simultaneously and don’t allow multi-wemo switch changes simultaneously so the workaround gets really complicated.
That's my hope. Apparently the Mini's don't handle the standard discovery process in the same way as older Wemo devices (at least, that what it seems like, but I don't have any, so I'm not entirely sure), but possibly being able to manually add them will work.
Not sure where you are located but if you flip me your address I would happily send you one 
Is there any way to turn off the debug notes? I seem to get a lot in the logs since I’m turning on 9 switches on at a time in some cases.
There's a toggle at the bottom of the Connect app for turning debug logging off and on.
1 Like
even with that off, there's a lot of information being put in the logs. hextoInt and hextoIP seem to be the culprits
In the app connect code, i changed the log.debug command to debugLog() under hextoInt and hextoIP and it cleaned it up a lot for me
private hexToInt(hex) {
debugLog("Converting ${hex} to int...")
Integer.parseInt(hex,16)
}
private hexToIp(hex) {
debugLog("Converting ${hex} to IP...")
[
hexToInt(hex[0..1]),
hexToInt(hex[2..3]),
hexToInt(hex[4..5]),
hexToInt(hex[6..7])
].join('.')
}Logging output was updated in the last couple of days. All the log.debug calls in Connect app were changed to debugLog in the last update (and the log statements in the hex conversion functions were removed).
1 Like
No. All DHCP.
It is now working. I removed from HE the devices that were causing the errors. I updated Wemo Connect and driver code. Wemo Connect rediscovered the devices.
I noted some duplicate Wemo devices in Google Home integration list. Working on resolving that next.
Thank you Jason.
What is the difference between the Wemo Switch and Wemo Insight Switch drivers?
The Insight is an older switch that can detect and report the amount of power used.
Looks like my discovery is seeing the same 9 again (duplicates) and not still not seeing the new mini insights.
How do you find the "12345" part of the IP address? When I look in my wifi router I only see the standard ip address?
Provide an address in the format 192.168.0.10:12345
I tried the ports that my other wemo's were using 49153/49154 but it says - The address was invalid or the device was unreachable. Please try again.
192.168.86.47:49153
192.168.86.47:49154
192.168.86.50:49153
192.168.86.50:49154
192.168.86.33:49153
192.168.86.33:49154
@jason0x43 would running this app on multiple hubs impact anything? before hub mesh was a thing, i did have the app on multiple hubs. haven't really had any issues since moving to the new code, but definitely don't want to cause any issues with constant polling on the devices. i'm most likely going to clean up my devices and only run it on one hub anyway, but just curious
