Tag S18-3 with Eddystone: unable to access device identifier

Comments

1 comment

  • Mathieu Hamel

    After further investigation, it seems that the problem is even more bizarre than it not working at all.

    Indeed, after trying to push another configuration to a beacon, the beacon would advertise the first one. Pushing a third configuration, the beacon advertises the second one, and so forth, effectively lagging behind by one configuration. Hence, the information that is shown in panel.kontakt.io is not reflecting what is actually on the beacon.

    All S18-3 beacons we tested have the behaviour (about 7 of the 100 we just bought). The whole configuration seems to be affected (not only Eddystone as in original post). Also, this bug is the same if we configure from the iOS app or from panel.kontakt.io with a gateway.

Please sign in to leave a comment.