xavbabe
Posts: 5
Joined: Sat Aug 09, 2014 11:52 am

Re: NRF24L01 RF Transceiver

Mon Sep 29, 2014 5:48 pm

Ah yes, sorry! :roll:

xavbabe
Posts: 5
Joined: Sat Aug 09, 2014 11:52 am

Re: NRF24L01 RF Transceiver

Tue Sep 30, 2014 1:27 pm

I'm using a Python wrapper for these modules and am experiencing a strange issue. Sometimes the code works perfectly and sometimes (randomly) it just can't recieve or send. I read somewhere about using a capacitor across the radio's vcc and GND but could someone with know how in electronics explain how this would work and how to wire it up?

My pi's code is here in case anyone's interested: http://github.com/xavbabe/heating/monitor.py
Arduino: http://github.com/xavbabe/heating/arduino/arduino.ino

dkosasih
Posts: 4
Joined: Tue Oct 14, 2014 1:53 pm

Re: NRF24L01 RF Transceiver

Tue Oct 14, 2014 2:02 pm

Wickedraspberry,
I am having the exact same problem like yours, except my pi is brand new and no other library is installed.

I get a perfectly fine detail printout, same as the arduino. However, I kept on receiving 0 for scanning too.

I have nothing to screenshot or code snippets to show as they are all original code from examples.

Could you point me to the right direction please.?

Thanks

wickedraspberry
Posts: 6
Joined: Thu Jun 19, 2014 6:37 pm

Re: NRF24L01 RF Transceiver

Tue Oct 14, 2014 3:04 pm

Hi dkosasih,

Did al the other values that the scanner outputs (with radio.printDetails(); look ok to you?
Are you trying to communicate between to pi's or do you have an arduino on which you can test?
You can also try some of the other examples and see what you get.

Good luck,
Wickedraspberry

dkosasih
Posts: 4
Joined: Tue Oct 14, 2014 1:53 pm

Re: NRF24L01 RF Transceiver

Tue Oct 14, 2014 10:19 pm

Thanks for the reply.

The scanner output was a few lines of non-0 characters, then followed by 0s.
however, the print details shows that it should be working as it has the TXT RX values displayed correctly.

Thing is I dont know if the pi or the arduino is the problem :(
but, this arduino I use to test as been proven working with other arduino before, so I am leaning towards the pi instead.

here is the print detail from pi.
================ SPI Configuration ================
CSN Pin = CE0 (PI Hardware Driven)
CE Pin = Custom GPIO22
Clock Speed = 8 Mhz
================ NRF Configuration ================
STATUS = 0x0e RX_DR=0 TX_DS=0 MAX_RT=0 RX_P_NO=7 TX_FULL=0
RX_ADDR_P0-1 = 0xf0f0f0f0d2 0xf0f0f0f0e1
RX_ADDR_P2-5 = 0xe2 0xe3 0xf1 0xf2
TX_ADDR = 0xf0f0f0f0d2
RX_PW_P0-6 = 0×20 0×20 0×20 0×20 0×20 0×20
EN_AA = 0x3f
EN_RXADDR = 0x3f
RF_CH = 0x5a
RF_SETUP = 0×27
CONFIG = 0x0f
DYNPD/FEATURE = 0x3f 0×04
Data Rate = 250KBPS
Model = nRF24L01+
CRC Length = 16 bits
PA Power = PA_MAX

Thanks for helping!

crashmeplease
Posts: 2
Joined: Sun Oct 19, 2014 6:34 pm

Re: NRF24L01 RF Transceiver

Sun Oct 19, 2014 6:58 pm

Not meaning to hi-jack this thread, but I am also having exactly the same issue as Wickedraspberry;

I installed Occidentalis v0.2, and then after doing all the updates, running the config for hardware SPI, and going through some tutorials eventually came to the TMRh20 library.

when I do ldconfig ; I think this is ok?

Code: Select all

sudo ldconfig -v | grep librf
ldconfig: Path `/lib/arm-linux-gnueabihf' given more than once
ldconfig: Path `/usr/lib/arm-linux-gnueabihf' given more than once
ldconfig: /lib/arm-linux-gnueabihf/ld-2.13.so is the dynamic linker, ignoring

	librf24-bcm.so.1 -> librf24-bcm.so.1.0
	librf24network.so.1 -> librf24network.so.1.0
ldconfig: /lib/ld-linux.so.3 is the dynamic linker, ignoring
when i run the gettingstarted example ;

Code: Select all

sudo ./gettingstarted
RF24/examples/pingtest/
================ SPI Configuration ================
CSN Pin  	 = CE0 (PI Hardware Driven)
CE Pin  	 = Custom GPIO22
Clock Speed	 = 8 Mhz
================ NRF Configuration ================
STATUS		 = 0x0e RX_DR=0 TX_DS=0 MAX_RT=0 RX_P_NO=7 TX_FULL=0
RX_ADDR_P0-1	 = 0xe7e7e7e7e7 0xc2c2c2c2c2
RX_ADDR_P2-5	 = 0xc3 0xc4 0xc5 0xc6
TX_ADDR		 = 0xe7e7e7e7e7
RX_PW_P0-6	 = 0x00 0x00 0x00 0x00 0x00 0x00
EN_AA		 = 0x3f
EN_RXADDR	 = 0x03
RF_CH		 = 0x4c
RF_SETUP	 = 0x07
CONFIG		 = 0x0e
DYNPD/FEATURE	 = 0x00 0x00
Data Rate	 = 1MBPS
Model		 = nRF24L01+
CRC Length	 = 16 bits
PA Power	 = PA_MAX
I assume it all seems to be connected ok, otherwise everything would be 0?

The crucial thing I notice is that ;

a) the addresses on the pi seem wrong, in the code it says Node1 and Node2 which on the Pi is 0xe7e7e7e7e7 and 0xc2c2c2c2c2, these values do not make any sense, while on the arduino code Node1 and Node2 return as 0x65646f4e32 and 0x65646f4e31, which is the correct hex translation.

b) the config code is different, on my arduino it is 0x0f

