geerlingguy / geerlingguy/time-pi
Getting TimeHATv6 + Neo-M9N working
- Dominant language
- Python
- Stars
- 285
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
I [forked time-pi](https://github.com/xiaodown/time-pi) then with the help of an AI figured out how to get my TimeHATv6 and Neo-M9N working.
You can see the diff at this PR: https://github.com/xiaodown/time-pi/pull/1
And there's a detailed discussion of everything here: https://github.com/xiaodown/time-pi/blob/master/docs/timehat-v6-neo-m9n-rpi5.md
The biggest part of it was probably getting the intel i226 driver working with the modern 6.18 kernel that comes on Debian 13-based raspberry pi os. The driver that comes from debian just doesn't work, and the one provided by the Time Appliances Project is targeted at 6.12 kernels, so the playbook downloads the Time Appliances driver, patches it, builds it, and installs it.
Anyway, I'm no ansible expert, so a good portion of this is vibe coded, but I did what I could, and I tested the heck out of it, given the hardware that I have on hand. I had a couple of sd cards basically swapping back and forth between being flashed and being used to test the playbook on a clean / default install.
While I'm confident that this will work on a TimeHATv6+Neo-M9N, some stuff I've done to the playbook may break other hardware configurations, so I am not suggesting that it be merged into Jeff's repo as-is. But if anyone is running into similar problems, feel free to either try my fork or cherry pick the bits and pieces of it that may be useful to you.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading docs/timehat-v6-neo-m9n-rpi5.md and the diff in the linked fork pull request, then inspect the existing Ansible playbook and its hardware assumptions. Any follow-up should define which configurations are supported, preserve existing hardware support, and be tested on a clean Debian 13-based Raspberry Pi OS install.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, debian, linux, raspberry-pi
- Domain
- devops, embedded-iot, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100