As promised a short description of my ESP8266/RFM69 gateway.

I made several attempts on building a gateway on breadboards/veroboards, but they didn't work well (NRF24 worked fine). The RF part was very sensible. I either had to touch the antenna with a finger to get things working, or move the antenna away from the board. Eventually I decided to try to make a real PCB. It was also a good excuse to get back into making my own PCB's as the last one I made was made with OrCAD under MSDOS, more than 20 years ago!

This is the schematic:

And the finished PCB - top layer:

...and the bottom layer with the RFM69

A few comments:
All passives are 0805 which are pretty easy to solder.
The library I used for ESP8266 have GPIO4 and 5 swapped, which means SDA and SCL are swapped on J1. Not a big issue for a gateway, but I decided to include I2C support for display or local sensors
I added the ATSHA204, because there was room on the board - I think I screwed up on this, since this is the 8-pin version and everyone else uses the 3-pin version with the proprietary Atmel interface.
PCB's was ordered from Dirty PCB's and showed up in approx 3 weeks - it's a 1.6 mm PCB - next time I should order 1.2 mm PCB's to avoid having to bend the legs on the SMA connector

On the positive side - it works. No issues with touching the antenna and the ESP8266 doesn't crash. I2C is also tested with a different (non-MySensors) sketch. ATSHA support is untested and probably doesn't work.

The reason for using GPIO16 as chip-select, is because chip select doesn't need a hardware interrupt and it frees up GPIO4+5 for I2C

The radio related part of the sketch:

#define MY_RADIO_RFM69
#define MY_RFM69_FREQUENCY   RF69_868MHZ
#define MY_RF69_IRQ_PIN 15
#define MY_RF69_SPI_CS 16
#define MY_IS_RFM69HW true
// #define MY_RFM69_ENABLE_ENCRYPTION true

@alexsh1 You need to have all modules running at the same frequency, but if you're willing to loose some coverage (and potentially harm the PA of the module) you can tune any version of the module to any frequency supported by the chipset (which is a significant part of the spectrum from 290 MHz to 1 GHz)

Since it's now possible to have sensors on the gateway and there seems to be a slight shift towards using more advanced hardware (Raspberry Pi, ESP8266, ARM based) I think it would be great to have some additional internal message types to report various internal data from both gateway and sensor nodes. So far I considered the following types

I_WIFI_RSSI - signal strenght from wifi network (dBm)
I_RADIO_RSSI - signal strengh from radio (dBm)
I_MEMORY - free memory (bytes)
I_UPTIME - uptime (seconds)
I_CPULOAD - CPU load (%)
I_VCC - supply voltage (volt)

• Jan

I find the Node and Gateway sketches, that comes with the RFM69 library, are very useful to validate the hardware setup.
They are available from https://github.com/LowPowerLab/RFM69/tree/master/Examples

It's also my experience that powering the RFM69 modules from an USB adaptor (either 3.3V directly, or 5V to a regulator), doesn't work reliable. I needed to power my RFM69 modules (even the non-H version) from a more reliable power source to get the hardware to work reliable

Same question as @b0rmann - is it possible to do OTA from a non-Windows environment (Mac OSX or Linux)? A simple implementation in python or perl, that could talk to the gateway, and do OTA from the command line, would be a really nice to have. I would prefer the dualoptiboot solution, since it'll work with RFM69 nodes as well (at least that's my understanding)

@Martin-Tellblom said:

My boards that I have doesn't look like the once in the guide and I don't really know where to cut to disable the power regulator
The red cut is the LED but should I cut at the green or the yellow?
The yellow is connected to Vcc 3.3V pin and the green cut is Vcc from the FTDI.
I think I should cutthe green one but I'm not sure

And the second thing If I use the sleep(very long number) is the Pro Mini going down in real sleep mode or do I have to do something else?

The Pro Mini's I have seen have two LED's - one is connected to VCC and the other to one of the GPIO pins. The one that lights up, as soon as the board is turned on, is the one to cut! You can leave the other one in place. As for cutting the regulator, I really don't see the purpose of doing that.
I have a chinese Pro Mini clone, where I cut the power LED, and nothing else. It's powered by 2x cheap AA batteries and reports every 30 seconds. Every report consists of a battery voltage, temperature and a combinered temperature/humidity measurement. It's been running 4 months and two days, and so far the battery voltage have dropped to 2.97V

If you use the sleep() function in a MySensors sketch it will put both the processor and the radio to sleep.

After adding another yield() to RFM69.cpp everything works. I have created a pull request to have this added to the code
https://github.com/mysensors/Arduino/pull/396

@jesper said:

How to measure small vibration?
I must measure when a vaskemasine stops , there are some who know what sensor i should use ?

In another thread this module was suggested - I have no personal experience with it

https://www.aliexpress.com/item/1pc-lot-SW-420-Normally-Closed-Alarm-Vibration-Sensor-Module-Vibration-Switch-30512/32259757483.html

• Jan

@thebillplease said:

@chrille - would you mind posting a diagram of your wiring? I'm looking at doing the same, but haven't been able to get it to work. Thank you in advance!

RFM69 <-> ESP8266:

DIO0 <-> GPIO4
SCK <-> GPIO14
MOSI <-> GPIO13
MISO <-> GPIO12
CS <-> GPIO15 (AKA NSS)

