joth

Why do you want the UVC to benefit from the stored energy in the buffer tank - for speed of heating the UVC, or feeling it will be 'wasted' energy if not used? To the former, the buffer tank is lower temperature so not sure it will make much of a dent in heating the UVC unless it has been totally drained and is stone cold. To the latter, so long as the buffer tank is inside the thermal envelope of the building, the energy in it should not go to waste: this escaping energy is usefully heating the house. This is how I'm reasoning about it anyway ?

Yes, basically a big relay. Allows a smart home system to control heavy loads. Same for towel radiator control. Fairly easy to drive it with a basic timer switch or something smarter as desired. And you can get them with a manual override switch so still usable when the smart controller inevitably crashes... ?

I'd say 'no' to that. I'm going pretty far with smart home nonsense (or at least, future proofing wiring ready to do so) and the most I'd want for the UFH spurs is a contactor to allow me to automate shutting them off when the house is empty, which also doubles as everything I'd need to automate timing or weather based usage or whatever. Nice thing is the contactor goes at the CU and can be a retrofit when actually needed. The less electronics - smart or otherwise - in the wet area the better.

It's not that clear cut. If every application had to, say, roll it's on SSL/TLS implementation you'd have several orders of magnitude more zero day exploits. Sure, shared libraries can often be infuriating to work with, and doubly so when it turns out to be the cause of a vulnerability, but some things should not be rewritten lightly. All depends on the libraries in question of course; due diligence certainly pays off.

My impression is that the "load of libraries" is exactly what it brings to the party - after all it's not just this 'general population' that benefits from reusing already working code. Admittedly I don't have much experience with Arduino per-se, but I also thought it is fairly chip-agnostic these days? e.g. ESP32 seems is also supported as an optional 'core' in arduino https://github.com/espressif/arduino-esp32 I'm becoming quite a fan of ESP32 - I've used them more with tasmota, platformio and mostly esphome. Even if you don't need wifi for a given current project, they're nice and very cheap little boards, and they're so pervasive I feel they're going to be about for a good while, and I was surprised how handy the wifi interface can be useful for maintenance & debugging tasks even if not needed in the core application.

>>