I have two arduinos working with the gettingstarted code, and previously several others with the manicbug library too, so I am certain the arduino code is not the issue.

Any pointers greatly appreciated.

dkosasih
Posts: 4
Joined: Tue Oct 14, 2014 1:53 pm

Re: NRF24L01 RF Transceiver

Mon Oct 20, 2014 4:33 am

I figured out my problem and I think you have the same as mine if you download the most recent RF24 Library.

Assuming if you have the pipes config right (i.e. the receiving and sending pipes configured correctly), if you notice the SPI configuration:
It says CE0 and Custom GPIO22. (I think) it's actually asking you to wire the into those pins, not changing the RF24 constructor in the code to fit into you wiring:

Code: Select all

RF24 radio(RPI_V2_GPIO_P1_15, RPI_V2_GPIO_P1_24, BCM2835_SPI_SPEED_8MHZ);
According ot the header file

Code: Select all

RPI_V2_GPIO_P1_15     = 22,  ///< Version 2, Pin P1-15
RPI_V2_GPIO_P1_15 was actually PIN 15 and the 22 was GPIO 22, not pin 22.
unlike many of the tutorial says to wire it to pin 22, it's wrong!! GPIO22 is pin 15.

I reckon it's a hardcoded into the library, regardless where you stick your CE and CSN, the print detail will always say GPIO 22 and CE0. it's as if ASKING you where to put your pin instead of informing you where you have stick your pin into.

I hope I don't make you even more confused.

crashmeplease
Posts: 2
Joined: Sun Oct 19, 2014 6:34 pm

Re: NRF24L01 RF Transceiver

Mon Oct 20, 2014 7:37 am

Well as daft as it sounds I must have had a loose wire!

I swapped the nrf module over between arduino and pi just to rule out that it wasn't damaged, when I ran the code still the hex addressing did not seem right, but what I didn't expect was that the pi started sending and receiving between the arduino. I know it wasn't the original module as I put that on an arduino to test.

Yes I agree with the confusion with the pin outs, lots of old tutorials with conflicting information. I did have the pinout as you suggested, so at least I was on the right track.

I didn't notice the fixed pinout in the header file, but for my project I don't think that will be a future issue. There was a time when I did try different configurations with RF24 radio setting with no joy, so that may have explained that.

Thanks, glad it is eventually working and now can move on to actually doing something with it.

John42
Posts: 7
Joined: Fri Oct 26, 2012 2:17 pm

Re: NRF24L01 RF Transceiver

Mon Nov 10, 2014 9:29 am

