It seems that adverts sent with a scope are not (correctly) picked up by the firmware.
"Last seen" does not update, I do not get coordinates (although in observer coordinates of the advert are visible/ device is on the online map of an observer).
Tested with repeaters.
Which device are you using
LilyGO T-Deck Plus
Which Firmware are you using
v0.9.12.3 (I cannot use v0.9.13 as described in #334).
Regards!
**Describe the bug**
It seems that adverts sent with a scope are not (correctly) picked up by the firmware.
"Last seen" does not update, I do not get coordinates (although in observer coordinates of the advert are visible/ device is on the online map of an observer).
Tested with repeaters.
**Which device are you using**
LilyGO T-Deck Plus
**Which Firmware are you using**
v0.9.12.3 (I cannot use v0.9.13 as described in #334).
Regards!
<!-- github-sync-id:5075010608 -->
An advert heard through a region scope now updates the contact's last-heard time and location. For safety this only happens after the advert's signature is checked.
## Fixed in v0.9.14
An advert heard through a region scope now updates the contact's last-heard time and location. For safety this only happens after the advert's signature is checked.
<!-- github-comment-id:5838296441 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Describe the bug
It seems that adverts sent with a scope are not (correctly) picked up by the firmware.
"Last seen" does not update, I do not get coordinates (although in observer coordinates of the advert are visible/ device is on the online map of an observer).
Tested with repeaters.
Which device are you using
LilyGO T-Deck Plus
Which Firmware are you using
v0.9.12.3 (I cannot use v0.9.13 as described in #334).
Regards!
Fixed in v0.9.14
An advert heard through a region scope now updates the contact's last-heard time and location. For safety this only happens after the advert's signature is checked.
Currently cannot check, so assuming it is fixed.