In service dates on these boards was around March 2024. Then I had issues connecting to my WIFI after they were power cycled. Well, two days ago both disconnected and won’t reconnect. I issued a ticket in 2024 and again yesterday. Both sit there blinking. I’ve spent way too much time on this. Also, I can’t complain enough about the cumbersome Konnected app interface. On one level this is an awesome idea, but the implementation and configuration leaves a lot to be desired. The two boards have been broadcasting their SSID, but now I’m only seeing one, konnected_872802 and espressif is connecting to my NW. WTF is espressif! I welcome anyone that will baby sit me thru getting my boards back online. Otherwise, in a day or so they’re going in trash.
Espressif is the name of the company that makes the chips.
If you see the device broadcasting a WiFi setup network, then just connect to it with your phone or computer, then go to http://192.168.4.1 to set your wifi credentials. Or, you can use the Add Device > WiFi Setup flow in the Konnected app.
Once they’re on your WiFi, just go to the My Devices screen in the Konnected app and refresh.
Configured each board powered by PC USB. Each connected and started working, but sure does take a long time. Now, moved them back to the alarm panel. Now the dreaded power cycle wait. They showed up fairly quickly on my router, but now 39 min later they’re still blinking. What the heck are these boards doing?
Finally, about a hour after they show up on my router, they decide to actually work.
It should connect in like 10 seconds. 39 minute wait doesn’t sound normal at all.
Which firmware platform are you using? Which smart home app do you plan on connecting to it?
Thanks. Firmware Version: 3.0.0 Konnected project version: 3.1.4 SmartThings
Hi @Keith_Welchel, from what I can see, both of your devices are online and communicating normally with our cloud service.
Yes, but only after several days from an arbitrary disconnect that required my intervention and that required a WIFI reconfigure. These boards have always taken significant time, after a power cycle, for the Blue led to stop blinking, even though they show up in my router as connected.
Keith, don’t give up on these boards. I have three and they are awesome. I’m wondering if there might be some weird issue with your router. It sounds like you’re able to connect to the boards WiFi with your phone or PC but the problem occurs when you configure them and reset for them to connect to your router right? Can you try a different router? For instance maybe your phone’s hotspot or something? How old is your router?
Thanks Keith. It’s not my router (RT-AX88U). Normally, they show as connected in my router in a timely manner after a power cycle, as expected, but the Blue light keeps blinking. The arbitrary disconnect this last week was a different response. For what ever reason, I had to reconfigure the WIFI. I’ve tried several routers over the course, including my travel router. No difference. Boards show up in router, and then some long period later blue light stops blinking and then they are online and working. My concern is I’m away and loose access to my alarm system and alarm system status. Also, I had a different router when theses boards were put in service.
@Keith_Welchel Sorry for the frustrating inconstancy, but let’s try to get to the bottom of this. The blinking blue light can mean a couple of things. It will continue blinking until the device is connected to WiFi and given an IP address by your router.
On our newer ESPHome firmware, it will also continue blinking if the Local Native API is enabled until a local client (i.e. Home Assistant, Hubitat) is successfully connected. I don’t think this applies to you though, because it sounds like you’re using our original Konnected/nodemcu firmware which is still required on the 6-zone boards for SmartThings connectivity.
So, the first thing I would check is any issues or logs from the router with assigning an IP address to the device. You can also capture a log from the device itself by USB via install.konnected.io and that should give us more insight into what’s going on on. Feel free to post the log here as either an attachment or screenshot or copy/paste and I can help interpret.
is Ethernet not an option?
I have three boards, the first has been connected for well over 3 years and it just works. I haven’t touched it since it was installed. The other two are in my home and have been online for going on two years now…again, other than updates they just work…but all of mine are connected via ethernet.
@greg9 The boards work when they finally connect. The issue is it’s taking a long time to get back online after a disconnect for any reason. Wired is not an option.
Not often, but if I need to reboot the router, I have to take into account having my security system offline for an undetermined amount of time.
Two boards do the same thing? I would suggest looking at your router settings
@greg That’s a possibility, but right now I’m not going mess with my router with 20+ devices that have no issues with it.
I power cycled one board and waited for the disassociation router log. Then powered on and board shows up within seconds, but the blue light is blinking. Here’s my router logs:
Jun 24 09:51:01 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 80:64:6F:87:06:48, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-56
Jun 24 09:51:01 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 80:64:6F:87:06:48, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-56
Jun 24 09:51:02 wlceventd: wlceventd_proc_event(662): eth6: Disassoc 80:64:6F:87:06:48, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jun 24 09:57:56 wlceventd: wlceventd_proc_event(685): eth6: Auth 80:64:6F:87:06:48, status: Successful (0), rssi:0
Jun 24 09:57:56 wlceventd: wlceventd_proc_event(722): eth6: Assoc 80:64:6F:87:06:48, status: Successful (0), rssi:-59
I had a ping set up and no reply until board came online about 13:05. Router shows board associated with router at 09:57, but board isn’t responding from 09:57 to ~13:05. No router logging around 13:05. Pull logs next…
This is interesting… I moved one board to my travel router (repeater) (GL-AXT1800) and it gets online in a few seconds. The other board that’s still on my home router, now gets online in a few seconds. I moved it also to the travel router and both now get online in a few seconds.
@keith_wilson, this is a long shot but is it possible that the 2 boards have identical MAC addresses? I had this happen with a pair of PCs I was configuring 20+ years ago.
@Matt_c MAC addresses are different