Skip to content

feat: Split the Counter from the Peeper - #7

Open
DoomHammer wants to merge 4 commits into
mainfrom
outsource-counting
Open

feat: Split the Counter from the Peeper#7
DoomHammer wants to merge 4 commits into
mainfrom
outsource-counting

Conversation

@DoomHammer

Copy link
Copy Markdown
Member

Also:

  • Add pyproject.toml
  • Add CI checks
  • Introduce new project structure
  • Add some initial tests

Also:
- Add pyproject.toml
- Add CI checks
- Introduce new project structure
- Add some initial tests
@DoomHammer DoomHammer self-assigned this Aug 17, 2025
@DoomHammer

DoomHammer commented Aug 17, 2025

Copy link
Copy Markdown
Member Author

CC @MartaSien @bartmkraus @KM-Kinter @Xorboo @Guziq

@DoomHammer
DoomHammer force-pushed the outsource-counting branch 4 times, most recently from 0c368f5 to d27c74f Compare August 18, 2025 12:18
@DoomHammer

Copy link
Copy Markdown
Member Author

Fixes #6

@reinhrst

Copy link
Copy Markdown
Collaborator

@DoomHammer can you explain what the plan is? Remove the AI away from the PI (leaving a camera with a counting 7seg LED), or something else?

I think right now I'm the one who has te deploy it through Balena; does it make sense to move it to your account (or make a HS3 account)?

@DoomHammer

Copy link
Copy Markdown
Member Author

I checked the Count and the guy is hot!

I mean, even for our standards. The enclosure looks a bit melted as well. Throttling the fan won't get us far. Probably just closer to meltdown. We would then have nice Count-looking stalactites.

So the idea is to split the logic in two. The Pi Count is peeping and displaying, but there's another more powerful Count that does the actual counting. The Powerful Count has fans that could probably put down fire, so we're kinda safe with that.

As for the Balena account, a dedicated HS3 account would work the best.

@reinhrst

Copy link
Copy Markdown
Collaborator

OK, makes sense. Good then I know what I'm looking at :)

image

@reinhrst reinhrst left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't see any obvious issues, but the devil is always in the details. Maybe just see if it works :)

@DoomHammer

Copy link
Copy Markdown
Member Author

I've tested the counting part and it seems to be fine. The peeping part is what I'm concerned about, especially since there are no libcamera2 and gpiozero mocks or fakes to test without actual hardware.

@DoomHammer

Copy link
Copy Markdown
Member Author

I've actually created an account for us on Balena but I'm not sure what the next steps should be.

Flash the OS they provide and then select the payload in the UI? That's it or do we need to do some tweaking first?

@reinhrst

Copy link
Copy Markdown
Collaborator

Yes, no better way than to test on the real hardware.

Indeed create a project and download the os. Voncount uses a wired connection so no need to do anything special.

Then boot up front that sd, and it should install your project. You can use local mode but I find that not all that useful; pushing through balena usually goes well.

Balena cli is very useful though ☺️

@DoomHammer

Copy link
Copy Markdown
Member Author

One more thing: I remember we had a problem with DNS server. How can we configure Balena to use only local DNS when resolving .hs3?

@reinhrst

Copy link
Copy Markdown
Collaborator

Good point. I will check the balena config I used when I get home. Things are either in there, or in the repository.

@reinhrst

reinhrst commented Aug 21, 2025

Copy link
Copy Markdown
Collaborator

Just showing you all the things that were set in Balena:

  • Device variables:
image (values: `192.168.0.44`, redacted, but I think well known, and `hs3`)
  • Device configuration:
image

(Note that these items can be set as device of fleet configs; if you only have a single device there is really no difference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants