Fyta provides a plant sensor. See https://fyta.de/en
This binding links the Fyta webservice.
Resources
Changelog
- 21.10.2023: Added new nutrients-status channel and deprecated salintiy channels
Fyta provides a plant sensor. See https://fyta.de/en
This binding links the Fyta webservice.
@seime Thank you for this binding.
An auto-discover for the beams would be great, but with the official App i managed to get the MAC und the first Beam connected.
It seems like there are no live-Data aviable. The name und thumbnail item was filled (and updatet) but Moisture_status and Last_reported_sensor_data remain null.
Do you have any advice?
Greetings
Hi, the API has changed a bit since I created the binding, and since noone seemed to download it I have not updated it yet.
I’m a bit short on time the next period, but if you would care to create a PR Im happy to merge.
Arne
I’ve added a new version. The only difference is the new nutrients-status channel to replace the salinity channels.
You need to set loglevel to TRACE and post the logs in order for me to assist you.
Regards
Have problems with setting up the FYTA Account Thing. Get the following error:
COMMUNICATION_ERROR
Error sending request to server: Exception caught trying to communicate with API: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Hi, yes they have messed up their certificate config. See fyta discord for details.
Rgds
Any updates here? - cannot interpret the discord messages in a way to get the add-on running again…
regards, Gerald
Mine too! What I just noticed independently is that autodiscovery of the sensors by the addon does not work. Have to add them manually with the MAC address. Not an issue, just want to mention.
Thanks for letting me know @wartel - the API had changed.
Fixed in latest version
Using version **Fyta Beam plant sensor binding [4.0.0.0;6.0.0.0) but auto discovery not working. It was on previous version. Thanks
Sorry for the late reply.
I ran a discovery, OH found a Fyta sensor and added it. It came online.
Could you please describe how to reproduce?
BRG
I create a FYTA bridge/thing OK and goes online
Ok, assuming that
.. I must ask you to send me DEBUG level logs for the binding so I can investigate.
BRG
Hi Arne!
thanks for your continous support with this FYTA binding ![]()
I want to step by to let you know, that actually (since today?) the FYTA account thing goes offline throwing the following error:
COMMUNICATION_ERROR
Error sending request to server: Exception caught trying to communicate with API: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
I am on OpenHAB 4.3.7. No other binding throws errors due to certificate problems.
runtimeInfo:
version: 4.3.7
buildString: Release Build
locale: de-DE
systemInfo:
configFolder: /etc/openhab
userdataFolder: /var/lib/openhab
logFolder: /var/log/openhab
javaVersion: 17.0.17
javaVendor: Debian
osName: Linux
osVersion: 6.12.25+rpt-rpi-2712
osArchitecture: aarch64
availableProcessors: 4
freeMemory: 119976496
totalMemory: 805306368
uptime: 101375
startLevel: 100
Do you already know of that issue? Is there something I can do to fix it? Or is a new binding needed? ![]()
Thanks again for your support!
@seime the same - error connection caused by the bridge
The TLS/SSL certificate on their API is broken again. HA and Homey users reports the same.
Seems like a similar issue they had 2 years ago; Fyta Beam plant sensor binding [4.0.0.0;6.0.0.0) - #6 by seime
The best thing to do is to have the FYTA devs fix their server, you can reach them on this discord channel: Discord
Thank you @seime !
They confirmed there have been problems updating their certificates, but they fixed it now and I can confirm, it’s working again after setting the FYTA bridge to offline and setting it to online again. ![]()
@seime Could you please provide a jar file for openHAB 5?
Hi @ThomasM102 , please try the lastest version (marked as OH4, but should work on OH5 as well)