ITEE Summer Programme · Course home
Build your Garden Spine project.
Use this site at the workbench. Follow the tutorials in order, keep your project charter open, and check every message in the developer view.
Core course path
Five tutorials, in order.
Stop at each success check before moving on. The sequence grows one working device: first connect, then sense, listen, move, and repair.
- 01TUTORIAL 01 / 05
Hello, spine.
Flash the reference publisher and make one device appear.
DONE WHENYour device appears on the developer view with a green alive badge. - 02TUTORIAL 02 / 05
Publish a real reading.
Wire one sensor and publish a number that changes when you breathe on it.
DONE WHENA live sensor value changes in the developer view. - 03TUTORIAL 03 / 05
Read someone else.
Subscribe to another team's topic and print their data to Serial Monitor.
DONE WHENThe visitor counter value appears on your screen. - 04TUTORIAL 04 / 05
Make it move.
Drive the servo from a subscribed garden value.
DONE WHENYour device reacts when another team's value changes. - 05TUTORIAL 05 / 05
When it breaks.
Follow one broken message from the device to the reject hint and fix it yourself.
DONE WHENThe deliberate reject appears, then the corrected message is accepted.
When you are working
Find the right page quickly.
You do not need to read the whole site. Choose the page that matches what you are doing now.
Developer view
Find your device ID, confirm it is alive, inspect values, and read reject hints.
30 ready device pages →Troubleshooting
Start with the first piece of evidence, then separate connection problems from message problems.
Follow the checklist →Git guide
Fork, clone, commit, and share the team repository without publishing credentials.
Open the guide →Garden view
Step back from one device and see what the whole class is publishing.
Open the dashboard →The one course rule
Prove the path before adding complexity.
Start with the fixed message in Tutorial 01. Only add a sensor after the device appears with a green alive badge. If something fails later, return to the last step that worked and use the developer view to find the first evidence.