Sounds like you got further in a morning than I've managed in several weeks with BlueIris so that's very promising (not that I've put a lot of focused effort in yet..) I forgot a nice thing with Synology is it will get a cert from let's encrypt for you, and then it should be good to go for various remote accesses you want to do with it. Certainly should be much simpler than setting this up for remote access to windows which I'm not looking forward to at all.

@JamesP thanks that's helpful! It has helped me find their "databook" which has more deatils too. I now also realize they have two active product variants at the moment: PUHZ-W85VAA and PUZ-WM85VAA (note the missing H). The former is MCS listed, but using R410, the latter is not MCS but uses R-32 (and has sligthly better COP for space heating). So another case where RHI is stearing consumers towards the more environmentally harmful choice! (I presume this is temporary, until they get the MCS listing, but that could be delayed in the current circumstances)

@JamesP sounds like this is sorted, can I ask is it working well? Do you use it for space cooling and DHW heating ln the same day without trouble? I'd be interested to know is there some documentation or how you knew to use SW2-4? I can't see it in the (UK) manual. (I'm still in the proces of selecting ASHP, the Ecodan looks to have very good COP for our needs, so interested if it has cooling capability too)

Here: https://www.ispreview.co.uk/index.php/2020/05/openreach-to-stop-selling-copper-phone-in-118-areas-go-fttp.html Mostly town centers so not going to impact self builders for a while, but, has anyone seen any openreach technical guidance on how to prewire a new build to future proof it to be FTTP ready? There's the obvious"flood wire it with cat6" but curious what their recommendations are for locating the entry and distribution, places where mains would be needed, where does the fiber ideally get terminated, is there even any call for running copper internal phone extensions anymore (I personally haven't for 2 decades, but still) etc. I'm now considering with going with only a Virgin install until FTTP is down our street (supposedly 18 months from now, so could be within a year of build finishing). But wondering how to prepare the external wall for the eventual fiber ingress without ruining airtightness.

Is that based on any inside info, or just expression of hope? Not sure when it was first published but the SMETS2 spec was had its last round of revisions in 2014, yet in 2020 still no-one is making/installing polyphase meters to that spec, and with the backlash against smart meters in general I don't hold much hope for them focusing on 3ph anytime soon...

Yeah - I went for Raid 10 across 4 drives mostly because my NAS is on Linux and I'm using btrfs which I love, but I don't fully trust its RAID 5 support (and probably never will as it looks like the winds are blowing towards zfs these days). Also I had some bad experience with Raid 5 on my old Infrant ReadyNAS that got slower over time but was a real pickle to convert back from. With the 1019+ my inclination would be same -- even start out with 4 or even three drives in Raid 5, put the NVR on it too, see how that goes and consider how to use the remaining 2 bays as space and speed demands evolve. I'll watch how you get on with interest! I'm sure 8GB RAM is plenty, but having seen the table above the lack of future expansion on this is the only hesitation I'd now have on it. (Full disclosure, I installed Home assistant on a Virtual Box VM (on ubuntu) yesterday , as they're deprecating the docker install I was using, and while it runs absolutely fine the act of carving out 2GB dedicated to the VM did make me twinge rather).

Thinking about these Pros and Cons in light of the current situation : - Pro: National bagged plaster shortage means Fermacell has distinct benefit in avoiding wet plastering - Con: Heavy two person lift makes it impossible to work with full sized boards while following social distancing Using half-sized Fermacell boards maybe a popular choice for upcoming projects. (Assuming there isn't a national shortage of these too)

It seems to be on permanent discount on https://store.ipcamtalk.com/shop/blue-iris-software/ $57.99 About £46. It's developed by a single person so can't be sure of its longevity, and unfortunate it's windows only.

Ah yes, I now recall the online reviews typically rate the Synology Surveillance station as more feature rich and easy to use than the QNAP built in software (e.g. per https://nascompares.com/2020/05/09/synology-ds920-vs-qnap-ts-453d-nas-drive-compare/) but the QNAP works out more economic. But a colleague had used both extensively and didn't rate either that much compared to Blue Iris, which is what pushed me down that route.

Well as you say, depends entirely what you're doing with it. 8GB should be plenty to host a Home Assistant installation, for example (the prime thing I'd likely want to do in an always-on NAS).

For pure storage, maybe, but the 1019+ has more RAM and beefier CPU so probably better if doing a lot of CCTV or media transcoding or VMs (or combinations thereof) https://nascompares.com/2019/02/15/synology-ds1019-vs-ds918-nas-which-should-you-buy/ has a table half way down that compares a lot of the range:

Yes I think if I was starting out from scratch now I'd go for that 1019+. The CCTV licenses have sticker shock, compared to the BlueIris one-off cost for unlimited cameras, but over the lifetime Synology is probably far better choice than keeping a Windows box alive.

It's often recommended not using RAID for the CCTV. You'd have to be very unlucky to have the drive go just as someone is breaking in. Another benefit of the segregated volumes is you can use something like WD Purple drive(s) for the CCTV which are designed for continuous write duty cycle. I very nearly went for a Synology 1019+ with 5 bays, so I'd have 4 for RAID10 and one for CCTV. In the end I realized my existing linux box RAID was just fine and not worth the cost of replacing. (Also CCTV licenses for Synology are pricy). I tried an Amthal dedicated NVR but the UI is super clumky and poor remote access so gave up on that. Now settled on a Windows 10 NUC running BlueIris. I'm not yet entirely at home with it, but it's widely supported for HA integrations and extensive power user options so I reckon I'll grow into it.

The Luxpower units look very interesting alternative, they even have a hybrid inverter that could take our 8kW array as direct input, although we'd loose out on 3kw of generation when the batteries are full as it only has a 5kw inverter. On balance I think I'll keep the batteries AC coupled just to keep the systems independent. Although the cost savings are substantial; at £950 their hybrid inverter charger is less than the solaredge PV inverter on its own. And having a single app for monitoring both is systems would be convenient Speaking of which, the one potential downside of the Luxpower is it almost certainly has a bunch of built in "phone home" code connecting to a server in Shenzhen I have no control over, for firmware updates and for their monitoring &control app service, which makes me a little uneasy. Not sure what local interface it supports for control, e.g. if it is blocked it off from public internet access.

It would be impractical and perhaps impossible to get a Tesla-battery qualified electrician to rewire my home if I'm not actually planning to install a Tesla battery at this point. I was hoping they'd say something more like "it depends whether you want to plan for a partial or a whole-house backup? Take a look at the UK version of this guide, and here's some additional information to help you figure what sort of backup you might eventually need". Answering my own question, I found the comprehensive Installation manual (generic, not UK targeted) here: https://www.tesla.com/sites/default/files/pdfs/powerwall/Powerwall_2_AC_BU_NA-EN_Installation_Manual.pdf Pages 40-48 have detailed diagrams of how it should be wired. Key thing (obvious really) is in a partial-backup scenario you need the powerwall and any solar PV inverter connected into the sub-main board that is feeding the backed up loads (downstream of the backup Gateway). Important to think about the relative locations of these things. As our supply meter, PV inverter and (eventual) battery will all be in the garage I need the sub-main there and have 2 feeds into the house (for grid and battery-backed resp.) Thinking out loud - it'd be nice if I could send both those feeds from garage to house down a single run of 5-core SWA, but it maybe a bit dodgy as they're coming from different boards. ... Unless one can use in effect a split load consumer unit, inserting the Tesla backup Gateway (cutout switch) between the 2 sides such that one half is direct grid supply and the other side is the battery backed circuits, and then send the feed to house from that single CU with a L/N pair coming from both sides. Hmmmm.

Very useful link. Do you have the Tesla equivelent? "This will only work when the customer has a three-phase meter capable of Net metering. This can be checked with the customer electricity supply company." if only it were possible in practice! But it does seem to suport the general assumption. For more motivation: Germany has a lot of domestic 3ph, and all the German PV and battery manufacturers seem to assume domestic installs have net metering and the SMETS2 spec is based on some EU conventions which Germany surely had a hand in writing, hence why I feel this is the longer term trend even if it will take a decade or 3 for UK to converge towards it.

Our PV installer told us to ask an electrician. I asked a few, and the DNO and three different suppliers (ovo, BG, Bulb) and none of them knew. Ovo was perhaps most enlightening as the customer services guy said he had no idea how 3ph export metering was supposed to work, but that they must be complicated as he fields a lot of calls getting an engineer out to put it right. The DNO confirmed that for residential installs they have no expectation or requirement of the usage being balanced a across phases, and billing (inc penalties for unbalanced use) is not in their control. If you go 3ph, one mitigation would be to sign up to the Octopus Tesla energy plan, as that charges the same for import and export so the metering is then moot. Definitely would make sense if the suppliers vaguely supported it! We're having 8kW PV and originally thought a 3ph inverter would be marginally cheaper vs 2 single ph (but not by enough to offset having the new supply installed), but we're having solaredge optimisers anyway and their new optimizer-optimized inverters will go up to 10kW on a single phase in a single box and actually works out cheaper than the 3ph one. On the plus side: inverters only last a decade or so, so you should have plenty of opportunity to change your mind over the lifetime of the house.

I wouldn't read too much into that manual, it's for one particular (albeit popular) manufacturers meter that is used in many countries and for commercial as well as domestic installs, hence supports many different metering modes. I found the SMETSv2 polyphase spec easier and more trustworthy, as described here (Tip: search for polyphase for more discussion on it) Snag is no-one makes / supplies those meters yet, and looks like they may never do so, but AIUI existing non-smart domestic installs are expected to work the same way. Personally for a new install I'd plan to install 3ph to the cut out but plan to put a single phase meter on it, unless something truly demanded 3ph from day 1.

Thanks all! My architect also pointed me to page 9 of https://www.passivhaustrust.org.uk/UserFiles/File/Technical Papers/BRE_Passivhaus_Airtightness_Guide.pdf which has some good info on this too. It seems like there is plenty of track record on taping OSB3 out there, but you need to know you're getting good quality material and [even more] attention to the detail in taping it. A good part of the attraction of Smartply Propassiv to specifiers and installers is giving a clear brand name and quality assurance around what you're getting and how to work it. Good luck and let us know how you get on :-) Did you have any trouble with getting the tape to adhere, vs any other surfaces? As ours if a retrofit, I'm already concerned about the effort needed in taping around existing joists, so anything that potentially adds additional points of weakness to the joint is my concern.