Is Clockstar v2 even supported?

⌚ Clockstar
#1

Sorry to be so blunt, but:

  • The code.circuitmess.com site doesn’t provide a project page for clockstar v2, only for v1
  • Doing some poking around in the code for the clockstar v1 webpage, it appears to specifically filter out the v2 chip from the USB connection script
  • There are a number of posts here and in the support page asking for help connecting v2 to the web IDE, and none of them have a resolution from CircuitMess

Please do not ask me to send an email to contact@circuitmess.com – you can instead reply to the one I already sent! :wink:

#2

First of all, please don’t apologize for being blunt, we truly appreciate the clear and direct feedback. It helps us identify exactly where our documentation or software is falling short, and in this case, you’ve pointed out some very valid concerns.

To address your points specifically:

  • Missing Examples: You are correct that there isn’t currently a dedicated copy of the Clockstar v1 examples for the v2 revision on the project page. This was a mistake on our part, and we are working to include these examples for Clockstar v2 officially. In the meantime, if you manually copy the v1 code examples into a new v2 project in CircuitBlocks, the code will function perfectly.
  • USB Filtering & Hardware Differences: The reason you noticed a filter in the connection script is due to a significant hardware upgrade. The original Clockstar used a standard ESP32, whereas the v2 revision features a much more powerful ESP32-S3 SoC (System on a Chip). Because of this change in processors, the firmware structures are different. We implemented the USB interface check to ensure that the correct firmware is always flashed to the correct chip to prevent any compatibility issues.

We are currently updating the web IDE to make this transition seamless for v2 users so that you don’t have to “poke around” to get it working.

Thank you for your patience and for your investigative work, it’s exactly this kind of community feedback that helps us squash these bugs.

1 Like
#3

I completely understand the frustration, and I appreciate you being blunt, honesty helps us fix things faster!

I have some good news: our team has just finished the update, and Clockstar v2 is now officially published and live on the platform. You can find the project page and the updated USB connection scripts specifically for the v2 chip right here: https://code.circuitmess.com/

1 Like
#4

I see it, thank you!!

#5

You’re very welcome! I’m glad you got it.

If any other questions pop up or if you need further assistance with your build, please don’t hesitate to reach out. We’re always here to help!
Happy making!

#6

Ive spent a significant amount of time looking for developer documentation for the Clockstar2 for a STEM product clearly targeting an educational audience the lack of development guides is a massive failure.
I’m posting this here because, while the Clockstar 2 is marketed as a programmable STEM wearable, there is a massive documentation deficit regarding its actual development environment.

Whilst the “Build Guide” is gratuitous and, frankly, patronising—it dedicates an unnecessary level of pedantic detail to what is essentially a perfunctory assembly (placing a prefabricated PCB, battery, and LCD into a case).

However, when it comes to the actual “STEM” promise—programming in C++ or Python—the resources are anemic and opaque.

To the CircuitMess team: Where is the actual technical documentation?

To use this product as advertised, the community needs more than a clear plastic case; we need transparency. Specifically, we are requesting that you post the following in a centralized, accessible location:

  1. Full API References: Comprehensive documentation for the libraries used to interface with the hardware beyond the “visual blocks.”
  2. Hardware Schematics: Detailed pinout diagrams and circuit schematics so we aren’t “black-box” testing the board.
  3. Low-Level Integration Guides: Actual documentation for the C++/Arduino/Python environments that isn’t just a “Getting Started” stub.

Until these shortfalls are remedied this device will remain the first and last Circuitmess device I will be purchasing.

#7

I am truly sorry to hear that your experience with the Clockstar 2 has been frustrating. We sincerely appreciate your direct and detailed feedback, it’s exactly what we need to hear to improve our resources for the developer community.

Our goal is to provide a smooth experience for beginners while still offering the depth that seasoned makers expect. It sounds like we missed the mark for you on the latter, and for that, I apologize. Regarding the technical transparency you’ve requested, please check our GitHub repository, which serves as our central hub for libraries, source code, and hardware definitions: CircuitMess · GitHub

We are continuously working on making this documentation more human readable and centralized. If you find that specific pinout diagrams or API calls are still missing from the GitHub, please contact us directly at contact@circuitmess.com. We would be happy to provide the specific technical files you need to ensure you aren’t black box testing.
CircuitMess Team