Open/closed sign: Difference between revisions

From NURDspace
No edit summary
Line 37: Line 37:
== Known issues ==
== Known issues ==


* the ESP32 seems to lose connection with the network after a couple of hours if the space is closed [esp32-07B018.dhcp.nurd.space]
* the ESP32 seems to lose connection with the network after a couple of hours if the space is closed [https://github.com/NURDspace/Nurdopen/issues/7]

Revision as of 13:54, 29 October 2022

Open/Closed sign for the space
NoPicture.png
Participants
Skills 1337 Skillz, coding
Status Broken
Niche Infra
Purpose Electronics, fun, world domination
Tool No
Location Zaal 2
Cost IDK Ask Melan
Tool category Electronics

Open/Closed sign for the space Property "Tool Image" (as page type) with input value "File:{{{Picture}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. {{{Picture}}} {{#if:No | [[Tool Owner::{{{ProjectParticipants}}} | }} {{#if:No | [[Tool Cost::IDK Ask Melan | }}

A open and Closed sign for our space!

Use case

To make it easier for visitors to see that someone is in.

How it was made

Melan helped me out a lot and provided 99% of the code as i'm a n00b at Python.

Flok messed around with things as well (added a few bugs).

Code

What/where

  • docker instance on erratic (vm 100)
  • /home/nurds/openClosedSign
  • start via Portainer (see Erratic, look for "goofy_chatelet" in the list of containers)
  • recreate: docker stop openclosesign && docker rm openclosesign && docker build --no-cache . -t openclosesign && docker run -d --name openclosesign openclosesign:latest

Known issues

  • the ESP32 seems to lose connection with the network after a couple of hours if the space is closed [1]