MikeSharp01

Clever / neat idea but I suspect @SteamyTea will tell you how much additional energy you are going to use in taking the coffee grounds up to 350DegC and then deduct form that the mass of concrete, and its carbon content, you won't need if the resulting concrete is 30% stronger. everything is connected to everything else!

+1 to that with steel you can reduce the bottom cord to 6mm thick provided the load is spread back to the rest of the beam correctly and the whole lot is fixed to the structure properly.

What is in the cupboard beside the bed? Is it service duct or some such? We have vaulted everything, all of upstairs and 50% of downstairs not sure how it will turn out as not boarded yet but I am not allowed any cupboards in strange places, other than in the plant room / utility, so I have either built them behind built in wardrobes / storage - so I can remove the back panel to get at things, or under removable sills.

That's interesting / worrying we have a void above the kitchen, all of which will be lined with fireline - separating it from the bedroom above, no glass other than the two FAKRO windows that will be automatic for house stack cooling. Not sure where glass might fit in. Anyway looking into the above I found this quite interesting on houzz: "Is there sufficient kitchen ventilation? In open-plan kitchens, mechanical ventilation needs to be installed for the kitchen extractor. A recirculating design is not sufficient, because not only do extractors get rid of smells, CO2 and other harmful gases, they also remove water vapour, which is created when you cook. Without correct extraction, mould can grow, just as it would in a bathroom without ventilation." (https://www.houzz.co.uk/magazine/ask-an-architect-8-key-open-plan-building-regulations-questions-to-ask-stsetivw-vs~55681353 accessed 23.08.2023) We will have MVHR, extract in the void. Wondering if I have it right!

No worries I have a bunch of the same sensors in the house so although I plan different way to do things. I thought it would be fun to pull out the address as a string. I convert the number to a meaningfull name in the code local code, MQTT the reading and store readings into a mysql db using node red.

OK - I understand. So below is some example code I built to give you an idea to play with and links to some tutorial stuff. I connected a DS18B20 to an ESP32 board and ran the code below. It explains, very simply, why sscanf can't be used out of the box, you will need to pre process the int8_t buffer before you could use it and if you pre processed it you wouldn't need it - if you get my drift. The tutorials point link in the code is quite good at explaining the syntax for sscanf. In some ways sprintf also needs a bit of work but would be a much more elegant solution in my view. I have tried to explain it all in the code as we go along. My code, with output, full code is below. The bottom line is printed from a string built up by iterating across the int8_t buffer, the line above it by just printing our each byte value as HEX and the line above that is the raw code output from the tutorial mentioned. Hope it makes sense. My setup looks like this, just one DS18B20 Full code: #include <OneWire.h> #include <DallasTemperature.h> // FROM https://lastminuteengineers.com/multiple-ds18b20-esp32-web-server-tutorial/ // Data wire is plugged into port 15 on the ESP32 #define ONE_WIRE_BUS 15 // Setup a oneWire instance to communicate with any OneWire devices OneWire oneWire(ONE_WIRE_BUS); // Pass our oneWire reference to Dallas Temperature. DallasTemperature sensors(&oneWire); // variable to hold device addresses DeviceAddress Thermometer; int deviceCount = 0; char str[20]; // I added this bit - we will use this to create the bytes as hex. String addressStr; // and this - our final string will appear here void setup(void) { // start serial port Serial.begin(115200); // Start up the library sensors.begin(); // locate devices on the bus Serial.println("Locating devices..."); Serial.print("Found "); deviceCount = sensors.getDeviceCount(); Serial.print(deviceCount, DEC); Serial.println(" devices."); Serial.println(""); Serial.println("Printing addresses..."); for (int i = 0; i < deviceCount; i++) { Serial.print("Sensor "); Serial.print(i+1); Serial.print(" : "); sensors.getAddress(Thermometer, i); printAddress(Thermometer); } } void loop(void) { } void printAddress(DeviceAddress deviceAddress) { // This the original code I am playing with. It pulls each int out of the // int8_t buffer and really just uses the clever bits of the Serial.print // function to pop out the hex values. You can do very little from here to // create a string. Howevere the basic process can be used and that is what // I have done below. for (uint8_t i = 0; i < 8; i++) { Serial.print("0x"); if (deviceAddress[i] < 0x10) Serial.print("0"); Serial.print(deviceAddress[i], HEX); if (i < 7) Serial.print(", "); } Serial.println(""); // This is the additional bit: /* Our unit8_t[8] is an eight byte array / buffer each byte of which holds a number that represents the HEX value of the byte address in that position so we will need to handle them one after the other and build up our final string as we go. So we need to iteratively pull all the HEX values out one by one and then build up our string of all the chars. Sprintf with the %x format does this neatly. It will put every hex pair into our str buffer a pair at a time. We will then need to take that pair and pop it into the bigger address buffer so we can print / add it to our data line later. */ //First set up a couple of things... Serial.println(""); // Give us a blank line addressStr = ""; // Clear our output buffer /* Now we can iterate down the uint8_t buffer pulling each byte out, use sprintf to create an ASCII pair from the value, print the pair out, as debug check, and add it to the addressStr buffer. sscanf can't be used directly as it needs char input and you have ints. You can read more at this tutorial https://www.tutorialspoint.com/c_standard_library/c_function_sscanf.htm */ for (uint8_t i = 0; i < 8; i++) { sprintf(str, "%x", deviceAddress[i]); Serial.print(str); addressStr = addressStr + str; //if (i < 7) Serial.print(", "); } Serial.println(""); // Give us a blank line Serial.println(addressStr); // Now print out our string - it should look // just like the line above it which was created // as we iterated but now we have it as a string // we can pass to other things EG your google sheet. }

