Started with MySensors and about to give up (some feedback)

[alex28]

Hi everybody. I'd like to give some feedback on my experience as a new MySensors user here. As you can guess from the title, it's not going to be very positive. I hope this kind of post is not unwelcome. It's also very long. Please don't take this badly. It's just my own experience with MySensors I'd like to share.

Short info on me. I'm a software developer mainly working on GPU low level code. Although mostly a software guy, I have some experience with the hardware side of embedded systems and I know my way around a soldering iron and a scope. I was looking for a way to improve my home automation setup, mostly made of ZWave and cheap 433Mhz devices, with something open that would give me more control. Basically build my own nodes. MySensors seemed to fit this perfectly.

So came the lockdown and hey, perfect opportunity to get started ! Got myself a couple of Arduino Nanos, a few NRF24L01+ and lots of motivation to get my first GW and test node running. Unfortunately it ended up being an extremely frustrating and time consuming experience. More than once I had to resist the urge to throw everything in the nearest trash bin.

Problem 1. The gateway.
I had an ENC28J60 lying around for some time. The MySensors getting started guide clearly mentions that this is a supported option. So I connected it, got the UIPEthernet libs linked in the guide. Cloned the ntruchsess repo as mentioned in the readme. Hit compile and - incorrect library version. Great start. Cloned the MySensorsArduinoExamples entirely, copied the lib from there. Incorrect library version. OK. Started to hunt around Google, found the original UIPEthernet repo. Cloned that and it compiles. Good.

Started the node, doesn't reply to pings. Searched the MySensors forums, found a topic titled 'Can't ping Ethernet Gateway ENC28J60 + Arduino Nano Clone' from 2017. In that topic some MySensor devs clearly state the ENC28J60 support is broken and that, I quote, 'Not sure anyone has bothered checking with the latest version of the library...'. Uh what ? If you know that this chip won't work since 2017, why is it still a recommended option on the building a GW guide ? Why not make it clear that only the w5x00 chips are supported ?

Problem 2. The Raspberry Pi gateway.
So ordering a w5100 for my GW is not an option right now. It would take a month to arrive due to lockdown. So I decide to use a Pi Zero as a GW. At least the ENC28J60 works with that one. I visit the 'Building a Raspberry Pi gateway' page. It talks about some radio communication bug in the 'latest Jessie'. Raspbian Jessie has been shelved in 2017. So uh, is that bug still an issue in current Raspbian Buster ? Do I still need to get the dev branch or not ? OK, I end up pulling the master branch. The Pi has two independent hardware SPI ports. I connect the ENC to spi0. Works. I connect the NRF24 to spi1. Oh wait, the pinout image in the wiring diagram section of the 'Building a Raspberry Pi gateway' is wrong. SPI1 CS0 is definitely not on pin 36 by default (but on pin 11). Why leave a clearly incorrect pinout diagram on your guide page ?

So I try to compile the GW for using spi1. Doesn't work, radio connection failed. Searching the forums. Found a post titled 'Double SPI Radio Raspberry Pi'. Great, sounds like that guy has figured it out and a MySensor mod commented on it. Sounds like that should work. Followed his quick guide. Doesn't work. Search more. Oh wait, it actually can't possibly work - his cs0_pin assignment in the config is wrong (this setting expects BCM pin numbering, not Pi pin numbering as he used). So that forum topic - which probably pops up for everyone searching how to connect the NRF24 to a Pi spi1 port - won't work because it contains a fundamental error.

Problem 3. NRF24 range is bad. Really bad.
So I finally get the GW and a test node to communicate. Yay ! Smooth sailing from now on. But wait. If I position the node across the room, it starts dropping packets. Searched the forums. Filtering caps on both NRF modules - check. Clean power - check (battery pack for the node, lab power supply for the GW Pi). Range is still bad. Some forum posts seem to indicate that the Nano 3.3V regulator is not good enough to power the radio and you need a separate supply. OK. But why not mention this in your build guides ? All your guides clearly show that the NRF gets directly connected to the 3.3v rail of the Nano. Well I don't have a voltage regulator. Searching more. Lots of conflicting information. Maybe the NRF is counterfeit. Yep it probably is. Order and try another one ? Order and try an external regulator ? Lockdown, week long waits for any oversea deliveries, so nope, not an option. Found lots of topics with people having range issues on that radio. Common solution seems to be switching to the RFM69 on a different frequency band. Would have been nice to know that before. Why not mention this in the guides if it's such common knowledge apparently ?

Well that's where I stand right now. What was supposed to be a fun and satisfying experience to build some home made IoT devices ended up being a long and frustrating one leaving me with a feeling of having wasted my time. I wanted to build some fun nodes but after all that time spent trying and searching and ripping my hair out, I still don't even have a stable network running.

And yes, some of this is probably due to bad counterfeit HW and also my own overexpectations. But a lot of the frustration came from the obsolete, outdated, conflicting and sometimes blatantly false information presented both on the official MySensors guides, as well as in the forums. I wasted so much time searching and trial'n'erroring solutions to problems that wouldn't even exist if they were clearly outlined in some up-to-date guides.

At this point I'm unsure about how to proceed. I like the idea behind MySensors and support in Home Assistant (which I use for HA) seems good. I could order an NRF24 PA LNA. Or some RFM69's. And try both. And have a more reliable network - maybe.

But I don't really feel like spending weeks on this just tinkering around and trying to make the basic network behave in a reliable way. Maybe I misinterpreted what the MySensors platform is about. My impression of MySensors was that this is a solid and well tested platform where the basics would just work out of the box without much tinkering around. And where I could spend my time on what actually matters to me - building my custom nodes. Trying out dozens of different radios from different manufacturers, different power supplies, different DIY dipole antennas and whatnot is just not something I'm interested in. Maybe I'll just get a commercial ZWave interface with digital inputs and connect it to the Arduino instead.

Thanks for reading.

[mfalkvidd]

Welcome to the forum @alex28 and thanks for taking time to share your experience. I'll digest it a bit before writing any further, to make sure I subdue my emotional response so we can keep this constructive.

To anyone else reading this feedback; please remember to not shoot the messenger. This is a great chance to make the MySensors project even better.

[mhkid]

@alex28 I think these are fair criticisms. I've spent a ton of time with mysensors and have backed away because of some of these same things. I love the idea and appreciate the effort that's went into the platform. You have to tinker a lot and you spend more time figuring out problems with the platform than you do actually building sensors. Spending time troubleshooting only to find out others have spent time on the same thing or info is outdated takes the fun out of the process for me.

However, having said that I keep coming back because I love the idea of this platform. Lots of really great ideas and great makers contributing here.

[BearWithBeard]

I'm sorry to hear that you had such a disappointing first contact with MySensors.

I can't really comment on the issues you had with the ENC28J60 ethernet module and RPi zero gateway, as I haven't worked with those yet. But from my personal experience as a simple community member, I think problem 1 and 2 are due to your hardware selection not being very popular and therefore might not be as well tested as others and a partially outdated documentation (you hinted at the Raspbian release which is currently two major versions behind, for example) may be the consequence of this. This should clearly be updated, no question. And I can totally understand your frustration if you continue to run from one issue into the next one like this. I think I speak for all of us if I say that I know how annoying and discouraging it feels.

