Never been able to get MySensors to work
-
More info from logs:
openhab> log:tail 18:08:40.219 [INFO ] [bpanel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel 19:26:55.033 [INFO ] [rthome.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007 19:26:56.968 [INFO ] [i.dashboard.internal.DashboardService] - Started Dashboard at http://192.168.0.41:8080 19:26:56.975 [INFO ] [i.dashboard.internal.DashboardService] - Started Dashboard at https://192.168.0.41:8443 19:26:58.438 [INFO ] [marthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui 19:26:58.572 [INFO ] [.ui.habmin.internal.servlet.HABminApp] - Started HABmin servlet at /habmin 19:26:59.304 [DEBUG] [org.openhab.binding.mysensors ] - BundleEvent STARTING - org.openhab.binding.mysensors 19:26:59.398 [DEBUG] [org.openhab.binding.mysensors ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=392, service.bundleid=232, service.scope=bundle, component.name=org.openhab.binding.mysensors.factory.MySensorsHandlerFactory, component.id=252} - org.openhab.binding.mysensors 19:26:59.412 [DEBUG] [org.openhab.binding.mysensors ] - BundleEvent STARTED - org.openhab.binding.mysensors 19:27:00.113 [DEBUG] [ensors.handler.MySensorsBridgeHandler] - Initialization of the MySensors bridge 19:27:00.130 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'mysensors:bridge-ser:e8bde86b' changed from UNINITIALIZED to INITIALIZING 19:27:00.189 [DEBUG] [sensors.factory.MySensorsCacheFactory] - Cache file: given_ids.cached exist. 19:27:00.193 [DEBUG] [sensors.factory.MySensorsCacheFactory] - Cache (given_ids) content: [] 19:27:00.219 [DEBUG] [ocol.serial.MySensorsSerialConnection] - Enabling connection watchdog 19:27:00.226 [DEBUG] [ocol.serial.MySensorsSerialConnection] - Connecting to /dev/ttyUSB0 [baudRate:115200] 19:27:00.239 [DEBUG] [org.openhab.binding.mysensors ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=401, service.bundleid=232, service.scope=singleton} - org.openhab.binding.mysensors 19:27:00.241 [DEBUG] [s.discovery.MySensorsDiscoveryService] - Starting MySensors discovery scan 19:27:00.243 [DEBUG] [ensors.handler.MySensorsBridgeHandler] - Initialization of the MySensors bridge DONE! 19:27:00.302 [DEBUG] [ocol.serial.MySensorsSerialConnection] - Serial port event listener started 19:27:00.304 [DEBUG] [ocol.serial.MySensorsSerialConnection] - Successfully connected to serial port. 19:27:00.317 [WARN ] [ocol.serial.MySensorsSerialConnection] - Skipping I_VERSION connection test, not recommended... 19:27:00.343 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 255;3;0;14;Gateway startup complete. 19:27:00.355 [DEBUG] [sensors.factory.MySensorsCacheFactory] - Writing on cache given_ids, content: [] 19:27:00.357 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'mysensors:bridge-ser:e8bde86b' changed from INITIALIZING to ONLINE 19:27:00.360 [INFO ] [ocol.serial.MySensorsSerialConnection] - Successfully connected to MySensors Bridge. 19:27:00.368 [WARN ] [orsAbstractConnection$MySensorsReader] - Exception on reading from connection java.text.ParseException: class java.lang.NumberFormatException : For input string: "Gateway startup complete." at org.openhab.binding.mysensors.internal.protocol.message.MySensorsMessage.parse(MySensorsMessage.java:342) ~[232:org.openhab.binding.mysensors:2.4.0.201812040738] at org.openhab.binding.mysensors.internal.protocol.MySensorsAbstractConnection$MySensorsReader.run(MySensorsAbstractConnection.java:338) [232:org.openhab.binding.mysensors:2.4.0.201812040738] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?] at java.lang.Thread.run(Thread.java:748) [?:?] 19:27:00.390 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;0;0;18;2.3.1 19:27:00.447 [DEBUG] [ors.internal.gateway.MySensorsGateway] - Presentation Message received 19:27:00.456 [DEBUG] [sensors.factory.MySensorsCacheFactory] - Writing on cache given_ids, content: [0] 19:27:00.459 [WARN ] [s.discovery.MySensorsDiscoveryService] - Cannot automatic discover thing node: 0, child: 255 please insert it manually 19:30:00.341 [DEBUG] [orsAbstractConnection$MySensorsWriter] - Sending to MySensors: 0;0;3;0;2; 19:30:00.358 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;2;2.3.1 19:30:03.338 [DEBUG] [gateway.MySensorsNetworkSanityChecker] - Network sanity check: PASSED 19:30:03.341 [DEBUG] [gateway.MySensorsNetworkSanityChecker] - Sending I_HEARTBEAT_REQUESTs 19:30:03.344 [DEBUG] [orsAbstractConnection$MySensorsWriter] - Sending to MySensors: 0;255;3;0;18; 19:30:03.357 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;22;4909969 19:33:06.346 [DEBUG] [orsAbstractConnection$MySensorsWriter] - Sending to MySensors: 0;0;3;0;2; 19:33:06.361 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;2;2.3.1 19:33:09.345 [DEBUG] [gateway.MySensorsNetworkSanityChecker] - Network sanity check: PASSED 19:33:09.348 [DEBUG] [gateway.MySensorsNetworkSanityChecker] - Sending I_HEARTBEAT_REQUESTs 19:33:09.350 [DEBUG] [orsAbstractConnection$MySensorsWriter] - Sending to MySensors: 0;255;3;0;18; 19:33:09.366 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;22;5095971 19:36:12.351 [DEBUG] [orsAbstractConnection$MySensorsWriter] - Sending to MySensors: 0;0;3;0;2; 19:36:12.363 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from eway received: 0;255;3;0;2;2.3.1 19:36:15.351 [DEBUG] [gateway.MySensorsNetworkSanityChecker] - Network sanity check: PASSED 19:36:15.354 [DEBUG] [gateway.MySensorsNetworkSanityChecker] - Sending I_HEARTBEAT_REQUESTs 19:36:15.357 [DEBUG] [orsAbstractConnection$MySensorsWriter] - Sending to MySensors: 0;255;3;0;18; 19:36:15.371 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;22;5281981I built a small breakout board for the radio and it appears to connect to the OH2 instance successfully with this pinout board.
Even though the gateway appears to be recognized by OH2, the node still looks like this:
16 MCO:BGN:INIT NODE,CP=RNNNA---,REL=255,VER=2.3.1 26 TSM:INIT 27 TSF:WUR:MS=0 33 TSM:INIT:TSP OK 35 TSF:SID:OK,ID=199 37 TSM:FPAR 1637 TSF:MSG:SEND,199-199-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: 3645 !TSM:FPAR:NO REPLY 3647 TSM:FPAR 5246 TSF:MSG:SEND,199-199-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: 7255 !TSM:FPAR:NO REPLY 7257 TSM:FPAR 8856 TSF:MSG:SEND,199-199-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: 10864 !TSM:FPAR:NO REPLY 10866 TSM:FPAR 12466 TSF:MSG:SEND,199-199-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: 14474 !TSM:FPAR:FAIL 14475 TSM:FAIL:CNT=1 14477 TSM:FAIL:DIS 14479 TSF:TDI:TSL@iamtheghost said in Never been able to get MySensors to work:
Both authentic, no "blobs", real chips.
Still, they can be counterfeit nRF24L01+ (e.g. https://forum.mysensors.org/topic/1664/which-are-the-best-nrf24l01-modules)
I don't feel like either of these are horrible soldering jobs.
The top appears OK, the DHT pins look 'battle-tested' though ;-)
Followed this guide "to the T"
That guide is already 2 years old; I'm not sure if it is correct. This is the official guide.
May 18 17:40:48 DEBUG !TSM:INIT:TSP FAIL
That is a clear indication of communication error between MySensors and the radio; the radio communication check by MySensors has failed.
There's no use trying to continue with this error.I built a small breakout board for the radio and it appears to connect to the OH2 instance successfully with this pinout board.
Not sure what you mean here...
Even though the gateway appears to be recognized by OH2, the node still looks like this
Yes, the gateway starts and can be connected to by OH2, but the gateway cannot communicate with the radio.
There's no use looking deeper into the node, cause your gateway is faulty for some reason.Would you be able to build an Arduino serial gateway (e.g. based on Uno or Nano) and test if that gets the communication running? That way we could rule out defective radio(s).
Beware to power the radio from 3.3V then. -
@yveaux said in Never been able to get MySensors to work:
That guide is already 2 years old; I'm not sure if it is correct. This is the official guide.
That guide is the only complete tutorial I've found to getting MySensors 2.4 working with OpenHab 2.4 via the serial gateway. While the original post is 2 years old, it has been updated multiple times. I've followed the official guide as well, to the same result, however.
Still, they can be counterfeit nRF24L01+ (e.g. https://forum.mysensors.org/topic/1664/which-are-the-best-nrf24l01-modules)
Looking at my ICs through a magnifying lens, it appears that mine have the "hole" in the middle of the "+" symbol on the etching. They were purchased from Amazon, but I can't recall which supplier.
Would you be able to build an Arduino serial gateway (e.g. based on Uno or Nano) and test if that gets the communication running?
Yeah, I can throw one together.
-
@iamtheghost said in Never been able to get MySensors to work:
Both authentic, no "blobs", real chips.
Still, they can be counterfeit nRF24L01+ (e.g. https://forum.mysensors.org/topic/1664/which-are-the-best-nrf24l01-modules)
I don't feel like either of these are horrible soldering jobs.
The top appears OK, the DHT pins look 'battle-tested' though ;-)
Followed this guide "to the T"
That guide is already 2 years old; I'm not sure if it is correct. This is the official guide.
May 18 17:40:48 DEBUG !TSM:INIT:TSP FAIL
That is a clear indication of communication error between MySensors and the radio; the radio communication check by MySensors has failed.
There's no use trying to continue with this error.I built a small breakout board for the radio and it appears to connect to the OH2 instance successfully with this pinout board.
Not sure what you mean here...
Even though the gateway appears to be recognized by OH2, the node still looks like this
Yes, the gateway starts and can be connected to by OH2, but the gateway cannot communicate with the radio.
There's no use looking deeper into the node, cause your gateway is faulty for some reason.Would you be able to build an Arduino serial gateway (e.g. based on Uno or Nano) and test if that gets the communication running? That way we could rule out defective radio(s).
Beware to power the radio from 3.3V then. -
Okay, threw together an Arduino Nano serial gateway. It's currently plugged into the Pi via USB. Same port, ttyUSB0, and appears to be responding to sanity checks. Need to look at the gateway logs, now.
@iamtheghost said in Never been able to get MySensors to work:
Looking at my ICs through a magnifying lens, it appears that mine have the "hole" in the middle of the "+" symbol on the etching. They were purchased from Amazon, but I can't recall which supplier.
We know now, that It is impossible to identify fakes from the outside (apart from the blob ones obviously).
Okay, threw together an Arduino Nano serial gateway. It's currently plugged into the Pi via USB. Same port, ttyUSB0, and appears to be responding to sanity checks. Need to look at the gateway logs, now.
Well, that sounds hopeful. Does the node find its parent now? Are the messages coming in correctly on the gateway?
-
If the proposed serial gateway wont work, then try something else, if you have a friend that also use home automation, maybe you can try to connect you gateway and sensor to his system, then you are away from your home, maybe something is disturbing your 2.4GHz communication
-
If the proposed serial gateway wont work, then try something else, if you have a friend that also use home automation, maybe you can try to connect you gateway and sensor to his system, then you are away from your home, maybe something is disturbing your 2.4GHz communication
@bjacobse IMHO wireless disturbance is quite unlikely to be the root cause here, as messages do come in to the gateway (they pass the radio's crc check, so they are almost certain valid messages).
The gateway just reads them as all zeroes from the radio for some bizarre reason. -
Is your power supply enough to supply the right current? Also play with the RF POWER when you build the gateway.
-
@iamtheghost I'm sorry I could not post any kind of solution, but just to say "Me too!".
Two years and half of experimentations, different platform (ESP8266 / ESP-12) but same radio and same h/w for the controller, and in the end I had your exact same results.
Same as you, I did everything I could to figure out the problem, including spending and "insane" amount of time (and money!) in sourcing the same hardware components from different sources.
I did change the hardware (wires, components, microSD, cables, power sources, etc. etc. ) so many times that I can't even count; that poor raspberry of mine has been flashed over and over; same goes for the ESP-module, which I have also tried in every possible "flavour" (NodeMCU, Lolin, Amica, WeMos, etc. ). And in doing so I left quite a trail of "weird and unsolved" problems here in the forum.
In the end, just like you have discovered, I could never make it work!
I was captivated by the idea of having a "mesh sensors network" working around my building, especially because I have wide areas not covered by WiFi and I was intrigued (to say the least) by the possibilities promised by MySensors. But as you said, "It promises all the bells and whistles for cheap home automation, but despite my every effort, I cannot even read a simple DHT11". (*)(to be precise, in my case it was also a BME280; I switched to those AIO sensors after failing with DHT variants)
I did never solve the issues, and I abandoned this platform when I reached the verge of my patience having exactly the same sketch with the same hardware (really, the same sensor, the same radio, the same wires, and two identical boards) working on one board and failing on another.
After 2 years and a half I gave up on the idea of a "mesh network" and moved to another library (still free and still available to install on a raspberry to use as a controller, and with a beautiful UI)... wish I had done it sooner. In 4 days I fixed my whole network, having a plethora of sensors constantly reporting, never hanging up for any reason (I mean, I tried removing power in 60 seconds intervals for 5 minutes and in the end they all rebooted correctly with no errors) and with the bonus feature of outputting "eye friendly" data due to the different controller.
Hence, I perfectly understand your situation and I know how it feels: the best suggestion I can give you is to "move on" and use a different library/architecture.
-
@iamtheghost I'm sorry I could not post any kind of solution, but just to say "Me too!".
Two years and half of experimentations, different platform (ESP8266 / ESP-12) but same radio and same h/w for the controller, and in the end I had your exact same results.
Same as you, I did everything I could to figure out the problem, including spending and "insane" amount of time (and money!) in sourcing the same hardware components from different sources.
I did change the hardware (wires, components, microSD, cables, power sources, etc. etc. ) so many times that I can't even count; that poor raspberry of mine has been flashed over and over; same goes for the ESP-module, which I have also tried in every possible "flavour" (NodeMCU, Lolin, Amica, WeMos, etc. ). And in doing so I left quite a trail of "weird and unsolved" problems here in the forum.
In the end, just like you have discovered, I could never make it work!
I was captivated by the idea of having a "mesh sensors network" working around my building, especially because I have wide areas not covered by WiFi and I was intrigued (to say the least) by the possibilities promised by MySensors. But as you said, "It promises all the bells and whistles for cheap home automation, but despite my every effort, I cannot even read a simple DHT11". (*)(to be precise, in my case it was also a BME280; I switched to those AIO sensors after failing with DHT variants)
I did never solve the issues, and I abandoned this platform when I reached the verge of my patience having exactly the same sketch with the same hardware (really, the same sensor, the same radio, the same wires, and two identical boards) working on one board and failing on another.
After 2 years and a half I gave up on the idea of a "mesh network" and moved to another library (still free and still available to install on a raspberry to use as a controller, and with a beautiful UI)... wish I had done it sooner. In 4 days I fixed my whole network, having a plethora of sensors constantly reporting, never hanging up for any reason (I mean, I tried removing power in 60 seconds intervals for 5 minutes and in the end they all rebooted correctly with no errors) and with the bonus feature of outputting "eye friendly" data due to the different controller.
Hence, I perfectly understand your situation and I know how it feels: the best suggestion I can give you is to "move on" and use a different library/architecture.
@neo-mod said in Never been able to get MySensors to work:
@iamtheghost I'm sorry I could not post any kind of solution, but just to say "Me too!".
Two years and half of experimentations, different platform (ESP8266 / ESP-12) but same radio and same h/w for the controller, and in the end I had your exact same results.
Same as you, I did everything I could to figure out the problem, including spending and "insane" amount of time (and money!) in sourcing the same hardware components from different sources.
I did change the hardware (wires, components, microSD, cables, power sources, etc. etc. ) so many times that I can't even count; that poor raspberry of mine has been flashed over and over; same goes for the ESP-module, which I have also tried in every possible "flavour" (NodeMCU, Lolin, Amica, WeMos, etc. ). And in doing so I left quite a trail of "weird and unsolved" problems here in the forum.
In the end, just like you have discovered, I could never make it work!
I was captivated by the idea of having a "mesh sensors network" working around my building, especially because I have wide areas not covered by WiFi and I was intrigued (to say the least) by the possibilities promised by MySensors. But as you said, "It promises all the bells and whistles for cheap home automation, but despite my every effort, I cannot even read a simple DHT11". (*)(to be precise, in my case it was also a BME280; I switched to those AIO sensors after failing with DHT variants)
I did never solve the issues, and I abandoned this platform when I reached the verge of my patience having exactly the same sketch with the same hardware (really, the same sensor, the same radio, the same wires, and two identical boards) working on one board and failing on another.
After 2 years and a half I gave up on the idea of a "mesh network" and moved to another library (still free and still available to install on a raspberry to use as a controller, and with a beautiful UI)... wish I had done it sooner. In 4 days I fixed my whole network, having a plethora of sensors constantly reporting, never hanging up for any reason (I mean, I tried removing power in 60 seconds intervals for 5 minutes and in the end they all rebooted correctly with no errors) and with the bonus feature of outputting "eye friendly" data due to the different controller.
Hence, I perfectly understand your situation and I know how it feels: the best suggestion I can give you is to "move on" and use a different library/architecture.
I knew I wasn't alone. I totally accept and encourage platforms that are geared towards EEs and programmers, and MySensors is definitely that. Even as a programmer by trade, it's still difficult.
What library are you using now? I'm piqued.
-
Is your power supply enough to supply the right current? Also play with the RF POWER when you build the gateway.
@badisensors I'm using the 'official' 5v 2A transformer that came with the Pi kit when I bought it from Adafruit. Multimeter reads a flat 5v, no jumping around, and amperage/current draw seems to be normal.
-
Make a last try and change the RF POWER parameter when you build the gateway. If it is at high power set it to low power or the opposite. Did you try with other RF24 module?
-
Sorry, but you select most difficult way for build your sensor network.
You spare one arduino like serial gateway or one Wemos like ethernet wifi gateway and two years hacking RPI gateway with no result.
And you choose bad radio module too, I think. Instead of NRF24 use RFM69 and no more problems with distance in your home and mesh network function no needed.
For all beginners I recommended step by step solution of problems, if something do not works.
For example, first try simple communication between two modules using basic examples from RFM69 library for example.
If it works, you have got certainty, that your hardware is OK ( radio properly connected to arduino ).
Then you can load sketches for gateway and normal node to both modules and I bet, it will work. -
You can also check if messages come in to your Pi ok using minicom.
For example:
minicom -b 115200 -o -D /dev/ttyUSB0You would have to install minicom (
sudo apt-get install minicom)
You may have to change settings a bit so that it displays the data on newlines. -
2 years and keep trying without ask help??!!!
I'm using lot of sensors since i'm registered on this forum and it works since first day.I only had problems with nrf24 chinese clones range,so a i changed all network to rfm69 and now i have an sensor 50m away from house and keep working every day.
the only diference is that i use a serial gateway connected to raspberry pi. It's the arduino version with and rfm69 conected by usb.
order some rfm69 from ebay and try again and order an arduino pro mini (1.x€) and an genuineftdi(clones won't work) or even an arduino nano with original ftdi chip and connect it by usb to the pi. I assure that it works.:+1: -
At first I'm no expert of MySensors or openHAB.
Perhaps I had luck but got the connection between MySensors and OH to work from
the beginning with only minor problems. The system has now been working for almost 2 years and I did it this way.
OH is installed on a RPi 3B, have a serial gateway on an Arduino Nano with nrf24L01 pa+lna the nodes (5 pcs) are built on Arduino pro mini.
The nodes are 3 Door/Window sensors, one relay and one tempereture/humidity sensor.
Since the gateway is placed in the basement and the nodes are on first floor one of the nodes is using nrf24L01 pa+lna and the other nrf24L01+.
The nrf24L01+ are chines and I bought about 15 of them and tested them at a distance of 12m through 2 wooden walls and have to scrap 3 of them.
The gateway and nodes have all standard sketches according to MySensors examples with minor changes. All nodes have fixed node_id.
Installation:
Downloaded "openHABianPi" SD card image file.
Wrote the image to a SD card and put it in the RPi.
Started the RPi and after some minutes OH was up and running.
Complete insructions can be found at https://www.openhab.org/v2.4/docs/installation/openhabian.html.
Connected the gateway to OH via a USB cable.
Went to MySensors/Controller/openHAB and followed the "Install instructions" at https://github.com/tobof/openhab2-addons/wiki.
Used Paper UI to configure the thing "MySensors serial gateway" and not .things file.
Now the nodes (things) pop up in the Inbox. Don't remember if I had to restart the RPi, gateway and nodes.
I hope this can help someone. -
@iamtheghost I feel your pain brother. I am a newbie to MySensors and although got up and running relatively quickly with openHAB and an old Raspberry Pi 1 controller/gateway - I still spend days trying to sort out radio issues. At the moment it's replacing a standard nrf24L01 with the pa+lna version ... been at it for a couple of days without successful comms with gateway.
Two years trying ... I salute you. Keep holding on to the fact that when it works it will be so satisfying :-)
-
@badisensors I'm using the 'official' 5v 2A transformer that came with the Pi kit when I bought it from Adafruit. Multimeter reads a flat 5v, no jumping around, and amperage/current draw seems to be normal.
@iamtheghost Much as I admire those who got it all to work first time, the tenacity of those who have managed to get radio working against the unknown, and every sympathy for those who haven't, I really question the logic of the default MySensors recommendation with so many pirates and scammers flooding the market, and known 2.4GHz penetration problems.
I have no doubt Nordic stand by their products, unfortunately it is their popularity which encouraged the pirates to flood the market such that even major suppliers have problems with verification.
I can only suggest doing as I did with a router and a mobile to verify radio paths are solid, then you will know if the 2.4 devices should work, if not change frequency.
My own decision to go go with 433MHz against 2.4GHz was based on this crude but effective first step, identifying blind spots. The standard RFM69 devices have not caused a single issue in 2 years, and as yet piracy is uncommon. -
@iamtheghost I feel your pain brother. I am a newbie to MySensors and although got up and running relatively quickly with openHAB and an old Raspberry Pi 1 controller/gateway - I still spend days trying to sort out radio issues. At the moment it's replacing a standard nrf24L01 with the pa+lna version ... been at it for a couple of days without successful comms with gateway.
Two years trying ... I salute you. Keep holding on to the fact that when it works it will be so satisfying :-)
@zookazim be carefull with the nrf24 amplified boards.some times you just have less range because you incresed the signal power and starting have ecos and distortions on signals. I only has 1 amplified card and had poor range,just before change everyting to rfm69w ,not even need to be the hight power(hw )version to have more range than on 2.4 ghz cards
-
I stopped using the amplified version and just used a normal version with an antenna. You can find them online. Works great.
-
@zookazim be carefull with the nrf24 amplified boards.some times you just have less range because you incresed the signal power and starting have ecos and distortions on signals. I only has 1 amplified card and had poor range,just before change everyting to rfm69w ,not even need to be the hight power(hw )version to have more range than on 2.4 ghz cards
@tmaster Be careful not to compare apples and oranges, the frequency of the two devices react differently, higher frequencies tend to be more liable to attenuation and have shorter range.
What is also often overlooked in the higher power versions of the 2.4 devices is the additional preamplifier stage which can make a difference at the reception extremes but overload in closer proximity...