And of course GND + VCC

Another forum user asked for the actual sketches I used for testing - I put them on github: https://github.com/janchrillesen/arduino-stuff
The gateway sketch also has the wiring in the comments section in the top

@LastSamurai said:

Thanks but thats a little expensive for me. Can anyone suggest a good and cheap crimping set for dupont cables?

I own both the crimping tools shown in this video https://www.youtube.com/watch?v=3Cw9YFLDZeo and I agree with Andreas that the Engineer PA-09 is far superior to the chinese crimper when it comes to crimping dupont connectors. It also works will with JST connectors

• Jan

@Martin-Tellblom The values are not critical, as long as the ratio is correct. 1k + 2k2 would work fine

Connect the two resistors in series and the 5V signal to the 1k resistor and the other end of the resistors to gnd. The 3.3v signal is available between the two resistors

@Martin-Tellblom said:

Can I connect a TTL-UART (TTL-serial) gps module to a ESP8266?

I have three of these on my desk and like to use them for something fun with a ESP8266 (Like a small battery powered gps tracker for the kids/dog or so)

There's conflicting information on whether the GPIO pins on ESP8266 will tolerate 5V. To make sure you don't harm the RX port on ESP8266 I suggest you use a level converter. A simple voltage divider with two resistors should work fine (I use it to connect an Arduino Mega to the serial port of an ESP8266)

@scalz said:

• List of changes, some notes, and current status : https://docs.google.com/spreadsheets/d/191NpTBogLPijYxS2V_oHZnVlcW4B65J1kXAqYrr4qeE/edit#gid=884074439
• https://github.com/scalz/Mysensors

Be a little bit more patient, PR should go soon now as you can see from the current status

It's great to see work being put into the RFM69 driver. I have tried to install your code and updated my gateway and a sensor node

On the sensor node I added

sendSignalStrength(1);
sendRadioTxLevel(1);

and in the debug window I see

6899 TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=29,pt=1,l=1,sg=0,ft=0,st=OK:51
7035 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=30,pt=1,l=1,sg=0,ft=0,st=NACK:0

Message type 30 always fails (st=NACK) - is this expected?

Gateway is ESP8266 and node is Anarduino (328p+RFM69CW)

@palande.vaibhav said:

I have DS18B20 which is child 5, SHT31-D temperature is child 6 and Humidity is 7.
Here child 4, 5, 6 have the same number #4 but they are not grouped, they show up as separate sensors in Devices tab.

I think there's two issue

1. Something is wrong with the presentation of child 5 (DS18B20) - it should have value V_TEMP - it's empty
2. You need to change the SHT31 code to present temperature before humidiy - else the humidity of the SHT31 would be grouped with the temp from the DS18B20

Same question as @b0rmann - is it possible to do OTA from a non-Windows environment (Mac OSX or Linux)? A simple implementation in python or perl, that could talk to the gateway, and do OTA from the command line, would be a really nice to have. I would prefer the dualoptiboot solution, since it'll work with RFM69 nodes as well (at least that's my understanding)

@palande.vaibhav said:

At the end of discssion gizmocuz says that "this is already taken care of, see the forum thread about mysensors/grouping". But I checked Domoticz forum and couldn't find a thread named grouping in mysensors subforum.

It does seem to work without any changes to the domoticz code. The following is from a node with DS18B20, Si7021 and TSL2561

Child 1+2 is the Si7021 and child 4 is the DS18B20. The enumeration goes from 1 to 2 as soon as a second V_TEMP is presented

To push it even further - here's a node with a Si7021 + 10x DS18B20

(MySensors 2.0.1 beta and Domoticz dev from yesterday)

This node also works fine with Domoticz and only shows the humidity for the first occurance of V_TEMP (which is the Si7021)

@palande.vaibhav said:

I am going to try what @AWI has suggested. Presenting sensors in sequence and then spacing them apart when presenting to see what this new feature in Domoticz does.
Can you also try this? and report here? That would be really helpful.

Yes, I'll test as soon as time permits and report back

@palande.vaibhav I agree this is very annoying. I have several nodes with a Si7021 and a DS18B20, where the DS18B20 is located some distance from the node (for instance in a freezer or outdoor). This means that the humidity measured by the Si7021 might be vastly different from the humidity where the DS18B20 is located
I wonder if it would make sense to implement a NODEID_ALIAS (or NODEID_VIRTUAL) in MySensors, so a node could actually present itself as two (or more node ID's), so some sensors/children would belong to the main NODEID and other sensors could belong to another (virtual) NODEID - for the home automation system it would look like two different nodes

• Jan

@NeverDie said:

Have you tried hand soldering a BME280? It looks a bit more challenging to me than the si7021, but perhaps it's still do-able.

I only tried the Si7021, where the pads is both on the bottom and a bit on the side. For DFN/QFN's where the pads is only on the bottom I agree it's harder. I saw a interesting concept where the layout had a lot of vias directly under the DFN/QFN and you could heat the PCB from the opposite site using a traditional soldering iron. Of course you would still need solder paste for this

@NeverDie I have no experience with reflow ovens but to me it seems that it's mostly useful for batches of boards, since you need to create a stencil for the solderpaste. For a couple of boards handsoldering still seems like the best solution to be. I've been surprised what can be handsoldered - even small DFN packages (like the Si7021) is pretty easy to handsolder