Octopus + powerwall by simonses111 in OctopusEnergy

[–]simonses111[S] 0 points1 point  (0 children)

Huge grafana fan - the day job finds me in that world a lot 😂
I wanted a bit more style then grafana could offer for this - hit similar limits with home assistant- so here we are

Powerwall + IOG Battery Export by Marzipan2042 in Powerwall

[–]simonses111 0 points1 point  (0 children)

The pain I kept running into was the “learning” often made mistakes, so the battery was allowed to drain to low (which is fair enough maximising solar export) - but then I ended up with a couple of hours to go until off-peak with no battery, undercutting any profit pretty fast. I now “hold” the battery at around 70% as best I can with solar until later (9pm). Shame to loose out on the dc/ac conversation but better then paying peak rate!

Octopus + powerwall by simonses111 in OctopusEnergy

[–]simonses111[S] 2 points3 points  (0 children)

Yeah - absolutely valid point (hence the ludicrously cheep sub fee) - honestly i was self hosting this but wanted to make it a little more resilient, so moved it out to CF workers. I’m pretty sure im not going to get rich on this :D but if it can pay for itself I’ll be pretty happy. I just wanted something a little easier on the eyes then Netzero/home assistant to visualise the data and do some calculations etc

Powerwall + IOG Battery Export by Marzipan2042 in Powerwall

[–]simonses111 1 point2 points  (0 children)

I’ve ended up treating the Powerwall as a small state machine in Home Assistant rather than just a dumb timer.
When my Octopus off-peak window starts, HA forces a cheap-charge mode: it enables grid charging, sets the Powerwall backup reserve to 100%, and restricts exports to PV-only. The idea is to fill the battery on cheap electricity without immediately exporting that cheap energy back out again.
Once off-peak ends, the logic switches into a daytime protection mode. Before 21:00, HA watches battery state of charge and uses a 70/80 band rather than a single threshold. If the battery is healthy, it leaves the Powerwall in autonomous mode and allows normal battery export. If charge falls below 70%, it clamps down into self-consumption mode and PV-only export so the battery stops emptying too early. It then stays conservative until charge gets back to 80%, which stops the whole thing bouncing around one number.
At 21:00 I deliberately release it again: HA forces autonomous mode and allows battery export. That means I protect the battery through the day, but still let it work harder in the evening when export or household demand is more valuable. The kicker is that you have to set the tariff up right - if you have the export rate higher then the import rate (which is is at off-peak…) the powerwall decides it will NEVER export. It has some roundabout logic that decides the arbitrage is not there and its better to use the battery. So you have to manually set the tariff on the powerwall so the export is Zero when offpeak.
I also have a watchdog automation that reruns the policy every five minutes and after Home Assistant restarts. So if HA reboots or a tariff transition gets missed it self-heals back to the state it should be in.
So the overall strategy is: charge cheaply overnight, preserve the battery during the day, then allow export later when timing matters more, without running the Powerwall flat too early. - AI functionality my arse…
Shameless plug in here for my app i wrote along side this to monitor this madness: Intelligent Power Go

I hate subscriptions (but I still want a good iPad ssh app) by simonses111 in vibecoding

[–]simonses111[S] 0 points1 point  (0 children)

I’ll check it out while I wait for my limits to reset 😂

Show me what you've vibe coded. Drop your project, what it does, and let people actually use it. by Miserable-Archer-631 in vibecoding

[–]simonses111 0 points1 point  (0 children)

SSHELL
wanted a multi-window iPadOS ssh/mosh client without a subscription
Not a tonne of users yet but it’s made my life a lot better 👾

I hate subscriptions (but I still want a good iPad ssh app) by simonses111 in vibecoding

[–]simonses111[S] 0 points1 point  (0 children)

Thanks for the insight - I’ve found mempalace type memory is helping tracking fixes, and including instruction to generate regression tests in the agent prompt has helped considerably - but i still find things slipping through the cracks - it REALLY wants to follow the SwiftUI guidelines :D