General Discussion

@flyyboyy A1: From the datasheet: 3.3V operation with 5V I/O signal tolerance A2: I think so A3: If I understand the library code correctly, the new RFM69 driver supports softspi but the old does not. Add this to your sketch (before #include MySensors.h) for both the gateway sketch and the node sketch. #define MY_RFM69_NEW_DRIVER A4: If you don't know you need it, leave it the way it is in the example. This goes for almost everything. A5: Do you mean MY_CONTROLLER_IP_ADDRESS? This is only used for client mode. I think OpenHab can use server mode. A6: Just leave the default A7: When you want to use local sensors, you'll hopefully know why :) There is absolutely no need for local sensors, but MySensors supports local sensors for those who want them. A8: Correct.

@mfalkvidd Yes, you can buy it here https://www.tindie.com/products/clayghobbs/pd-buddy-sink/ Or order the PCB and do it yourself here https://oshpark.com/shared_projects/B7h1WKOi This does require very fine SMD soldering!

@dbemowsk Thank you for the help so far. The first time we flashed tasmota successfully I did update the drivers from the USB converters website and were able to select COM5. We have since tried pogo pins and other USB adapters. I will check everything again.

I used a Pro Mini as slave over SoftwareSerial for a project. Maybe you could use that for inspiration and reuse some code. https://forum.mysensors.org/topic/3438/physical-mood-light-color-and-brightness-selector-based-on-lcd-touchscreen-with-demo-video/

@nca78 said in Fewer home automation postings? What's behind it?: The only problem I see is it's based on an atmega setup which will probably soon be deprecated for MySensors. Yes that is an issue. For now I'm trying to keep the sketches so simple that the simple signing and encryption feature will still work. I read that in MySensors 2.3 a goal was to make the encryption and signing features use less ram, so there might still be some life left in the Nano :-) I also found an STM32 board that has a NRF socket built in. But that has to be manually soldered, and it also make sensors less easy to connect (fewer GND and VCC pins).

@derby-jhon Why are you concerned about sending it serially? Is there a reason you can't use I2C?

@alexsh1 signing fits fine on atmega328p. Just comment out any calls to your libraries and the linker will garbage collect any code drawn in by them. Once you confirm your security is operational, disable the debug prints alltogether and add your library calls. Of course, if you have space issues even then, there is not much to do but optimize the code.

@bladeback This has been asked before several times, for further investigation you might look for "node to node communication". As a starting point, you may use the following thread starting with this posting: https://forum.mysensors.org/post/84724

Thanks for all the ideas. I think I will start buying some bowls :) Thanks

I really like mysensors.org, but I've always had difficulties with the site organization. In my opinion, is not intuitive at all, although it has a great and appealing theme. Well, maybe it shouldn't, but this sets me back when trying to build anything... I know this excellent initiative for a couple of years now, and from time to time I try to do something but I end up de-motivated because it takes too long to find simple answers/solutions. At the moment, I have nothing built although I have all the equipment I need, including SenserBenders. Yes, frustrating like r-nox commented 2 years ago. Anyway, my point is: For the ones looking for a library that makes this DHT sketch work, mysensors have compiled a set of libraries that include this DHT.h and many others. Just go to https://www.mysensors.org/about/arduino#optional---install-external-mysensors-examples (yes, the name is not intuitive, maybe the keyword library would make it more obvious?), or jump directly to here and follow the standard library instructions. It took me two hours to find this, hope it saves time for future followers of mysensors like myself. Good luck!

38/5000 I am asking here because maybe there is a new project

@soloam OK, so in the end this seems to be a problem related to that particular controller software. Imo it would be better to address this issue by enhancing the controller software towards a more constant handling of added infos from user side like renaming devices rather than using the limited space on the mcu to store info not needed by other controllers.

May I ask why are you using such old setup?

Again: Look at "MockMySensors" sketch in MySensors example library. All type of sensors has got presentation and sending or receiving function examples for them there.

@gohan What do you mean? The rPi or the Esp? For the rPi I first used a NRF24 pa lna getting power from the 5v line with a voltage regulator (ams1117 based) Then I thought could be problems with this radio or supply and ditched it for a normal NRF24. With identical behavior. Sometimes works for a week or a couple of them or I have to restart the whole Pi several times a day only for being able to go out of home. When I first implemented the rPiGw worked for weeks. Then the problem appeared. then vanished and was working for months until some point that became worse. I even thought that my wifi hotspot could be dying and changed it for a unify-pro (nice gadget) I live in a house far from others, so wifi interference seems not an issue. I run the Pi from a readonly sd for boot partition and then uses an usb drive for the system+controller. logs on tmpfs. I was fastly implementing it in my home, but as this problems arose, I only have the power monitor node, the garaje door node and a doorbell that is offline because suspiciously started to eat batteries two months ago. I'm in Domoticz beta. For the esp gw it's just a nodemcu board on a breadboard paired to a normal nrf24. Edit: Ups! mysensors versions are all 2.2.0. The arduinos are all 3v3 8mhz boards and one 5v (power)

Perhaps using a different microcontroller could also be an option? I'm personally not to deep in these things, so this might be completely wrong, but at first sight I'd try to get this working with a STM32F1 board. Seems that using them in conjunction with direct access to the ADC might speed up things, see http://wiki.stm32duino.com/index.php?title=API#Reading_from_.26_Writing_to_pins as a short reference. And using MySensors with STM32F1 seems to be used by several users here.

@Sergio-Rius I have split your discussion in this new thread : https://forum.mysensors.org/topic/9256/aggregating-data-from-multiple-arduinos-into-one-sensor

@alexsh1 yes, correct! :+1: