Because why not?
- Events bus scalfolding
- Events bus autodiscovery (zeroconf)
- Sensor: ak9753 hardware support
- Sensor: persistent state (during restart)
- Sensor: support other sensors model
- Sensor UI: display of sensor data
- Sensor UI: auto add/remove sensors
- Sensor UI: Remote configuration
- Sensor UI: Generic configs ui
- Display: simulator
- Display: pico matrix 5x5
- Display: flame panel (rs285)
- JSON/GRPC webservice for imperative API
- Seq: simple display sequencer
- Game Logic
- docker compose
- deamonise processes
Read outs the data from a ak9753 sensor.
--mean int number of sample to use for mean (default 6)
-n, --name string sensor name used for discovery
--no-presence disable presence detector
--orphan don't try to connect to muthur
-t, --threshold float32 presence threshold (default 100)
--type SensorType sensor model [ak9753, amg8833] (default None)
--ui ak9753_display real time information on the terminal
Connects to muthur (nats server, display sensor data and set remote configuration.
Simulate one or more sensors.
A webservice used to query the current state of all sensors and display.
Central service to be used for service (dis/re)covery. Also will tell you human are expendable if a xenomorph is present on your spaceship.
Pretty much a embedded nats messaging server with a zeroconf service for discovery.
Small program which use a novation launchpad to display pixel's sequence
Visualised data from an amg8833 ir matrix camera unto a 8x8 launchpad midi controller.
Run a display on a 2 small pimoroni 5x5 led matrix.
Simulate a display device (flame panel).
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent