S2D2
Members-
Posts
427 -
Joined
Everything posted by S2D2
-
Others have covered this, but just to be clear: 9kW heat output / CoP of 3 = 3kW electric import 3kW * 24 hours = 72kWh per day 72kWh * price cap unit rate of somewhere below 30p = £21.60/day £21.60 * 31 days in the month = £669.60 6696kWh of heat per month. The heat pump can keep your house above "seeing your breath" temperature. The real issue is, you don't want to spend £700 a month on heating, which is absolutely fair enough. But it also has absolutely nothing to do with whether the heat pump can heat your property. Now let's back out what you're actually putting in. £70 monthly might equate to around £60 a month on heating in the winter. Don't focus on that number, it's an estimate and we're just concerned with order of magnitude at this stage. £60 per month / £0.30/kWh = 200kWh electricity import 200kWh * CoP of 3 = 600kWh of heat per month About 9% of the rated heat pump output. Of course the house is going to be cold. For reference, I have a moderately insulated house and in the last 30 days it required 2508kWh of heat to hold its temperature. You've input 24% of that into your uninsulated property. Only you can decide how much you value warmth. You have a very wide range to play with for the coldest month of the year, £60 to £600.
-
Your monthly bill would have to be circa £700 to test this theory. It would be useful to know what your next bill actually is. I'm glad your noise issues are sorted and you've found some balance in the heated hut. If you think selling the house would improve matters then that seems very pragmatic. Do not dig out the floor and install ufh. It's a complete waste of money in your situation. All credit to @-rick- for thoughtful suggestions, unfortunately you're not going to get the answers you need to progress the train of thought, it's just not what zoot is looking for from this forum.
-
I can't speak for other companies but most Octopus smart tariffs are on the same standing charges as the standard variable tariff. Obviously if you're on a fix the new standing charges will come as a shock, but you'll probably find that either way at renewal. You can also be on a smart electricity tariff and whichever gas tariff you want, e.g. tracker. I factor in 15% round trip losses, which do make a difference, I stopped using Flux because of this. But Cosy/Go still have a large worthwhile saving. The degradation point is an interesting observation, I wonder how the value per unit degradation calculations would come out?
-
Existing one year fixed tariffs will continue at 15p but they've been renewing onto variable for months now, which is the one that changes in March.
-
In winter I need the 3 charging windows of cosy due to a small battery and big usage from the heat pump. The other 9 months of the year solar replaces those charges and ASHP usage drops dramatically, so Go is cheaper for charging the EV and the battery once a day (8.5p/kWh vs ~14p/kWh). If you do enough miles, it can make sense to stay on Go year round, so some due diligence is needed as my setup will not fit everyone.
-
Yes if you have an EV and heat pump as mentioned. I switch between these two tariffs twice a year and it's within 24 hours now, often same day.
-
I still advocate a smaller battery and the Cosy tariff in winter as you get three charges a day. Yes the cheap rate is more than Go but it de-risks the battery payback uncertaintly. ASHP still runs 24/7 from the battery and ignore the really cold days where you end up importing at standard rate, they are expensive but there are very few of these days a year. 60% of my annual bill has been the last 60 days of usage.
-
Any recommendations for where to buy a good rigid silencer that could mitigate OPs issue? I thought these did the vibration decoupling between mvhr unit and ducting? https://bpcventilation.com/products/quiet-vent-125mm-150mm-rubber-flexible-circular-duct-connector-2-x-clips
-
It's real, I noticed today Octopus have a banner linking to it at the top of their home page. It's made by an employee.
-
Via local http. There's no explicit rate limit, 10s was good enough for me but even still, I have to disable it when Solax do remote updates as it does cause them to fail.
-
I've done this with an x1 hybrid g4, in case anyone has questions about that. You can pull data every 10s on the standard wifi dongle.
-
The reply it gave is complete nonsense, it didn't even use the dateutil method it's saying it did.
-
Nope. Great if it works for you but hopefully this exercise has proven care is needed and dont trust the code "AI" generates.
-
It added 37 lines to fix the time parsing and did indeed do so. It only needed one of those lines.
-
Thanks - it disappears on mobile due to the lack of space!
-
The first failure is incorrect timestamp parsing, i.e. it will throw an error. It's at this point no value is being added imo, far quicker to just fix the timestamp parsing than convince gpt it needs to. Then you can move on to the other bugs.
-
Personal highlight is how it's started cramming multiple env entries onto one line to get the line count down 😂. It still fails to parse the response in the same way as before.
-
Nope, yours is far, far worse. 222 lines 😂. It gets the right endpoint at least which mine didn't, then fails completely when it comes to parsing the response.
-
Dunno, the original prompt is gone. Here's one that spits out non-functioning code: Here's some info on data collection: https://help.openai.com/en/articles/5722486-how-your-data-is-used-to-improve-model-performance
-
I disagree, but I didn't use the exact same prompt so it could be pure coincidence. Not that comes to mind and I'm not logged in, so you could see what I do with a logged out session.
-
Apologies for the formatting and you'll have to sanity check the output for me!
-
This is no longer possible as it has seen my working code and will now produce a working example - you're welcome ChatGPT! Previously it accessed into JSON data using an invalid key and tried to store cumulative data as hourly totals (PV forecast from forecast.solar). The former is easy to spot, an outright error. The latter will look like it has worked but the values are nonsense, much more dangerous. I appreciate I'm being overly negative, it's a useful tool for getting started or finding relevant information but a lot of care is needed when using the output code.
-
To check I'm not talking nonsense I asked GPT-4.1 to replace a 30 line Python file I have to access a public API and store the returned data in a database. Took 10 minutes to write and test. Given no context, it produces code that looks fine. It doesn't even vaguely work as it gets the API syntax (which is publicly documented) very wrong. Fixing it requires replacing many lines of code (which are now 56, not 30). Given my existing script, it rehashes it to 76 lines without adding value and introducing a few unwanted side-effects. When told what the problems are, the code works, because the meat of it is the existing code. When asked to improve some timestring parsing that was written in a hurry it happily introduces bugs whilst claiming it has been improved. It will get you 80% of the way there, but so will copy-pasting the documented example from your provider's readme. The rest is from you if you actually want it to work, at which point you might as well just write the code.
