smartuni / teamagochi Goto Github PK

Lwm2m wrapper and create events from them
make and get changes on the server

!! Every event should have its log_write(LOG_DEBUG) !!

The frontend should have a pet creation system that allows you to decide:

• Colour
• Pet Type (Frog, etc.)

1. Device connects to Server/Router
2. It broadcasts/showcases a unique ID
3. The backend checks whether the ID exists
4. If it does, it'll send the pet info to the device
5. If it doesn't, it'll send a registration code that will be shown on the device
6. User enters code into the frontend
7. User creates pet
8. Pet gets uploaded to the device

Some points to include:

# Login Process
# Frontend Mockup
# Web Backend Authetnication showcase
# Hardware Details
# Flow Diagram of App (Node)
# Lower M2M Objects (Node)
# Timeline

Since the repo name was changed, the references to documentation in the README.md are not valid.

Create initial fully soldered product to test it

The frontend should showcase highscores based on the happiness or other stats provided by the backend

picture of whiteboard is in teams in the nodes chat

• #23 Only run CI when docs change (Reduce action runs)
• #22 Update teams list to include the people that were missing

create functions for using the actuators
before the dispatcher works you can just LOG_DEBUG

!! Every event should have its log_write(LOG_DEBUG) !!

Which sensors do we need?
How can we access them?

for the MVP

!! Every event/state change should have its log_write(LOG_DEBUG) !!

How do we connect a sd card and access it.
Which GPS sensor can we use.

and add it to the docu

• Feed
• Clean
• Play
• Pet
• Medicine

Use mental and physical stats

see teams node chat

which type of display (monochromatic or color/ touch or not)

How we want to draw the Pet

• Frontend UI to change pets
• Backend request to Node
• Node has to respond to request and change the pet

After #62 has been done, we can try to set up a proper CI workflow for the Frontend to properly deploy it. This might cause some issues with the documentation CI workflow.

• resistors on the back
• front 3.3V / back GND
• mosfet on the back, diode to the top
• add debounce to the switches (Capacitors)
• better schemetic with label connections

We need some type of persistent storage (mostly for the shared ID)

Currently (in theory) two threads could ask the dispatcher to be subscribed to a new event at the same time and cause chaos. In reality this will probably not happen, esp. since normally subscriptions only happen in the main thread but it'd still make sense to properly guard the list.

Increasing the happiness over a longer duration should increase the overall possible happiness. This should be done on the backend.

Which protocol
How to communicate with border router
How does the border router works, with what api we communicate with the backend team?

Requires #78

create a dispatcher for asynchron events

RIOT Docu link:
https://api.riot-os.org/group__core__msg.html#gac5347725c3d203ac72604c0ab8b7d6d8

When all sensors and actuators are evaluated

create the design and menu flow for the display
and get it to work on the display

get the backlight control working, PIN is soldered. PIN #3 can controled with PWM Signal

maybe implement LVGL

!! Every event should have its log_write(LOG_DEBUG) !!

Just upload a template React project to Github so we can test CI stuff

create functions for IRQ and send events
before the dispatcher works you can just LOG_DEBUG

!! Every event should have its log_write(LOG_DEBUG) !!

Requirements:

1. A user needs to be able to create an user account
2. A new device needs to register with the server
3. A user is able to connect a user account and a device in a secure manner

For this to be done each team needs to come up with required steps and problems to solve.