# \[APP\]\[Pro\] Virtual Radar App

**URL:** <https://community.homey.app/t/app-pro-virtual-radar-app/14605>\
**Category:** Apps\
**Tags:** app, homey-pro\
**Created:** [June 20, 2019, 9:26am UTC](https://community.homey.app/t/app-pro-virtual-radar-app/14605 "2019-06-20T09:26:07Z")\
**Posts on this page:** 6\
**Page:** 4

<div class="post-metadata">

**Author:** ![Kasper\_Kvist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kasper_kvist/32/148796_2.png) [@Kasper\_Kvist](https://community.homey.app/u/Kasper_Kvist)\
**Post date:** [July 24, 2026, 1:43pm UTC](https://community.homey.app/t/app-pro-virtual-radar-app/14605/61 "2026-07-24T13:43:45Z")

</div>

Hi Tom. Actually there is (I’ve checked my Flightrader24 app on my phone at the same time I get the Homey notifications).

But I can see, that you also don’t have any content (N/A) in the tags To and Operator. The very same tags I use in my flow/push notification.

---

<div class="post-metadata">

**Author:** ![Tom\_ten\_Den](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tom_ten_den/32/120986_2.png) [@Tom\_ten\_Den](https://community.homey.app/u/Tom_ten_Den)\
**Post date:** [July 24, 2026, 2:19pm UTC](https://community.homey.app/t/app-pro-virtual-radar-app/14605/62 "2026-07-24T14:19:27Z")

</div>

@Kasper_Kvist correct Unfortunately, not always on the website either.

---

<div class="post-metadata">

**Author:** ![Koen\_S](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/koen_s/32/168206_2.png) [@Koen\_S](https://community.homey.app/u/Koen_S)\
**Post date:** [August 4, 2026, 2:43pm UTC](https://community.homey.app/t/app-pro-virtual-radar-app/14605/63 "2026-08-04T14:43:01Z")

</div>

**Bug: radar latitude/longitude are rounded to whole degrees when saving device settings (v3.4.2)**

Hi Bretislav, thanks for keeping this app alive — the OpenSky API-client support works great.

I ran into a bug that makes the Radar device unusable after any settings change, and I think I’ve narrowed down the cause.

**Symptom**

Saving the Radar device settings rounds `lat` and `lon` to whole degrees. `52.53306289 / 4.71264712` becomes `53 / 5` — a location 55 km away, so the radar silently finds nothing.

It happens on _every_ save, including saves where I don’t touch the coordinates at all. Changing only the scan interval is enough to move the radar 55 km.

**Steps to reproduce**

1. Pair a Radar (ADS-B) device. The app writes the correct coordinates itself, with 8 decimals — this part is fine.
2. Open device settings, change nothing but the scan interval, press Save.
3. Reopen the settings: latitude and longitude are now whole numbers.

**Extra clue**

The settings field itself rejects its own valid value. Typing `4.71264712` makes the browser flag the last digit as invalid (“please enter a valid value”), and on save it becomes `5`.

**Not a UI-only problem**

I tested every route — all of them round:

| Route | Result |
| --- | --- |
| Settings screen (web app) | rounded |
| Settings screen (mobile app) | rounded |
| Cloud API `PUT /api/manager/devices/device/:id/settings` | rounded |
| Local API (same call, direct to Homey) | rounded |

And every precision rounds the same way:

| Value sent | Value stored |
| --- | --- |
| 52.5 | 53 |
| 52.53 | 53 |
| 52.533 | 53 |
| 52.5330629 | 53 |
| 52.53306289 | 53 |

Pairing is the only path that stores decimals correctly, which fits: `onPair` writes the settings from inside the app and bypasses Homey’s settings validation.

**Likely cause**

The `lat` and `lon` settings appear to declare a `step` attribute. The rendered input carries `step="1e-8"`, and Homey’s validator seems to snap the value to a multiple of that step — but ends up treating the step as `1`, giving whole degrees. The `dst`setting has no `step` and renders as `step="any"`, and it keeps its decimals without any problem (5.6 saves fine).

**Suggested fix**

In `drivers/radar/driver.settings.compose.json`, drop the `step` from both coordinate fields so they behave like `dst`:

json

```auto
{
  "id": "lat",
  "type": "number",
  "label": { "en": "Latitude", "nl": "Breedtegraad" },
  "hint": {
    "en": "The distance of aircraft will be based on the radar location.",
    "nl": "De afstand van toestellen wordt bepaald op basis van de radar locatie."
  },
  "attr": { "min": -90, "max": 90 },
  "value": 52.228936
},
{
  "id": "lon",
  "type": "number",
  "label": { "en": "Longitude", "nl": "Lengtegraad" },
  "hint": {
    "en": "The distance of aircraft will be based on the radar location.",
    "nl": "De afstand van toestellen wordt bepaald op basis van de radar locatie."
  },
  "attr": { "min": -180, "max": 180 },
  "value": 5.321492
}

```

If the step has to stay for the UI spinner, writing it as a plain decimal instead of exponential notation may also do it:

json

```auto
"attr": { "min": -90, "max": 90, "step": 0.00000001 }

```

I couldn’t verify the exact manifest because the 3.4.x source isn’t on GitHub (the repo is still at 3.2.0), so the snippet above is my best reconstruction from the rendered input attributes — worth a look at your end.

**Workaround for anyone else hitting this**

Don’t open the device settings. Delete and re-pair the device instead; pairing takes the coordinates straight from your Homey location and stores them correctly. The trade-off is that you’re stuck with the pairing defaults (5 km range, 20 s scan interval).

**One small request**

Would you consider pushing the 3.4.x source to GitHub? The repo still sits at 3.2.0, so there’s no way to check or contribute a fix from the outside.

Thanks!

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [August 4, 2026, 6:25pm UTC](https://community.homey.app/t/app-pro-virtual-radar-app/14605/64 "2026-08-04T18:25:06Z")

</div>

Let me have a look on that…

> [@Koen\_S](#):
>
> Would you consider pushing the 3.4.x source to GitHub? The repo still sits at 3.2.0, so there’s no way to check or contribute a fix from the outside.

It is always up to date - [GitHub - shaarkys/com.gruijter.virtualradar: Virtual Radar app for Homey based on ADS-B data · GitHub](https://github.com/shaarkys/com.gruijter.virtualradar/)

Maybe you are looking on previous/old repo ?

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [August 4, 2026, 6:53pm UTC](https://community.homey.app/t/app-pro-virtual-radar-app/14605/65 "2026-08-04T18:53:38Z")

</div>

Fixed in [Virtual Radar | Homey](https://homey.app/en-cz/app/com.gruijter.virtualradar/Virtual-Radar/test/), can you please test and report back ?

---

<div class="post-metadata">

**Author:** ![Koen\_S](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/koen_s/32/168206_2.png) [@Koen\_S](https://community.homey.app/u/Koen_S)\
**Post date:** [August 5, 2026, 6:54pm UTC](https://community.homey.app/t/app-pro-virtual-radar-app/14605/66 "2026-08-05T18:54:20Z")

</div>

Tested and works, perfect! Thanks for the swift reply, and I missed the GitHub on my part. Sorry for that 😉

Have a great evening! Kind regards

[Previous page](https://community.homey.app/t/app-pro-virtual-radar-app/14605.md?page=3)