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

Good stuff. Which coin cell are you using? What transmit power?

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

There is a collection of techniques that can reduce energy consumption of the Nano. (eg, remove power applied LED) I've read about µA's during sleep periods. The ESP-12F clearly achieves this and can be a MySensors by adding a radio. Note that if WiFi is not disabled, savings are probably lost because the WiFi is energy hungry. This would have me leaning towards MySensors rather than ESPHome. My experience tells me that the Nano is more durable than the ESP. Another tip: If you're going to put your sensor in a harsh environment, after you have assembled it, "paint" it with electrical lacquer.

@mfalkvidd After giving this some thought, wouldn't that imply that at sufficiently low flow rates, the the meter would not detect any flow. A leaky faucet? While I'm pretty sure that my pump can't pump that slow, the pressure would drop, eventually triggering the pump to start. A leak could be detected by periods of pumping that are very short? An experiment could be run to see how much water must be released to trigger the pump to start. The time between pumpings could then be used to determine this flow rate. And after reading this, I see I have to much time on my hands which could be used to address more pressing issues.

Stainless steel probes are a solid choice for durability. If you're thinking about power efficiency, integrating a sleep mode could really stretch out battery life.

Hello, I am reviving this as I upgraded my kernel to 7.0 and now have communications issues. I discovered that I had to force port speed when opening it up to the right speed, then it communicates a bit then nothing... driver is ch341 any idea ?

Nice work @Kokosnoot I think you could use #define MY_RFM69_IRQ_PIN 2 #define MY_RFM69_IRQ_NUM digitalPinToInterrupt(MY_RFM69_IRQ_PIN) This should convert the pin number to interrupt number automatically.

@KevinT should be one of these https://github.com/mysensors/MySensors/pulls?q=is%3Apr+esp8266+sort%3Aupdated-desc+

Hi, The sensor has a lux setting you can adjust to block triggering during daylight, but I just add an "after sunset" condition to my automation script to prevent daylight triggering. [image: 1778010220665-pir-settings.png] On AliExpress: PIR no base PIR with base

nice! I'm happy that there is another radio to use

Start with a simple communication method like Bluetooth or Wi-Fi on your sensor platform, use something like Arduino/ESP32 with a mobile app (e.g., Flutter or React Native), send data via APIs or Bluetooth, and design your platform to expose readable data and basic control commands for the app.

I have a very well working setup with jeedom & mysensors. do you have access to the logs in debug mode ?

I get what you mean. One thing I still appreciate with MySensors is the control over how nodes communicate and behave, especially for simple, purpose-built setups. It’s not always the quickest to deploy, but it can be more predictable long-term for small, dedicated systems.

Around 30–50 N·cm holding torque is typically sufficient for most focusers, and a standard NEMA 17 with microstepping (e.g., 1/16 or higher) usually provides enough resolution without needing a gearbox, though 0.9° motors offer slightly finer native precision than 1.8°. To reduce vibration and resonance, use lower current, acceleration ramps, and a flexible coupler, and for long sessions set the current just high enough to avoid missed steps while lowering holding current to manage heat.

With debug on I can conform it works just fine. So far I can see all sensors reporting and all actuators respond without any problems. Accept for one, but that radio is in a cage of Faraday and I knew it would need a repeater close by. Next step making the shield for the rfm69, so that I have one form factor for my Gateways and Repeater(s). But it has to wait until after Eastern. as it's the same for adding an extra decoupler capacitor.

As we all know, the nRF24 works pretty well, but there is a lot of device-to-device variation. This would be a nice thing to have when debugging the network. @juliefen will you be creating a github project with schematic, board layout, code, construction tips, theory of operation, calibration and operating manual, examples, etc.?