Sprintf does it - here is a little experiment I just did!

Post your code and we can take a look.

I suppose it makes some sense but the WiFi speeds, and frequency groups, are now such that you should not even need CAT6 cabling for 8K video you do need to assume that the next technology for moving video around won't be looking for cat 7/8/9 or fibre - perhaps more likely. Usually you are not watching two TVs at the same time so unlike audio coming from different places you won't ever be worried about latency, which is a problem already with HDMI over cat6, and they will sort that over wifi anyway if needs be like they have with audio

Is there any PV in the mix anywhere here?

Sounds like a couple too many, what will you need them for? We have 2xCAT6 and 2xHDMI going back to the AV cabinet (HDMI cables can carry ethernet if your devices are HEC compatible - not likely though as very few are, seems to have died a death).

Exactly. That is what we have (I think) but I will do the calcs myself again when the time comes and will look at the full equation - carbon in / carbon out and then on a 10 year horizon make the call.

Have a word with / read of @TerryE's numbers on the Willis heater on straight economics it wins for a long time, eventually the ASHP will catch up but by then you would probably be close to needing a new heat pump as thy don't last forever do they!

No - you are OK, was just interested in how it was done.

Some resins don't like UFH I dimly recall reading somewhere

Ah I see - how about the Parliament hinge design to fold back on itself.

Probably and so does decrement delay as a concept. Not sure that is correct - they are / it is an example of 'porridge words' Edward De Bono framed the term I believe and since then the idea has somewhat grown into a Gestalt! EG: Porridge words Porridge words are rather meaningless words. It is precisely because they are meaningless that they are so immensely useful in thinking. They act as link words to keep thought moving from one idea to another. If there were no such words then thinking would come to a dead end when there was no direct step to another specific idea. The various uses are listed below: Porridge words allow one to set up vague questions when one has not enough information to ask a specific question. Porridge words offer usable explanations when one cannot provide any more detail. Porridge words act as cross-links for movement from one idea to another. Porridge words can act as black boxes to enable one to leap-frog over an area of ignorance and carry on. Porridge words prevent too early a commitment to a specific idea and so keep options open as long as possible. The paradox is that porridge words arise from ignorance and yet they become immensely useful thinking tools in their own right. (From: https://bobembry.blogspot.com/2012/03/porridge-words.html 13.08.2023) I sort of favour 5 as the option here but we can discuss / disagree as needed.

How are you logging into that and how is the rest of your network protected?

I would use 'Full-Wrap' hinges, on the swing out portions so you are fixing into the rear face of the door depending on size / weight you may need 3 or 4 of them. The center hinge much more challenging as you need get then on the inside and close the leafs. Here is an example - loads of style available all over. https://www.kitchenfittingsonline.co.uk/product/amerock-half-wrap-hinge-copy/

That's a pain! Can't help really, every time I look at Hue I get more confused by it complexities, but just to be clear you can still see the rest of your network remotely EG doorbell and the remote reset is actually working.

Intello plus membrane, 50mm service void finally fire rated plasterboard (dry lined).

Our architect gave us the idea of a composite insulation scheme so as to get the great decrement delay of blown Cellulose and the effective insulation properties of PIR as well. So we went stick (using engineered 300mm I-Beams) with an outer sheathing of OSB. Outside the OSB we have a layer of PIR (varies between 40 and 75mm thick) and between the I-beams we have blown cellulose. So we now have the best of both worlds thinner walls than would have been needed to achieve our U value using just the blown cellulose and still great U value of (generally) 0.099 W/(m²K)

Killing the Bees that are there wont stop them coming you need to encourage them to go elsewhere. Either make life a bit easier for them IE get a Bee brick ( or even a wall) or much tougher, IE see what the effect of washing the wall with waterproofing solution is or a weak mixture of peppermint oil and water - works for spiders.

Absolutely - anything from stick / brick to factory prefab can be done well, or indeed poorly, and all of the methods have their pros & cons. Stick/brick is time consuming and somewhat skilled but you get to make choices as you go along while factory prefab means making all the decisions up front and so is far less evolutionary (should you wish to evolve your build - we didn't, we wanted to follow the architects ideas as closely as we could.) Then its down to the range of technologies chosen and how they work together to create the home (house).

But, by the looks of it you are still driving the same van!