Argh... I've spent about 4 hours on getting it work, it has been working in the past.
I think I had cabling problems, but then even when I rewired with another I had software problems.

So, my experiences:
- Wiring: triple-check the wiring. If you have a Rev2 PI board, this is the good wiring (see middle of page)
http://hack.lenotta.com/arduino-raspber ... -nrf24l01/

- Modules: I didn't configure the raspi-config enable i2c (on my new Pi), also i2c-bcm2708, i2c-dev (not sure if all is needed), /etc/modprobe.d/raspi-blacklist.conf should not contain these blacklisted

- But, the worst! Some of the examples are very misleading!
If you see the startup fine (with good data, like below), BUT! your sending/receiving doesn't work, you don't have the CE/CSN pins correct in the initialization routine.

For the wiring on the mentioned page above, this is the good config:

Code: Select all

RF24 radio(RPI_V2_GPIO_P1_22, RPI_V2_GPIO_P1_24, BCM2835_SPI_SPEED_1MHZ);
DO NOT use RPI_V2_GPIO_P1_15 because that is a different pin!

This is good below (but not enough by itself):

Code: Select all

================ SPI Configuration ================
CSN Pin          = Custom GPIO8
CE Pin           = Custom GPIO25
Clock Speed      = 1 Mhz
================ NRF Configuration ================
STATUS           = 0x0e RX_DR=0 TX_DS=0 MAX_RT=0 RX_P_NO=7 TX_FULL=0
RX_ADDR_P0-1     = 0xf0f0f0f03c 0xf0f0f0f05a
RX_ADDR_P2-5     = 0x69 0x96 0xa5 0xc3
TX_ADDR          = 0xe7e7e7e7e7
RX_PW_P0-6       = 0x20 0x20 0x20 0x20 0x20 0x20
EN_AA            = 0x3f
EN_RXADDR        = 0x3f
RF_CH            = 0x4c
RF_SETUP         = 0x27
CONFIG           = 0x0f
DYNPD/FEATURE    = 0x00 0x00
Data Rate        = 250KBPS
Model            = nRF24L01+
...
You should see: Model: nRF24L01+ and other meaningful data.

GigaGuy
Posts: 4
Joined: Mon Mar 23, 2015 7:31 pm

Re: NRF24L01 RF Transceiver

Mon Mar 23, 2015 7:43 pm

I know its been a while but I am just getting around to playing with this, and wanted to see if anyone has gotten it working on the new Pi2 model b?

I have followed several different sites, but none use Pi2. Currently, I am using John42's config. still nothing. cant even get the ***SPI Configuration *** to come up.

Help please?

GigaGuy
Posts: 4
Joined: Mon Mar 23, 2015 7:31 pm

Re: NRF24L01 RF Transceiver

Tue Mar 24, 2015 8:01 pm

Figured it out, thanks to this post.
http://www.raspberrypi.org/forums/viewt ... t=NRF24L01

ChrisHigs
Posts: 14
Joined: Tue Apr 14, 2015 8:23 am

Re: NRF24L01 RF Transceiver

Tue Apr 14, 2015 8:39 am

Hi
I'm using my Raspberry Pi to receive temperature data sent from an Arduino and log it in a database on the Pi. I have a little C program, TempReceiver, base on the RF24Network RX example and another I've seen.

It's working perfectly with the 2 Arduinos I use and I've even had the data sent to a third one for displaying on an LCD.

I'd like to expand things to add a web interface for remotely controlling other Arduinos but not sure how to do this. I noticed someone mention a hub at the start of this thread. Any examples of this or anyone have any help to work this out?

Thanks

danjperron
Posts: 4104
Joined: Thu Dec 27, 2012 4:05 am
Location: Québec, Canada

Re: NRF24L01 RF Transceiver

Tue Apr 14, 2015 11:47 am

Hi sorry to steal this post.

I'm writing new code for the NRF24L01 and I will use MQTT. I'm practically there.

I thing that you should look at it also.

This will decouple the RF24 I/O from the GUI interface.

Check thingstud.io

Daniel.

ChrisHigs
Posts: 14
Joined: Tue Apr 14, 2015 8:23 am

Re: NRF24L01 RF Transceiver

Tue Apr 14, 2015 12:41 pm

Thanks. I'll have a look into that.

