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.?

Can't give you a 100% answer. I've noticed with FETS I sometimes have a low leak Voltage. But I've seen Chinese designs that gave a negative voltage when the FET was turned off haha

Thank you Buxtronix

I have learned the hard way, many times, "If it's not broken, don't fix it". MySensors fills a niche, very low power, very low cost, sensors (albeit, DIY). The range is about the same as Bluetooth. The data is usually a boolean or an integer. So let us not say, abanddoned but at a development plateau. A mature technology that still has legs.

This is really not a MySensors topic! Just by the way present you request indicates that you are way over your head. I have a degree in electrical engineering, the study of electrical energy generation, transmission, distribution, etc. and substation design would take me years of study to be competent. Any discussion about electrical energy delivery start with safety. Fuses and breakers, basically, but these have to be able to break 1000's of amps ... not a trivial task. The trick is to bring down the circuit without damaging other equipment on the circuit. Just detecting a fault is a doctoral candidate dissertation. Basic components: transformers, breakers, switches and a lot of instrumentation. Voltage levels are pretty much already defined because the equipment available is already set for those levels. Transformer basic rating is KVA, input and output voltage. There's a lot more to it ... a lot more. As far as books for beginners ... I can't imagine that there are any. There are probably books for people who have been in the industry for more than a few years.

Awesome project!

Hi. I'm running cppcheck 2.18.3 Just grabbed the latest. The above were from MyCryptoGeneric.cpp. Perhaps some new checks were added since 2.1

Welcome @aliansari. I hope MySensors gives you as much you as it has given many others.

@OldSurferDude as long as we’re using nRFs this project is still relevant :D Great little tool to check for efficiency of modules I can even « aim » a pcb antenna to get the best result !

Glad you clarified the scope of your project. Small scale solar projects are much easier. One of my projects is a "battery powered soil moisture sensor, battery recharged by a solar panel" I use a tp4056 board to charge the battery from a 1W solar panel My Arduino Nano wakes up every hour to sample the moisture report the current moisture level. Corrosion is problematic. My house battery project is really outside the scope of MySensors, I'll send that in a chat

@monte thank you for that one. Although almost 2.5 times the price it's cheaper than other European options.

Quick update: i wanted to hide and protect the Nano in a housing. Aliexpress supplies very nice enclosures that fits on Din rails. https://fr.aliexpress.com/item/1005005505247992.html They fit in electrical cabinets thanks to standard dimensions. [image: 1771086807073-a.png] [image: 1771086818359-b.png] One 3Dprinted part later (glued inside enclosure) and the Arduino is safely held in place! [image: 1771086835896-c.png] [image: 1771086853317-d.png] [image: 1771086860801-5.png] stl file of adapter : dinRailEnclosureMountForNano-revE.stl

I'm not sure about Tart, but Grove is an interface for I2C that is used by Seeed studio. With the right connector, it should be easy to make a Grove compatible MySensors node. Adafruit has Stemma and Sparkfun has Qwiic. These are all similar ways to make I2C sensors more plug and play (at least from a hardware perspective).

@Eliza-Collins Thank you for a more knowledgeable explanation! When I wrote: said in Imitating a LoRaWAN(R) with ESP8266/ESP32 and MySensors: with a number of compromises You filled in some of my nebulus's with: @Eliza-Collins said in Imitating a LoRaWAN(R) with ESP8266/ESP32 and MySensors: ADR, security, scalability, and multi-gateway roaming are among the issues that LoRaWAN resolves. Thanks for pointing these out

Good project. Let us know how this works out for you!

Thanks @Sasquatch. I did some testing also. The values below seem to be the correct ones. I had similar -100 RSSI at all power settings when using the opposite settings. When I use these, I got reasonable RSSI's that changed approximately linearly with the power setting. I got at least 500m range with an E5-LE in a quick test. That's a 5x improvement and there were many obstacles and buildings in the path. I look forward to trying it somewhere where I have more line of sight. I made an update to my code on github. {STM32WLx::MODE_TX_LP, {HIGH, HIGH}}, // For the E5-LE {STM32WLx::MODE_TX_HP, {LOW, HIGH}}, // For the regular E5