emericg
commented
2 years ago I think I am one of the few people who installed it on a mobile device. I was curious, if I can exchange the proprietary FlowerCare App with GNU software. In overall a lot of effort has been put in WatchFlower for a usable app, that I want to appreciate. However, some things do not work as Intendant or are missing, but first I want to give feedback of core functionalities.
If you build it yourself on Android then yes I think you might be the first! The version published on the store is using the exact same code than the open source version, but:
- the package signature is different
- I deploy a patched version of Qt for better Bluetooth advertisement support, like its mentionned in the readme (https://github.com/emericg/WatchFlower#using-flowercare-live-mode-and-historical-data). These patchs will be included in Qt 6.3 (probably).
The sync routine will not finish, blocking other threads of the app until it is force closed
This is weird, it's obviously not supposed to do that. If you are running your own version you should be able to use the debugger to check what's blocking the app. The history sync can be run while the app is refreshing other sensors, and is very tolerant to the bluetooth communication being stopped without warning (happens all the time...).
one themometer with alternative firmware removed
Yeah I don't support those. I write documentations for device APIs (like this https://github.com/emericg/WatchFlower/blob/master/docs/thermobeacon-ble-api.md), if these custom firmware have a common and documented API it might be worth doing it. Otherwise it's really not worth the efforts.
Thermometer history is not supported in WatchFlower.
Some have history support (it's mentionned on the website: https://emeric.io/WatchFlower/#devices). But every device needs a proper reverse enginering of its API, and this takes time an efforts...
TUstudents
Hi,
I think I am one of the few people who installed it on a mobile device. I was curious, if I can exchange the proprietary FlowerCare App with GNU software. In overall a lot of effort has been put in WatchFlower for a usable app, that I want to appreciate. However, some things do not work as Intendant or are missing, but first I want to give feedback of core functionalities.
Bug Registered devices are synced on app start, but syncing with device history needs a manual start for every device with the "Update history" command. The sync routine will not finish, blocking other threads of the app until it is force closed. However, synced history data is visible in the app.
Expected behavior After history syncing of one device the "update history" should be available for other devices again. Ideally, history syncing should be made available as part of the auto sync queue routine for every device
Details After multiple scanning of sensors I was able to register 2 MiFlora produced a few years ago, 2 VegTrugs and 2 Miflora of the newest generation produced June 2021. Additionally 1 Thermometer was registered and one themometer with alternative firmware removed. Thermometer history is not supported in WatchFlower. After every history sync the app will no longer follow new commands like update, blink led,.. but history values are displayed in app. History is not deleted from device after sync, which is very good as history can also be imported to FlowerCare, which resets history after import in Mi's database. I think the sync routine just never finishes or is throwing an error. In logcat some errors are logged. These errors are produced during switching to watchflower and are there regardless of sync command.
From a quick google search this is unreleated to bluetooth and indicates an issue with flutter and garbage collection.
Environment Android 11 on a rooted device, custom firmware similar to Lineage OS. Flower Care is running fine as well as other bluethooth devices (smart watch, phones, Mi thermometers...)