Docker image for alexa-fhem

A FHEM complementary Docker image for Amazon alexa voice assistant, based on

• Node 14 - Debian Buster
• alexa_fhem

Installation

Pre-build images are available on Docker Hub and on Github Container Registry.

From Github container registry

Updated version, only with Version tags

• NodeJS 14

• Alexa-Fhem 0.5.61

    docker pull ghcr.io/fhem/fhem/alexa-fhem:2.0.0
  

To start your container right away:

docker run -d --name alexa-fhem -p 3000:3000 ghcr.io/fhem/fhem/alexa-fhem:dev

Permanent storage

Usually you want to keep your FHEM setup after a container was destroyed (or re-build) so it is a good idea to provide an external directory on your Docker host to keep that data:

docker run -d --name alexa-fhem -p 3000:3000 -v /some/host/directory:/alexa-fhem fhem/alexa-fhem 

Verify if container is runnung

After starting your container, you may check the web server availability:

http://xxx.xxx.xxx.xxx:3000/

You may want to have a look to the alexa-fhem documentation or FHEM Connector documentation for further information.

Image flavors

This image provides different variants:

• latest (default, can introduce breaking changes)
• 2.0.0 ( latest released Version. Can be a prerelease version)
• 2 ( latest stable release in Major v2)
• dev (development tag, not updated anymore)

You can use one of those variants by adding them to the docker image name like this:

docker pull ghcr.io/fhem/fhem/alexa-fhem:latest
    docker pull ghcr.io/fhem/fhem/alexa-fhem:2	
docker pull ghcr.io/fhem/fhem/alexa-fhem:2.0.0

If you do not specify any variant, latest will always be the default.

Supported platforms

This is a multi-platform image, providing support for the following platforms:

Linux:

• x86-64/AMD64
• ARM32v7, armhf
• ARM64v8, arm64

Windows:

• currently not supported

The main repository will allow you to install on any of these platforms. In case you would like to specifically choose your platform, go to the platform-related section in the container repository.

The platform repositories will also allow you to choose more specific build tags beside the rolling tags latest or dev.

Customize your container configuration

Tweak container settings using environment variables

• Change alexa-fhem system user ID: To set a different UID for the user 'fhem' (default is 6062):

    -e ALEXAFHEM_UID=6062
  

• Change FHEM group ID: To set a different GID for the group 'fhem' (default is 6062):

    -e ALEXAFHEM_GID=6062
  

• Set timezone: Set a specific timezone in POSIX format:

    -e TZ=Europe/Berlin
  

Use docker-compose.yaml

No problem at all. To connect alexa-fhem to your alexa container, you need a common network. Named it fhem_net. You should connect your fhem container to the same network to support communication via alexa-fhem and fhem itself.

version: '2.3'

networks:
  fhem_net:
    driver: bridge
    ipam:
      driver: default
      config:
        - subnet: 172.27.0.0/24
          gateway: 172.27.0.1
        - subnet: fd00:0:0:0:27::/80
          gateway: fd00:0:0:0:27::1

services:
  alexa-fhem:
    # image: fhem/alexa-fhem:latest
    image: ghcr.io/fhem/fhem/alexa-fhem:dev
    restart: always
    networks:
     - fhem_net
    ports:
      - "3000:3000"
    volumes:
      - "./alexa-fhem/:/alexa-fhem/"
    environment:
      ALEXAFHEM_UID: 6062
      ALEXAFHEM_GID: 6062
      TZ: Europe/Berlin

---

Production Build and Test

Development Build and Test