App Store Page: FYTA App voor Homey | Homey
FYTA helps you to keep your plants healthy.
I enjoy creating apps for Homey and try to support them as best as I can. If you enjoy using my apps a donation in return for the time I put into this is much appreciated.
A big shout out to @Frank_Hooft for providing me access to his FYTA account! Thank you! 
– Reserved –
Installed it and works fine! Thank you for this app.
One request for enhancement:
Can you add support for german language? I could help on translation 
I would also like to use this app.
My idea:
As soon as a plant reports that it has too little light, I would like to switch on a Hue Spot.
If the light is sufficient, then switch it off again.
Can anyone help me with the implementation?
Which card do I need to use? Which values do I need to enter?
Many thanks
How do I connect to fyta? Does it have to be on the same network as the homey? I have a segregated network.
Update: Got FYTA hub on the same network as homey, but I still cannot add the beams.
Can you send me a diagnostic report after you get that error, please?
Kode is: ec05369e-75dc-4055-9aac-81e9033e9422
Thanks for your report.
I will fix this in the next version, there is a deleted plant in your account.
– Edwin
I released a new version of the app. It should work as expected now.
If not, please let me know.
– Edwin
Worked. Thanks 
thanks for creating the app! looking forward to start using it
Getting this error
FYTA API has denied access to this device
4e1fae3b-75d0-46a4-9ab4-b33bd720e48b
Edit: Deleted the app and reinstalled it. That fixed it.
I experienced the exact same thing today. Uninstall and install corrected the issue.
Hello,
I think I discovered an edge case with the app.
If you ever need to add a new beam, the process of authing revokes the token/session for any existing beams in your homey. This is really inconvienent if you add beams on a regular basis. Is there any way you could add reauth workflow in order to repair the session without having to delete and re-add the beams?
Hi Andy,
Thank you for your message.
I will try to check if I can solve this.
The only thing is, I only have 1 active device, so adding a second device is a bit difficult.
I will send you a personal message when I publish a test version for you to validate, allright?
– Edwin
works for me. thank you
Hi Andy,
When I add a second device, the log is showing a different session ID (source), but when the device is added, the already existing session ID is used. See the logs below and the source.
Why do you think it revokes the session when adding a second device? Can you show me some logs?
<< First device is already added >>
2024-09-11T22:17:20.427Z [log] [App] [Client] [c:default] [s:eb41c620-09de-409b-8338-2666a4402b75] Initialized
<< Pairing second device >>
2024-09-11T22:18:25.254Z [log] [App] [Client] [c:default] [s:c33c6ced-fa3c-4032-af4e-a887bee27f1d] Initialized
2024-09-11T22:18:25.256Z [log] [ManagerDrivers] [Driver:xxxx] Multi-Session disabled. Selected eb41c620-09de-409b-8338-2666a4402b75 as active session.
2024-09-11T22:18:26.459Z [log] [ManagerDrivers] [Driver:xxxx] Pairing devices
<< Adding second device >>
2024-09-11T22:23:30.112Z [log] [App] [Sync] Started
2024-09-11T22:23:30.118Z [log] [App] [Client] [c:default] [s:eb41c620-09de-409b-8338-2666a4402b75] GET /my/device/details
– Edwin
i say this because the moment i add a new beam. the other beams session no longer worked. thats what the exclamation points in my screenshot are indicating. and theres no way to fix them or reauth from what i can tell. deleting readding is the only fix. i was able to reproduce this behavior. when adding a beam and logging into fyta, the already added beams break.
Can you send me your login details via a private message, so I can see that is going on?
hi sorry you may disregard. im no longer able to replicate the issue.
