Fun... my dumbass wanted to save work by getting a premade controller and somehow now I'm rewriting their firmware for them. I probably should have just built one but hindsight and all that...
Yeah, in my case, the Pi was sitting around already. And targeting the Zero W makes it surprisingly cheap, while giving more wiggle room than an Arduino or similar.
What the heck is fast forward?
Demo/Preview/etc. Play the schedule very quickly. Feel free to mock my inability to name things.
I can think of a few similar projects in the DIY section; Pi + wifi shield.
The one guy shared the hardware config, had a PCB printed (can be built without pcb) and uploaded his code to github. It might be worth checking out. You will get much farther with your limited time leveraging his code base.
I assume you are referring to FishNet, yes? Took a quick look, it's interesting, but building it pretty much exclusively in Node-Red makes some things easier, and some things harder. I looked at Node-Red myself, but decided python was going to be fairly straight-forward and could be bolted onto a front-end built in some other way once it was time for that. Node-Red-Dashboard would be an interesting stop-gap for a web front-end, but not really ideal.
There's a good reason he went the route he did, but there's a good reason I decided against that route. Node-Red just isn't flexible enough for the thing I'm looking to build. It's a great sandbox, and a great way to make it easier for someone to play with the IoT. But not really ideal once you hit the edges of the sandbox.
I also looked at iAqua/iAqua Lite. But if you are referring to something different, and my search didn't catch it, I'd be happy to take a peek.
And yeah, this probably should be moved to the DIY section, whoops. I'll see if I can get a mod to do that.
I was going to build it but then sanity struck and I realized a $30 controller does what I need and that my time is worth much more than .05/hour.
I wish that were true for what I wanted.
Very nice .. any plans for adding some mqtt functionality? Is the idea that this will be an end node or also a basic hub for other sensors and features?
Fully agree with No Online Accounts ....
Plans should be driven by a need, and a goal. Right now the need I have is to have a controller that I can use to dim my Twinstar light (and my second Twinstar down the road), and have better timing configuration than the Storm/HurricaneX or the Bluefish, but isn't tied to Windows-only software that seems to break for me like the TC-420 does.
That's the need. That's the thing I will
deliver, since it's mostly done already.
The goal though, is more that I want to chase the AI Prime's configurability. That's the north star.
Now, if I can deliver on that goal with
the web UI is a good question (The REST API is effectively the path to get to a Web UI). But with the prototyping I've done so far, it should be possible to at least capture the feature set, using a JSON config file at a minimum without too much work being done.
If you approach this as expecting a single-mode TC-420 that you can more easily build to what you need, and configure it without proprietary software, you won't be disappointed. If you want this to become the next iAqua, I doubt it. The only automation I do on my tanks is lighting.
no, no no,, these projects fall down a rabbit hole and never finish...or get lost in endless revisions/confusion/demands..
I hear ya. I want to focus as much as possible on providing smaller chunks of functionality that can be used as early as possible.
Personally, I was hoping
to be able to hook this up on one of my tanks this weekend and let it run through the week to see how well it works. I was set back a little bit on prototyping the scheduler. Technically, I could still do it right now, but I wasn't happy with how much timing drift I was seeing with the super-dumb sleep method I was using to space apart events.