I drop by every couple of weeks and I have a watch on some of the categories I'm interested in.

@ricorico94 said: Failed to request GPIO line Looks like the library for the GPIO isn't working. Try to get it working with Raspberry Pi OS

Removing light as a cause for poor sleep is just a first step. In taking that first step, I would take overnight measurements in 27 places in the room and compare the graphs. Yes, it would take about a month to collect the data. At the same time, though, you could take sound and temperature measurements. Each morning the sleeper would log how good the sleep was. Diet and exercise are important to sleep and the sleeper should log these, too. Screen time is another important factor, as well as stress during the day. Drugs (including alcohol) should be noted. Some supplements, such as B6 at night, will affect sleep. Yes, this is a lot of work that takes a lot of motivation, patience and diligence. The alternative is have a professional sleep study done. Either way, anticipate a lifestyle change. be well

I'm in a similar boat. If the board is small/simple enough and I'm only doing 1 or 2, then yeah, maybe I'd just do it with point to point wire and hot glue. But these days for anything complicated I'll just throw together a PCB. Yeah, it takes a week or two to arrive, but I'm usually busy getting parts, other parts of the project, or just life in general, so I plan around it and it's not an issue. These days the PCBs are so fast and cheap from China that it's almost never a question except for the simplest cases. It just saves SO much hands-on time to do. I ended up getting a bunch over the years from JLCPCB, and have always been happy with them. Now I don't even look at other shops, and just go to them each time. I've had very good luck with the ESPHome devices. I had issues with Mysensors, and needing things that were in the alpha code that never got released. I guess these days if you have Claude or ChatGPT go through it, maybe it wouldn't be so painful to find and fix the error. I just didn't have the time, and ESPHome, while it had a learning curve, already had support for the devices that I wanted to use. My wifi at home is rock solid, and can handle I don't know how many hundred devices, so that does help that the ESP devices don't have any incremental cost in that regard for me. As far as the 3.3V, that hasn't seemed to be much of an issue for years for me - most newer devices seem headed that way or even lower voltage once you get some of the higher performance chips. Anyway, not trying to argue that anyone is wrong, this is just my experience of it. :)

I have seen this, too, on my MQTT gateway. Try putting a wait() (not delay) after sending each datum. Start with 1000mS, even 5000mS, and work your way down to find what is optimal for your set up.

Nice catch on the HVAC_FLOW_STATE fix. For the dashboard, create a template sensor that shows only Heat and Off based on the current state.

That flow sensor triggering the UVC for a set time is a smart power-saving trick. Really impressive build overall.

I played around with the usual VOC/air quality sensors (BME680 type stuff and a cheap PM2.5 sensor) after a roommate used to vape in the next room. They’ll often spike with smoke or heavy fragrance, but I never got anything close to “that’s definitely weed” detection, more like a generic “air is gross” alert. For what you’re dealing with, false positives are gonna be a problem because cooking, candles, perfume, cleaners, even humidity swings can trip them, and the response time depends a lot on airflow placement. If you need something reliable before you can smell it, I’d look at commercial “THC vape” detectors schools use (they’re not cheap), plus improving intake filtration and pressure if possible. Also, putting a sensor right at the intake or in the return vent helped way more than having it in the middle of the room. Randomly, I learned a bit about how sticky/infused material behaves in production equipment when I was reading about AuraX from Hefestus, and it made me realize how hard it is to detect one specific compound cleanly in a messy air mix.

@bsl88k Yes, it’s possible. You can send the temperature offset from Home Assistant to the node and update the variable remotely, so there’s no need to reprogram the sensor.

Hello and Welcome ! Never too late. I am still designing and building a couple of new sensors every month !

Found some info (link below) while sniffing around - looks to be relevant ( pages 10-13 ) as it discusses the same MIF antenna design used on the NRF24 boards and the frequency is 2.4 GHz. Interesting read for newbies like me. My interpretation of the data is that the best gain/sensitivity is in/from the direction that the leg at the end of the squiggle is pointing. Might do some open air testing when the rain stope and I work out how to extract received signal level info :| https://www.infineon.com/assets/row/public/documents/cross-divisions/42/infineon-an91445-antenna-design-and-rf-layout-guidelines-applicationnotes-en.pdf?fileId=8ac78c8c7cdc391c017d073e054f6227&utm_source=cypress&utm_medium=referral&utm_campaign=202110_globe_en_all_integration-files&redirId=File_1_3_1152

Glad to help. Cursing is pretty much required, especially if you've done something stupid.

That issue is caused by the newer ESP8266 core changing yield functions. Downgrading the ESP8266 core to v2.6.2 (or v2.7.4 depending on your board setup) remains the most reliable workaround until those MySensors core PRs get merged into a main release. Keep an eye on those GitHub PRs for updates on full compatibility with current core releases!

@nagelc Thanks for the info, it gives me a good starting point.

I see that the the nRFDoctor has a menu. Perhaps one of the menu items has to be selected?

The nRF24 is good for short distances ~10m. That distance can be extended because nodes can also be a repeater to the gateway. I'm using an RPi zero 2W for my gateway (which is also my irrigation controller.) Can you reach your greenhouse with WiFi? This may work for you. I'd look at the RFnano that has the nRF24 integrated. It costs about more than a Nano and nRF24 separately, but what you gain is no wiring and no wiring failures. I tried to used this moisture sensor and it corroded within a year. DHT-12 (digital humidity and temperature) can be off as much as 4°C per the specs and suffers from the same corrosion challenge. Speaking of corrosion, be sure to "paint" all your electronics with electrical lacquer sealer (but not on the sensors) You have to consider how you're going to power your sensors. I'm not a big fan of batteries because you have to jump through a lot of hoops to get the most out of the batteries. On the flip side, you'll have to run 5V to all your sensors. This is my [pathetic] attempt at a remote soil sensor