Securifi Community Forum
Securifi Products => Almond+ => Topic started by: bwainscott on April 11, 2015, 11:26:10 am
-
I was going to try the "plug in the peanut plug to update the firmware" trick this morning, and the "connected sensor" widget on the LCD UI isn't working. Everything else I tried on the LCD UI was fine, but if I pressed the connected sensor widget I got a brief flash of a black box with some words like "starting application", and then it immediately went back to the main screen. Acts like the connected sensors app is failing. I carefully noted the time, then tried it 3 times in quick succession so that I could easily identify anything in the system log, and I saw this:
Apr 11 08:19:30 AlmondPlus user.info sysinit: Address already in use: End Client binding failed
Apr 11 08:19:31 AlmondPlus user.info sysinit: Address already in use: End Client binding failed
Apr 11 08:19:32 AlmondPlus user.info sysinit: Address already in use: End Client binding failed
(BTW -- I have ntp setup in openwrt, but the time on my A+ is 13 seconds fast... I've noticed before that it always seems to be just a bit off.... is ntp not working correctly? I don't see an ntp daemon running, but don't know if that is significant.)
Anyway, since I need to reboot I guess I might as well do the R70->update plug->R72 thing....
-
I was going to try the "plug in the peanut plug to update the firmware" trick this morning, and the "connected sensor" widget on the LCD UI isn't working. Everything else I tried on the LCD UI was fine, but if I pressed the connected sensor widget I got a brief flash of a black box with some words like "starting application", and then it immediately went back to the main screen. Acts like the connected sensors app is failing. I carefully noted the time, then tried it 3 times in quick succession so that I could easily identify anything in the system log, and I saw this:
Apr 11 08:19:30 AlmondPlus user.info sysinit: Address already in use: End Client binding failed
Apr 11 08:19:31 AlmondPlus user.info sysinit: Address already in use: End Client binding failed
Apr 11 08:19:32 AlmondPlus user.info sysinit: Address already in use: End Client binding failed
(BTW -- I have ntp setup in openwrt, but the time on my A+ is 13 seconds fast... I've noticed before that it always seems to be just a bit off.... is ntp not working correctly? I don't see an ntp daemon running, but don't know if that is significant.)
Anyway, since I need to reboot I guess I might as well do the R70->update plug->R72 thing....
Unlikely, but if you have any SDK application that uses the HA callback function (HADevices::genericCallback), the connected sensors app on the LCD won't work for this reason (uses the same address). At least this was true back in R6X, I assume it's still true.
-
Unlikely, but if you have any SDK application that uses the HA callback function (HADevices::genericCallback), the connected sensors app on the LCD won't work for this reason (uses the same address). At least this was true back in R6X, I assume it's still true.
What is the fix or work around for this?
Most SDK work will involve the callback function, which will then break the LCD apps. This is not a workable solution.
Has anything changed with R80