Would it allow me to wake up my wireless temp sensor every minute or so, send it's data to the Pi, and also have a web/other interface for sending commands to different Arduinos?

danjperron
Posts: 4104
Joined: Thu Dec 27, 2012 4:05 am
Location: Québec, Canada

Re: NRF24L01 RF Transceiver

Tue Apr 14, 2015 1:55 pm

I do a post on where I'm at about this design
viewtopic.php?p=739624#p739624

I'm using the shock burst method instead.
This method has some inconvenients but also has great capabilities. Very easy to control a lot of sensors without worry about collision.

The way to use MQTT is to have a server running the RF24 task and send or receive all the data by socket to the MQTT broker.

The way I think it should work is ,

RF24 server ask info on a specific sensor at the schedule time, the sensor reply and go to sleep until the next scheduling, the RF24 server send the MQTT socket topic corresponding to the sensor.(This includes the data).

I'm using mosquitto V1.4 to handle the MQTT socket. and for the GUI there is a lot of IOT that are able to handle MQTT like thingstud.io

The beauty of this method is that you could have one Pi dedicated to the RF24 and send/received all the data to/from a MQTT broker which could be anywhere or be the Pi.

In reality you split the complexity and made it simpler.

Daniel

ChrisHigs
Posts: 14
Joined: Tue Apr 14, 2015 8:23 am

Re: NRF24L01 RF Transceiver

Tue Apr 14, 2015 2:36 pm

That does sound like it could work well, however I've spent a little while optimising my Arduino module for battery use. For example the module checks the temp every minute but only sends if the temp has changed from last time. With the MQTT server requesting the data from the Arduino the radio would have to be listening all the time.

I've seen an example using node.js to run "remote" to send a command to an Arduino. I'll investigate getting something like that working alongside my TempReceiver program. I assume the two won't work well running st the same time.

danjperron
Posts: 4104
Joined: Thu Dec 27, 2012 4:05 am
Location: Québec, Canada

Re: NRF24L01 RF Transceiver

Tue Apr 14, 2015 3:25 pm

Not really, if you look the code int my github you will notice that the transmitter is only ON for a very short time. This is all to do with the python code trying to read it at specific time in advance or until it got an answer.

I let the second led on the arduino pro mini and it is link to the transmitter. This way I could see if the nRF24L01 is waiting and the light just flash very fast. The deal is time scheduling from the Python code.

The shock burst method is tricky because you fill the transmitter fifo and you wait for the connection. When it receives the data it is send automatically.

I changed the setRetries to (7,3). The python code will get a lot of time out since it will ask for a sensor in advance and again until it got an answer.

This is the trick to limit the transmitter time ON on the arduino. The Pi could transmit continuously but not the sensor.

I put code to limit the time ON of transmitter to 1 second. On time out the arduino will go to sleep and wake up on the next schedule. It is up to the Pi to handle the communication correctly.

I do have to change the way I address the scheduling , I know how to do it better, but it is working quite well right now.

Also the python code also send the next time it should wake up and I integrate a sync variable to adjust the timing error. Normally after 15 minutes of operation the sensor will be on +/- 1 seconds of its schedule target.

I'm using type 357 cell, they are only 150mah. This gives me a shorter life span. It is ideal to fix the power consumption problem.

danjperron
Posts: 4104
Joined: Thu Dec 27, 2012 4:05 am
Location: Québec, Canada

Re: NRF24L01 RF Transceiver

Tue Apr 14, 2015 3:45 pm

With the MQTT server requesting the data from the Arduino the radio would have to be listening all the time
MQTT doesn't work that way. It is just a way to transport information from one device to another.

When a sensor send something to the RF24 server on the PI,
the data will be send via socket to the MQTT broker. On the other end you need another MQTT client which will listen to a topic which is link to the sensor. The MQTT protocol is just an intermediate between the two clients.

The end client should be one of the IOT webserver.

ChrisHigs
Posts: 14
Joined: Tue Apr 14, 2015 8:23 am

Re: NRF24L01 RF Transceiver

Tue Apr 14, 2015 3:59 pm

danjperron wrote:Not really, if you look the code int my github you will notice that the transmitter is only ON for a very short time. This is all to do with the python code trying to read it at specific time in advance or until it got an answer.
Ah, I see now. Sorry, I didn't read your post properly when i was in work.

Do you have a program running continuously which send a message so the Arduino or is the program that sends the message scheduled to run at intervals?

