bitraf / bitraf-iot Goto Github PK

Bitraf's server-side configuration of mosquitto should be documented here on github.
That is all files in /etc/mosquitto/conf.d that doesn't contain secrets.

Current version of door opener buttons have a network name like "ESP_9c6052" where the part after 'ESP_' is related to the MAC address. It would be nice to give it a name instead, like "bitraf-guestbutton", "bitraf-3office-button" and so on. That way it would be easier to identify the devices in network management tools (like UniFi controller) for fault finding purposes.

Because they attempt to subscribe to topics on form myparticipant.PORT, which is currently not allowed to read/write from in our mosquitto config. In general only /public/* is open for R/W...

So either all participants must obey a prefix (msgflo/msgflo-nodejs#11 and same in msgflo-python, etc), or we change this configuration to make most things open. This should be fine as long as we ensure that our security sensitive topics. A test-suite that ensures this would be probably be the best anyways.

While debugging found that there are no error for subscription failures:
msgflo/msgflo-nodejs#10

Today, office users reported that the open-door buttons on the 3rd floor didn't work. Opening the door with door.bitraf.no worked. I checked and found that:

• both buttons (workshop and office3rdfloor) was online and sent mqtt messages, also when the button was pressed.
• the service that tells the doors to open was running
• opening the doors via door.bitraf.no was working
  info about the service

root@bomba:~# systemctl status bitraf-iot-opendoor3floor.service
* bitraf-iot-opendoor3floor.service
   Loaded: loaded (/etc/systemd/system/bitraf-iot-opendoor3floor.service; enable
   Active: active (running) since Thu 2017-11-09 15:35:52 CET; 1 weeks 0 days ag
 Main PID: 23348 (msgflo-python)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bitraf-iot-opendoor3floor.service
           `-23348 /usr/bin/python /usr/local/bin/msgflo-python components/OpenD

Warning: Journal has been rotated since unit was started. Log output is incomplete

and

root@bomba:~# journalctl _SYSTEMD_UNIT=bitraf-iot-opendoor3floor.service
-- No entries --

I restarted the service
root@bomba:~# systemctl restart bitraf-iot-opendoor3floor.service

and the buttons work again.

Unintended side-effect: this IoT device is also a WiFi accesspoint. See
#14
for details.

We have discovered that ESP32 devices (like ESP8266 etc.) defaults to client + AP (accesspoint) at least when configured as a client (WiFiClient) with Arduino IDE. Usually, you don't want an extra AP when you set up a IoT device that only works as a client. To fix the problem you need to add the line

WiFi.mode(WIFI_STA);

when setting up the wireless in your Arduino code.
The current PirMotionSensor code needs this fix.

the p2k16-label service currently lives on the server heim, in Elias' home directory. It has a systemd service (label-writer.service), but everything is manually installed. This breaks when we do upgrades. Today I fixed it by manually installing

sudo apt install python3-pil
sudo apt install python3-qrcode
sudo apt install python3-paho-mqtt
sudo pip3 install brother_ql

and restarting the label-writer.service.

Needs fixing:

• make a proper home for it (on heim, under a dedicated user? Or somewhere else?)
• create an ansible role for it
• make sure that all dependencies gets installed