Metainformationen zur Seite
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende Überarbeitung | ||
plugins:foshkplugin:foshkplugin_generic_version [2024/03/27 20:52] – Oliver Engel | plugins:foshkplugin:foshkplugin_generic_version [2024/05/07 11:55] (aktuell) – Oliver Engel | ||
---|---|---|---|
Zeile 74: | Zeile 74: | ||
* changed: all incoming get-requests will be URL-decoded now | * changed: all incoming get-requests will be URL-decoded now | ||
* new: enable signal quality acquisition on supported consoles with Export\ADD_SIGNAL = True (default: False) | * new: enable signal quality acquisition on supported consoles with Export\ADD_SIGNAL = True (default: False) | ||
+ | * new: with the option FWD_OPTION = blacklist=False, | ||
+ | * new: Introduction of a naming scheme for beta versions ("Beta YYMMDD" | ||
+ | * new: ADD_SCRIPT - offers the possibility to integrate data from third party devices - see https:// | ||
+ | * changed: postroot.sh - check Pillow installation fixed (newer versions named pillow instead of Pillow) - LoxBerry only | ||
+ | * changed: sed is now working globally in postinstall.sh & postupgrade.sh - LoxBerry only | ||
+ | * new: enable debug mode if file debug.enable found in the config directory\\ enable debug mode with bin/ | ||
+ | * changed: **changed default SUN_COEF from 0.8 to 0.92** - should fit better for Germany (too little sunshine recorded: decrease value; too much: increase) | ||
+ | * changed: all sun related values (e.g. sunshine, srsum, sunhours, ...) are only transmitted if solarradiation is present | ||
+ | * improved: better integration with Home Assistant (MQTT discovery) - see [[https:// | ||
Zeile 3102: | Zeile 3111: | ||
\\ | \\ | ||
Another option - if an MQTT broker is available - is to transmit the data via [[https:// | Another option - if an MQTT broker is available - is to transmit the data via [[https:// | ||
- | However, this entails longer configuration work because you have to make an entry in a YAML for each desired data point in the Home Assistant: | + | However, this entails longer configuration work because you have to make an entry in a YAML for each desired data point the Home Assistant: |
<code syntaxhighlighter-pre> | <code syntaxhighlighter-pre> | ||
Zeile 3126: | Zeile 3135: | ||
FWD_URL = 192.168.15.236: | FWD_URL = 192.168.15.236: | ||
FWD_ENABLE = True | FWD_ENABLE = True | ||
- | FWD_OPTION = MQTTCYCLE=5, | + | FWD_OPTION = MQTTCYCLE=5, |
FWD_SID = MQTT-username | FWD_SID = MQTT-username | ||
FWD_PWD = MQTT-password | FWD_PWD = MQTT-password | ||
Zeile 3140: | Zeile 3149: | ||
If the MQTT broker requires a login, the credentials can be configured with FWD_SID (user name) and FWD_PWD (password).\\ | If the MQTT broker requires a login, the credentials can be configured with FWD_SID (user name) and FWD_PWD (password).\\ | ||
\\ | \\ | ||
- | By default, all values including the min/max values (if configured) are transmitted via MQTT. To prevent the transmission of the min/max values, minmax=False can be set as an additional option in FWD_OPTION.\\ | + | By default, all values including the min/max values (if configured) are transmitted via MQTT. To prevent the transmission of the min/max values, minmax=False can be set as an additional option in FWD_OPTION. If the status messages from FOSHKplugin are also to be made available via MQTT, FWD_STATUS should be set to True. Alternatively, |
- | If the status messages from FOSHKplugin are also to be made available via MQTT, FWD_STATUS should be set to True. Alternatively, | + | The time format for the output of timestamps (e.g. lightning_time and all min/max times) can be defined with dtime_format. For possible formatting options, see the recipe [[plugins: |
+ | If the sensor data is to be separated from the diagnostic data (info data, battery and signal values), this can be realised via the additional option diagnostic=True in the FWD_OPTION. Two separate cards for sensor data and diagnostic data are then generated in the Home Assistant. If diagnostic=False is set or the diagnostic option is missing within the FWD_OPTION, all data is displayed together in one card.\\ | ||
\\ | \\ | ||
<WRAP center round important 100%> | <WRAP center round important 100%> | ||
- | **Attention!**\\ | + | **Attention!**\\ |
</ | </ | ||
Zeile 3173: | Zeile 3183: | ||
All data points generated by FOSHKplugin should now be available within Home Assistant for further use and visualisation.\\ | All data points generated by FOSHKplugin should now be available within Home Assistant for further use and visualisation.\\ | ||
\\ | \\ | ||
+ | {{: | ||
+ | \\ | ||
+ | \\ | ||
+ | **Advantages of the connection via FOSHKplugin and MQTT** | ||
+ | * Signal quality values of the sensors are transmitted (if the console supports the http/JSON API) | ||
+ | * Additional values available such as wind chill, dew point (also for all indoor sensors), spread, feelslike, heat index, AQI for WH41/ | ||
+ | * Any values from other sensors can be integrated | ||
+ | * Availability of min/max values with respective times | ||
+ | * Warnings (thunderstorm, | ||
+ | |||
**Note:**\\ | **Note:**\\ | ||
The [[https:// | The [[https:// | ||
+ | |||
+ | ++++ | ||
+ | |||
+ | ---- | ||
+ | |||
+ | {{anchor: | ||
+ | |||
+ | ++++ Android weather widget based on clientraw.txt with FOSHKplugin | | ||
+ | |||
+ | **Android weather widget based on clientraw.txt with FOSHKplugin** | ||
+ | |||
+ | After I found a very nice weather widget for Android with [[https:// | ||
+ | Now the temperature graph (in WPW the green graph in the background of the temperature) and the icon for the " | ||
+ | \\ | ||
+ | {{: | ||
+ | \\ | ||
+ | \\ | ||
+ | Unfortunately, | ||
+ | However, the current status is quite respectable and helps me at least to check the essential weather data at the location of a station at a glance. The advantage is that the widget updates the data every time it is unlocked - so you should always see the current data. | ||
+ | |||
+ | In addition to FOSHKplugin, | ||
+ | A corresponding forward would look like this, for example: | ||
+ | |||
+ | <code syntaxhighlighter-pre> | ||
+ | [Forward-66] | ||
+ | FWD_CMT = save via ftps as remote clientraw.txt | ||
+ | FWD_ENABLE = True | ||
+ | FWD_SID = ftp-username | ||
+ | FWD_PWD = ftp-password | ||
+ | FWD_TYPE = CLIENTRAWTXT | ||
+ | FWD_URL = ftps:// | ||
+ | </ | ||
+ | |||
+ | The credentials for the FTP(s) access must be entered under FWD_SID and FWD_PWD and the target URL under FWD_URL.\\ | ||
+ | \\ | ||
+ | Another - unfortunately also discontinued - project for a widget based on clientraw.txt is [[https:// | ||
+ | \\ | ||
+ | {{: | ||
+ | \\ | ||
+ | \\ | ||
+ | At least the source code is available - so you could still make changes if necessary. Perhaps someone will find someone who can take the current status and develop it further.\\ | ||
+ | When I find the time, I'll upload it to Android Studio and see what I can do with it.\\ | ||
+ | \\ | ||
+ | Personally, I find the font a bit small and I would also prefer German-language terms. I also like the icon for the current weather (or the forecast) from the Weather Personal widget, which is unfortunately missing here.\\ | ||
+ | But I think it's a good basis for my own experiments ...\\ | ||
+ | \\ | ||
+ | This Android widget also uses a file in clientraw.txt format as the data source - so a forward would have to be configured in the FOSHKplugin as specified above. Of course, **ONE** Forward and therefore **ONE** clientraw.txt is sufficient for both widgets as well as for any other applications.\\ | ||
+ | \\ | ||
++++ | ++++ |