I have my receiving bit sorted I'm not sure how to send data too. For example a button on a webpage to turn a light/something else on/off.

ChrisHigs
Posts: 14
Joined: Tue Apr 14, 2015 8:23 am

Re: NRF24L01 RF Transceiver

Tue Apr 14, 2015 4:00 pm

danjperron wrote: MQTT doesn't work that way. It is just a way to transport information from one device to another.
I see. Well I don't but I will have a look at how that all works.

danjperron
Posts: 4104
Joined: Thu Dec 27, 2012 4:05 am
Location: Québec, Canada

Re: NRF24L01 RF Transceiver

Tue Apr 14, 2015 4:49 pm

Now you are way ahead of me. I'm still on the enfancy of it.

I'm mostly done with the arduino codes. Still need to clean them up.

Right now I will concentrate on the scheduler code.

The scheduler is simple.

1 - Read sensor table and calculate timing and spread the schedule time target on each sensor. You don't want to talk to the sensor all in the same time.

2 - When one sensor is near is scheduling time, start sending information request with the next scheduling time.

3 - Keep sending data alternating with other sensors request , we can't forget other sensors, until we got a an answer.

4 - On reply, validate and send the information to the MQTT broker.

5 - If it failed send a time out info to the MQTT broker. and keep sending data until is up again.(In alternance with other sensors).

Presently part 4 and 5 are just a log file which old all the data. MQTT not done yet.

This is my github https://github.com/danjperron/nRF24L01_With_Sensor.git

and nRFReader.py is my current scheduler with no MQTT yet.

Code: Select all

pi@Pi2 ~ $ tail -f RFLog.txt
Sensor C2:C2:C2:C2:C5 D:-67.1 O:0.0 - Tue Apr 14 12:35:25 2015 VCC:4.913V - MAX6675 T:21.5 C
Sensor C2:C2:C2:C2:C6 D:-68.4 O:0.0 - Tue Apr 14 12:35:39 2015 VCC:4.152V - DS18B20 T:17.62 C
Sensor C2:C2:C2:C2:C3 D:0.1 O:2.8 - Tue Apr 14 12:36:02 2015 VCC:3.788V - DS18B20 T:18.93 C
Sensor C2:C2:C2:C2:C4 D:-0.0 O:2.0  - Tue Apr 14 12:36:17 2015 VCC:4.913V - DHT22   T:18.90 C H:29 %
Sensor C2:C2:C2:C2:C5 D:-67.1 O:0.0 - Tue Apr 14 12:36:25 2015 VCC:4.935V - MAX6675 T:22.0 C
Sensor C2:C2:C2:C2:C6 D:-68.4 O:0.0 - Tue Apr 14 12:36:39 2015 VCC:4.152V - DS18B20 T:17.62 C
Sensor C2:C2:C2:C2:C3 D:-0.1 O:2.7 - Tue Apr 14 12:37:02 2015 VCC:3.788V - DS18B20 T:18.93 C
Sensor C2:C2:C2:C2:C4 D:-0.1 O:2.0  - Tue Apr 14 12:37:17 2015 VCC:4.935V - DHT22   T:18.90 C H:29 %
Sensor C2:C2:C2:C2:C5 D:-67.1 O:0.0 - Tue Apr 14 12:37:25 2015 VCC:4.913V - MAX6675 T:21.75 C
Sensor C2:C2:C2:C2:C6 D:-68.4 O:0.0 - Tue Apr 14 12:37:39 2015 VCC:4.152V - DS18B20 T:17.62 C
Sensor C2:C2:C2:C2:C3 D:-0.1 O:2.8 - Tue Apr 14 12:38:02 2015 VCC:3.788V - DS18B20 T:18.93 C
Sensor C2:C2:C2:C2:C4 D:0.0 O:2.1  - Tue Apr 14 12:38:17 2015 VCC:4.913V - DHT22   T:18.90 C H:29 %
D: Means delta in second from the reception - target time and this my little bug I have to fix. modulus (60sec) problem. I will try to change my scheduling method to deal whit it. It's a problem when you stop and restart the program without waiting 60 sec.

O: is the variable timing delay to compensate for timing error. Sensor C3 and C4 are always +/- .1 sec from their target. C3 and C4 should also but apparently my little scheduling bug prevent this to append.


