https://github.com/andreasscherbaum/ansible-raspbee
Install a RaspBee II on a Raspberry Pi
https://github.com/andreasscherbaum/ansible-raspbee
ansible ansible-playbook ansible-role deconz kernel playbook raspbee raspberry raspberry-pi raspberrypi zigbee
Last synced: about 2 months ago
JSON representation
Install a RaspBee II on a Raspberry Pi
- Host: GitHub
- URL: https://github.com/andreasscherbaum/ansible-raspbee
- Owner: andreasscherbaum
- Created: 2020-05-26T21:12:06.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2020-06-06T22:40:28.000Z (about 6 years ago)
- Last Synced: 2025-12-29T23:06:07.481Z (6 months ago)
- Topics: ansible, ansible-playbook, ansible-role, deconz, kernel, playbook, raspbee, raspberry, raspberry-pi, raspberrypi, zigbee
- Homepage:
- Size: 3.91 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# ansible-raspbee
Install a RaspBee II on a Raspberry Pi
## Description
This Ansible Role will install the Raspbee RTC kernel module and the software for a [Dresden Elektronik](https://www.dresden-elektronik.de/) [RaspBee II Zigbee Gateway](https://www.dresden-elektronik.de/produkt/raspbee-II.html) on a Raspberry Pi running Raspbian.
## Installation
### Directly into the Roles directory
Clone the repository into the "roles/" directory in your Playbook roles directory:
```
cd roles && git clone https://github.com/andreasscherbaum/ansible-raspbee.git raspbee && cd -
```
### Symlink into the Roles directory
```
cd ..
git clone https://github.com/andreasscherbaum/ansible-raspbee.git
cd -
cd roles
ln -s ../../ansible-raspbee raspbee
cd -
```
## Configuration
The Role uses variables to configure if the source code should be deleted after building the module, and if the compiled code should be removed. Removing the source will refresh the source after the next kernel update. Removing the build code removes any debugging information in case something fails.
Change the defaults in _vars/main.yml_:
* raspbee_remove_source: True/False, remove source after building the kernel module
* raspbee_remove_build: True/False, remove build after building the kernel module
## Usage
Use the role name ("raspbee") in your Playbook:
```
roles:
- raspbee
```
## Important notes:
This Playbook will reboot the Raspberry Pi when the kernel module is installed. Seems to be necessary, otherwise the module can't be loaded.
The error message in _/var/log/syslog_ is:
```
May 26 23:20:15 rasbpee systemd[1]: rtc-pcf85063.service: Service RestartSec=15s expired, scheduling restart.
May 26 23:20:15 rasbpee systemd[1]: rtc-pcf85063.service: Scheduled restart job, restart counter is at 39.
May 26 23:20:15 rasbpee systemd[1]: Stopped Enable RTC-PCF85063.
May 26 23:20:15 rasbpee systemd[1]: Started Enable RTC-PCF85063.
May 26 23:20:15 rasbpee bash[2449]: /bin/bash: line 0: echo: write error: Invalid argument
May 26 23:20:15 rasbpee kernel: [ 996.219934] i2c i2c-1: Failed to register i2c client pcf85063 at 0x51 (-16)
May 26 23:20:15 rasbpee systemd[1]: rtc-pcf85063.service: Main process exited, code=exited, status=1/FAILURE
May 26 23:20:15 rasbpee systemd[1]: rtc-pcf85063.service: Failed with result 'exit-code'.
May 26 23:20:15 rasbpee systemd[1]: Configuration file /lib/systemd/system/rtc-pcf85063.service is marked executable. Please remove executable permission bits. Proceeding anyway.
May 26 23:20:15 rasbpee systemd[1]: Configuration file /lib/systemd/system/rtc-pcf85063.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
May 26 23:20:15 rasbpee systemd[1]: Reloading.
```
If you have an idea how to load the module without above error, please provide a PR, or open an Issue.
## Documentation
* https://phoscon.de/de/raspbee2/install#raspbian
* http://phoscon.de/app