Unable to determine OTA (Pro board app)

Konnected Alarm Panels
,
1

Hello, when I make configuration modifications to the Pro board configuration via the Konnected app on my phone, I always see this error when attempting to push the changes to Hubitat. Does anyone else see this and has any ideas on how to resolve it? Thanks

7B1FB651-7B70-4F42-9DD8-E7F20A1D5FEA_1_105_c
7B1FB651-7B70-4F42-9DD8-E7F20A1D5FEA_1_105_c602×1304 98.3 KB

2

Hello, I am using Smartthings and not Hubitat but similar thing happens. I just close the Konnected app and oen it again and can go to settings.
I will also point out that when I was setting up the system I had cut power to Konnected after that (wait for couple of minutes before turning power off) and turn it ON again. And sometime just the reset button on Konnected board did the trick.
But yes this happens.

3

Thank you for the reply - this seems to happen every time, howerver the process of updating the firmware locally and on my Hubitat process correctly. So at this point I just ignore the error message and go on with my day…

4

yes… its everytime. by design :slight_smile:

5

We are trying to solve this. It’s trickier than it seems.

After a firmware update is done, the board should reboot and then re-broadcast itself on the network via mDNS/zeroconf with the updated version number. The Konnected app is listening for up to 90 seconds I think to see this broadcast. If it doesn’t see it, that’s what prompts this message to come up.

It doesn’t necessarily mean that the firmware update failed (usually it went through fine). What it means is that for whatever reason the app never saw the board come back up within 90 seconds and broadcast it’s updated version. This could be a problem, like if the board went offline or lost the WiFi, or it could be just a glitch in mDNS/zeroconf discovery which isn’t always perfect.

Workaround is to exit and re-start the Konnected app, and it should re-discover again. Usually, if the board is online, that’ll fix it.

We’re trying to make this less flaky in the app.

6

Thanks for the info, Nate. Since this process is only used during initial configuration and when changes are made, it is infrequent, so it’s not a big problem. Since the process to update firmware works regardless of the OTA error its really just “cosmetic” at this point but a fix would be appreciated. Thanks as always :slight_smile:

-peter-