But here's the thing: I don't think the devs and mods are to blame for this. While there is mainly a core team contributing to the project, MySensors is open and community-based. Those who contribute regularly and actively have most likely enough things to do, to also constantly worry about keeping the guides up to date and verify the compatibility of every third party library. As the project grows over the years, adding more and more components, functionality, transports and so on, it's getting harder and harder to keep an eye on everything. I guess that's where we all have to accept responsibility to point out wrong, outdated or ambiguous information to help and improve MySensors.

In this sense, I think it is very helpful to get critical feedback from someone who is just starting out and has a technical background. You have a totally different perspective than someone who is completely new to it and also to the regulars. The former lack the expertise to identify and then express their problems when they hit a roadblock, while the latter may take specific things for granted and just know where they get their information from.

I just had a closer look at the wiring guide - which is part of the third problem you mentioned - and noted that there is indeed room for improvement in some places. Things which I've never noticed before because I didn't feel like I needed more information. But on second thought, yeah, that's because I've been through this before and gained knowledge along the way I now take for granted. For example, while the guide does recommend to use capacitors, it may not be communicated prominently enough - especially considering, that a lot of NRF24 troubleshooting threads in this forum seem to be caused by noisy signals / missing caps. On top of that, a list of (dis-)advantages for every radio type (range, reliability, power consumption, frequency, ...) might be a good addition to give beginners an idea what they should choose, because the radio introduction doesn't elaborate on this topic either. Maybe also a list of NRF24 modules which are known to be less troublesome than the common black one might be helpful.

I don't see the pin-to-pin wiring diagrams between Arduino and radio as a problem though. I always perceived MySensors as a beginner friendly platform and as such I understand why it is shown like that. It's the basics. You don't need more to get started, but of course, when you dig deeper and your expectation rise (or are high from the beginning), there's much more to it and you start wondering where to go from there, how to improve the signal quality, etc. Maybe there's room for an "advanced follow-up" to the basic guide, which goes into more detail.

As a personal consequence, I'm happy to take a closer look at any guide I'm familiar with and try to figure out if and how they can be improved. But I honestly don't expect to find a ton - without the intention to downplay your personal experience, I don't think it is representative for the majority of users - because the guides are generally in a good state already.

Let's not forget that MySensors has hugely lowered the entry barrier to IoT and home automation for countless people, which wouldn't be possible without the extensive contributions from the devs and every community member, who is actively helping. I invite you to participate and help to improve the project as a whole. Your input is very welcome.

---

Another general idea I just had is to add some kind of "I just made this and it worked / I tried to make it and it didn't work [because,... (optional questionaire)]" on every guide / article to get a feedback about its current state.

[bjacobse]

@alex28 As your critics reads for me as constructive feedback, then I will suggest for you to enable you to get a positive experience (I have been around Mysensors since May 2015) I use it with Domoticz as this is what I like
Anyway start with simple things, I have my Domoticz on a RPI attached to the serial gateway, it's simple and reliable and "easy" to debug

Make sure the gateway is working on your home automation, and then proceed to make 1 simple windows sensor
https://www.mysensors.org/build/binary

And then you can make additional sensors to your network. Please note that Domoticz is the controller, and hence it's Domoticz that will allow a sensor/node to be "added" to your network. The serial gateway is not having anything to do with "adding" nodes to your network, it's just a "dum" gateway moving data from the sensors to your homeautomations

Any other Homeautomation than Domoticz is equally good, if they have Mysensors support

To make your start easy:

• Don't use ENC28J60 to make a gateway
• Make a serial gateway
  https://www.mysensors.org/build/serial_gateway
• Don't spend too much time on NRF24L01+ as MANY of those are counterfeit China-shit, and you can debug for hours not understanding why your setup isn't working. Replace NRF24L01+ immediately if it ain't working
• Verify that your NRF24L01+ are in good working condition, before using them (if possible). Do you have a friend that have a some known good working NRF24L01+, then borrow a few pieces
• ALWAYS use a capacitor as close as possible to your NRF24L01+ radio modules voltage supply/GND
  https://www.mysensors.org/build/connect_radio#connecting-a-decoupling-capacitor

And then I'm quite sure the Mysensors-community would like if you can support to update the documentation to become better for the next new persons that would like to start using Mysensors, so the frustration that have been around your start can be reduced for the future

[mhkid]

@BearWithBeard I think the frustration is more that the information is out of date in many areas or leaves it open to people repeating the same thing that others have already solved. The antenna is always a problem. Maybe a prominent guide/recommendation on how to avoid buying counterfeits. A better FAQ on the common errors with communication messages and top solutions. Much of the information is there, I think it could be curated better. However it's hard to find sometimes in the forum because information is conflicting because people have different experiences because of different setup.

A one recommended path for beginners would be much more helpful. Meaning use specific hardware: gateway, antennae, nodes and whatever else and you're likely to have success. Part of the frustration is using something you have on hand only to find out after you built things out it has some other known problem or limitation that if known up front you would have avoided. The battery nodes for some reason took me a while to figure out. Then I bought 3.3v pro minis to only realize as I built some of the simpler sensors out they needed to be 5v (like motion) and they either run on more batteries or had to be plugged in, which defeated my purpose for a remote sensor. I'm sure you'll say but all that info is there. It is in some cases but you spend hours trying to find it in the forum.

I too have a software engineering background so I'm not a technical novice. I enjoy this as a hobby but because of ease of use I've started to not use the platform. If there were a known path to success that was documented that way I'd come back in a minute. I have no doubt there is a setup and hardware config (including where to buy from) that works nearly all the time it just isn't clear to me what that is.

Please take as constructive. I'd love to see MySensors adopted by even more people because I think it really is a platform that could be good for way more people.

[alex28]

Hi, thanks a lot for all your replies. I really appreciate that my post wasn't just taken as a rant from a disgruntled new user, but as constructive criticism from a different perspective.

I'd like to address some points made. Please keep in mind that all this is from my own personal experience. I can't claim that it's universal, but just some subjective observations from one guy who tried MySensors. That said -

@BearWithBeard I have to respectfully disagree about the guides being generally fine. Yes, they are nicely written and well presented. They're very inviting for new users. That's important and sets MySensors apart from many other open projects which often look very unwelcoming to new users with very steep learning curves. Having been involved in a few FOSS projects, god knows I have been guilty of that myself. The problem with the guides is the information contained in them. It's outdated and misleading.

From what I could gather on the forums and also from replies here (as the one from bjacobse), is that there are a number of best practices to follow with a MySensors project. And you have to follow them closely. If you don't, you will inevitably run into problems. Don't use the ENC28J60 network chip, it won't work. Don't use the NRF24L01+ if you want a reliable connection. Use external voltage regulators. OK that's all fair. But while these practices seem to be very well known by the community, even taken for granted, they are not documented for new users. In fact, the very guides written to draw new users to the platform will actively encourage bad practices - by presenting them as perfectly valid options.

Yes the information is out there somewhere. But it's often hard to find, spread out and riddled with confusing and conflicting (and sometimes plain wrong) info, sidetracking you.

I'm also not that sure if my choice of hardware is so unusual. Maybe people selecting such HW will simply never show up on your radar, because they give up early on due to all the problems they run into.

