Bei mir ist es gerade umgekehrt, es wird Sonnenschein erkannt, obwohl der Wert deutlich unter 120W/m² liegt.
Macht das so Sinn?
changed: added python3-paramiko as apt package (service.sh and install script) changed: set ImageFile.LOAD_TRUNCATED_IMAGES = True to prevent error message "image file is truncated" (FWD_TYPE = BANNER) fixed: Fixed detection of unknown HA items (was reporting an error for all temperature related values) fixed: WU-Server-Emulation https://ipaddress:port/observations/current/json/units=m[&stationId=FOSHKplugin&apiKey=MMM] (epoch, obsTimeLocal) fixed: output of missed sensors for MQTT/HA and InfluxDB repaired - key missing reverts to an empty string when the sensor starts transmitting again new: add stationtype as a field in daily CSV to monitor the firmware version new: Loxone version: integrate internal FOSHKplugin help page as Help button new: Loxone version: animated Optional Settings to illustrate the folding mechanism on plugin config page improved: Loxone version: improved accessibility (help texts can now also be accessed via the keyboard) improved: Loxone version: Translations slightly improved changed: Service file foshkplugin.service modified: now with Documentation, Wants/After=network-online.target, optional /etc/environment and without StandardOutput/StandardError=syslog changed: Heatindexs calculation includes now the Low-RH-Adjustment: RH < 13% and 80°F <= temp <= 112°F and the High-RH-Adjustment RH > 85% and 80°F <= temp <= 87°F new: with Export\ADD_HUMIDEX = True you can enable/disable the Humidex calculation for outdoor/indoor sensor, WH31 and WH45/46 - default: False new: with Export\ADD_APPARENT = True you may enable/disable the AT (Australian apparent temperature) calculation - default: False
https://foshkplugin.phantasoft.de/files/loxberry-FOSHKplugin-0.0.10Beta.zip
$ grep -e Err -e error foshkplugin.log Err:4 https://deb.nodesource.com/node_18.x bullseye Release Err:5 https://repos.influxdata.com/debian stable InRelease Err:6 https://packages.grafana.com/oss/deb stable InRelease W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DA61C26A0585BD3B W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.grafana.com/oss/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 14:57:48.215 <ERROR> Error updating apt database - Error 100 Err:5 https://deb.nodesource.com/node_18.x bullseye Release Err:1 https://packages.grafana.com/oss/deb stable InRelease Err:4 https://repos.influxdata.com/debian stable InRelease W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.grafana.com/oss/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DA61C26A0585BD3B 14:58:09.501 <ERROR> Error updating apt database - Error 100 14:58:09.894 <ERROR> Error updating apt database. All servers give an error. Internet connection available? Giving up. 14:58:22.041 <CRITICAL> Error installing python3 python3-pip python3-setuptools libstring-escape-perl python3-pil libopenjp2-7 python3-venv python3-paramiko - Error 100 14:59:47.255 <WARNING> An error or warning occurred
Collecting influxdb-client Downloading influxdb_client-1.50.0-py3-none-any.whl.metadata (65 kB) Collecting reactivex>=4.0.4 (from influxdb-client) Downloading reactivex-5.1.0-py3-none-any.whl.metadata (6.5 kB) Requirement already satisfied: certifi>=14.05.14 in /usr/lib/python3/dist-packages (from influxdb-client) (2025.1.31) Requirement already satisfied: python-dateutil>=2.5.3 in /usr/local/lib/python3.13/dist-packages (from influxdb-client) (2.9.0.post0) Requirement already satisfied: urllib3>=1.26.0 in /usr/lib/python3/dist-packages (from influxdb-client) (2.3.0) Requirement already satisfied: six>=1.5 in /usr/local/lib/python3.13/dist-packages (from python-dateutil>=2.5.3->influxdb-client) (1.17.0) Collecting typing-extensions<5,>=4.15.0 (from reactivex>=4.0.4->influxdb-client) Downloading typing_extensions-4.16.0-py3-none-any.whl.metadata (3.3 kB) Downloading influxdb_client-1.50.0-py3-none-any.whl (746 kB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 746.3/746.3 kB 3.0 MB/s eta 0:00:00 Downloading reactivex-5.1.0-py3-none-any.whl (257 kB) Downloading typing_extensions-4.16.0-py3-none-any.whl (45 kB) Installing collected packages: typing-extensions, reactivex, influxdb-client Attempting uninstall: typing-extensions Found existing installation: typing_extensions 4.13.2 error: uninstall-no-record-file × Cannot uninstall typing_extensions 4.13.2 ╰─> The package's contents are unknown: no RECORD file was found for typing_extensions. hint: The package was installed by debian. You should check if it can uninstall the package. yes: standard output: Broken pipe <WARNING> Python influxdb-client installation failed! The plugin will not work without. <WARNING> Giving up. 10:00:24.714 <CRITICAL> Script/Command fails. Installation cannot be continued. <LOGEND> 30.07.2026 10:00:25 TASK FINISHED
fixed: HA-Icon for apparent temperature in docs: Loxone --> LoxBerry changed: code-cleaning changed: calculation of weather condition in case no coords set changed: LoxBerry version: added more python3-packages (python3-influxdb, python3-influxdb-client, python3-requests, python3-paho-mqtt, python3-urllib3, python3-pil) in dpkg/apt for better compatibility changed: with additional parameter "keyonly" you may show the keys only with getFullDict improved: better support InfluxDB v2 (newer InfluxDB versions rejects the key named "time") changed: key "time" in status dict renamed to "stattime" and is localtime (no Loxone time anymore) - ATTENTION! may cause compatibility issues! new: experimental support of InfluxDB v3 (FWD_TYPE = INFLUX3MET/INFLUX3IMP) - keep in mind there's a hard limit of 500 keys in InfluxDB v3 - you may reduce the data with FWD_OPTION (weather/diagnostic/minmax/missing/iot/sun/status=False) improved: HA-Icons fuer WS6210 keys: imei, iccid, imsi, up_mtd, msisdn, ext_volt, console_batt, consolebattp, wifimode, charge
https://foshkplugin.phantasoft.de/files/loxberry-FOSHKplugin-0.0.10Beta.zip
fixed: HA-Icon for apparent temperature in docs: Loxone --> LoxBerry changed: code-cleaning changed: calculation of weather condition in case no coords set changed: LoxBerry version: added more python3-packages (python3-influxdb, python3-influxdb-client, python3-requests, python3-paho-mqtt, python3-urllib3, python3-pil) in dpkg/apt for better compatibility changed: with additional parameter "keyonly" you may show the keys only with getFullDict improved: better support InfluxDB v2 (newer InfluxDB versions rejects the key named "time") changed: key "time" in status dict renamed to "stattime" and is localtime (no Loxone time anymore) - ATTENTION! may cause compatibility issues! new: experimental support of InfluxDB v3 (FWD_TYPE = INFLUX3MET/INFLUX3IMP) - keep in mind there's a hard limit of 500 keys in InfluxDB v3 - you may reduce the data with FWD_OPTION (weather/diagnostic/minmax/missing/iot/sun/status=False) improved: HA-Icons fuer WS6210 keys: imei, iccid, imsi, up_mtd, msisdn, ext_volt, console_batt, consolebattp, wifimode, charge
https://foshkplugin.phantasoft.de/files/loxberry-FOSHKplugin-0.0.10Beta.zip
Wir verarbeiten personenbezogene Daten über Nutzer unserer Website mithilfe von Cookies und anderen Technologien, um unsere Dienste bereitzustellen, Werbung zu personalisieren und Websiteaktivitäten zu analysieren. Wir können bestimmte Informationen über unsere Nutzer mit unseren Werbe- und Analysepartnern teilen. Weitere Einzelheiten finden Sie in unserer Datenschutzrichtlinie.
Wenn Sie unten auf "Einverstanden" klicken, stimmen Sie unserer Datenschutzrichtlinie und unseren Datenverarbeitungs- und Cookie-Praktiken wie dort beschrieben zu. Sie erkennen außerdem an, dass dieses Forum möglicherweise außerhalb Ihres Landes gehostet wird und Sie der Erhebung, Speicherung und Verarbeitung Ihrer Daten in dem Land, in dem dieses Forum gehostet wird, zustimmen.
Kommentar