General Discussion

@nca78 said in Combining orders at OpenHardware.io?: Just make a paypal donation of the PCB price difference to MySensors for that. Maker of PCB will lose their share but it's pretty small and it ends up given as donation to MySensors most of the time. Excellent idea!

Thanks, I'll try it!

@gohan Disabled my Firewall and Virusscanner and now it seems to work :)

@gohan Nope, hourly measurement is quite sufficient. I had bought two of these with onboard RTC to pass time control to the DS3231M and let the Nodes sleep, at the time it was purportedly energy advantageous. I'm aware I could have used a non-RTC version and a sleep time, although have yet to succesfully make sleep for an hour for some reason, yet 30 minutes is no problem. Just puzzled how it should be deployed, hence the query..

Thought I'd share a couple cool things I've learned recently. One is that meshmixer offers treelike supports, which is pretty cool, and it's free: [image: mainpage_download.png] You can import your model and just add the supports without using the rest of meshmixer, if that's all you want. That's how I plan to use it. The other is that if you want to print faster, but with good print quality, you should definitely look into linear advance. https://www.youtube.com/watch?v=c5jjwBqARpo&t=255s Anyone else learned anything cool lately?

You can use this category (general discussion) if you like. Or try the openhardware category, if it is open to new threads. It is open to me, but that might be because I have admin privileges.

@zboblamont After a lot of headscratching I solved part of this puzzle and feeling a little stupid. Nothing to do with Library conflicts, both Wire and softwareSerial work as they are supposed to, the level converter works perfectly, it was a combination of sketch issues and the manner in which sleep was invoked on both Master and Slave, as well as a problem ultrasonic board. 1 - The DYP-ME007Y I could only ever get to read on a Russian developed sketch using softwareSerial. Although I got the reading once, the Slave was locked in an endless loop in the background, never going to sleep or giving the battery reading. By doing the ADC battery measurement first at least I got both readings, but with the Slave running endlessly even with the ultrasonic board shut down, it was killing the batteries. So I gave up on that one and switched to the second tank which uses time of flight calculation, readily incorporated as a function. This time I incorporated LED flashes so I could see what WAS and was NOT happening. 2 - The JSN-SR04T-2.0 Slave went to almost immediately per Gammon's sleeping Slave routine, would waken when prodded, but would not return a battery reading. The problem lay in Gammon's preparations prior to sleeping the Slave, where he turns off the ADC, but it remained off when awake. Commenting out the ADC shutdown at least solved that issue for now, at least the Slave gave the required readings and went to sleep, but... it never started again. 3 - The Master was going to sleep but never wakened on the onboard RTC alarm set to Int1. Switching to a straight Sleep period did not work either, until it finally it dawned that the Wire service may be interfering. Only when Wire was shut down and re-invoked after wakeup did both Master and Slave sleep and awaken as intended. Left it running overnight, and it has been consistently reporting every 30 minutes, so will look again today at getting the DS3231M to work properly on the Master and read how to restart the ADC on the Slave. Frustrating as a relative amateur, but lessons learned. If there is no function to interrogate the DYP ultrasonic, may just order another device from China and hope it proves simpler, cheap enough even if it takes a month...

@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