READ-ONLY mirror of the main Subversion repository trunk, updated daily. Hint: Any Git pull request to the master branch will be rejected!
Go to file
dependabot[bot] 81d838e7bc
Bump actions/cache from 4.0.0 to 4.0.1 (#59)
Bumps [actions/cache]( from 4.0.0 to 4.0.1.
- [Release notes](
- [Changelog](
- [Commits](

- dependency-name: actions/cache
  dependency-type: direct:production
  update-type: version-update:semver-patch

Signed-off-by: dependabot[bot] <>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]>
2024-03-02 15:35:33 +01:00
.github Bump actions/cache from 4.0.0 to 4.0.1 (#59) 2024-03-02 15:35:33 +01:00
LICENSE Initial commit 2019-01-05 11:24:15 +01:00 recreate svn tags as fhem tags (#24) 2021-12-28 18:19:49 +01:00
authors.txt Update authors.txt 2019-03-22 15:08:40 +01:00


READ-ONLY mirror of the main Subversion repository, updated multiple times every day.


  1. The master branch hosts the current source code from FHEM SVN Trunk.
  2. The travis branch is controlling the mirroring process, running on Github Actions.
  3. Under tags FHEM Releases are mirrored also.

Pull requests

Pull requests to any other branch besides travis will be rejected. Instead, a module may have its own repository here on and will accept your patch using a pull request.

If you can't find a repository for the module you would like to contribute, visit the official FHEM support forum to post your patch. However, it might not be very welcome as it easily mixes up with user support requests and makes version control extremely difficult to handle. For that particular reason, please consider contacting the maintainer using the forum direct message function and send a link to where s/he can find your changed version or patch file.

Author matching

Authors from the Subversion repository will be referred here without any email relation.

Those that also have an account might have a different username here.

The authors.txt file will ensure to re-write authors from the Subversion repository to their username and email address. Should an author want to be re-matched for any future commits, s/he may modify authors.txt file and send a Git pull request.

For that purpose, remember to fork the correct branch travis, not the master branch.