I was able to discover 2 of the Konnected Alarm Interface wifi modules with no issue at all. Then I tried to set up 2 more modules, but HE was unable to discover them. I have tried resetting the Konnected wifi, rebooting HE, downgraded HE version from 2.1.3.x to 2.1.1.122 (and versions in between), but still no luck. Then I deleted the Konnected Drivers, App Code and App and start all over again, but now I couldn't even re-discover the 2 modules that were previously discovered.
I have restored the configuration from a HE backup to at least get the first 2 modules back into HE, but stuck in setting up the 2 additional modules. I have contacted Konnected, but unable to come to any resolution. I think the issue is with HE, not Konnected at this point. HE is running fine otherwise. Has anyone run into this issue before? Any suggestion on how to fix it? If there is no solution, maybe I need to try Smartthings, but I prefer to have a local system vs. an internet dependent system.
can you post the logs when you run the discovery process?
Have you tried rolling the hub back to an earlier release to see if it works with that? I am not aware of any changes that would have occurred with discovery though.
I have rebooted and power cycled the HE at least 10 times.
No change in the Google Mesh wifi network between the first 2 successful discovery and now
I haven't tries the upnp tool. I am able to use web browser to connect to all 4 modules with something like: http://192.168.1.151:24542, so the devices seem to be connected to wifi (just not to HE). For the UPNP tool, do I just press M-Search? What data am I looking for?
Logs shows it just keeps trying:
app:72019-08-01 04:55:26.422 pm debugDiscovering Konnected devices on the network via SSDP
app:72019-08-01 04:55:23.452 pm debugDiscovering Konnected devices on the network via SSDP
app:72019-08-01 04:55:20.419 pm debugDiscovering Konnected devices on the network via SSDP
app:72019-08-01 04:55:17.424 pm debugDiscovering Konnected devices on the network via SSDP
app:72019-08-01 04:55:14.421 pm debugDiscovering Konnected devices on the network via SSDP
app:72019-08-01 04:55:11.415 pm debugDiscovering Konnected devices on the network via SSDP
app:72019-08-01 04:55:08.428 pm debugDiscovering Konnected devices on the network via SSDP
app:72019-08-01 04:55:05.430 pm debugDiscovering Konnected devices on the network via SSDP
app:72019-08-01 04:55:02.424 pm debugDiscovering Konnected devices on the network via SSDP
I have rolled back HE version from 2.1.3.125 to 2.1.1.120. I have also deleted all Konnected related Drivers, App Code and App. After that it won't even re-discover the first 2 modules what were successfully discovered before. I have restore from backup to get the first 2 module backup, but still unable to add the 2 additional modules.
Have you posted this question on the Konnected forum? Somewhere, in the back of my mind, I seem to recall these Google mesh WiFi systems causing issues with network discovery. Have you tried unplugging all of the extra Google mesh access points, except the main router and trying the discovery again? This assumes your Hubitat hub is also connected directly to the main router.
You should not have to press anything, when it starts up it should do a search and find any upnp devices on your network. If your konnected devices are responding properly you should seem them there. FYI, you should also be able to find your Hubitat hub with this app, both of mine show up with a picture of our hub.
I have powered down 2 of the 3 Google Mesh and only have one (closed to the Konnected) running. Konnected modules are 5 feet away but between 1 wall from the wifi. Reception should be no issue. I can bring up the IP from a web browser (http://192.168.1.151:24542). On the Google Mesh, I have turned of PUnP and turned it back on, still no luck.
Last night I did a full factory reset on Hubitat, re-did all the App Code, Drivers and App, also reset the wifi on Konnected wifi module, still no luck. I have chatted with Nate and Andy from Konnected, we couldn't figured out how was the issue. So I am at a roadblock.
I have ordered a Smartthings hub and check if the problem is with Hubitat. If same issue persist, then it is an issue with Konnected (or maybe my wifi).
Hi Chuck,
I ran the tool. I saw the Hubitat, but I don't see any of the 4 Konnected modules. Does that mean the problem is with the Konnected wifi module? I have reset the Konnected wifi connection from the web page of the module (http://192.168.1.151:24524). I have also used the ESPlorer to reset the module. Anything else I can try?
Thanks!
There is an option during the initial setup to disable device discovery. Do you remember if you set this option? If so, they will no longer be discoverable and you may need to reflash them altogether. @nate is part of the forum and hopefully can assist but you may want to reach out on the Konnected forums as well. You may get better advice there as these devices are their bread and butter.
@jlmoped @chuck.schwer
I have Konnected too. I just have the two boards, but am considering connecting more. I am using Orbi mesh.
Thanks for the tip on the UPNP Tool. I installed it and it searched immediately. It found my router, Wemo light switches, etc. but it did not find the Konnected system. Everything is working on my Konnected system within Hubitat. I am not sure why the UPNP Tool can't find it.
I also run FING and FingBox and it found the Konnected device just fine.
Fing scans the whole IP range and doesn't rely on SSDP/ upnp for discovery. As long as the device has an IP address in your network Fing will find it.
I have a Netgear Nighthawk router and I installed the tool Chuck linked above. It doesn't find my functioning Konnected device. I had discovery disabled for the device at first but even after re-enabling discovery in the Konnected app, it still doesn't find it.
@chuck.schwer, the upnp tool seems to discover my Konnected board, but only after I reboot the device. It doesn't seem to show up in the log after that. If I reboot the device again, it pops up in the log again but doesn't seem to appear in any subsequent scans.
It has never shown up in the upnp tool's device list only in the logs and only shortly after it is rebooted. See below
I don't have a Konnected board myself, I figured that upnp tool would find it, but they might be doing something proprietary or not responding to the upnp tool the way it expects. Konnected will need to comment on this.
Maybe @nate can chime in? Alternatively, the OP might try posting in the Konnected Facebook group - Andy Wulff is usually pretty active on there and quick to respond.
Yes, the devices should respond to a standard discovery request. I hadn't used that particular tool before, but I just tried it and it seems to be by default searching for upnp:rootdevice which Konnected will not respond to. change M-SEARCH to ssdp:all to get everything or urn:schemas-konnected-io:device:Security:1 to get just the Konnected devices. They do show up in the Log Viewer section of the app for me.
In related news, I'm working on a mobile app to help debug discovery issues and will ultimately be a tool for performing OTA updates and Konnected configuration. It's very, very basic and early right now, but you're welcome to try it to help with discovery. Scan below to install for Android only:
EDIT: updated QR code for Android pre-release install
I will try UPnP tool tonight with the M-Search option. The QR code image you have provide isn't showing up in the message. Can you re-send?
I have also tried connecting Konnected to SmartThings, that also didn't work. So I think it is a connection issue not allowing Hubitat and SmatThings to discover it.
That would be VERY WELCOME!!! It is a pain to dig through my wife's closet to get to the alarm box, remove the wifi modules, keep the 3 modules straight and not mix them up ( ), and flash them at a computer.
I tried Upnp tool again with the M-Search parameter and got the following, but still unable to discover it from Hubitat. What component is not working right?
We've been getting a lot of reports very recently about discovery issues with the latest update to Google WiFi (11895.108.11). They seem to have broken multicast across segments of the network. It's not specifically a Hubitat problem, but it seems that UPnP/multicast/SSDP broadcast from the wired network is not reaching the 2.4GHz wifi network where the Konnected devices are connected, and that affects Hubitat in a big way because most IoT devices are WiFi and Hubitat is wired.
), and flash them at a computer.
