zigbee home automation for arm 32 bits
88
This version is similar than edge-zigbee application but customized for armv7 32 bits architectures (armhf). This image can be used, for example, with devices as:
To get more information about zigbee application: zigbee documentation
Web APP:
To run zigbee container you can execute following command:
docker run -d -ti \
-p 4443:4443 \
-v /mnt/logs \
-v /mnt/conf \
-v /mnt/data \
-e "CONTAINER_TIMEZONE=Europe/Madrid" \
-e "NODE1_ZIGBEE_PORT=/dev/ttyS50" \
--privileged \
--device "/dev/ttyACM0:/dev/ttyACM0" \
--restart always \
--name edge.zigbee \
onesaitplatform/edge-zigbee-armhf:community
Another way to launch database application is to use docker-compose schema; docker-compose.yml file must be located at the same execution directory .
docker-compose pull
docker-compose up -d
version: '2'
services:
#Inner mqtt broker mandatory by Edge Engine architecture.
mqtt:
restart: always
image: onesaitplatform/edge-mqtt:community
container_name: edge.mqtt
#Remember define these volumes with edge device local paths.
volumes:
- /mosquitto/log
- /mosquitto/data
networks:
- edgenet
#Edge Engine Zigbee contanier for working with Zigbee-HA & Zigbee-Lighting devices.
zigbee:
restart: always
image: onesaitplatform/edge-zigbee:community
container_name: edge.zigbee
environment:
CONTAINER_TIMEZONE: Europe/Madrid
NODE1_ZIGBEE_PORT: /dev/ttyS50
#Remember define these volumes with edge device local paths.
volumes:
- /mnt/logs
- /mnt/data
- /mnt/conf
#Java detects Zigbee chips connected by USB. It is necessary symbolic link from ttyACM0 to NODE1_ZIGBEE_PORT (ttyS50).
#Privileged attribute is required to get devices from host.
privileged: true
devices:
- "/dev/ttyACM0:/dev/ttyACM0"
depends_on:
- mqtt
links:
- mqtt
ports:
- 4443:4443
networks:
- edgenet
networks:
edgenet:
driver: bridge
Content type
Image
Digest
Size
84.7 MB
Last updated
about 7 years ago
docker pull onesaitplatform/edge-zigbee-armhf:community