# \[APP\]\[Pro\] FYTA - The smart fitness tracker for plants **URL:** \ **Category:** Apps\ **Tags:** app, official, homey-pro\ **Created:** [March 30, 2024, 3:26pm UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367 "2024-03-30T15:26:42Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![evdpol](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/evdpol/32/26730_2.png) [@evdpol](https://community.homey.app/u/evdpol)\ **Post date:** [October 8, 2024, 11:54am UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/21 "2024-10-08T11:54:23Z")
I can, haha! This will be fixed in the next version of the app. ---
**Author:** ![aesubs](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/aesubs/32/113989_2.png) [@aesubs](https://community.homey.app/u/aesubs)\ **Post date:** [July 24, 2025, 9:57pm UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/22 "2025-07-24T21:57:29Z")
Hello @evdpol Would you be open to some QOL improvements I’ve thought of while using the app for a while? 1. **Onboarding filter** Right now every plant in the fyta account shows up, even those without a beam sensor. It could be more focused if only plants with data capability appeared—e.g. by filtering /user-plant for entries where sensor.has\_sensor === true (or skipping ones tagged isNoBeam === true). 2. **Beam-move recovery** If a beam gets moved to a different plant, that homey device is now “dead”. No data will flow because the sensor moved to a different /user-plant/id endpoint. From the homey side, your only option is to delete the plant and pair the new plant location as a new device to “follow the sensor”. My suggestion is that instead of storing a plant id as the device, you instead store the sensor id, and simply follow it to its current plant association by simply querying /user-plant before fetching the data from /user-plant/{{plant\_id}}. It is one more api call per polling period, but thats hardly any overhead at all. a sample response to illustrate my meaning ```auto { "plants": [ { "id": 85301, #plant id for the data endpoint that can be fetched prior to polling instead of being stored once during pairing process "nickname": "thai", "sensor": { "id": "FA:11:23:6A:EC:0E", #id of actual hardware "has_sensor": true, #filter property ... }, ... ] } ``` ---
**Author:** ![evdpol](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/evdpol/32/26730_2.png) [@evdpol](https://community.homey.app/u/evdpol)\ **Post date:** [August 1, 2025, 1:14pm UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/23 "2025-08-01T13:14:04Z")
> [@aesubs](#): > > **Onboarding filter** … The check on `sensor.has_sensor === true` wil be added in the next release, thanks! > [@aesubs](#): > > **Beam-move recovery** … I wil keep it how it is _for now_. Storing all plants in the app, and lookup the sensor ID of the plant from the device is the correct option. Still, the `id` of the device can’t be changed, so I have to store the sensor ID that on the device. Maybe I will introduce a migration from plant ID to sensor ID in the future. Thanks for the feedback! ---
**Author:** ![aesubs](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/aesubs/32/113989_2.png) [@aesubs](https://community.homey.app/u/aesubs)\ **Post date:** [August 1, 2025, 3:48pm UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/24 "2025-08-01T15:48:20Z")
thank you kindly for your consideration ---
**Author:** ![Sophie\_Pfluger](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sophie_pfluger/32/121620_2.png) [@Sophie\_Pfluger](https://community.homey.app/u/Sophie_Pfluger)\ **Post date:** [September 11, 2025, 7:41pm UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/25 "2025-09-11T19:41:00Z")
Does communication between Beam and Homey still work if the internet fails? ---
**Author:** ![evdpol](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/evdpol/32/26730_2.png) [@evdpol](https://community.homey.app/u/evdpol)\ **Post date:** [September 11, 2025, 9:10pm UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/26 "2025-09-11T21:10:27Z")
No, it does not. It uses the FYTA API to get the data from their servers. ---
**Author:** ![Sophie\_Pfluger](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sophie_pfluger/32/121620_2.png) [@Sophie\_Pfluger](https://community.homey.app/u/Sophie_Pfluger)\ **Post date:** [September 19, 2025, 9:13am UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/27 "2025-09-19T09:13:24Z")
Thank you for the reply. Are there any plans to integrate the Mini 2.0 in the future? So that it can be connected directly to Homey via BLE? ---
**Author:** ![tomasko](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tomasko/32/79143_2.png) [@tomasko](https://community.homey.app/u/tomasko)\ **Post date:** [June 25, 2026, 11:37am UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/28 "2026-06-25T11:37:43Z")
hi, all my devices have come into state: **Device Unavailable** FYTA API has denied access to this device But i am not sure how to re-initiated login process.. any idea what should i do? when i try to add new FYTA device there seems to appear login for a split of a second, but then the screen changes.. i have several flows that use data from fyta sensors and uninstalling and installing the app would require to remap all of these flow ☹ thanks in advance for any help… ---
**Author:** ![evdpol](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/evdpol/32/26730_2.png) [@evdpol](https://community.homey.app/u/evdpol)\ **Post date:** [June 25, 2026, 3:12pm UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/29 "2026-06-25T15:12:05Z")
You can try to repair the device which requires you to login again. ---
**Author:** ![dferch](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dferch/32/82976_2.png) [@dferch](https://community.homey.app/u/dferch)\ **Post date:** [June 27, 2026, 4:23pm UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/30 "2026-06-27T16:23:11Z")
Hi, I’d to move some Fyta sensor to new plants and now I won’t know, which sensor it is in Homey. Can you add information like sensor Mac-adress or serial number? So I could find matching pairs in Homey and in Fyta app. In Fyta public api I found this: ``` "sensor": { "id": "AA:AA:AA:2B:AF:F4", "has_sensor": true, "status": 1, "uuid_android": null, "uuid_ios": "AAAAA6BF-0457-3233-8A43-032B5377E763", "version": "0.30.0", "is_battery_low": false, "received_data_at": "2023-01-01 10:10:00", "created_at": "2022-01-01 01:10:10" }, ``` If you could map the “id” it would help. Using the Homey developer tools I can not find this attribute currently. Greetings, David ---
**Author:** ![evdpol](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/evdpol/32/26730_2.png) [@evdpol](https://community.homey.app/u/evdpol)\ **Post date:** [June 27, 2026, 6:33pm UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/31 "2026-06-27T18:33:39Z")
Yes, I will add a new setting which will display the sensor ID in the upcoming version. ---
**Author:** ![evdpol](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/evdpol/32/26730_2.png) [@evdpol](https://community.homey.app/u/evdpol)\ **Post date:** [July 3, 2026, 9:43am UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/32 "2026-07-03T09:43:54Z")
A new test version is available: [FYTA | Homey](https://homey.app/a/de.fyta/test/) Can you all try it out and see if everything works as expected? ---
**Author:** ![dferch](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dferch/32/82976_2.png) [@dferch](https://community.homey.app/u/dferch)\ **Post date:** [July 3, 2026, 11:48am UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/33 "2026-07-03T11:48:18Z")
The new version crashes anytime after starting it: ![CleanShot 2026-07-03 at 13.47.30@2x](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/b/eb2a736f79516bfd166037f0d62ea66736dd8048.png) ---
**Author:** ![evdpol](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/evdpol/32/26730_2.png) [@evdpol](https://community.homey.app/u/evdpol)\ **Post date:** [July 3, 2026, 12:05pm UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/34 "2026-07-03T12:05:21Z")
Could you send a diagnostic report? ---
**Author:** ![dferch](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dferch/32/82976_2.png) [@dferch](https://community.homey.app/u/dferch)\ **Post date:** [July 3, 2026, 12:09pm UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/35 "2026-07-03T12:09:49Z")
Yes, of cause. Here’s the diagnostic report id: `17134cf7-d4ce-41fd-97e9-21919fb6c31a` ---
**Author:** ![evdpol](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/evdpol/32/26730_2.png) [@evdpol](https://community.homey.app/u/evdpol)\ **Post date:** [July 3, 2026, 12:13pm UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/36 "2026-07-03T12:13:11Z")
Ah, I see the problem… Thanks. ---
**Author:** ![evdpol](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/evdpol/32/26730_2.png) [@evdpol](https://community.homey.app/u/evdpol)\ **Post date:** [July 3, 2026, 12:21pm UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/37 "2026-07-03T12:21:15Z")
Can you try again with the latest test version? ---
**Author:** ![dferch](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dferch/32/82976_2.png) [@dferch](https://community.homey.app/u/dferch)\ **Post date:** [July 3, 2026, 12:30pm UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/38 "2026-07-03T12:30:58Z")
Now it’s running fine. Do you know how fast the update for the sensor id is pulled from Fyta API? After waiting for some minutes it won’t update: ![CleanShot 2026-07-03 at 14.28.25@2x](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/a/1aa1bd1bfdfc7b1761dbf56c51ade960e3b8a7c1.png) And two of my plants (devices in Homey) are showing this error: ![CleanShot 2026-07-03 at 14.30.15@2x](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/d/fd47c5fb7a553fe3393272ecfc33d4e5e5cda3b6.png) ---
**Author:** ![evdpol](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/evdpol/32/26730_2.png) [@evdpol](https://community.homey.app/u/evdpol)\ **Post date:** [July 3, 2026, 1:40pm UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/39 "2026-07-03T13:40:28Z")
Can you send me your login details via PM or email? I’m not sure why `sensor.id` is empty at this point. ---
**Author:** ![evdpol](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/evdpol/32/26730_2.png) [@evdpol](https://community.homey.app/u/evdpol)\ **Post date:** [July 3, 2026, 2:45pm UTC](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367/40 "2026-07-03T14:45:44Z")
Which 2 plants give this error? [Previous page](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367.md?page=1) [Next page](https://community.homey.app/t/app-pro-fyta-the-smart-fitness-tracker-for-plants/107367.md?page=3)