For the network chip, yeah, it's not widely used on Arduino. Yet the ENC28J60 is not uncommon for giving RPi Zeros an ethernet port. Like most of these cheap Chinese modules they're usually sold in packs, so probably more than one newcomer to MySensors will have such a module lying around in a drawer somewhere. Especially if he comes from the RPi community. Your starting guides make it sound like this module is a perfectly fine choice. You just have to install these libs that MySensors specifically modified for it (but they were never updated and don't work with the new AVR stuff anymore), and you're good to go ! Well no. And then later on, after hours of frustration, you find a forum thread where mods openly say that the ENC is unstable, untested and should be avoided, then reading the guide sounds almost cynical to me. If something is known not to work for years, then remove it as an option from the newbie guides. Having only one single network chip class supported (the w5x00 line) is perfectly fine. Just don't mislead people into using unsupported HW.

The NRF24 situation is similar. I understand that historically this was the only supported radio. I also understand that it is again unwritten community knowledge that mostly due to the market being submerged by barely functional Chinese clones, there's a good chance the performance with this module will be abysmal. And also that the RFM69(HW) is a much better and more stable choice for many use cases. Yet, this is not mentioned anywhere in the newbie guides. The NRF24 is still presented as the primary and default choice of a radio. With an image of a cheapo Chinese clone module right next to it. I think your idea of adding the pros and cons of each radio would be tremendously helpful when starting out. Had I known the issues with the NRF clones, I would have either ordered a better nRF based module (like the one from Sparkfun) or something RFM69 based, before even starting. And this would have saved me from a big disappointment later on.

Also, please don't underestimate the number of users coming to MySensors from the RPi communities. A lot of DYI home automation people use controllers like Domoticz, Home Assistant or similar running on a Pi. I'm sure that many of your own established community members also do. It only makes sense for many to install the MySensors gateway directly on their Pi. And that's where people will inevitably run into issues like I mentioned in my OP. If you browse the forums from these communities, when people ask about creating their own IoT devices, they will more often than not be pointed to the ESP8266 / NodeCMU stuff running on Wifi. With the result that all their DIY IoT devices are directly connected to a public IP network, with all the fun and not so fun consequences this can have. MySensors would be a perfect and safe alternative here. But I can't stress this enough from my personal experience, having the newbie guides be up to date, working and promoting best practices is absolutely primordial here. They're the first contact people will have with MySensors. And not everybody will have the persistence to keep going through the rough to try to make it work. Many will probably just give up and turn to things like the ESP.

@bjacobse, I appreciate your comments and advise. I have a running ethernet GW at this point, albeit with very unreliable radio link. A serial GW was not an option due to the way my current HA infrastructure is laid out, which is an entirely Ethernet based internal IoT subnet. Your comments about best practices with the ENC and the NRF are spot on and should be made more clear to newcomers.

Again, please don't see this as a direct attack on the MySensors project. I think it's a great idea and a lot of awesome work has been put into it. But communication is really important for new users. And please also think about the type of user who is 'only' looking for a working and stable base platform he can build sensors on. For these type of users a known stable setup, both HW and SW wise, should be recommended in my opinion. Along with best practices and pros and cons for HW with valid options (like the radios).

[Sergio Rius]

@alex28 In my opinion you are presenting fair points.

[GaryStofer]

@alex28 Hi Alex, sorry for your frustration.

I think documentation, either incomplete or outdated, is the crux of most open source projects.

I can not speak to the Hardware you used to try to get a network up as I have stuck to the more simple approach of using the simple Arduino ( ATmel328P) nodes for both sensors, repeaters and gateways, while using a RPI as the network controller with something like Domoticz running on it. I started years ago , even before the RFM069 was an option and made PCBs that incorporate the NRF24 and the ATMEL 328P along with the necessary voltage regulators etc. Maybe it was easier to get started then because there where less options and less misleading documentation was available, but I don't recall running into any problems worthwhile of mentioning or having the level of frustrations you have encountered.

I have two sites running with 8 and 12 nodes each. All sensors running on batteries. The range of the NRF24 is limited in that I only get through one or two sheet rock walls inside the house, but using the NRF24 module with the built in PA/LNA on the gateway and one repeater opened up the range considerably. I'm fairly positive that all the NRF modules I have a re clones....

I use the serial gateway on the Atmel328p and connect that directly to the serial port of the Rpi Zero-W, without USB adapters then run Domoticz on the PI to get onto the internet .

If you look on OSH - PCB you will find many good PCBs that you can make MYsensors nodes with using the more simple Arduino platform.

Most of my frustrations stemmed from the Linux configuration for the RPI so that it doesn't clobber the SD card on surprise power failure.

Cheers -- Gary

[pptacek]

I'm an experienced embedded developer and I spent weeks tinkering with various things around MySensors. Here are my 2 cents to anybody who wants to start quickly and painlessly.

1. Do not bother with anything but Arduino, nano is especially simple to use due to the built-in USB. I personally prefer pro minis due to the form factor. Do NOT bother with Raspberry Pi, it is too much work to get something done unless you have pre-build images you can just dd on your SD card.
2. Please, if you are starting with Arduino and stuff, USE some shield for your radio module. Order some Nano RF24 shield like this one https://www.amazon.com/Emakefun-Terminal-Expansion-ATMEGA328P-Interface/dp/B07N8PLFVC to avoid self-wiring. nRF24 4x2 header is idiotic and it is easy to make frustrating mistakes, have loose wires, miss a capacitor, have a weak voltage regulator, etc.
3. A serial gateway with a nano on a shield can be put together in 5 minutes. You just stack things up, make sure you CE and CS pins are right and upload a sketch. You are done.
4. nRF24 is a radio on 2.4GHz. Let it sink for a bit. Almost everything wireless (and microwaves) in your house runs on that frequency. Do yourself a favor, run a simple wifi scan on your phone and see which part of the band is messed up and which is available. It is simple to do today with free Android and Apple apps.
5. Watch your signal strength! What do you do when you start dropping packets? Put both modules closer and bump signal UP right? WRONG! That will make it worse and you will go down the spiral trying to figure out why your nRF24 radio is total crap. Closer you get, weaker signal you need. Seriously. If you will be operating the same room, set a signal to LOW. When you will go over one wall, set it to HIGH. I'm using nrf24l01+pa+lna modules (one with antenna) between house and garden, three walls in between, 50 yards, and on LOW I have 100% reliable connection, no dropped packets.

As of now, I'm using these battery-powered stacks (nrf24l01+pa+lna & jModule2 & pro mini 3.3V) around the backyard and I'm happy camper:

[mbj]

I started with a small MySensors project more than 4 years ago and life was easy then The choices were few and I felt they were well documented.

I began with an Ethernet gateway but moved to MQTT (ESP8266 because of WiFi) once it was available. The choice of radio was easy and even if there were problems most could be solved. I still run 10 - 15 items using NRF over MQTT to OpenHab and also have quite a few Z-wave items connected to this system.

Today there are heaps of choices and the development continues but my feeling is that MySensors is still mainly driven by a small community of enthusiasts working on this on their very limited free time. As more and more functions/variations are added the complexity grows and the need for correct documentation increases exponentially but the resources are not at all growing in same pace.

I have some experience with using much larger projects (OpenHab, ArduPilot, PX4 etc.) and and also here documentation often is a mixture of updated and outdated info. Many times the forums are where the correct answers can be found but very often there are many erroneous answers per one correct one.

For a project like MySensors I am convinced that the only way to go is to select an entry level configuration with few well working choices which are always kept alive and up to date.

As users become more and more experienced they will have come across a lot of useful info as well as have learnt how to find more. Hopefully some find documentation so important that they are willing to contribute also.

For the advanced stuff of course there should be an ambition to document it well and keep it actual but why not accept this as playground for the advanced users who know enough to find the answers as well as are able to assist others.

Last but not least. We always get what we pay for, don't we To keep a full blown MySensors activity well documented will cost a fortune and require very up scaled resources.

Cheers
Mats

[mhkid]

@alex28 I agree exactly with what you've said. I've spent hours with MySensors and the website and community kept me here for a long time. Would love to just see the quickest path to success. I would have never messed around with a rpi to do this if I would have known the troubles I would run into.

[Jens Jensen]

FWIW,
on a more specific tweak, one of the things I struggled with for a while was why the mysensors defaults for RF24 transport use tx power level RF24_PA_HIGH (-6 dBm) by default instead of RF24_PA_MAX (0 dBm)

I wound up setting:
#define MY_RF24_PA_LEVEL (RF24_PA_MAX)
in all my sketches, as it seems to make the difference for those several walls and/or extra few meters of range.

(Not sure why the -6 dBm setting was chosen?)

[mickecarlsson]

I started with MySensors, Pro Mini and NRF24. I had tons of problems. I borrowed from work our WiFi scanner equipment and checked the 2.4 GHz. It was a total mess. Our DECT-phone almost killed the channel that was used for MySensors. And I discovered, as many has, the NRF24 was all counterfeit.
So, i trashed all NRF24 and moved to RFM69. That was nearly three years ago. My gateway is a Raspberry Pi.
My controller is Domoticz.
Conclusion, and a note to all MySensors users out there. Move away from NRF24 and go with RFM69, you will never look back.

[sundberg84]

Or you can do both (RFM/NRF), which is another positive thing about Mysensors. I have also noticed how dependent NRF is on other traffic. I sometimes lose some nodes during high peak wifi hours, but only the nodes that are on "the edge" of their coverage range. So - its quite easy and cheap to build another RFM gateway, dont have to throw the NRF gateway since I have alot of indoor nodes working with that one. The garden nodes and some basement nodes are running RFM protocol - and that is a big upside with MySensors in my world.

How i see this thread is that MySensors team or any other interested and dedicated person needs to make this clearer and maybe in some newbie guide or on the main homepage start this discussion/ state this information. In this way we can avoid all these things... For example changing the chapter "Radio" in https://www.mysensors.org/about/components so it not only shows the NRF module but also other options, and also have this "common issues" stated.

[BearWithBeard]

I agree with @sundberg84. Let's just make clear that none of this implies that MySensors is fundamentally flawed. My understanding is that the criticism / objection is solely directed at the documentation and how it is presented for new users. If I may try to summarize the consensus in this topic so far:

• Having a proper documentation is very important.
• MySensors used to be simple and straight forward to setup, because options were few.
• The ever-increasing feature set makes it harder for new users to find out which components might be the best choice for their use case ...
• ... and some of the options or their documentations are currently outdated, deprecated or insufficiently tested. They should at least be labeled as such.
• If you are new to a project and follow an introductory guide, the expectation is that you can succeed without seeking information in additional sources ...
• ... or else new users who run into problems may quit in silence and one may never find out, if there is an issue with the documentation.
• There is a desire for a simple step-by-step guide with a "core" set of hardware (and software), both for beginners and people who are simply looking for a stable, reliable setup without hours of fiddling, debugging, searching and swapping components.
• NRF24 might be widely adopted in other Arduino-related projects and the "go-to" radio in MySensors for historical reasons, but many are seemingly frustrated by its comparatively poor range and stability, so RFM69 may be pushed more ...
• ... and there is a lack of explanation, which transport method new users should pick up. A list of pros and cons may be helpful.

Honestly, I think one of the greatest features of MySensors is the fact, that you have tons of options to build your network with. Whether you decide to use Arduinos or other beginner friendy dev boards and premade modules, bare AVRs, ESPs, ARM or NRF5x chips and design your own boards, 2.4 GHz, sub-GHz or wired, lots of controllers to choose from... but I see how this variety can cause problems if they're not well documented, because every component has a different set of quirks and requirements.

Propably the best way so far to get issues related to the guides fixed right away, would be to comment on a guide directly, for example Building a Raspberry Pi Gateway, and mention the problem in there. Suggestions to improve the overall guide could also be discussed in there and a staff member could update it in a timely manner.

But I agree that the process for new users could be more streamlined. Maybe we should collect some ideas how this situation could be improved?

Short term:

• Compile a list of guides which contain outdated or otherwise flawed information. Mark the respective sections as such with a note in a colored box for the time being, if they can't be fixed / reviewed right away.
• Colored boxes may be used in general for asides / cross-references, to emphasize important bits or refer to related information.
• Explain the differences and (dis-)advantages of every available transport method in a separate article: "How to choose the right transport method"
• Add a "Build your first MySensors network step by step" guide in the Getting Started section, which focuses on a single set of hard- and software. The user may learn how to configure and connect to a controller, sending and receiving messages, using two Arduinos with USB interface (Uno, Nano) and NRF24 radios - one Arduino as a serial gateway, attached to a computer running Home Assistant and the other one as a node with a simple button and a relay attached to it. (The selected hardware should just serve as an example here.)

Mid / long term:

• Review all guides. Best practices need to be added and / or mentioned more prominently. Test if the components are still supported; fix or remove them.
• Add feedback buttons to every page like "I made this" and "Didn't work for me". Clicking the latter could open a modal and ask for the users input (without registration). It could also serve as a public popularity indicator (besides analytics, I guess).
• Users currently have to choose between each a bunch of 1) controllers, 2) gateway hardware options, 3) ways to connect to the controller, 4) ways to connect nodes and 5) microcontrollers for the nodes and we may want to find a way to suggest different paths which are known to work well together, for users with different levels of expertise or different needs. Possibly by adding additional step-by-step walkthroughs as mentioned above. One that focuses on simplicity, one on flexiblity, or range, low cost, fully wired,...
• Or implement some sort of configurator where the user can select components or features they want to use and the system suggests which hardware / software would be a good fit by internally weighing them.
• Maybe turn the currently solely staff-curated pages into some kind of Wiki format or GitHub repo, where everyone can participate and submit changes (moderated, of course).

