I can, haha! This will be fixed in the next version of the app.
Hello @evdpol
Would you be open to some QOL improvements Iāve thought of while using the app for a while?
-
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).
-
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
{
"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
...
},
...
]
}
The check on sensor.has_sensor === true wil be added in the next release, thanks!
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!
thank you kindly for your consideration
Does communication between Beam and Homey still work if the internet fails?
No, it does not. It uses the FYTA API to get the data from their servers.
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?