da hier bereits mehrfach von eingefleischten RaspberryMatic Nutzern der Wunsch geäußert wurde doch vielleicht vor einem Release einer neuen Version etwaige Release-Candidate / Test- Versionen mit testen zu wollen, habe ich soeben in meinen privaten Cloud Speicher die entsprechenden *.zip archive eines solchen Release-Candidate hochgeladen. Die entsprechenden Archive für rpi3, rpi0 und Tinkerboard können also von folgender Stelle heruntergeladen werden:
https://cloud.light-speed.de/s/EcpidnFSKtzWYat
Bitte hierbei beachten das diese Version natürlich nur Personen testen sollten die wissen was sie tun bzw. auf was sie sich hier einlassen. Das beinhaltet mögliche geringfügige Probleme bis hin zu event. möglichem Verlust der gesamten Konfiguration. Deshalb heisst es hier nicht nur vorher ein entsprechendes Backup zu machen, sondern eben auf etwaige unvorhersehbare Dinge vorbereitet zu sein. Natürlich sollte meiner momentanen Einschätzung nach keine größeren Probleme mit dieser Version zu erwarten sein, aber ich möchte hier trotzdem entsprechend vor etwaigen Problemen warnen da ich diese Versionen wie gesagt selber noch nicht ausreichend getestet habe.
DIe Version träg die Versionsnummer 3.47.10.20190712 und wird dann zum geplanten Releasetermin (13. Juli) entsprechend noch einmal umbenannt/angepasst werden.
Wer aber trotz dieser Warnungen gerne aktiv mithelfen will die kommende Version (3.47.10.20190713) vorher zu testen um etwaige Last-Minute-Probleme besser ausschliessen zu können sei herzlich eingeladen dies zu tun und mir dann bitte entsprechend im GitHub bzw. hier im Forum etwaig aufkommende Probleme (oder aber auch nur ein "Alles ok") zu melden.
P.S: Die in dieser Version eingearbeiteten Änderungen sind wie folgt (nur in Englisch verfügbar momentan):
Code: Alles auswählen
#### General changes:
- updated [OCCU](https://github.com/eq-3/occu) firmware to [3.47.10-4](https://github.com/jens-maus/occu/tree/b_3_47) version with full compatibility to the [CCU3 3.47.10 firmware](https://www.eq-3.de/Downloads/Software/CCU3-Firmware/CCU3-3.47.10/CCU3-Changelog.3.47.10.pdf) coming with the following changes:
- Integrated the following new Homematic devices: `HmIP-ASIR-2`, `HmIPW-STHD`, `HmIPW-STH`, `HmIPW-WTH`, `HmIP-FALMOT-C12`, `HmIPW-FAL24-C6`, `HmIPW-FAL230-C6`, `HmIPW-FAL24-C10`, `HmIPW-FAL230-C10`, `HmIP-MIO16-PCB`.
- Channels of the virtual remote control (`HmIP-RCV-50`) could not be deleted from rooms and maintenance groups.
- When adding a direct connection to a `HmIP-MP3P` from a wind sensor a color selection was displayed rather than a sound selection.
- The button "Geräte-Firmware" on the page "Einstellungen" was renamed to "Geräte-Firmware-Übersicht".
- Integrated a WebUI patch to prevent remote HTML injections during Add-on version requests.
- Fixed a problem where under certain circumstances a session ID could be generated without a valid login.
- The displayed amount of rain for a `HmIP-SWO-*` were accidentally doubled on each CCU restart.
- JSON-API: The access level for `get-/setMetadata` calls were now set to GUEST and ADMIN accordingly.
- A dialog was added for a `HmIP-MP3P` to configure playlists within WebUI programs.
- Integrated a WebUI patch to prevent the web server from sending any `Server:` response header.
- In direct connections between a motion sensor and a switching/dimming actor the actor should not be switched off anymore if there is still identified motion in place if the actor reacts upon ambient light brightness.
- `HM-ES-TX-WM` - Integrated the changed behavior if firmware version > 2.x.y is used and which comes with SML protocol compatibility to read out electric smart meters. With firmware version 2.x.y only ES-IEC sensor is supported anymore and no IR, Gas or LED sensor can be used with a HM-ES-TX-WM device.
- Added new functionality (week programme) for `HmIP-MIOB`.
- Added new functionality (MIOB switching for heating/cooling support) for all `HmIP-FAL` devices.
- Added automatic transmission of location and timezone data to supported HmIP devices with astro functionality included.
- Added some security relevant HTTP response headers to generally improve the WebUI security.
- updated Linux kernel version to [4.19.57](https://github.com/armbian/build/tree/master/patch/kernel/rockchip-next) for ASUS Tinkerboard and to [4.19.57](https://github.com/raspberrypi/linux/tree/rpi-4.19.y) for RaspberryPi including the corresponding firmware files.
- updated U-boot boot loader version to 2019.01 version coming with Buildroot.
- integrated all third-party changes from https://github.com/alexreinert/piVCCU/tree/master/kernel where
`eq3_char_loop` and `rx8130` was modified and dts changes proposed. Furthermore we use the latest `generic_raw_uart` sources for upcoming builds now (@alexreinert).
#### WebUI changes/fixes:
- added a WebUI fix to bind the new DutyCycle ProgressBar display to the content of the "DutyCycle" system variable generated by our `updateDCVars.tcl` helper script or otherwise the progressbar and the variable could have slightly different numbers. In addition, the DutyCycle sysvar update interval was changed from every 3 minutes to every minute to be in sync with the new WebUI way of displaying the DutyCycle.
- integrated a smoother timezone/utcOffset/utcOffsetDST calculation routine which doesn't require to maintain an own utcOffset list in addition to the anyway mostly obsolete timezone list implemented in `cp_time.cgi`. Now the utcOffset and position sync functionality in latest WebUI doesn't require this utcOffset list anymore while allowing to set way more time zones.
#### Bugfixes:
- fixed `checkHmIPdevices.sh` helper script to use a better search pattern and only move away `ap`/`apkx` files if the regadom already contains HmIP-RCV devices which means that there are references to the RF module at all. This should fix issues where people were coming from earlier versions of RaspberryMatic not containing HmIP-RCV devices already and thus the `ap`/`apkx` of the GPIO rf modules were accidentally
moved away leaving no HmIP devices in the WebUI at all.
- fixed another bug in `checkHmIPdevices.sh` which accidentally moved away `*.ap` and `*.apkx` files from HmIPW-DRAP devices. Now it will check `metaData.conf` for a reference to a HmIPW-DRAP and if it identifies it it will skip the found SGTIN (#655).
- integrated a workaround for a problem with the Mediola NEO Server add-on web configuration pages which could not be accessed if the WebUI itself was accessed via https.
- added `nofail` mount options where appropriate so that upon startup the system doesn't complain if a certain filesystem is missing during boot.