Thoughts? Other ideas?

Of course, I don't expect the devs and mods to do all the work. Everyone who has the time and expertise to contribute is invited to help out if any of this is welcome.

---

@Jens-Jensen The other wireless transports aren't configured for max TX power either. I guess they are set a little bit conservative to work with a wider variety of hardware and power sources out of the box. I don't have actual numbers for common NRF24 modules at hand right now, but there are modules like the CDEbyte E01-2G4M27D which can draw up to half an amp with RF24_PA_MAX. RFM69 radios draw about 30 mA during TX with the default +10 dBm setting, about 45 mA with +13 dBm (max. for modules without PA) and > 130 mA at +20 dBm (PA). I think this approach is fine, but I agree that this setting could be documented better (Is it even? Can't find it outside of example sketches and apidocs right now).

About NRF24 range in general: I have a gateway and a repeater with PA-LNA modules with RF24_PA_MAX in our house (reinforced pumice stone walls and concrete ceilings) and cover all four floors and even some places in the garden with them. None of my sensor nodes need to go above RF24_PA_HIGH, many work fine with RF24_PA_LOW, increasing the battery life, which is especially nice for nodes running off CR2032 coin cells. But I understand that RFM69 might be the better choice for a sensor network and it should be considered to push it more or even make it the default / recommended radio for MySensors in the future, even though they might be harder to use for beginners.

[rejoe2]

Starting with MySensors in the 2.0.0-beta days with nRF24 (and no technical or IT educational background), I completely agree with a lot of the things already mentionned here.
It was a lot easier then and most of the transceivers (even the most likely couterfeied ones) worked with some caps added. But I saw a lot of people struggling when trying out themselfes, be it counterfied chips, struggling with what the controller sw (FHEM in my case) does or (often) - using the Arduino framework to get combined nodes.
So I started doing some wiki work with focus on FHEM (MySensors Starter Guide), collecting also the experience from some other users there.

As atm some new users became interested especially in wired solutions, I was very happy to see the PJON integration making good progress. Imo this is a very good and easy approach, as no additional hardware is required. This makes this transport layer imo the best choice to get into the basics on MySensors and it's interaction with the controller sw as well. Choice for controller in most cases might already been done when joining the community here, so imo this could really help to "join this train here" more easy, as testing doesn't need much wiring or additional hardware.

The only disadvantage is the lack of RF. So starting with PJON as "learning level transport layer" and adding then RFMxx als wireless option might be considered as primary recommendation for the first steps towards wireless then?

[scalz]

Hi there,

so far the main "culprits" I identified are:

• add a picture of a genuine nrf24 module (eg cdebyte) near the cheapo nrf24, and why not a rfm69/95 module too, in the Getting Started/Component/Radio
• add a comparison of pros/cons of nrf24 vs rfm69 in Build/Connect radio, before the wirings
• remove en28j60 from doc, and keeps only w5x00. Let the community handle en28j60 if this is really needed. I don't think anyone in the team is using en28j60 for gw. The fact it's not uncommon in rpi community, doesn't mean it's common in mysensors community (more based on arduino than rpi)
• update store links and try to remove cheapo nrf24 clones
• rpi section

else I don't see so many outdated infos.

Regarding howto connect a controller to mysensors, I've no idea if this should be on mainsite. As controller choice is very subjective. For example, I've already tried Openhab and others, even HomeAssistant for months too (imho having to configure yaml etc is not noob friendly, I couldn't recommend that to noobs and non-computer people, same for nodered as automations tool ) and I still prefer Jeedom..

Other notes:

• it's hard for the team to support and guarantee what we do not use.. regarding all the options available in MySensors (gw, hw platforms..). Example: I'm not sure, but I think rpi as gw is not widely used in the team for example.
• a reproducible howto get started, with 100% success, would be nice sure.
  Still it's important to remember that will always need to learn new skills in mid-longterm. Not because you're a dev, that you know electronics, rf recommendations, the framework etc
  It's hard to follow and compile all forums infos in one place, with limited resources. This would need a book!
• I'm also in favor of subghz but I can understand it's maybe less plug&play for noobs. I also think when you want to get started, it's easier to get success with Serial GW.

[Sergio Rius]

@scalz After the "cleaning" there should be an example on each supported endpoint platform. I mean, if rj45+mqtt is supported, rfm should have a working example with all the components (level adjusters, etc...)

The big problem with rf24, said that it's so dependant on the environment, is that different countries have different regulations. And could be that what seems perfectly ok for some or all developers, doesn't work for other people in their houses.

Documentation doesn't say anything about checking country's wireless regulations as it's neglected.

[scalz]

@Sergio-Rius
sure these are good points. especially country regulations
That said this needs some research, personally I don't know rules for all countries & frequencies.
In that case, we should also mention that anyone making&selling his board/device with a rf module is maybe out of the rules without fcc/ce certifications. So many things to say on regulations, you're right.

The trickier point is docs for all possible usecases. There are so many different combo. I don't know if educating and covering "all" electronics possibilities, arduino coding, handling third parties libs etc, is the goal of a software framework here, I don't know exactly the original goals.

"If I was in charge and alone for all this work" (personal point of view), I would remove from howtos all things that I don't use, and would let this stuff live in the community hands, on the forum for example.
Like I said, supporting/maintaining/documenting stuff that you don't use, for free, in spare time, is pita.
Franlky, there are many platforms+mysensors that we don't even use. It has been added to the framework, mostly because it's fun to learn/discover new platforms etc, not because of an urgent need at home.

The problem is the more you show&provide, the more users may want and expect, whereas we hope it will be community driven.
It's like you provide for free young plants to someone, and he expects you'll always feed&water it

Unfortunately, regarding documenting the stuff I don't use, I've no time for the moment..busy on other projects, hobby in my spare time must be fun.

I hope we'll find a way to improve docs so it's 100% success each time someone new get started. Hopefully I think there are lot of people who already got success with MySensors and helping on the forum

[monte]

@alex28 said in Started with MySensors and about to give up (some feedback):

Problem 2. The Raspberry Pi gateway.

Yes you need to add overlay to /boot/config.txt to use both SPIs. I have working gateway which utilizes both SPI ports and works without issue.
So have you achieved working GW on raspberry?

@alex28 said in Started with MySensors and about to give up (some feedback):

Problem 3. NRF24 range is bad. Really bad.

I am using this NRF24 PA LNA module on my gateway and the cheapest NRF24 modules on my nodes. This works pretty good. I suggest you buy some good quality PA LNA module for your gateway as they require proper shielding and the cheap ones don't have it. CDEBYTE modules are considered to have original Nordic chips and has many good reviews on this forum. And yes, you need to ensure you have good power supplied to radios. Also 2.4GHz can be easily blocked by concrete or metal obstacles if it is placed closed to them, for example I have outdoor light node with concrete base, and I had to stick radio module above concrete part to achieve stable connection, same goes for metal enclosures and boxes. My GW is places in metal distribution box, so I mounted external antenna on its door to avoid shielding of a signal.

I understand your frustration, but you've chosen not the easiest or common way to begin with. Most people on this forum use standalone serial or ethernet gateway and don't bother connecting radio directly to Raspberry, that's why you had such a bad time finding correct answers to your problems. Good thing is that you seem to be close to a working result and have gain much experience and can make valuable contribution to this community.

Radio networks are flawed by design in my opinion, I've had hard time with commercial Zwave products, and community support wasn't great either, as that is proprietary protocol and you basically rely solely on manufacturer once you've bought a node for 50$ you almost on your own.

[mhkid]

@monte this is exactly the point. There is no mention or way to know you're choosing the hardest possible combo of hardware until you've spent hours fiddling with it. You'll find more posts about counterfeit radios rather than what a good radio is. There is saying that they don't teach treasury agents what every counterfeit bill looks like because there are too many and it's always changing. They teach them what a real bill looks like so they will know a fake when they see it. Same thing here. Just post the place to buy a good radio. Don't post a guide on rpi gw if it's the hardest and least used option, leave that to the forum.

I would rather spend my time building and using the sensors rather than troubleshooting and figuring out problems, which it seems like that's what I do a lot of. It could very well be the choices of hardware I'm making I'll completely admit that but I don't know because there are so many paths you can take. OTA updates are something I'd like to incorporate but there is no clear path to success there for me. I feel like that will lead to frustration based on what I've read in the forum. Again because there are too many options without the clear path laid out.

I keep coming back because I really see the potential and there really is no other platform like MySensors. If I had that strong reliable baseline to build from I'd have some pretty cool ideas and sensors to contribute.
Instead I'm building sensors with Wi-Fi connections all over the place when a single gw connecting to the internet or a controller would be a much better solution.

[mhkid]

@pptacek said in Started with MySensors and about to give up (some feedback):

jModule2

Do you have details on these sticks? What is jmodule2?

[monte]

@mhkid Well, I think tutorials must be updated and graded in terms of difficulty, that will ensure that newcomers will first build serial node based on arduino nano and only after having working network will try harder solutions.
That said, I believe that troubleshooting is the best way to learn new topic. Especially if you have helping community to come for an answer when you feel like you've come to a dead end.

[alex28]

@monte mhkid summed it up nicely. My entire point here was that there was no way to know that my choice of hardware was uncommon. The guide made it sound like this would be a perfectly valid and well supported choice. Yes, I have a functioning Pi based GW now, but the radio link is far too unreliable to make it useful. After considering all pros and cons, I decided to not proceed with MySensors at this point. The lockdown is over and I now have much less time to put into this. Instead I will try the Z-Uno, which seems more in line with my specific use case.

Still, I'm glad my feedback has spawned some discussion around this. Maybe it will help to improve MySensors in that respect. Maybe I'll come back to MySensors at some point too, because it is an interesting platform after all.

@monte said in Started with MySensors and about to give up (some feedback):

That said, I believe that troubleshooting is the best way to learn new topic. Especially if you have helping community to come for an answer when you feel like you've come to a dead end.

Well that depends. Stupid analogy : If you're a photographer and get a new camera, a nice customizable one that gives you lots of manual options to play around with, you would still expect it to work out of the box for simply taking some basic photos. If you have to take it apart entirely and start swapping out its internal components using trial and error, just to be able to use it for the one thing you ultimately got it for - taking photos - then you'd probably not be very happy.

[kiesel]

I hope it is OK to post this here, I am not sure how to add this to the documentation, but my biggest pain point when starting out was that you have to use mysensors >2.2 when running on a raspberry pi 4, but the rfm gateway code has a bug in versions bigger than 2.2. I spent more than a week debugging that until I found the github issue and settled for a serial gateway, which I am very happy with, thank you mysensors!

If a warning could be put on the gateway page that would be great!

[scalz]

Hello,
@mhkid @alex28
That's too bad that you never asked for help (except mhkid, one time) while you were so many times in a dead end.. some waste of time, I completely agree with you. Don't be shy
Actually I'm a dev too, high or low or blackbelt level doesn't matter, but what I know very well is that I like to fix problems by myself, I rarely ask for help too. But the truth is when someone can save me some time, my precious spare time, I'm always very glad to find him.

@alex28 that's good to hear that perhaps you found another framework which can fit your need. I really hope and wish you success, especially if it costs 50€ per devboard.

This is quite interesting actually, now I wonder about something..

To people:
if we would sell boards for 50€, eg on mainsite "Store" page, with MySensors howtos and high success rate, would you really buy it?
or would you still try to use what you have left in your drawers?

If so, it's maybe possible to make your dream become true.
Of course, high rate of success would only apply to these kits

Note: to any newcomer reading this topic, regarding the "don't know where to buy genuine nrf24", you can find links on mainsite, "Store page", for some recommended modules. And don't forget those decoupling capacitors

[alex28]

@scalz said in Started with MySensors and about to give up (some feedback):

That's too bad that you never asked for help (except mhkid, one time) while you were so many times in a dead end.. some waste of time, I completely agree with you. Don't be shy

That's a personality thing. Documentation is very important to me. When I encounter a technical problem, on personal projects or on work projects alike, I will do extensive research in order to assess, understand the cause and eventually solve the problem. I will very rarely post a technical question on a forum. That's just the way I work. Then again, I did mention that this was purely a personal experience report Different people have different approaches and will have different experiences.

@scalz said in Started with MySensors and about to give up (some feedback):

@alex28 that's good to hear that perhaps you found another framework which can fit your need. I really hope and wish you success, especially if it costs 50€ per devboard.

Thanks. You pay mostly the proprietary ASIC on it, the ZWave license/brand, but also compliance with pretty strict performance specifications on the HF/radio side. Let's see how it goes.

In fact, the cheaper component price was not the reason that made me consider MySensors in the first place. The open nature of the platform was. I'm perfectly fine with paying more for solid and reliable hardware. I think that is also an important point to keep in mind. As far as I see it, this open and community driven aspect is the greatest strength of MySensors. While the cheap component aspect is certainly important for many people, it can also lead to a lot of problems due to counterfeit low quality HW.

[mhkid]

@scalz not sure how to take the comment. I've posted and contributed (even developing a library) so it's not like I haven't participated. I bought parts from the links and still had issues with radios. Whether help was asked for or not that doesn't make the constructive feedback invalid. Feedback is a gift and in this case it should be taken that way. These are suggestions to make MySenors accessible to more people.

Yeah there is a good chance I would buy it. When I started my journey into home iot devices I was buying $45 light switches so if it was a good product I would.
I've looked at the MySensors gw but several of the comments mentioned issues so l steered clear. It's not the cost. What's being suggested here is not a huge criticism it's just asking to have a clear path to a high probability of success. Which is mainly cleaning up the documentation. If I had a solid working setup I'd help do it but I don't. I love the platform and the idea is really great, it's just too scattered and needs to be more focused. Don't try to be all things to all people.

[scalz]

@alex28 @mhkid
I just meant what I thought.
I like to find solution by myself too. Like you it's super rare that I ask for help. But, I'm also an impatient guy, very impatient, I hate being stuck during a rush etc. I always feel getting stuck more than one day is like wasting time and money, don't you think. Still it happened more than once to me, of course. That's funny I'm saying that, as I actually I'm working in research field

This is why I said you shouldn't have hesitated to ask community for help, lot of kind people here.

@alex28 said in Started with MySensors and about to give up (some feedback):

In fact, the cheaper component price was not the reason that made me consider MySensors in the first place. The open nature of the platform was. I'm perfectly fine with paying more for solid and reliable hardware. I think that is also an important point to keep in mind. As far as I see it, this open and community driven aspect is the greatest strength of MySensors. While the cheap component aspect is certainly important for many people, it can also lead to a lot of problems due to counterfeit low quality HW.

I completely agree, that's why I trusted in MySensors years ago.
And supporting low quality, and too many platform, is pita, especially when you just have very little spare time, all of that for free of course. That's why we trust in community to help us.

About my own xp, I got success the first time I got started with MySensors+rf24Serial gw.
But it was just a quick test, as my first goal was to use rfm69. No one told me rfm69 was superior to rf24, to me it just made sense.

I'm in favor of serial gw actually because I think it's :

• more "simple"
• secure. Just a serial connection. no tcp connection etc
• reliable. doesn't rely on an OS to run the network, and stronger against noise in radio which could be introduced by rpi for example, when power supply is not polished, filtered, decoupled etc. No one said that in the docs, I know, it's certainly missing infos. It's just, imo, from personal xp.

That said, we have heard your wish about improving docs, and providing hw with trusted howtos (we have some good hw designs, for gw or nodes, with variable bom cost).
Thank you for your feedbacks

[Psilin]

What an interesting thread this became. Over some time/years ago I tried to start with MySensors. Unfortunately I failed miserably because I tried it to combine with starting with Openhab, and connect mysensors by mqtt.

The Openhab route combined with Mysensors is still the route I want to go: combine the open architecture of Openhab to connect different vendor approaches added with the flexible way of MySensors.

To be complete: My background is a bachelor in Physics. So the basic programming and electronics may not be the real problem, although I am certainly not claiming to know everything.

To end up this post: in the next couple of weeks/months I have spare time to invest in the project. When I combine this with the things the topic starter ave addressed I have the following to offer to the Mysensors community:

“I am offering to write and give feedback of the guides and information found in the forum, to document at what point I am stuck with the given information. I hope the community can and will do something with this feedback. So long as I am not going to be completely stuck, I can and will be writing the feedback.”

Off coarse I need to know if the community is waiting for such an approach before I start to write.

My thoughts of devices to use in the network:

• mqtt gateway: wired based on cloned arduine with hat ethernet
• mqtt gateway based on wifi based esp8266 nodemcu board
• radio network: base the nrf24 version
• radio network: based on rfm69 for secure transmission (opening doors with nrf24 does not feel safe)
• repeaters as needed or extra gateways (3 story concrete house)
• sensors and actuators: starting with wallpowered, later adding battery powered

So, how does this approach sound to you all?

[wergeld]

@pptacek Had not seen those before. Order some and a few nanos to go with it. I had been using the slim node v2 AA battery boards using just the 328p bare chip. Issue I have with that board is the layout of the pins for my needs. It is a great board and I use the nodes I have a lot - no disrespect meant to the developer of it.

I agree that the entry ramp to get mysensors working is a bit complex. I started with the RPi as the gateway because well, it should work. Had a hell of a time making it function. Ended up getting the RPi hat that has the capacitor and NRF slot on it that plugs into the GPIO headers. But, issues persisted with the library for the RPi not working on the RPi 2 until some very helpful folks pointed me in the right direction. A lot of this is pure tinkering and not yet a prime time off the shelf system. I knew that going in and accepted. It has been a great learning experience. The frustration I initially had was all because I expected the guides/docs to be up to date. They are not. As bad as that is, once you accept it and decided to a) add to the docs yourself or b) carry on screaming it becomes rewarding. As an example, getting MySensors to work in Hom Assistant is easy using an MQTT gateway....until you realize that HA tells the nodes what measurment units to use and the nodes then flip (from Celsius to Fahrenheit) when you think it should do the conversion on the front end of HA. I still, for the life of me cannot get the nodes to flip back to Celsius from an MQTT command (had to reflash the nodes with the code).

At the end of all this I am still having fun and learning new things. As the OP said this is not my first programming rodeo (currently a senior SQL developer working with epic sized data with a massive helping of javascript, R, python, and .NET). The micro controller code paradigm was (is still?) new to me even after almost 6 years of messing around with various projects including MySensors.

If we can help any new people stay on this journey it is time well spent. I offer my services for any help that may be needed for docs or guides.

[monte]

@Psilin I suggest you look into Home Assistant instead of OpenHAB. It is much more flexible and easy to set up and I feel like it has better perspective in general.

[alowhum]

I'm far from objective since I'm behind the project, but I think the easiest way to get started with MySensors is to use Candle. I've given a lot or workshops with it now, and it's getting to be quite good.

• It uses Mozilla's WebThings Gateway, which is much more userfriendly than the other smart home controllers.
• It offers voice control for all mysensors abilities.
• The Candle Manager plugin allows you to upload code to Arduino's through a step by step wizard. It even allows you to make changes to the code in a wysiwyg manner. No need to install the Arduino IDE.

Perhaps the guide could point to it as an option for absolute beginners?

[Psilin]

@monte @alowhum : the choice I made for OpenHab was based on the open structure which allows connecting different vendor devices by the development of a glue layer, called bindings. A large pre for me is the support of my alarm system, so (in theory) I already have wired sensors that I can use at all my (external) doors and windows. I am really looking for a controller that will fit my needs, and grow with it.

I'm sure Home Assistant and/or Candle (never heard of it before) will also be fine for use with MySensors/MQTT. But is is like selecting a car: multiple vendors will bring you from A to B, most vendors will do the job at a decent speed and reliability. At the same time some people prefer a german car, other people prefer a French brand an so on. In a later post I will explain my selection of OpenHab more in depth.

@scalz @Yveaux @hek @kiesel You all 'voted' or 'liked' my post. So I guess this needs a decent follow up. At what place do you want me to document my struggles? In this thread, or a new thread ? And when a new thread has the advantage, please let me know in what section I should start it!

[Yveaux]

@Psilin we are currently discussing behind the scenes if/how we can let users edit the documentation pages. We'll come back to you as soon as things get more solid.

[alowhum]

Sounds great.

This all reminds me of this post I made when I started out with MySensors. That was about how a lot of the example code used out of date sensors.

[monte]

@Psilin I know about OpenHAB's bindings, I was going to build my system on it. But then I found HA and fell in love with it. HA has a huge number of integrations and you can always write your own too. But if you prefer java to python, then I can understand your choice.

[GaryStofer]

For people who like a clean PCB sensor or serial gateway node based on Atmel 328P for battery or 5-12V operation check out the PCB I made here on https://oshpark.com/shared_projects/5RV25Fc0. It incorporates the voltage regulators , capacitors and connector to simply plug in a NRF24 module and be done with it. Soldering is required but not terribly difficult. I usually just depopulate an Arduino nano for most of the parts ...

[pptacek]

@mhkid here you go: https://www.openhardware.io/view/332/jModule2

I honestly use it for much more than MySensors.
I made myself a little RC transmitter/receiver ecosystem out of the "3.3V Pro Mini + jModule2 + NRF24L01+(PA+LNA)" sandwich.
I have about 4 RC transmitters (mostly made of PS2 analog controller + above) and a bunch of RC receivers (DRV8833 + above) for little boats, cars, robots, or whatnot. If you buy these at bulk, they are under $10 with driver for two motors, you can program them in any way you want and kids can have a lot of fun. And if they break/drown/burn few, I can whip another 5 in a couple of hours.

IMHO 3.3V Pro Mini + jModule2 + NRF24L01+(PA+LNA) + DRV8833 + 2xAA or 1S LiPo battery is very powerful combination, completely customizable, tiny and cheap.
I might make an Instructable for it or something.

[mhkid]

I think all the replies highlight the challenges / difficulties with what happens. You read the thread and there are at least 3 or 4 different thoughts on each element (GW HW configuration, PCB recommendations, node recommendations, controllers, mqtt vs not, etc.) If you're coming to this for the first time you just see a bunch of what people have done and so you have to blindly pick a direction. Which then can lead you down a rabbit hole.

All of that discussion is great and this is what should happen in a forum is to share experiences. The problem, again, is that there is no baseline to start from that gives you the initial nearly guaranteed path to success when you're starting out. It that existed then you could tweak and adjust, try more advanced configurations, and experiment from a working baseline. Right now when you ask a question like what GW hardware should I use, you get multiple answers back and there is no consensus or "standard" to refer to. This thread has gotten way OT IMO because it's evolved into "here's what worked for me."

For me personally if I had the working baseline then I could add features on as I had the need or wanted to experiment. The challenge is you are experimenting from the start and then you get frustrated because you run into barriers all the time. There is no baseline and there are so many variants that it's a little chaotic. My suggestion is to come up with the baseline (hardware for GW, type of transport, ONE suggested controller) The KISS approach (Keep It Simple, Stupid) , publish it, and then clearly document other avenues as variants or advanced config. That at to me doesn't seem all that big of an update. The information is there as far as building and config just organize it and be more clear on the best path to success.

Again, MySensors is a great platform. I want to use it and promote it, just need to have that clear pathway.

[mhkid]

@pptacek Great, thank you.

[Psilin]

@mhkid perhaps make together a base line and help each other this way?

[mhkid]

@Psilin sounds good to me.

[franz-unix]

Interesting topic!
I agree, the amount of time required to learn how to do the things is quite high and after a lot of research you will find that other people have had the same issue... so in the end you have just reinvented the wheel!

In any case I think that MySensors is a very good project and probably underrated respect to how good and useful it is for a maker that wants to build its own domotic sensor and actuators.

For the reasons above (and others), some times ago I have started the d-diot project:

• The hub (Raspberry Pi + d-diot board) implements, among the other things, two MySensors gateway (RFM69 868 Mhz + NRF24L01). All the software configuration steps are well documented in the dedicated section of the wiki.

• In general the software part is easy because all is preconfigured in the d-diot image. Just burn the iso image to an SD card and you will have Home Assistant and MySensors working and ready to go.

• 3d printable sensors and actuators and the relative PCBs and firmware are part of the project. All parts (hardware, firmware, 3d printable case) are open source

• In the wiki you will find the detailed build instructions (with pictures) for each device, so @mhkid and @Psilin maybe here you can find some useful information or a at least a good starting point for your nodes. In particular the Mini-BT-Pcb-328P is a general purpose and flexible board that could be useful for a lot of small (battery or USB powered) RFM69 or NRF24L01 nodes.

Now I'm in contact with PCBway, a PCB manufacturer that offers also soldering service, so If there are enough people interested, I think that it is possible to start thinking about the possibility to start a small production of some boards, maybe already assembled. In my opinion this will be helpful for other people.

Let me know... maybe we can start something

[TRS-80]

@alex28,

Feedback from new people is valuable! New people have a different perspective than those who have been here a long time, and have grown with the platform (or watched it grow up around them). We should never forget that, all of us. Personally, when I am learning some new software or something for the first time, I always try to give my fresh perspective as a new user (assuming it is F/LOSS; I absolutely refuse to commit a single ounce of my time/energy/money otherwise), help to update docs, or whatever (as much as possible).

Having said that, this is a tinkering platform. On the bell curve of HA stuff, we are at the far right; the smallest number of people and most difficult, requiring the most knowledge (short of making things from absolute scratch). This is not off the shelf, ready to go stuff. This is building your own custom sensors from modules and components, nearly from scratch.

If there is one thing I think we (as a community) can do better, it would be to make this more clear up front.

I just looked at my profile page, it says I joined "23 Mar 2016." I'm pretty sure I started reading / studying even before that. But right from the beginning, I fell in deeply in love with what I saw, even if the vast majority of it was all way beyond me at that point.

Actually now that I think about it, I have had interest in HA stuff since our first X-10 modules I remember playing with as a child to turn on the outside Christmas lights, and the electric "candle" in the garage... I thought that was just the coolest thing ever!

Every so many years during my 20s and 30s, I would check back in on the HA situation again but it was always the same story: very over priced devices that could not talk to one another. Until I came across MySensors! We are actually living in wonderful times right now if you are a fledgling hacker; boatloads of information available on the Internet, inexpensive parts, and an explosion in Free / Libre Open Source Software (and increasingly, Hardware!).

Eventually I bought some parts, made a couple attempts, got some stuff working, but it was unreliable. I was in over my head. No time to spend on the stuff for months, years at a clip. But I kept reading, and reading...

I finally had my first real success with nRF24L01+ just a few days ago (I like to think I give some good tips in that post about initial radio setup and testing, which IMHO should be linked from the Troubleshooting post / page; I would also be happy to adapt to a wiki / doc page or whatever). It has been a very long road for me, but I kept coming back... and the success was very sweet when it finally came! And now I know how to build and maintain my very own custom sensors, and the sky is the limit!

By the way, I disagree with those who say nRF24L01+ are not worth it. But maybe I have just had good luck (now that I know how to test, position, etc.). Great, inexpensive little radios. I bought mine right off AliExpress, 2 x 10 pack of them IIRC...

One thing that kept me going in the meantime was having some successes along the way. At one point I must confess to giving up and I ordered a bunch of cheap 433mhz stuff. It works great! I still use it. If I hadn't done that though, I may have given up completely. But it was enough to keep the flame of HA alive.

The Tasmota / ESPxxxx stuff is similarly much "easier" to get started with, tradeoff being it uses Wi-Fi of course. But MySensors is for when you outgrow those sort of "off the shelf" solutions. And then you use something like OpenHAB (or whatever you prefer) to tie it all together seamlessly.

Speaking of OpenHAB, that is another complicated and famously high learning curve thing. Difference is, over there, they are very up front (in forums anyway) about that. They will tell you outright that you are creating a bespoke HA system. It is going to be a lot of work, learning, trial and error, etc. Back to the case of MySensors here, we are talking about tying together many disciplines from radio propagation, to electronics, to programming, etc...

One other difference between OpenHAB and MySensors that I personally perceive is that they have a bigger and more active community perhaps. At least on the forums, which are very active and you almost immediately get questions answered (I have come across a number of unanswered questions here while searching around). They are relentless about updating docs (they also make it easier for everyone to do so, more on that below). The MySensors devs are great and have shared this wonderful platform they have made with the world. But by now I think the community, docs, whatever maybe have not kept pace with the growth of the platform and new users? Maybe that is where we should concentrate our collective effort?

@Yveaux said in Started with MySensors and about to give up (some feedback):

we are currently discussing behind the scenes if/how we can let users edit the documentation pages

I'm actually surprised this isn't the norm. Let's remove friction here; many hands make light work! As I alluded to above, they make this super easy at OpenHAB. Every page has a link to "Edit this page on GitHub" where you don't even need to submit a PR or anything. They make it very easy. It would be great if we could move more towards something like this.

I bet anyone who cared enough to reply to this thread (and has the time to do so) would probably even pitch in a bit to help out in that department, so the small handful of you devs don't get burnt out trying to keep up with everything yourselves...