Skip to content

Releases: ct-Open-Source/ct-Smart-Home

c't-Smart-Home 1.3.2

04 Feb 12:45
1cfed90
Compare
Choose a tag to compare

This update adds a missing dependency needed for the Bluetooth integration to work.

c't-Smart-Home 1.3.1

21 Dec 18:29
93b3333
Compare
Choose a tag to compare

c't-Smart-Home 1.3.1

This is just a small hotfix for permission errors regarding Node-RED. If Node-RED doesn't start anymore run start.sh fix to correct the permissions.

In older setups the Node-RED configuration folder was owned by root. Now Node-RED runs with the UID and GID 1000 inside the container for security reasons. This causes permission errors.

c't-Smart-Home 1.3.0

16 Dec 11:52
8d728c1
Compare
Choose a tag to compare

c't-Smart-Home 1.3.0

This release adds multiple changes and updates to the Node-RED image. Additionally, the Zigbee2Mqtt service changed a few things, as well as Mosquitto. If you have an existing setup, look at the Moquitto section. There is a future breaking change.

Please have a look at the new Security section in the README to secure your setup properly. Having no authentication is only recommended for testing stuff and not for production. If you use your MQTT server in a productive environment, enable authentication for all services. See the README to learn how.

Always clone this repository and use the update function of the start.sh to use c't-Smart-Home. Simply downloading the repo will break the update mechanism and forces you to update manually.

Node-RED

In addition to the images for Node 10 and 12, there is now a build for Node 14. Node 12 is now the default base for the :latest image. The release images will now be rebuilt every Monday. This ensures, that all the operating system and Node-RED updates are delivered in a timely fashion.

The Bluetooth support in the image has been rebuilt. The hacky modification of node dependencies is gone and the image now integrates node-red-contrib-noble-bluetooth.

We also integrated node-red-contrib-zigbee2mqtt. It interfaces with Zigbee2Mqtt and makes it much easier to interact with Zigbee devices inside Node-RED. No more meddling with messy JSON.
If you upgrade from an existing installation, you must add homeassistant: true to ./data/zigbee/configuration.yaml.

We've also removed the following nodes:

  • node-red-node-base64
  • node-red-node-msgpack
  • node-red-node-random
  • node-red-node-suncalc

You can reinstall them via the palette if you miss them.

Zigbee2Mqtt

You'll now be able to use the (still experimental) Zigbee2Mqtt webinterface. It provides an easy way to control the Zigbee service, check devices and troubleshoot connection issues.
If you upgrade from an existing installation, you must add

frontend:
  port: 1881
  host: 0.0.0.0
experimental:
  new_api: true

and

homeassistant: true

to ./data/zigbee/configuration.yaml. This is not needed for new setups.

Mosquitto

From version 2.x onward Mosquitto won't accept anonymous connections anymore. So you'll have to make a small change to your configuration file to enable them, if you are using it without any authentication. As of this release Mosquitto still serves version 1.x as their :latest image.

Having no authentication is only recommended for testing stuff and not for production. If you use your MQTT server in a productive environment, enable authentication for all services. See the README to learn how.

To reactivate anonymous logins open the file ./data/mqtt/conf/mosquitto.conf and add the line allow_anonymous true.

Docker images et al.

The docker images have been optimized further to be as slim as possible, while still providing a lot of features.

Now we host the ct-Smart-Home image on GitHub's Container Registry ghcr.io. This is due to the fact, that docker implemented some harsh policies regarding rate limiting and image retention. It will make no difference to the end user. We still provide images on the Docker Hub to not break people's setups.

The S390X image was never intended for productive use and has been dropped.

The compose file has been cleaned up and conflicting statements have been removed.

Start script

The start script now checks if the .git folder is present and recommends a manual update if it's missing.

It also now has a bunch of nice emojis.

Node-RED 1.0.6

25 Apr 23:00
1e37ed3
Compare
Choose a tag to compare

Update for Node-RED 1.0.6

Node-RED 1.0.5

09 Apr 13:41
1e37ed3
Compare
Choose a tag to compare

Update for Node-Red 1.0.5.

Node-RED 1.0.4

02 Apr 13:41
1e37ed3
Compare
Choose a tag to compare

Just an update for Node-RED to version 1.0.4

Node-RED 1.0.3

23 Jan 21:26
1e37ed3
Compare
Choose a tag to compare

Just an update for Node-RED to version 1.0.3

Node-RED 1.0

20 Oct 16:29
0307b4d
Compare
Choose a tag to compare

This release changes the Node-RED base image to the official one provided by the project. This means a switch from Debian to Alpine and a smaller image.

The image is now based on Node.js version 10. There is also a one based on Version 12 available. Just append -12 to the Docker image tag.

Thanks to the new base image and crossbuliding with docker buildx there are more CPU architectures available. As of now only ARM32v7 and AMD64 are tested.

The README has been updated to show the new container tags. latest is always the current release. devel is created if there is a push to the master branch.

The Docker images are now built by GitHub Actions and not the Docker Hub anymore.

Update to latest Node-Red

17 May 12:40
2ff0c3a
Compare
Choose a tag to compare

Make sure we get the latest Node-Red.

Removed useless output of start sh.

Simpler setup

17 May 11:54
2ff0c3a
Compare
Choose a tag to compare

Reduced complexity thanks to upstream changes in containers.

Extended README to correct misunderstandings.

Fixed some small issues and typos.