Posts: 60
Threads: 5
Joined: Jan 2025
Reputation:
4
Not sure where to report this, but three bugs I've found with the KCS firmware, latest version (v2.2.8).
- The LAN activity LED (green) flickers constantly even though there's no activity on the LAN. Since this is a network activity indicator it should only be lit when there's network traffic.
- The WiFi status indicator in the Network settings is wrong, it always displays enabled even if it's not. To see this, go to Network -> WiFi, click on "enable" to make it disabled (greyed out), click Save, the system restarts and it's marked as enabled again. The only way to tell its actual state is via a WiFi scanner to see if the KC868... AP is present or not.
- Time handling is wrong, with the default time zone of UTC the board displays the current time as 17:41 but it's actually 12:41, so it's five hours out. It's also not possible to set all time zones, it stops at UTC+12 but there are countries which are currently at UTC+13. A better way to handle this would be to allow for DST, since UTC+13 is actually UTC+12 + DST offset of 1 hour. Without this, it's necessary to manually change the time on the board every time a DST changeover occurs.
Posts: 7,453
Threads: 917
Joined: Oct 2020
Reputation:
188
can you test with newest firmware v2.2.10 , download link: https://www.kincony.com/forum/showthread.php?tid=7283
Posts: 60
Threads: 5
Joined: Jan 2025
Reputation:
4
(01-31-2025, 12:21 AM)admin Wrote: can you test with newest firmware v2.2.10 , download link: https://www.kincony.com/forum/showthread.php?tid=7283
Sure, just reflashed with 2.2.10:
- LAN LED still flickers continuously.
- WiFi status bug is still present.
- Time bug is still present, time is out by five hours.
So none of the bugs are fixed in 2.2.10.
Posts: 7,453
Threads: 917
Joined: Oct 2020
Reputation:
188
which kincony board model you are using. after our new year holidays, will feedback to our software team to check it.
Posts: 60
Threads: 5
Joined: Jan 2025
Reputation:
4
Kincony A868-A16 Rev 1.6.
I've just had another look at the LAN status LED and it's settled down to a solid colour, so maybe the initial constant flickering was due to some diagnostic running or something. I left it for awhile and it was still flickering, but it looks like it settles down after some time.
Posts: 7,453
Threads: 917
Joined: Oct 2020
Reputation:
188
will check it then give you feedback about time zone.
Posts: 60
Threads: 5
Joined: Jan 2025
Reputation:
4
An update for the KCS v3 firmware, specifically the latest version, v3.7.2:
- The time bug seems to be fixed, the time is now (almost) correct. I say almost because we're currently at GMT+12 summer time which is GMT+13 but there's no way to set that in the config. So it's correct for GMT+12, however we're on GMT+13.
- The WiFi bug is still present, turn off WiFi (so set enable = off), reboot, and it's shown as enabled again. I can't find the AP on a WiFi scan so it's been turned off, however the status info still shows it as enabled.
Posts: 60
Threads: 5
Joined: Jan 2025
Reputation:
4
03-06-2025, 04:09 AM
(This post was last modified: 03-06-2025, 04:11 AM by twostar.)
Just re-checked the time and the bug is still there. When you do a "Sync browser time" it's correct (or at least almost correct, see above) but at some point it appears to have done an NTP sync and it's now 13 hours behind the actual time. Given that we're at GMT+13 it looks like it's ignoring the time zone and using straight UTC without the local time zone offset for the time.
So it looks like there are still time-handling bugs in the v3 firmware, just different to the ones in the v2 firmware.
Posts: 60
Threads: 5
Joined: Jan 2025
Reputation:
4
Another update, the incorrect time setting happens on a reboot, for example to apply settings. Once the system has restarted, it shows a time in the wrong time zone. To see this in action: - Click on Sync Browser Time, the board time will be set to the correct time.
- Click on Restart Board.
- Once the board has restarted, the time will be (presumably) set from NTP and incorrect, meaning not showing the time for the local time zone. In my case it's currently 13 hours out, so it seems to be showing UTC, not the local time.
Posts: 60
Threads: 5
Joined: Jan 2025
Reputation:
4
Another update after some more testing, this bug is even stranger than described above: The time toggles between reboots from being 12 hours out to being 0 hours out (with the 1-hour summer-time offset mentioned). So: - Reboot board, time is 12 hours out.
- Reboot board, time is 0 hours out.
- Reboot board, time is 12 hours out again.
This is with the local time zone set to UTC+12.
I can understand a fixed error, but one that toggles between the two is a bit difficult to explain.
|
