My experiences with MySensors
-
Well, unfortunately I cannot agree with the stories of success.
It's ok that a tool works for someone, but it can't be so weak that things like radio clones, track shapes or cap variations renders something unusable. And still did not mention interference or houses construction materials. All things that should be tested. WiFi/mobile interference should not be a problem, everyone has em.
Just only think that if Chinese manufacturers are making these clones in that volumes, and they are sold, it's because they took a look at the original and made a product profile with what specs are acceptable for the expected application and clones are the result. I mean that perhaps mysensors expected to much from them.
I guess everyone already knows that I only had problems trying to use mysensors, and now I have a defeating gw problem while using original radios all around. I have nrf52s in the box for testing but I'm so defeated, that I have no strength to try them.
I've ordered parts for making a good ole rj45 gw, but I'm already working in a custom base sketch for moving to esp+mqtt.
My influx data is full of "holes"Now I'm thinking in the fact that my gw started to make this more or less after the installation of a Google home and a echo Dot, for testing. It already seems paranoia.
-
That is just the point I had in my mind. I'm convinced that mysensors is a great project and the work done here is golden, really. But I would like to know why the documentation always seems to recommend hardware that when you fail to implement, at some point someone tells you that it was expected.
That happened me again this week with the Ethernet gw. Following the documentation, hours and hours trying to make the module work, to share spi port, etc... and then someone tells me better getting a w5100. Then why is this board in the official docs? Let's take it out and put a warning.
The docs are full of pinout pics of nrf24. But if you use the search (for hours) you get plenty of posts from vip telling... Better going with rfm69.
I hope it's not the same with rfm69. -
@rodaman
Although fully agree with @mickecarlsson and @tbowmo (I have been lucky with really cheap nrf24L01+ modules I think) and have a similar experience as @TheoL (MySensors works fine with nr24L01+ modules) I can state that mySensors is very much alive.However, I'm interested in your Wemos setup.
I've got some questions from which I'm sure you can give me the right quidance:
I guess it used some bandwith in your Wifi network? can I use it similar as mySensors topology or even with mySensors libraries?
Can it be used with batteries (sleep modes and so on) for a long time?thank you in advance for your values answers,
BR, Boozz
@rodaman: May I remind you of my questions:
@rodaman
...
However, I'm interested in your Wemos setup.
I've got some questions from which I'm sure you can give me the right quidance:
I guess it used some bandwith in your Wifi network? can I use it similar as mySensors topology or even with mySensors libraries?
Can it be used with batteries (sleep modes and so on) for a long time?thank you in advance for your values answers,
BR, Boozz
Unfortunately no reaction from your side till today. In the meanwhile I've searched the internet for a ESP8266 or ESP32 mesh network as an alternative for the mySensors network. I cannot find a good working open source (read Arduino based) startpoint, so I'm wondering if you could direct me to a good starting point.
Thanks,
Boozz
-
I've been away from the forum a couple of days.. But the W5100 is actually the one that is promoted around the site. It does however have a problem with sharing SPI port in some circumstances, as it doesn't let go of MISO (if I remember right).
For ENC28J60, it does say that you might run into trouble with memory, as it does have a larger memory footprint.mysensors "store" : https://www.mysensors.org/store/ethernet
build instructions: https://www.mysensors.org/build/ethernet_gateway -
I've been away from the forum a couple of days.. But the W5100 is actually the one that is promoted around the site. It does however have a problem with sharing SPI port in some circumstances, as it doesn't let go of MISO (if I remember right).
For ENC28J60, it does say that you might run into trouble with memory, as it does have a larger memory footprint.mysensors "store" : https://www.mysensors.org/store/ethernet
build instructions: https://www.mysensors.org/build/ethernet_gateway@tbowmo Thanks Thomas, I was trying to make an ENC28J60 module work with RF24 then RFM69, and I was getting crazy at it. Finally the module was a failed one. I'm so embarrased, as I was convinced I first tested the module on arrival, and I missed the point.
I've already ordered a W5100, but it may take weeks. :pensive: -
@tbowmo Thanks Thomas, I was trying to make an ENC28J60 module work with RF24 then RFM69, and I was getting crazy at it. Finally the module was a failed one. I'm so embarrased, as I was convinced I first tested the module on arrival, and I missed the point.
I've already ordered a W5100, but it may take weeks. :pensive: -
@rodaman: May I remind you of my questions:
@rodaman
...
However, I'm interested in your Wemos setup.
I've got some questions from which I'm sure you can give me the right quidance:
I guess it used some bandwith in your Wifi network? can I use it similar as mySensors topology or even with mySensors libraries?
Can it be used with batteries (sleep modes and so on) for a long time?thank you in advance for your values answers,
BR, Boozz
Unfortunately no reaction from your side till today. In the meanwhile I've searched the internet for a ESP8266 or ESP32 mesh network as an alternative for the mySensors network. I cannot find a good working open source (read Arduino based) startpoint, so I'm wondering if you could direct me to a good starting point.
Thanks,
Boozz
@boozz
I am not user "roadman", but I am using MySensors and ESP8266 ( Wemos) so hopefully I can answer some of your questions.I am using only one wifi access point (AP or router) in my home without problems.
But you can use one AP for your computers and TV and etc. and other for your sensors.
AP hw is cheap....My house is 8x12 meters and wifi AP is in 2nd floor about in center of house.
It covers the entire house and very close ( 3m )out of house.
Near this wifi AP is RFM69 MySensors gateway, which covers up to the edge of my property 60 meters away.
( may further )MySensors is goot for nodes a far away in my garden and for nodes with low energy consumption and fast reaction when wake up.
When MySensors node is sleeping and then wake up, it immediately continues in program flow immediately from the place of "sleep" command.
Wemos, when sleeping an wake ups, reboots and must connect to AP, which takes 8s to 2s when we do some tweakings.But Wemos is very user friendly.
You can use some "ready use" solutions like ESPeasy or Tasmota and configure your node trough its web page.
Configure means select which sensor connect to which pin, send value to which contrtoller etc.
Write some programs or scripts:
All without the need to compile a new program.
And you can send to your controller what you want, not just what is implemented in MySensors.
( Using JSON API in my case with Domoticz )
And your controller can send anything to your node.And for "MESH" topology.
Arduino "painlessMesh" library for ESPs exists.
But I think it is more easier to use more AP units - they are cheap .... -
@boozz
I am not user "roadman", but I am using MySensors and ESP8266 ( Wemos) so hopefully I can answer some of your questions.I am using only one wifi access point (AP or router) in my home without problems.
But you can use one AP for your computers and TV and etc. and other for your sensors.
AP hw is cheap....My house is 8x12 meters and wifi AP is in 2nd floor about in center of house.
It covers the entire house and very close ( 3m )out of house.
Near this wifi AP is RFM69 MySensors gateway, which covers up to the edge of my property 60 meters away.
( may further )MySensors is goot for nodes a far away in my garden and for nodes with low energy consumption and fast reaction when wake up.
When MySensors node is sleeping and then wake up, it immediately continues in program flow immediately from the place of "sleep" command.
Wemos, when sleeping an wake ups, reboots and must connect to AP, which takes 8s to 2s when we do some tweakings.But Wemos is very user friendly.
You can use some "ready use" solutions like ESPeasy or Tasmota and configure your node trough its web page.
Configure means select which sensor connect to which pin, send value to which contrtoller etc.Write some programs or scripts:
All without the need to compile a new program.
And you can send to your controller what you want, not just what is implemented in MySensors.
( Using JSON API in my case with Domoticz )
And your controller can send anything to your node.And for "MESH" topology.
Arduino "painlessMesh" library for ESPs exists.
But I think it is more easier to use more AP units - they are cheap ....@kimot said in My experiences with MySensors:
But you can use one AP for your computers and TV and etc. and other for your sensors.
AP hw is cheap....Or you can get a VLAN compliant Wifi access point, do the things as should be and implement a separate VLAN for your IoT devices and services.
If you buy, for example an ubiquity AP, you can configure as many SSIDs as you need, each one on it's own VLAN, and even you can specify that the IoT network should only be N-type increasing the range.
By using only one access point you also reduce radio interferences. Radio appliances are not perfectly made and cheap ones tend to be noisy and get worse with the age.I'm not particulary an ubiquity fan, in fact I only have the ap_ac_pro one, but I'm so satisfied with it that I would recommend their switch+router solution. The web management is awesome.
For my adventures I prefer having an ordinary 10gb d-link switch and a custom opnsense router.Range of the ap_ac_pro inside a 20m radius house with 25cms stone walls is just in the limit. Just one in the very center. A long range unit would cover anything, but mine is freaking fast. :ghost:
-
@boozz
I am not user "roadman", but I am using MySensors and ESP8266 ( Wemos) so hopefully I can answer some of your questions.I am using only one wifi access point (AP or router) in my home without problems.
But you can use one AP for your computers and TV and etc. and other for your sensors.
AP hw is cheap....My house is 8x12 meters and wifi AP is in 2nd floor about in center of house.
It covers the entire house and very close ( 3m )out of house.
Near this wifi AP is RFM69 MySensors gateway, which covers up to the edge of my property 60 meters away.
( may further )MySensors is goot for nodes a far away in my garden and for nodes with low energy consumption and fast reaction when wake up.
When MySensors node is sleeping and then wake up, it immediately continues in program flow immediately from the place of "sleep" command.
Wemos, when sleeping an wake ups, reboots and must connect to AP, which takes 8s to 2s when we do some tweakings.But Wemos is very user friendly.
You can use some "ready use" solutions like ESPeasy or Tasmota and configure your node trough its web page.
Configure means select which sensor connect to which pin, send value to which contrtoller etc.Write some programs or scripts:
All without the need to compile a new program.
And you can send to your controller what you want, not just what is implemented in MySensors.
( Using JSON API in my case with Domoticz )
And your controller can send anything to your node.And for "MESH" topology.
Arduino "painlessMesh" library for ESPs exists.
But I think it is more easier to use more AP units - they are cheap ....@kimot said in My experiences with MySensors:
MySensors is goot for nodes a far away in my garden and for nodes with low energy consumption and fast reaction when wake up.
When MySensors node is sleeping and then wake up, it immediately continues in program flow immediately from the place of "sleep" command.
Wemos, when sleeping an wake ups, reboots and must connect to AP, which takes 8s to 2s when we do some tweakings.Ok, so if I do not misinterpret your words, it's better / easier to use mySensors for the tasks as specified above and use WEMOS / 8266 for other tasks. Some pretty distinct way of where and how to use it.
Thanks a lot for the info provided. I appreciate that. I will give this a try sooner or later for sure.
Up to now my experience with mySensors is positive. Yes, now and then the radio's give me some troubles, but that's part of it. Still a very inexpensive way to collect data and switch on the lights in my garden house, dim some LED's all over the house and get alarmed once the ground-water reaches a level so I have to watch out my basement isn't flooded.Thanks
Booz
-
@boozz
I am not user "roadman", but I am using MySensors and ESP8266 ( Wemos) so hopefully I can answer some of your questions.I am using only one wifi access point (AP or router) in my home without problems.
But you can use one AP for your computers and TV and etc. and other for your sensors.
AP hw is cheap....My house is 8x12 meters and wifi AP is in 2nd floor about in center of house.
It covers the entire house and very close ( 3m )out of house.
Near this wifi AP is RFM69 MySensors gateway, which covers up to the edge of my property 60 meters away.
( may further )MySensors is goot for nodes a far away in my garden and for nodes with low energy consumption and fast reaction when wake up.
When MySensors node is sleeping and then wake up, it immediately continues in program flow immediately from the place of "sleep" command.
Wemos, when sleeping an wake ups, reboots and must connect to AP, which takes 8s to 2s when we do some tweakings.But Wemos is very user friendly.
You can use some "ready use" solutions like ESPeasy or Tasmota and configure your node trough its web page.
Configure means select which sensor connect to which pin, send value to which contrtoller etc.Write some programs or scripts:
All without the need to compile a new program.
And you can send to your controller what you want, not just what is implemented in MySensors.
( Using JSON API in my case with Domoticz )
And your controller can send anything to your node.And for "MESH" topology.
Arduino "painlessMesh" library for ESPs exists.
But I think it is more easier to use more AP units - they are cheap ....
