1
0
Fork 0
forked from calum/Smart512
Matter Smart Device to Art-Net Lighting Node
  • Kotlin 63.6%
  • Python 26.7%
  • JavaScript 3%
  • Roff 2.4%
  • Swift 2.1%
  • Other 2.1%
Find a file
2026-05-15 23:20:40 +01:00
.gradle-home Checkpoint: commissioning stabilization, live control UI updates, and DMX runtime ingress wiring 2026-04-15 01:06:36 +01:00
.tools Checkpoint: commissioning stabilization, live control UI updates, and DMX runtime ingress wiring 2026-04-15 01:06:36 +01:00
apps docs: record ios testflight path 2026-05-15 23:20:40 +01:00
assets/brand Package Smart512 alpha and brand companion app 2026-04-26 20:19:19 +01:00
certs v0.1.15 robust mobile QR scanning fallback 2026-04-13 01:31:45 +01:00
debian fix: refine companion server button spacing 2026-05-15 20:24:30 +01:00
deploy/systemd Checkpoint: commissioning stabilization, live control UI updates, and DMX runtime ingress wiring 2026-04-15 01:06:36 +01:00
docs docs: record companion button spacing release 2026-05-15 20:32:55 +01:00
packages/backend fix: refine companion server button spacing 2026-05-15 20:24:30 +01:00
tests fix: treat hostname node names as defaults 2026-05-15 20:08:50 +01:00
.codex v0.2 semantic fixture evaluation layer 2026-04-12 15:07:28 +01:00
.gitignore Package Smart512 alpha and brand companion app 2026-04-26 20:19:19 +01:00
changelog.md fix: simplify ios commissioning action 2026-05-15 20:51:24 +01:00
continuation_prompt.md docs: record ios testflight path 2026-05-15 23:20:40 +01:00
featurelog.md fix: simplify ios commissioning action 2026-05-15 20:51:24 +01:00
pyproject.toml feat: use deterministic appliance discovery names 2026-05-15 20:03:49 +01:00
README.md Document primary Git remote 2026-04-27 02:54:02 +01:00

Smart512

Matter Smart Device to Art-Net Lighting Node

Development Source

Primary Git remote:

https://repo.calhta.com/calum/Smart512.git

The active development checkout on the appliance is:

/opt/smart512-dev

Use main as the ongoing branch. Normal development commits should be made in /opt/smart512-dev and pushed to origin/main.

Debian/APT package publishing remains a separate release step documented in docs/debian_package_release_runbook.md. Pushing Git commits does not publish a new APT package.