- Willkommen im Forum „FHEM Forum“.
Neueste Beiträge
#1
FHEM Code changes / Revision 30966: 76_SolarForeca...
Letzter Beitrag von System - 17 März 2026, 00:21:02Revision 30966: 76_SolarForecast: contrib Version 2.4.0
76_SolarForecast: contrib Version 2.4.0
Source: Revision 30966: 76_SolarForecast: contrib Version 2.4.0
76_SolarForecast: contrib Version 2.4.0
Source: Revision 30966: 76_SolarForecast: contrib Version 2.4.0
#2
Solaranlagen / Aw: 76_SolarForecast - Informa...
Letzter Beitrag von DS_Starter - 17 März 2026, 00:05:35Habe das Problem gefunden und beseitigt. Es war eine "Spezialität" bei der Speicherung der AI::FANN Objekte.
Update liegt im contrib.
Update liegt im contrib.
#3
Sonstige Systeme / Aw: Rademacher Duofern Wandsch...
Letzter Beitrag von paulbaumann - 16 März 2026, 23:22:14Nein funktioniert nicht, bin über "define WTaster1 DUOFERN .." nicht hinaus gekommen
Log sagt: No I/O device found for WTaster1
Und ich kann ja nur "set WTaster1 remotePair" eingeben ohne das was passiert
Den Befehl pair akzeptiert er nicht.
Wo ist mein Denkfehler?
Log sagt: No I/O device found for WTaster1
Und ich kann ja nur "set WTaster1 remotePair" eingeben ohne das was passiert
Den Befehl pair akzeptiert er nicht.
Wo ist mein Denkfehler?
#4
Heizungssteuerung/Raumklima / Aw: LAN-Anbindung für BSB-Bus ...
Letzter Beitrag von freetz - 16 März 2026, 23:15:39Nach einem Jahr steht mal wieder eine neue Release-Version an, nachdem diese jetzt seit einiger Zeit stabil läuft. Hier das ChangeLog - bitte die "breaking changes" beachten, und die _config.h Einstellungen im Auge behalten bzw. updaten, da durch die Änderungen in der EEPROM-Struktur wieder die Defaults aus der Datei übernommen werden.
Version 5.1
16.03.2026
- ATTENTION: BREAKING CHANGE! EEPROM layout has changed - this leads to re-reading configuration from `BSB_LAN_config.h`, and thus overwriting EEPROM configuration. Take note of any settings in the web-interface before updating!
- ATTENTION: (potentially) BREAKING CHANGE! BSB-LAN is migrating to using TLS (transport layer security) on ESP32 microcontrollers. TLS requires a substantial amount of additional flash memory. For most users, it should still be fine, but if you have a large number of parameters (>1000), you might run out of flash memory. In that case, you can disable TLS by enabling the `#define NO_TLS` definement in `BSB_LAN_config.h`. If you want to use SSL with self-signed certificates add the definement `I_WANT_INSECURE_TLS_AND_I_KNOW_WHAT_I_AM_DOING` to `BSB_LAN_config.h`.
- ATTENTION: (potentially) BREAKING CHANGE! We have begun with using TLS to connect to remote MQTT brokers. If your remote broker uses a self-signed certificate, connection will fail. Connection to local brokers will continue to be made without TLS. (Poor man's) detection whether it is remote or local is done by checking the broker's address: if it is an IP address (i.e. starting with a digit), it is assumed to be local. Otherwise it is considered remote.
- ATTENTION: Potential wrong assignment of data type for `VT_HOURS_WORD` in the past: If you have problems setting a parameter with data type `VT_HOURS_WORD`, then change it to `VT_HOURS_WORD_N`. It _should_ only affect parameter 7040, but let me know if others are also affected as well.
- Custom code can now also react to broadcast messages (beyond already existing MQTT functionality) by using BSB_LAN_custom_GetMessage.h
- New parameters 10196 to 10199 for displaying numerical error messages that should work on almost all devices.
- New configuration variable `MQTTRefAD` controls whether auto-discovery entries should be resent to the broker in case the broker lost the session state. This might take a while if you have many parameters and the broker does not provide persistency.
- New configuration variable `mqtt_unit_set` defines how measurement units are sent via MQTT when using Rich JSON or auto-discovery: The default CF_MQTT_UNIT_LOCALIZED will send unit strings in the configured language, exactly as shown in the BSB-LAN web interface. CF_MQTT_UNIT_HOMEASSISTANT sends unit strings in the format used by Home Assistant to avoid warning messages about unknown unit strings. CF_MQTT_UNIT_NONE will send MQTT messags with no unit text. This setting only applies to MQTT and does not affect the web interface which will always show units in the localized language. When selecting Home Assistant as the unit format, the 'device_class' string will be sent for compatible parameters during MQTT auto-discovery so that automations can correctly identify sensor classes.
- Configuration variable `replaceDisabled` defines the value for a deactivated/inactive status in parameters with numerical values. Defaults to `---`; Home Assistant expects `None` here, others might expect `0`. Keep in mind that both is inexact information, but depending on the circumstances, this might be the closest you would get if otherwise the external systems would not accept the data coming from BSB-LAN.
- Added option `,IP` for URL command `/Gxx` to activate pull-up for GPIO `xx`.
- Added functionality to monitor parameter changes and send out push notificatons upon changes. See `custom_functions/Push_notifications_for_changed_parameters`. Currently works with pushsafer.com, but adaptation to other services should be easy.
- Added a minimal recovery firmware upload function via WebSerial (requires Google Chrome or Microsoft Edge). Go to https://docs.bsb-lan.de/recovery_flasher.html and connect your ESP32 using a data-capable USB cable and select the microcontroller you are using. No other software required.
- Some parameters expect valid, non-zero values even when disabling that parameter. BSB-LAN now queries the current value and then sets the parameter as disabled while using that previous value as payload. This results in two MQTT pushes, one for querying the old value and then another one with the disabled value.
- Upon failed parameter query, BSB-LAN now sends "---" (or "None", depending on the settings) to the MQTT broker instead of skipping the update.
- Added definement CUSTOM_PARTITION_TABLE in case you use a microcontroller with larger flash memory. Activate it in BSB_LAN_config.h in order to select a partition scheme other than "Minimal SPIFFS"
- Security check for caps letters removed because almost all letters are being used nowadays anyway.
- MQTT broker address increased to 64 characters to accommodate HiveMQ's long URLs.
- Updated PubSubClient from knolleary's repository to pubsubclient3, thanks to @uschindler. MQTT publish and subscribe now runs with QoS 1. However, on publish, there are no resends from BSB-LAN to the broker, QoS is only passed on from the broker to the subscriber. So make sure that your subscriber (such as Home Assistant) uses at least QoS 1 when subscribing.
- If you use the Arduino IDE 1.8.18 on Linux ARM, please take note that ESP32 framework version 3.0.7 is the last framework version that is currently running on these systems. [See our Wiki](https://github.com/fredlcore/BSB-LAN/wiki/Installing-BSB%E2%80%90LAN-using-arduino%E2%80%90cli) for using `arduino-cli` as a command-line-based alternative that brings the most recent frameworks to ARM and other architectures
- This release has been supported by the following sponsors: matze-dev
Version 5.1
16.03.2026
- ATTENTION: BREAKING CHANGE! EEPROM layout has changed - this leads to re-reading configuration from `BSB_LAN_config.h`, and thus overwriting EEPROM configuration. Take note of any settings in the web-interface before updating!
- ATTENTION: (potentially) BREAKING CHANGE! BSB-LAN is migrating to using TLS (transport layer security) on ESP32 microcontrollers. TLS requires a substantial amount of additional flash memory. For most users, it should still be fine, but if you have a large number of parameters (>1000), you might run out of flash memory. In that case, you can disable TLS by enabling the `#define NO_TLS` definement in `BSB_LAN_config.h`. If you want to use SSL with self-signed certificates add the definement `I_WANT_INSECURE_TLS_AND_I_KNOW_WHAT_I_AM_DOING` to `BSB_LAN_config.h`.
- ATTENTION: (potentially) BREAKING CHANGE! We have begun with using TLS to connect to remote MQTT brokers. If your remote broker uses a self-signed certificate, connection will fail. Connection to local brokers will continue to be made without TLS. (Poor man's) detection whether it is remote or local is done by checking the broker's address: if it is an IP address (i.e. starting with a digit), it is assumed to be local. Otherwise it is considered remote.
- ATTENTION: Potential wrong assignment of data type for `VT_HOURS_WORD` in the past: If you have problems setting a parameter with data type `VT_HOURS_WORD`, then change it to `VT_HOURS_WORD_N`. It _should_ only affect parameter 7040, but let me know if others are also affected as well.
- Custom code can now also react to broadcast messages (beyond already existing MQTT functionality) by using BSB_LAN_custom_GetMessage.h
- New parameters 10196 to 10199 for displaying numerical error messages that should work on almost all devices.
- New configuration variable `MQTTRefAD` controls whether auto-discovery entries should be resent to the broker in case the broker lost the session state. This might take a while if you have many parameters and the broker does not provide persistency.
- New configuration variable `mqtt_unit_set` defines how measurement units are sent via MQTT when using Rich JSON or auto-discovery: The default CF_MQTT_UNIT_LOCALIZED will send unit strings in the configured language, exactly as shown in the BSB-LAN web interface. CF_MQTT_UNIT_HOMEASSISTANT sends unit strings in the format used by Home Assistant to avoid warning messages about unknown unit strings. CF_MQTT_UNIT_NONE will send MQTT messags with no unit text. This setting only applies to MQTT and does not affect the web interface which will always show units in the localized language. When selecting Home Assistant as the unit format, the 'device_class' string will be sent for compatible parameters during MQTT auto-discovery so that automations can correctly identify sensor classes.
- Configuration variable `replaceDisabled` defines the value for a deactivated/inactive status in parameters with numerical values. Defaults to `---`; Home Assistant expects `None` here, others might expect `0`. Keep in mind that both is inexact information, but depending on the circumstances, this might be the closest you would get if otherwise the external systems would not accept the data coming from BSB-LAN.
- Added option `,IP` for URL command `/Gxx` to activate pull-up for GPIO `xx`.
- Added functionality to monitor parameter changes and send out push notificatons upon changes. See `custom_functions/Push_notifications_for_changed_parameters`. Currently works with pushsafer.com, but adaptation to other services should be easy.
- Added a minimal recovery firmware upload function via WebSerial (requires Google Chrome or Microsoft Edge). Go to https://docs.bsb-lan.de/recovery_flasher.html and connect your ESP32 using a data-capable USB cable and select the microcontroller you are using. No other software required.
- Some parameters expect valid, non-zero values even when disabling that parameter. BSB-LAN now queries the current value and then sets the parameter as disabled while using that previous value as payload. This results in two MQTT pushes, one for querying the old value and then another one with the disabled value.
- Upon failed parameter query, BSB-LAN now sends "---" (or "None", depending on the settings) to the MQTT broker instead of skipping the update.
- Added definement CUSTOM_PARTITION_TABLE in case you use a microcontroller with larger flash memory. Activate it in BSB_LAN_config.h in order to select a partition scheme other than "Minimal SPIFFS"
- Security check for caps letters removed because almost all letters are being used nowadays anyway.
- MQTT broker address increased to 64 characters to accommodate HiveMQ's long URLs.
- Updated PubSubClient from knolleary's repository to pubsubclient3, thanks to @uschindler. MQTT publish and subscribe now runs with QoS 1. However, on publish, there are no resends from BSB-LAN to the broker, QoS is only passed on from the broker to the subscriber. So make sure that your subscriber (such as Home Assistant) uses at least QoS 1 when subscribing.
- If you use the Arduino IDE 1.8.18 on Linux ARM, please take note that ESP32 framework version 3.0.7 is the last framework version that is currently running on these systems. [See our Wiki](https://github.com/fredlcore/BSB-LAN/wiki/Installing-BSB%E2%80%90LAN-using-arduino%E2%80%90cli) for using `arduino-cli` as a command-line-based alternative that brings the most recent frameworks to ARM and other architectures
- This release has been supported by the following sponsors: matze-dev
#5
Solaranlagen / Aw: APSystems EZ-1
Letzter Beitrag von Ralf9 - 16 März 2026, 23:03:27Wenn Du auf die 1.12.2 updatest, dann müsstest Du es auch bestätigen können:
ZitatWarum kappt mein EZ1-M die Leistung bei den MPPTs bei ca. 416W? Sollte es nicht bis maximal 500 W je MPPT möglich sein bei unsymmetrischer PV Leistung?https://www.facebook.com/groups/227105673557652/posts/887513790850167/
Firmware habe ich die EZ1 1.12.2 drauf, die kürzlich installiert wurde. Vorher war es die 1.9.2
#6
Solaranlagen / Aw: 76_SolarForecast - Informa...
Letzter Beitrag von 300P - 16 März 2026, 22:35:33Hab mal gesucht....war mir bislang nicht in die Augen gesprungen 
Der erste dieser Perl Error erfolgte nach Update aus Contrib am 10.03.2026
Danach bei jedem restart... leider nicht gesehen weil da immer vom DoIf (Card-Nutzung) eine gleiche Reihe von Perl-Error kommt - dann den nicht gesehen...
.
Der erste dieser Perl Error erfolgte nach Update aus Contrib am 10.03.2026
Code Auswählen
2026.03.10 09:19:08 2: Forecast - start download Update Solarforecast from Contrib ====>>> wird gestartet
2026.03.10 09:19:08 2: Forecast - end download Update Solarforecast from Contrib
2026.03.10 09:19:08 2: Forecast - attr Forecast userFn_LoadContribcUpdate 0 ====>>> wurde ausgef�hrt
Danach bei jedem restart... leider nicht gesehen weil da immer vom DoIf (Card-Nutzung) eine gleiche Reihe von Perl-Error kommt - dann den nicht gesehen...
.Code Auswählen
2026.03.10 09:20:10 1: MB_CFG_SBS25: loading config from cfg file
2026.03.10 09:20:13 1: PERL WARNING: (in cleanup) object of class struct fann * expected at ./FHEM/76_SolarForecast.pm line 9822.
2026.03.10 09:20:15 1: Zisterne: loading config from cfg file
2026.03.10 09:20:32 1: Including ./log/fhem.save
2026.03.10 09:20:35 1: PERL WARNING: Use of uninitialized value $arcEnd in addition (+) at ./FHEM/98_DOIF.pm line 6402.
2026.03.10 09:20:35 1: PERL WARNING: Use of uninitialized value $arcBegin in addition (+) at ./FHEM/98_DOIF.pm line 6402.
2026.03.10 09:20:35 1: PERL WARNING: Use of uninitialized value $arcEnd in numeric gt (>) at ./FHEM/98_DOIF.pm line 6403.
2026.03.10 09:20:35 1: PERL WARNING: Use of uninitialized value $arcBegin in numeric gt (>) at ./FHEM/98_DOIF.pm line 6403.
2026.03.10 09:20:35 1: PERL WARNING: Use of uninitialized value $arcBegin in sprintf at ./FHEM/98_DOIF.pm line 6849.
2026.03.10 09:20:35 1: PERL WARNING: Use of uninitialized value $arcEnd in sprintf at ./FHEM/98_DOIF.pm line 6849.
2026.03.10 09:20:35 1: PERL WARNING: Use of uninitialized value $arcBegin in sprintf at ./FHEM/98_DOIF.pm line 6867.
2026.03.10 09:20:35 1: PERL WARNING: Use of uninitialized value $arcEnd in sprintf at ./FHEM/98_DOIF.pm line 6867.
2026.03.10 09:20:35 1: PERL WARNING: Use of uninitialized value $endAngle in numeric gt (>) at ./FHEM/98_DOIF.pm line 6438.
2026.03.10 09:20:35 1: PERL WARNING: Use of uninitialized value $startAngle in numeric gt (>) at ./FHEM/98_DOIF.pm line 6438.
2026.03.10 09:20:35 1: PERL WARNING: Use of uninitialized value $angleInDegrees in subtraction (-) at ./FHEM/98_DOIF.pm line 6394.
2026.03.10 09:20:35 1: PERL WARNING: Use of uninitialized value $startAngle in subtraction (-) at ./FHEM/98_DOIF.pm line 6445.
2026.03.10 09:20:35 1: PERL WARNING: Use of uninitialized value $endAngle in subtraction (-) at ./FHEM/98_DOIF.pm line 6445.
2026.03.10 09:20:36 1: PERL WARNING: Argument "initialized" isn't numeric in numeric gt (>) at (eval 2257) line 1.
2026.03.10 09:20:36 0: Featurelevel: 6.4
2026.03.10 09:20:36 0: Server started with 444 defined entities (fhem.pl:30719/2026-01-11 perl:5.036000 os:linux user:fhem pid:1049601)
2026.03.10 09:21:05 2: AttrTemplates: got 270 entries
2026.03.10 09:21:07 1: PERL WARNING: Use of uninitialized value in subroutine entry at ./FHEM/99_Utils.pm line 21.
2026.03.10 09:22:01 1: PERL WARNING: Argument "" isn't numeric in sprintf at (eval 8751) line 1.
2026.03.10 09:27:01 1: PERL WARNING: Argument "" isn't numeric in sprintf at (eval 22789) line 1.
2026.03.10 09:32:01 1: PERL WARNING: Argument "" isn't numeric in sprintf at (eval 38772) line 1.
2026.03.10 09:37:01 1: PERL WARNING: Argument "" isn't numeric in sprintf at (eval 53420) line 1.
2026.03.10 09:42:01 1: PERL WARNING: Argument "" isn't numeric in sprintf at (eval 68552) line 1.
2026.03.10 09:47:04 1: PERL WARNING: Argument "" isn't numeric in sprintf at (eval 82588) line 1.
2026.03.10 09:52:01 1: PERL WARNING: Argument "" isn't numeric in sprintf at (eval 97845) line 1.
2026.03.10 09:57:02 1: PERL WARNING: Argument "" isn't numeric in sprintf at (eval 117069) line 1. #7
Sonstige Systeme / Aw: Rademacher Duofern Wandsch...
Letzter Beitrag von paulbaumann - 16 März 2026, 22:26:00Oder vielleicht ist ja das gemeint?
https://wiki.fhem.de/wiki/DUOFERN
https://wiki.fhem.de/wiki/DUOFERN
#8
Sonstige Systeme / Aw: Rademacher Duofern Wandsch...
Letzter Beitrag von paulbaumann - 16 März 2026, 22:17:37@Tinus
Danke, ich weiß ich stelle mich dumm an aber nach einigen Wochen habe ich nun rausgefunden wie die Rademacher Kennung ist bei mir, über die Rückseite des 9494-1 war da Nichts Brauchbares anscheinend.
Irgendwelche Ziffern und Buchstaben die nicht ins Schema passen. Dann kam ich auf die Idee mal den QR Code der Rückseite zu scannen und da kam "Data Matrix" und er spukte auch die Rademacher-Kennung aus.
Die 2 Knöpfe am 9494-1 zum Pairing kann ich auch drücken. Aber wie nun weiter ich stehe im Dunkeln.
FHEM auf "pair" stellen, ja wie nur? Was muss ich in FHEM konkret machen wenn ich die 2 Knöpfe gedrückt habe und dann runter an meinen Rechner renne und FHEM im Browser offen habe?
Ich habe schon gesucht im Forum aber irgendwie nichts passendes gefunden...
Danke, ich weiß ich stelle mich dumm an aber nach einigen Wochen habe ich nun rausgefunden wie die Rademacher Kennung ist bei mir, über die Rückseite des 9494-1 war da Nichts Brauchbares anscheinend.
Irgendwelche Ziffern und Buchstaben die nicht ins Schema passen. Dann kam ich auf die Idee mal den QR Code der Rückseite zu scannen und da kam "Data Matrix" und er spukte auch die Rademacher-Kennung aus.
Die 2 Knöpfe am 9494-1 zum Pairing kann ich auch drücken. Aber wie nun weiter ich stehe im Dunkeln.
FHEM auf "pair" stellen, ja wie nur? Was muss ich in FHEM konkret machen wenn ich die 2 Knöpfe gedrückt habe und dann runter an meinen Rechner renne und FHEM im Browser offen habe?
Ich habe schon gesucht im Forum aber irgendwie nichts passendes gefunden...
#9
Homematic / Aw: HM-PB-6-WM55 soll Shelly 2...
Letzter Beitrag von Otto123 - 16 März 2026, 22:16:13Hi,
Vermutung: das notify wird mehrfach getriggert: den HM Aktoren ist es egal, der shelly ist verwirrt.
Anschauen könntest Du Dir das mal im Eventmonitor.
Gruß Otto
Vermutung: das notify wird mehrfach getriggert: den HM Aktoren ist es egal, der shelly ist verwirrt.
Anschauen könntest Du Dir das mal im Eventmonitor.
Gruß Otto
#10
Solaranlagen / Aw: 76_SolarForecast - Informa...
Letzter Beitrag von 300P - 16 März 2026, 22:06:11Ja läuft:
Code Auswählen
Informationen zum neuronalen Netz der Verbrauchsvorhersage
letztes KI-Training: 15.03.2026 21:04:47 / Laufzeit in Sekunden: 3781
KI Abfragestatus: ok
letzte KI-Ergebnis Generierungsdauer: 61.82 ms
Verbrauchernummer Wärmepumpe: 08
=== Modellparameter ===
Normierungsgrenzen: PV=10450 Wh, Hausverbrauch: Min=0 Wh / Max=7598 Wh
Trainingsdaten: 8052 Datensätze (Training=6441, Validation=1611)
Architektur: Inputs=98, Hidden Layers=80-40, Outputs=1
Hyperparameter: Learning Rate=0.001, Momentum=0.6, BitFail-Limit=0.15
Aktivierungen: Hidden=GAUSSIAN_SYMMETRIC, Steepness=1.0, Output=LINEAR
Trainingsalgorithmus: INCREMENTAL, Registry Version=v1_heatpump_active_pv
Zufallsgenerator: Mode=1, Period=20
Modellalter: 25 h
=== Trainingsmetriken ===
bestes Modell bei Epoche: 863 (max. 15000)
Training MSE: 0.002559
Validation MSE: 0.003974
Validation MSE Average: 0.007886
Validation MSE Standard Deviation: 0.000305
Validation Bit_Fail: 34
Model Bias: 90 Wh
Model Slope: 0.9
Trainingsbewertung: Retrain
=== Fehlermaße der Prognosen ===
MAE: 375.54 Wh
MedAE: 307.94 Wh
RMSE: 439.05 Wh
RMSE relative: 20 %
RMSE Rating: good
MAPE: 18.54 %
MdAPE: 15.26 %
R²: 0.68
=== Rauschen ===
Rauschen Bewertung: low
Empfehlung für Bit_Fail: 0.28 (Einstellung von aiControl->aiConBitFailLimit)
=== Drift-Kennzahlen ===
Drift Score: 2.24
Drift RMSE ratio: 2.83
Drift Slope: 0.140
Drift Bias: 970.16
Drift Bewertung: mild
Slope recalibrated: -
Bias recalibrated: -
Code Auswählen
2026.03.16 22:00:16 1: Forecast DEBUG> start add AI raw data for hour: 22
2026.03.16 22:00:16 4: Forecast DEBUG> AI raw add - idx: 2026031622, day: 16, hod: 22, sunalt: -26, sunaz: 305, rad1h: 0, pvrl: 0, con: 1966, wcc: 85, rr1c: 0.00, temp: 2.8
2026.03.16 22:00:16 1: Forecast DEBUG> AI raw add - 1 entities added to raw data pool (set verbose 4 for output more detail)
2026.03.16 22:00:16 1: Forecast DEBUG> AI raw data saved into file: ./FHEM/FhemUtils/AIraw_SolarForecast_Forecast
2026.03.16 22:00:16 1: Forecast DEBUG> DRIFT [con]: Flag=mild | Block=0 | SlopeLive=0.122 | DriftSlope=0.140 | BiasLive=1060.41 | DriftBias=970.16 | RMSErelLive=56.5 | RMSErelRatio=2.83 | BiasVarNorm=0.17 |DriftScore=2.24 | Zone3Hours=1 | Hist=[mild,mild]
2026.03.16 22:00:16 1: Forecast DEBUG> AI FANN drift data type 'con' successfully written to file: ./FHEM/FhemUtils/NeuralNet_SolarForecast_Forecast