I did made some code for MQTT using the DS18B20 on the PI itself and it should be easy to implement.

Daniel

User avatar
DougieLawson
Posts: 42232
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK

Re: NRF24L01 RF Transceiver

Tue Apr 14, 2015 5:32 pm

If your connection is unreliable you may want to convert to using MQTT-SN which is a lighter weight protocol than MQTT.
Languages using left-hand whitespace for syntax are ridiculous

DMs sent on https://twitter.com/DougieLawson or LinkedIn will be answered next month.
Fake doctors - are all on my foes list.

The use of crystal balls and mind reading is prohibited.

danjperron
Posts: 4104
Joined: Thu Dec 27, 2012 4:05 am
Location: Québec, Canada

Re: NRF24L01 RF Transceiver

Tue Apr 14, 2015 6:03 pm

Thanks Dougie I will check MQTT-SN

The python server assume time out all times because we start to request data on a sensor before they wake up. I design it this way to minimize the sensor transmitter ON time.

Then it is quite reliable. The only real time out I got, if I exclude the pre-fetch one , is when I disconnected a sensor or did a test on how far away I could get a signal.

danjperron
Posts: 4104
Joined: Thu Dec 27, 2012 4:05 am
Location: Québec, Canada

Re: NRF24L01 RF Transceiver

Wed Apr 15, 2015 3:50 am

I added in the github a python script application which reads the RF24 sensor and send it to the MQTT broker.

The MQTT broker is mosquitto V1.4 compiled with websocket enabled. It is on the PI then the IP is 127.0.0.1 (local host).

I used this url to install mosquito V1.4 https://gist.github.com/taka-wang/1c47cde3e4c9c2d83156

On the python side I used paho.mqtt

Code: Select all

sudo pip install paho.mqtt
The script will publish, to the mqtt broker on "RF_DATA" topic, all sensors information.

To test it, you could just run the mosquitto_sub application. This will allow you to see what you publish.

Code: Select all

pi@Pi2 ~/nRF24L01_With_Sensor $ mosquitto_sub -d -t "RF_DATA"
Client mosqsub/10684-Pi2 sending CONNECT
Client mosqsub/10684-Pi2 received CONNACK
Client mosqsub/10684-Pi2 sending SUBSCRIBE (Mid: 1, Topic: RF_DATA, QoS: 0)
Client mosqsub/10684-Pi2 received SUBACK
Subscribed (mid: 1): 0
Client mosqsub/10684-Pi2 received PUBLISH (d0, q0, r0, m0, 'RF_DATA', ... (91 bytes))
Sensor C2:C2:C2:C2:C5 D:-0.0 O:1.9 - Tue Apr 14 23:48:15 2015 VCC:4.913V - MAX6675 T:22.5 C
Client mosqsub/10684-Pi2 received PUBLISH (d0, q0, r0, m0, 'RF_DATA', ... (91 bytes))
Sensor C2:C2:C2:C2:C6 D:0.0 O:2.6 - Tue Apr 14 23:48:31 2015 VCC:4.152V - DS18B20 T:18.93 C
Client mosqsub/10684-Pi2 received PUBLISH (d0, q0, r0, m0, 'RF_DATA', ... (92 bytes))
Sensor C2:C2:C2:C2:C3 D:-0.0 O:0.6 - Tue Apr 14 23:48:45 2015 VCC:3.776V - DS18B20 T:19.62 C
Client mosqsub/10684-Pi2 received PUBLISH (d0, q0, r0, m0, 'RF_DATA', ... (99 bytes))
Sensor C2:C2:C2:C2:C4 D:0.0 O:2.0  - Tue Apr 14 23:49:00 2015 VCC:4.935V - DHT22   T:19.60 C H:30 %
Client mosqsub/10684-Pi2 sending PINGREQ
Client mosqsub/10684-Pi2 received PINGRESP
Now that the communication with MQTT is working . I had to implement the MQTT GUI client. This is the think left to do

Daniel

ChrisHigs
Posts: 14
Joined: Tue Apr 14, 2015 8:23 am

Re: NRF24L01 RF Transceiver

Wed Apr 15, 2015 7:37 am

I haven't looked at what MQTT can do yet and if I can get it working with my setup.

Not sure whether to embed Mongoose or some other C++ web server in my receiver program.

Return to “HATs and other add-ons”