You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by mevadapts February 10, 2024
Hello,
I have observed that the Eddystone URL broadcast has been successfully configured when I double-click on the beacon card. This is an important step towards triggering alarms when users broadcast a specific URL. Especially in emergency situations, users will be able to quickly access necessary information using the beacon card.
Currently, I have noticed that to detect this broadcast, the following JSON data needs to be included in the existing topic espresense/devices/xxxxxxxx/yyy:
json
{
"mac": "ac233fe07f26",
"id": "ccdd11220026", "url": "http://example.com/sos",
"idType": 55,
"rssi@1m": -71,
"rssi": -99,
"raw": 6.31,
"distance": 4.32,
"var": 0.92,
"int": 8533
}
However, I am concerned that with future updates, this data might be lost. Therefore, would it be possible to incorporate this Eddystone URL into the project? This way, the data can be made accessible before it is lost.
Thank you,
The text was updated successfully, but these errors were encountered:
Discussed in #1226
Originally posted by mevadapts February 10, 2024
Hello,
I have observed that the Eddystone URL broadcast has been successfully configured when I double-click on the beacon card. This is an important step towards triggering alarms when users broadcast a specific URL. Especially in emergency situations, users will be able to quickly access necessary information using the beacon card.
Currently, I have noticed that to detect this broadcast, the following JSON data needs to be included in the existing topic espresense/devices/xxxxxxxx/yyy:
json
{
"mac": "ac233fe07f26",
"id": "ccdd11220026",
"url": "http://example.com/sos",
"idType": 55,
"rssi@1m": -71,
"rssi": -99,
"raw": 6.31,
"distance": 4.32,
"var": 0.92,
"int": 8533
}
However, I am concerned that with future updates, this data might be lost. Therefore, would it be possible to incorporate this Eddystone URL into the project? This way, the data can be made accessible before it is lost.
Thank you,
The text was updated successfully, but these errors were encountered: