as an "advanced hobbiest" i can tell why i am not getting really warm with mysensors.. I have a gateway and two nodes. One node (RFID garage opener) is working now but has range issues that i can not reach the gateway in the place i need it. And the other is a temperature sensor to play. So it works, but in real it does not, and to be honest the functionality is just nice to have for the moment
In my case i got stuck in details with my configuration. The one night a month i have to code is not enough to solve it. (and of course i am not a professional)
In the first view does mysensors look very cool. It wants to be an easy to use arduino library. A lot of examples for different gateways and nodes. Seems to be easy, "build = fun", no?
No, it is not that easy.
Mysensors is a framework. It hijacks already base functions of arduino.
As soon as you leave the application which is given in the example something does not work. And than you have to dick deep in the functionality of the mysensor framework and it is not easy to collect all necessary information in the documentation - at least for me.
- Standard EEPROM functions are hijacked and can not be used as you are used to.
- pin configuration is done in the framework. If your other things connected to the MCU need also a special treatment (RST-pin) you need to find out how
- took me a while to release that there is a completely new version 2.0 of the radio-driver which worked for me instantly and i still no not know why the same code does not work with the standard version.. And you should use the newest development branch, not the released one
- the examples are not consistent to each other and are not even compatible in all cases...
So i think it is difficult to catch the user or it is not clear which kind of user is addressed.
The normal arduino dummy user can use it for the very simple examples. As soon he wants to combine function and the issues come, he will get stucked. And of course you get the same function in the meanwhile out of the box from a lot of cheap commercial products. Maybe you have different systems running but for that money you can buy every two years new things. And most people use a Controller which can handle directly the different systems and the configration there is easier. The Controllers made big improvements in user friendly configuration!
The advanced user is getting rare. And honestly the mysensor framework is so big with all that #define-cases for the different platforms and configurations that it takes a while to go through and find your adaption. This users have already made their own private libraries which will not work directly on the mysesnors framework. They switch to a different system or maybe start extract the things they need from mysensors.
And than i also have the impression that the help in the forum is "superficial". Not because the forum does not want to help.
The problems occur in the system and it is not easily clear why something does not work without taking the time and go thorugh everything.
It is open source and the documentation is suffering. The contributors have limited time and nobody can expect to get a 24/7 full support.
Everything okay, please do not misunderstand me, i really appreciate the work behind mysensors and i can only imagine complicated it is to keep such a system administrated.
But to come back to the beginning it is the question which user should be addressed.
For the dummy user the documentation should be reduced but therefor everything should be consistent and straight. As the Controller software does, the work should focus on not technical functionality for easy configuration and usage.
For the advanced user the documentation should go more in detail in general in one place and the code should focus on a layer structure to make it easier to operate on different systems or exchange modules/versions (maybe without the arduino framework as base or an approach as FreeRTOS).
And i am not sure if it is just me, but i could imagine it would help to make it easier to get part of the active community and bring improved code or new functions back in the mysensors-core.
greeting from Germany
P.S.: i am sorry that i did not gender everything and always wrote "he" as "the user". Should of course also be a woman or girl or ...