Thats sound like a possible reason but i used the device for over a year and it was always correct in the web gui.
When i pay attention to both devices in the log i cant say your right.
2021-05-03 23:30:55 INFO: [0fad4956: h02 > 18.197.xxxx] HEX: xxxx
2021-05-03 23:30:55 INFO: [0fad4956] id: 917xxxx, time: 2021-05-03 23:30:52, lat: 53.xxxx, lon: 5.xxxx, course: 244.0
2021-05-03 23:30:56 INFO: [f6ac5eb8: watch < 83.232.xxxx] HEX: xxxx
2021-05-03 23:30:56 INFO: [f6ac5eb8] id: 905xxxx, time: 2021-05-03 23:30:54, lat: 53.xxxx, lon: 5.xxxx, course: 0.0
Time on web gui:
917xxxx: Time 2021-05-03 23:30:52
905xxxx: Time 2021-05-03 23:47:01
But the 905xxxx is presenting it self as a h02 device on the web interface as its clearly not.
Thats sound like a possible reason but i used the device for over a year and it was always correct in the web gui.
When i pay attention to both devices in the log i cant say your right.
Time on web gui:
917xxxx: Time 2021-05-03 23:30:52
905xxxx: Time 2021-05-03 23:47:01
But the 905xxxx is presenting it self as a h02 device on the web interface as its clearly not.