@sundberg84 Hi, I'm not using level converters becuse I use a ProMini with 3,3V (with W5100 and rfm69hw).
Maybe I have a small clue: The Interrupt Pin is high all the time. It seems that the interrupt request from the RFM Module is not processed. I cant see interrupts when I start a node. (With a working setup with ESP8266 and RFM69, the pin is low most of the time except when new packets arrive from a sensor).
@sundberg84
It does not work for me with softspi too. Although the debug output does not look that bad..
MCO:BGN:INIT GW,CP=RPNGA---,FQ=16,REL=255,VER=2.3.2<\n>
4 TSM:INIT<\n>
5 TSF:WUR:MS=0<\n>
8 TSM:INIT:TSP OK<\n>
10 TSM:INIT:GW MODE<\n>
12 TSM:READY:ID=0,PAR=0,DIS=0<\n>
14 MCO:REG:NOT NEEDED<\n>
577 GWT:TIN:IP=192.168.178.203<\n>
1581 MCO:BGN:STP<\n>
1583 MCO:BGN:INIT OK,TSP=1<\n>
1585 TSM:READY:NWD REQ<\n>
Hello,
thank you scalz for the very good clarification.
@sundberg84 I can confirm that it does compile with the #define MY_RFM69_NEW_DRIVER option. AFAIK Arduino changed the way setDataMode should be called (see links in first post). I'm not a SW-Expert but I think Someone would have to change the coresponding SoftSPI calls in the old RFM69 (old) driver if you want to use it. I currently use an ATMega2560+W5100+NRF24PA with SoftSPI which is working (but I do not know with which Arduino Verison it was compiled).
I will go with the new driver. I think it takes some time until I really do the change in HW, because I have to change several productive nodes. As we have big heat at the moment and my lab is under the roof my motivation is currently not that high... 
Sorry for replying this late, just having some "real world" issues 
Yes, with the new driver it works. Do we have a comparison about pros/cons of the new RFM69 driver. As I'm migrating all my nodes from nrf24 to rfm69 its no problem to use the new driver in all sketches. Just wondering what has changed in the new driver..
Thanks, DirkH
Hello,
im trying to build a Gateway based on ATMEGA2560 with W5100 Ethnernet Chip and RF69 Radio Module.
I'm using the stock GatewayW5100 from the MySensors Examples folder. Becuase I'm using a RF69 and not a NRF24 I disable the NRF24 driver and enable the RF69 Driver by (dis)commenting the specific lines.
However my Arduino 1.8.8 gives me an error message: 'class SoftSPI<16u, 15u, 14u, 0u>' has no member named 'setDataMode'. Arduino.cc says that setDataMode shall not be used anymore. I think something is screwed up here...
The debug output of Arduino says the following Versions are used:
Bibliothek Ethernet in Version 2.0.0 im Ordner: D:\Program Files (x86)\Arduino\libraries\Ethernet wird verwendet
Bibliothek MySensors in Version 2.3.2 im Ordner: D:\EigeneDaten\Dokumente\Arduino\libraries\MySensors wird verwendet
Bibliothek SPI in Version 1.0 im Ordner: D:\Program Files (x86)\Arduino\hardware\arduino\avr\libraries\SPI wird verwendet
Source of the Gateway Sketch (only put a comment on #define MY_RADIO_RF24 and removed comment from #define MY_RADIO_RFM69.
/*
* The MySensors Arduino library handles the wireless radio link and protocol
* between your home built sensors/actuators and HA controller of choice.
* The sensors forms a self healing radio network with optional repeaters. Each
* repeater and gateway builds a routing tables in EEPROM which keeps track of the
* network topology allowing messages to be routed to nodes.
*
* Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
* Copyright (C) 2013-2019 Sensnology AB
* Full contributor list: https://github.com/mysensors/MySensors/graphs/contributors
*
* Documentation: http://www.mysensors.org
* Support Forum: http://forum.mysensors.org
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License
* version 2 as published by the Free Software Foundation.
*
*******************************
*
* REVISION HISTORY
* Version 1.0 - Henrik Ekblad
* Contribution by a-lurker and Anticimex
* Contribution by Norbert Truchsess <norbert.truchsess@t-online.de>
* Contribution by Tomas Hozza <thozza@gmail.com>
*
*
* DESCRIPTION
* The EthernetGateway sends data received from sensors to the ethernet link.
* The gateway also accepts input on ethernet interface, which is then sent out to the radio network.
*
* The GW code is designed for Arduino 328p / 16MHz. ATmega168 does not have enough memory to run this program.
*
* LED purposes:
* - To use the feature, uncomment MY_DEFAULT_xxx_LED_PIN in the sketch below
* - RX (green) - blink fast on radio message received. In inclusion mode will blink fast only on presentation received
* - TX (yellow) - blink fast on radio message transmitted. In inclusion mode will blink slowly
* - ERR (red) - fast blink on error during transmission error or receive crc error
*
* See http://www.mysensors.org/build/ethernet_gateway for wiring instructions.
*
*/
// Enable debug prints to serial monitor
#define MY_DEBUG
// Enable and select radio type attached
//#define MY_RADIO_RF24
//#define MY_RADIO_NRF5_ESB
#define MY_RADIO_RFM69
//#define MY_RFM69_NEW_DRIVER
//#define MY_RADIO_RFM95
// Enable gateway ethernet module type
#define MY_GATEWAY_W5100
// W5100 Ethernet module SPI enable (optional if using a shield/module that manages SPI_EN signal)
//#define MY_W5100_SPI_EN 4
// Enable Soft SPI for NRF radio (note different radio wiring is required)
// The W5100 ethernet module seems to have a hard time co-operate with
// radio on the same spi bus.
#if !defined(MY_W5100_SPI_EN) && !defined(ARDUINO_ARCH_SAMD)
#define MY_SOFTSPI
#define MY_SOFT_SPI_SCK_PIN 14
#define MY_SOFT_SPI_MISO_PIN 16
#define MY_SOFT_SPI_MOSI_PIN 15
#endif
// When W5100 is connected we have to move CE/CSN pins for NRF radio
#ifndef MY_RF24_CE_PIN
#define MY_RF24_CE_PIN 5
#endif
#ifndef MY_RF24_CS_PIN
#define MY_RF24_CS_PIN 6
#endif
// Enable UDP communication
//#define MY_USE_UDP // If using UDP you need to set MY_CONTROLLER_IP_ADDRESS or MY_CONTROLLER_URL_ADDRESS below
// Enable MY_IP_ADDRESS here if you want a static ip address (no DHCP)
#define MY_IP_ADDRESS 192,168,178,66
// If using static ip you can define Gateway and Subnet address as well
//#define MY_IP_GATEWAY_ADDRESS 192,168,178,1
//#define MY_IP_SUBNET_ADDRESS 255,255,255,0
// Renewal period if using DHCP
//#define MY_IP_RENEWAL_INTERVAL 60000
// The port to keep open on node server mode / or port to contact in client mode
#define MY_PORT 5003
// Controller ip address. Enables client mode (default is "server" mode).
// Also enable this if MY_USE_UDP is used and you want sensor data sent somewhere.
//#define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 254
//#define MY_CONTROLLER_URL_ADDRESS "my.controller.org"
// The MAC address can be anything you want but should be unique on your network.
// Newer boards have a MAC address printed on the underside of the PCB, which you can (optionally) use.
// Note that most of the Arduino examples use "DEAD BEEF FEED" for the MAC address.
#define MY_MAC_ADDRESS 0xDE, 0xAD, 0xBE, 0xEF, 0xFE, 0xED
// Enable inclusion mode
#define MY_INCLUSION_MODE_FEATURE
// Enable Inclusion mode button on gateway
//#define MY_INCLUSION_BUTTON_FEATURE
// Set inclusion mode duration (in seconds)
#define MY_INCLUSION_MODE_DURATION 60
// Digital pin used for inclusion mode button
//#define MY_INCLUSION_MODE_BUTTON_PIN 3
// Set blinking period
#define MY_DEFAULT_LED_BLINK_PERIOD 300
// Flash leds on rx/tx/err
// Uncomment to override default HW configurations
//#define MY_DEFAULT_ERR_LED_PIN 7 // Error led pin
//#define MY_DEFAULT_RX_LED_PIN 8 // Receive led pin
//#define MY_DEFAULT_TX_LED_PIN 9 // Transmit led pin
#if defined(MY_USE_UDP)
#include <EthernetUdp.h>
#endif
#include <Ethernet.h>
#include <MySensors.h>
void setup()
{
// Setup locally attached sensors
}
void presentation()
{
// Present locally attached sensors here
}
void loop()
{
// Send locally attached sensors data here
}
@LastSamurai The SST25VF020B... should work fine with the 2.0 developversion and #define MY_SPIFLASH_SST25TYPE set. It seems to be very close to the SST25PF020B I used. However keep an eye on the even more limited voltage range of the SST25VF Type which needs at least 2,7V which would be a problem if you want to power your circuit directly by 2xNiMH Batteries.
The SST25VF512 needs also 2,7V but additionally does not support the 64k erase command (see my comments on that issue some posts above where I wrote something about the AT25F512).
About the AT25F512N wich was proposed by @AWI: tbowmo was right, I got confused by Sector, Page and Block erase. Like tbowmo said atmel does call blocks sectors... The AT25F512 does not support Block Erase 64k, which is defined but AFAIK not used in SPIFlash.cpp BUT it is used in the Bootloader if the "Imagesize" is > 32k. But I dont know how Image size is retrieved. Also I think for an ATMega 328p the image size should never be >32k. So this Flashtype could probably work as long as the image size is below 32k. I'd expect the Bootloader to crash or fail when program size is >32k.
About the S25FL... @bjacobse proposed I see the problem that it does not support the Bock Erase 32k opcode which is used in SPIFlash.cpp and Bootloader. Both must be changed when S25FL... should be used. (I would emulate the 32k Block erase by 8 times 4k Block erase.) However remember that Dualoptiboot must also be altered which requires "non-arduino" programming and some work / knowlegde about makefiles / compiler/linker settings in IDE.
@AWI
The AT25F512 (from Atmel?) is quiet different from the Adesto AT25DF512. As far as I can see the Atmel one seems not to have a Block erase command (32k/64k), which is used in MySensor AND in Bootloader code.
If I'm not wrong with that assumption (and I dont think I am), I would NOT recommend to use the Atmel AT25F512.
To all: please provide links to the Datasheet if you expect help... Its tedious to search them every time. Gulpman did great preparation work in his post above.
Edit: Never mind what I said in this Post. I got confused with sectors pages and blocks 
... I'll write some more later.
Yes the AT25DF512 seems to outperform other memories and is truly a good chip. However unfortunately its hard to get in Germany (and maybe other parts of the world ). The common distributors here do not have it in stock...
@tbowmo
I looked at the defines inside the DualOptibootloader, I truly hope that there is no "hardcoded" opcode hidden somewhere... Assuming this, dualoptiboot does not write to the SPIFlash. It does erase, however thats not writing in this scope
#define SPIFLASH_STATUSWRITE 0x01 // write status register
#define SPIFLASH_STATUSREAD 0x05 // read status register
#define SPIFLASH_WRITEENABLE 0x06 // write enable
#define SPIFLASH_ARRAYREADLOWFREQ 0x03 // read array (low frequency)
#define SPIFLASH_BLOCKERASE_32K 0x52 // erase one 32K block of flash memory
#define SPIFLASH_BLOCKERASE_64K 0xD8 // erase one 32K block of flash memory
#define SPIFLASH_JEDECID 0x9F // read JEDEC ID
@Koresh please post a link to the datasheet. You can also check on your own: check if your spi-flash supports all commands listed in the SPIFlash.h defines. Of cause obvious things such as pinning and supply voltage range must also be checked.
A caveeat I fell into, was that opcode 0x02 supports byte and pageprogramming for some SPI-Flash types but not for all (e.g. SST25 does not support pageprogramming but therefore has the AAI Wordprogramming feature).
@tbowmo
I tested the complete chain with SST25. I.e. I prepared two sketches and uploaded them via OTA with MYSController and checked that the sketch changed via presentation Message.
Dual Optiboot does not need modification because AFAIK it only reads from Flash, which works the same way for SST and other Flash Types.
@Gulpman @hek
Hello everybody,
I just added a pullrequest which will support SST25 Series flash for OTA Bootloader:
https://github.com/mysensors/Arduino/pull/445
SST25 Series flash mentioned by Gulpman as 1st and 2nd Alternative are currently not supported, because the dont support pagewriting with opcode 0x02. Instead they support Automatic Address Increment Word writing (opcode 0xAD). I updated teh SPIFlash.cpp and .h so they will take care of that if #define MY_SPIFLASH_SST25TYPE is set somewhere.
I tested with this SPI Flash: http://www.reichelt.de/25PF020B80-4C-S/3/index.html?&ACTION=3&LA=446&ARTICLE=137365&artnr=25PF020B80-4C-S&SEARCH=25pf020b80 which is of Type SST25PF020B-80-4C-SAE (2MBit) and working now.
I only hat a short look at the ISSI and Winbond flash Datasheets mentioned by Gulpman before. At first look I think they both could work with the current Mysensors / SPIFlash Version becuase they support Pagewriting with opcode 0x02 and seem to implement the other relevant opcodes. However I did not test..!
Best Regards
DirkH / D-H-R 
-edited on 2016-06-01 to take care of changed Name for define (added "MY_")
@Anduril I had problems with 8MHz with 3,3V and 115200kBPS. I only use 38400kBPS with my 8MHz nodes. (Of cause your Bootloader must also be set to the same Baudrate as specified in the board.txt, they must match, i.e. you cannot just change the Boards.txt and have another Baudrate for programming.)
I'm not sure if @tekka is providing a Bootloader hex file with 38400kBPS and 8MHz. From his first post I'm assuming he ueses a 57600kBPS with 8MHz. This might also work, however 57600kBPS with 8MHz introduces a baud rate error of 3.5% which sometimes causes problems with my PC/FTDI Dongle. So I personally use 38400kBPS which only has 0.2% Error: http://wormfood.net/avrbaudcalc.php (fosc=8MHz)
@gonzalonal @tekka
Yes I can confirm the exact same behaviour gonzalonal describes. Please say if you need any more details tekka (with the @ function).
@hek Thank you very much. I found out most of it the hard way (reading code and die trying). I did not found the document which wold have helped me very much. Is it mentioned in the Github Repo? Maybe you should put a link to it in the readme .md?
Glad it helped David. I just thought about it again, maybe sleep(0xff, 0x00, 0) does work too. I did not test it but I think it calls the same function anyway.
However the method of direct calling sleep(0xff, 0x00, 0xff, 0x00, 0) should save some clocks because one less jmp is required
1st you need to make sure that there is an active interrupt that wakes up the controller, otherwise the microcontroller will sleep forever.
To solve your above Problem: remove the lines "sensor_node.RF24::powerDown();" and "LowPower.powerDown(SLEEP_FOREVER, ADC_OFF, BOD_OFF); //power everything down, wake up only by (PinChange) interrupts".
Replace with "sleep(0xff, 0x00, 0xff, 0x00, 0);"
Remember the things I mentioned above!
I'd try where the problem is, but I dont even get the MySesors class up and running. Is there already any API Reference/Documentation/Example for MySensors 2.0?
@drock1985
Hi good to hear that you found it out. I just made a third channel and in the message handler i react on both dimmer channels if a message with the third sensor is incoming (in my case sensor 0 for both channels; 1/2 for sepearte channels)
However maybe its better to do the coupling of the channels in your home-automation.. I did it this way because maybe I want to build a remote and it should have the possiblity to set both channels with one mysensors message.
regards
DirkH
@drock1985 What exactly do you need? In the project I mentioned is currently some more stuff with some dirty hacks I don't want necessarily to share
I think you only need the incoming message handler, or do you need more?
@siklosi could you please share your makefile and describe your building environment (linux? which packets installed?). I stil dont get any success... 
Hi DrJeff,
you need to check if the message you got was for the first or second relay/child. I did something similar recently for a two channel dimmer. However I wanted also to be able to set both channels at once. So in the following exapmle child 0 means set on both channels, and 1 or 2 at the appropriate channel.
Maybe my code excerpt can help you.
if (message.type == V_LIGHT || message.type == V_DIMMER) {
if (message.sensor <= 2){
//0: All Dimmers
//1: LED 1
//2: LED 2
// Retrieve the power or dim level from the incoming request message
int requestedLevel = atoi( message.data );
// Adjust incoming level if this is a V_LIGHT variable update [0 == off, 1 == on]
requestedLevel *= ( message.type == V_LIGHT ? 100 : 1 );
if ((message.sensor == 1) || (message.sensor == 0)){
fadeLEDToLevel( requestedLevel, LED1_PIN );
// Inform the gateway of the current DimmableLED's SwitchPower1 and LoadLevelStatus value...
gw.send(Light1Msg.set(requestedLevel > 0 ? 1 : 0));
gw.send(Dimmer1Msg.set(requestedLevel) );
}
if ((message.sensor == 2) || (message.sensor == 0)){
fadeLEDToLevel( requestedLevel, LED2_PIN );
// Inform the gateway of the current DimmableLED's SwitchPower1 and LoadLevelStatus value...
gw.send(Light2Msg.set(requestedLevel > 0 ? 1 : 0));
gw.send(Dimmer2Msg.set(requestedLevel) );
}
if (message.sensor == 0){
gw.send(Light0Msg.set(requestedLevel > 0 ? 1 : 0));
gw.send(Dimmer0Msg.set(requestedLevel) );
}
}```HI,
I don't get it running.... 
At the moment I dont know what I could do. Im trying to build it with the avr-gcc that came with arduino 1.6 and MySensors 1.4.2. Maybe it just dont works with Arduino... I dont know.
Can anyone at least sayif it should be "-x c" or "-x c++"?
I get tons of "conflicting declaration 'typedef uint8_t boolean" and error: redeclaration of 'RF24_PA_LOW'. maybe I'm including too much or the wrong things?
My current command for use with ARduino 1.6 environment (of cause I'm not actually using Arduino) is
"D:/Program Files (x86)/arduino-1.6.1/hardware/tools/avr/bin/avr-gcc" -x c++ -mno-interrupts -funsigned-char -funsigned-bitfields -DF_CPU=16000000L -Os -DARDUINO=10601 -fno-inline-small-functions -fno-split-wide-types -ffunction-sections -fdata-sections -fpack-struct -fshort-enums -mrelax -Wall -mmcu=atmega328p -c -std=gnu99 -MD -MP -MF "MYSBootloader.d" -MT"MYSBootloader.d" -MT"MYSBootloader.o" -I../libraries/MySensors -I../libraries/MySensors/utility -I"D:/Program Files (x86)/arduino-1.6.1/hardware/arduino/avr/libraries/SPI" -I"D:/Program Files (x86)/arduino-1.6.1/hardware/arduino/avr/cores/arduino" -I"D:/Program Files (x86)/arduino-1.6.1/hardware/arduino/avr/variants/mega" -I"D:/Program Files (x86)/arduino-1.6.1/hardware/arduino/avr/cores/arduino/WInterrupts.c" MYSBootloader.c -o MYSBootloader.o
Any help (still) greatly appreciated.
Dirk H.
@Oitzu said:
[..]
CFLAGS = -x c -mno-interrupts -funsigned-char -funsigned-bitfields -DF_CPU=$(CLK) -Os -fno-inline-small-functions -fno-split-wide-types -ffunction-sections -fdata-sections -fpack-struct -fshort-enums -mrelax -Wall -mmcu=$(MCU) -c -std=gnu99 -MD -MP -MF "$(@:%.o=%.d)" -MT"$(@:%.o=%.d)" -MT"$(@:%.o=%.o)"(There is a space missing in fron of the -Os option.)
I already found the space before the -Os, but I'm wondering that the -x c argument is ok..? I left it like that at first but got an error message that "class" in an unknown variable type or something like that. This sounded ok for me because in plain c there are no classes. So I thought I've to switch to -x c++. Any Ideas about that? Or shouldn't it reallly matter?
At the moment I tried with MYSensors 1.4, where it complains that it cannot find <SPI.h> . I've to search for that one as I dont know where the compiler gets libraries that are in <>. As already said I'm really a rookie in this area...
See you later, hopefully
Hello,
I'm trying to make / build the MYSBootloader. There seem to be various problems with the make file and maybe also some parts of the code?
I altered the makefile:
1.) changed BINPATH to my bin path (obviously good idea).
2.) I commented out the Java stuff, since it is not used and I dont have Java installed
3.) I added the ../libraries/MySensors/utility folder to include because nRF24L01.h was not found (btw. is this ok?)
4.) I had to change the -x c to -x c++ because I assume c++ is used (class type is unknown to c)
5.) I exchanged #include arduino.h and Wprogram.h to #include <stdint.h> #include <stddef.h> #include <stdlib.h>
now my avr-gcc command is:
"D:/Program Files (x86)/arduino-1.6.1/hardware/tools/avr/bin/avr-gcc" -x c++ -mno-interrupts -funsigned-char -funsigned-bitfields -DF_CPU=16000000L -Os -fno-inline-small-functions -fno-split-wide-types -ffunction-sections -fdata-sections -fpack-struct -fshort-enums -mrelax -Wall -mmcu=atmega328p -c -std=gnu99 -MD -MP -MF "MYSBootloader.d" -MT"MYSBootloader.d" -MT"MYSBootloader.o" -I../libraries/MySensors -I../libraries/MySensors/utility MYSBootloader.c -o MYSBootloader.o
It starts to compile but I get tons of errors, some examples:
MYSBootloaderHW.h:21:17: error: redeclaration of C++ built-in type 'bool'
MYSBootloaderRF24.h:7:30: error: redeclaration of 'RF24_PA_MIN' (actually the whole typedef rf24_pa_dbm_e seems to get redeclarded)
Can anyoune (@tekka) give me some hints what I'm doing wrong? Usually I use Atmel Studio where I dont have to bother with makefiles, so I'm no expert here.
Thanks for your help
Dirk H.
Ok, finally I found the Problem.
I changed the prescaler value of Timer0 becuase I needed a higher PWM Frequenciy.
Unfortuneatly this also affects the millis() function that is used in gw.wait.
It turns out taht with the changed TImer 0 Prescaler 1ms was not 1ms anymore but less. So the gw.wait(750) where only 750ms/64 which is not enough for DS18S20 conversion to take place.
Hi,
pls do a quick (picture) search for "pullup resistor". It should become clear then. Yor are likely to put it at the microcontroller because you would need 3 cables to your door key when putting the resistor somewhere else
Hi, I'd deactivate the internal pullup when using an external one. But it shouldn't really matter (the internal pullup would just be in parallel with the external one, reducing its value somewhat).
If the external pullup does not work, please check the resistance of the wiring when button is not pressed (shuld be infinite) and when button is pressed with a multimeter.
Hi,
I assume you use internal pullup from the Arduino and switch to GND with the switch?
In this case you can try to use an external pullup (with dedicated resistor). I'd start with 1k and then try 470Ohm.
If this does not fit your quetion, please try to make a small sketch / diagram about your actual circuit. So we can give more precise answers
Greetings
DirkH.
Hello everybody,
I'm trying to transmit temperatures from 1Wire 18S20 Sensors via MySensors. However MySensors just works fine, but I always get old Data from the 18S20 Sensors using onewire and DallasTemperature libs.
I Transmit and get the temps in the following manner
TempSns.requestTemperatures();
gw.wait(750);
for (i=0; i<j; i++)
{
uint8_t Adr[8];
temperature = TempSns.getTempCByIndex(i);
Serial.println(temperature);
gw.send(TempVals[i]->set(temperature,1));
}
However when I use a lighter to heaten up the Temperature Sensor I first get the old value. I have to request a second sample to get the "real value".
Is anyone able to help me, please
Thanks so much
Dirk H.
THanks! it worked for me too!
@hek Maybe we should put a small hint about this (first delete old MySensors 1.4) on the Downloadpage?
@Fabien
I dont understand what you mean by "I told MysController" that the node is battery powered. It should find that out automatically I think. Anyway I'm pretty sure that I read somewhere that battery powered sensors cant be updated OTA. (If it relly is battery powered). I think I read a define somewhere that disables the firmware low level commands in the MySensors Library if the Node is battery powered.
@gloob
same here. Has left on 04.06.2015 - no more info. Also on local post service (link below on hk post) no entry.
As I live in Germany and the post is on strike and our customs work with "german gründlichkeit" I dont expect it to arrive too fast...
@pjeterinfo said:
After some troubleshooting I tried allso IDE1.0.6 which gives me a more clear error message:
Binaire sketch-grootte: 15.754 bytes (van een 14.336-byte maximum?
ATMega 168 is too small on memory as the error message clearly indicates. It has 16k Flash memory for program where some is needed for the bootloader which is round about 2k 16-2 = 14k. The sketch is 15.7k big which does obviously not fit into 14k. You need 32k ATMega like ATMEGA328p on Arudino nano/uno.
There are some efforts of some people to strip down the libs to fit into smaller devices. However especially in the beginning I'd recommend to not spend this effort.
it also amplifies received signals, which works very well. I cover my whole flat (100m²)with this version for the gateway (and only the gateway, rest ist normal nrf24l01 modules)
The non PA/LNA was not able to get into all corners of the flat.
AFAIK PA stands for Power Amplifier (meant for TX) and LNA for Low Noise Amplifier ( meant for RX).
@marceltrapman
when you change the BAUD rate setting in the source/config file to something lower/other you can also use 3.3V Arduinos as (Serial)Gateway. Of cause your controller needs also to be told about the lower BAUD rate.
Check out http://wormfood.net/avrbaudcalc.php?postbitrate=9600&postclock=8 for an overview of Clockspeeds (usually 8MHz for 3.3V and 16MHz for 5V types) and coresponding BAUD rates.
@ServiceXP @Stric
I can confirm the problems of Stric. I also had them some months ago. see here http://forum.mysensors.org/topic/824/mysensors-serial-gateway-minimal-example-to-send-data/6
@axillent
do you know anything how debugging in Eclipse with Arduino is supported?
I find major disadvantage of Visual Studio with Arduino/Visualmicro is that "real" HW-debugging through JTAG/1Wire is not possible easily. I'm not sure if this is really that complicated or if visulmicro just wants to sell their SW debugging tool.
I also built a 6way wall switch. It does not have lights but is battery powered and very well documented. It is kind of rocket science because it has a 3d printed housing and a self etched pcb but maybe it helps anyway at least for the (very easy) source code:
@jaumard
yes nrf24L01+ works fine. in fact only the plus version works fine because mysensors typically uses the slower but more power effective 250kbps mode which was introduced with the + version. Older version (without +) needs some tweaks to work..
@phil83
I fear you've already ordered the ATSHA204A ? I'm also in Germany so that would be easy.
If not - I'd take 10 pcs. They cost close to nothing -> nice
@Anticimex
I don't agree with "This is an unlikely usecase because it is really no reason to sign sensor values. If you for some reason want to obfuscate sensor data, encryption is a better alternative."
I think of Sensors used for Alarm-Systems. You need to trust the sensor reading because otherwise the attacker might jam the original Sensor and send his own Sensor data to let the alarm-system think the window is still closed (e.g.).
One more question: Are the Serials in the ATSHA in ascending order (i.e. when you have a reel of ICs is each S/N old S/N+1 ?) If this is the case, would it be possible to steal a keyfob to get a valid signing device, read the serial, use that S/N +1, sign the message and get still access to the garage door? I.e. do something one could call "S/N spoofing"? (I know that it is much easier to just break the garage door with a crowbar, but I'm intrested in this - at least hypotheticaly :))
Unfourtunately I don't have much time at the moment to try it out by myself, but I'm still really excited about your work and effort!
@scalz
Hi, regarding you first qeustion I'll copy somehting from my Project Documentation from the Wall Remote below.
I dont really understand your second question. If you enable the interrupts on pin5 and pin6, the interrupt will always be triggered if the pin changes its voltage level... It can obviously not discover what caused the voltage level only that it did.. But I fear I do not understand exactly what you mean..
To wake up the controller from sleep mode, which is used to save power, the PinChange Interrupts
have been used, but Arduino compiles also the MyGateway.cpp where PinChange interrupts also
have been used. Because every Interrupt Vector is only allowed to be once in the compiled code this
is a problem.
However the workaround for this is to rename the “MyGateway.cpp” from the “{Arduino
Sketchbooks}\libraries\MySensors” into something the compiler does not try to compile e.g.
“MyGateway.cpp.nolib”. Remind to undo this renaming if you want to compile a MySensors
Gateway!
You find the {Arduino Sketchbooks} location by “File-Prefernces” in the Arduino IDE.
When the files have been renamed it is possible to compile the WallRemote sketch. When
everything is connected like shown above you can also download the sketch to the hardware. For
the download the correct Board and COM port must be selected. Make sure the
“Tools->Board->Arduino Pro or ProMini (3.3V, 3.6864 MHz) w/ ATmega328” is selected. This
board has been added earlier to the Arduino environment in section 2.7.
@fot said:
Yes, I'm using 2x1.5V and it seams to work well..
The card uses around 30uA (+- the precision of my multimeter) in idle/sleep and that should give a pretty long run time on batteries.
I have nodes that has been online since before Christmas and still going strong.
/Magnus
Have you something else connected than Arduino and NRF? Any Sensors or Powersupply? I got down to below 4uA with Atmega and NRF sleeping, measured with Agilent precision desktop multimeter. (Nothing else connected because it was a remote with only buttons). If you have your ATMega in deepsleep you should have less than 10uA (datasheet says so). Just seeing that you use the Arduino Pro Mini. I used dedicated ATMega w/o Arduino HW... Anyways 30uA is also quiet good I think. it should give you more than a year stand by time (theoretical).
(800mAh Battery / (30uA circuit + 30uA self discharge) /24h = 555 days)
If you look at the Netatmo devices you can see that they have plastic caps and a long plastic notch. I'd bet that the antenna can be found in such an area...
I dont think that a small thickness will help to let the radio signal pass. Think of that very thin µ-metal sheet covers on high frequency circuits e.g. in TV or Radio inputs (where you want to stop a radio transmission). They are built to not let radio waves pass and they are thin - so I dont think the thickness plays a major role. As Bulldog wrote paramagnetic blocks radio waves. And aluminum stays paramagnetic even if you reduce the thickness.
But I made the experience that relatively small areas, where the radio waves will not get blocked (e.g. plastic caps) can make the difference between no signal and "its working". Also keep in mind that nearly all antennas have a direction. So changing the orienation of the antenna might dramatically change the transmitting capabilties.
I want also say thank you for the congratulations. I hope that the project will help some people to go on with MySensors and their Home Automation system or whatever they want to switch with MySensors
I'm already working on the next projects, altough they are not directly MySensors related (Raspberri Pi USV, Reflow Oven controller).
Ok thanks for clarification Anticimex. I meant if you have a remote to open your garage and leave it in your car which e.g. gets stolen. However it good that you pointed out that locking the device is no "must". I think in many applications it might be even contraproductive.
locking the device would only prevent the thief from copying but not from using - Which would have higher importanance in this case. Maybe this lokcing feature is generelly more used for dongle like applications.
@Anticimex Wow this is really good work AND explanations.
I'm thinking about one issue: Lets assume I use a remote as garage opener. Now on a bad day I loose this remote. Is it possible to block the commands of the remote. I.e. have a blacklist like thing? Is it even possible to (in theory with the used components and in practise with the current code) to identify each SHA device? I.e. does Bob know "the message comes from someone I turst" or does he know "the messages comes from allice (which I trust)".
Obviously I'd be unable to change the PSKs because I need to lock the PSK Memroy area... So I'd have to throw away all devices for this approach - right?
Thanks for your great work again.
Hello everybody,
finally I manged to contribute my Project to the MySensors Contest 2015.
It is a 3d printable Wall Remote control for Home Automation. The Size is 55x55mm, so it fits into many "switch frames" (e.g. Berger, Gira, Merten etc.) The project consists of the 3d printed Parts, the PCB (with Eagle sources), the Sketch, an FHEM example and of cause a detailed documentation which describes howto rebuild this Project on your own. All this is included in the zip file I will provide.
Because the pdf, where the building is described precisely, is quiet long (20 pages I guess, but many photos) I don't want to put it here in the post. If you are intrested in the Project just have a look at the pdf inside the zip file. There are also more pictures included.
To finish this project you need the following equipment/skills: 3D printer, SMD soldering capabilites, AVR Programmer (to install bootloader)
Enough of talking, lets let the pictures speak for themselve:
A 3d preview of the printer parts can also be found on Thingiverse: http://www.thingiverse.com/thing:692238
I'm looking some days into this topic, although I found not the time to test your very good looking software - The issue mentioned by dzairo would also be important for me. As I run my nodes at 8MHz I cannot use the default 115200kbps and use (also) 38kbps - so it would be important for me to change the BAUD rate too.
Anyways - nice work!
Hi,
I'm not 100% sure especially for Ethernet but shouldn't the string to send be:
"20;1;1;1;2;0\n" (no trailing semicolon at the last argument).
You can also check if the output of ASCII.GetBytes is ok. \n should get a 10 (dec). But this should work I think.
It is relatively easy to send a command to an existing node (you can do this via serial monitor and a gateway node or even with any other mysensors node). But you did not write the setup of your system. Who will send the command (the fhem gw node)? which node will receive (another node especially for controlling the relais)? I did not get who shall do what with which ressources..
Thanks for sharing your project, very nicely documented. I don't have a real use for it at the moment but enjoyed very much to read a complete solution beginning with hardware and ending with FHEM.cfg code. Good Work! 
Best regards
Dirk H
hi amitach
I'm not sure if you have already seen this - I think this answers your question:
http://www.mysensors.org/about/network
I'm not sure but I think I read somehwere that a packet will do max. 5 hops per default? As said I'm not sure about this...
Hello,
Can I use the Pinchange Interrupts (PCINT), which are available for every Pin, to wakeup the Arduino/MySensors module?
I think I read in a Sketch which uses Sleep Mode that only the "real" 2 Interrupt pins can be used.
Is this true? I also think that I saw a sketch somewhere where someone used the pinchange Interrupts to wake up (but it was not in conjunction with MySensors I think).
Anyway has anybody tried to use PinChange Interrupts or can give some more Information on that topic?
Tanks in advance
Dirk_H
Hi,
it would also be possible to just use a Timer and Interrupt. This might be not as flexible as using the time as reference but you dont have to deal with getting the RTC from the gateway etc.
For an example have a look at:
http://playground.arduino.cc/Deutsch/HalloWeltMitInterruptUndTimerlibrary
regards
Dirk_H
I'd use a DCDC Step up converter (there is a 1-5V to V mentioned in the MySensors shop).
For a 5V device I'd not connect directly to the batteries, because the voltage might drop below 5V although the batteries are still far away from beeing empty. You don't want your approach with the diodes (or any other linear voltage regulator) because it wastes expensive energy to produce heat (In order to get the higher voltage down).
With 3.3V Device I'd (and will in the near future ) try to just use two batteries (without regulator). They'll have 3V max. Voltage and Adrduino Pro mini / nrf24l01 work down to 1.9V - so most if not all of the charge from the battery can be used. (rechargeable batteries shouldn't go below 0.8V so this fits quiet nicely (2*0.85 = 1.9).
Additionally I think it might be easier to use the 3.3 V Arduino over the 5V, because more lowpower people use it and because the power consumption typically drops if you use less voltage as long as we are talking about some mA. E.g. Modern CPUs are working <1V to keep down the (thermal) losses.
As a last sentence: Designing real low power and battery applications is hard work. It is dependet on sofware but also -maybe somewhat more- on hardware. You must design/find a power supply that matches the application very well and have to think of the parts of your sensor/circuit you can / must switch off. Maybe some of them must be switched off in hardware (cut power supply). Then it is part of the software to re-enable them in the correct sequence and with proper startup times to have everything work.
However for a start I'd recommend to try the mentioned ste up converter. But I fear it has a relative large quiescent current because it is able to deliver 500mA which is much. Maybe someone else knows some modules that suit better and have a defined quiescent current.
Best regards
DirkH
@tbowmo I don't see a Load Capacitor on the crystal. Especially if you need a precise clock you should use some. Have a look at https://www.adafruit.com/blog/2012/01/24/choosing-the-right-crystal-and-caps-for-your-design/ for example about Load Capacitors.
If you create a temperature sensor you should also have in mind the thermal performance of the battery you are using.
If you are in for rechargeable batteries: Lithium-Polymer will have the highest energy density AFAIK. However tehy perform bad with low temperatures. I'd probable do some research with LiFePo4 technology which performs better when its cold and also they are somewhat more robust.
I once worked for a company which developed sensors and such stuff to be used on the seas floor. They used Saft LS Lithium batteries - however they have not been rechargeable (nothing there to charge it with at some 1000m depth under water 
)
regards
Dirk_H
I'd recommend to buy all leds that you plan to use in a single shot because leds will have slightly different colors even when buying quality ones. If you have a look in the datasheets of e.g. osram leds you see that there are more than 20 different colors (shades of white). If you buy 1000 of leds you are able to choose exaxtly matching colors. But we as normal people are dependent on the distributor. That means you should get closely matching colors if you buy your leds in a single shot... at least the ones you will see at the same time.
best regards
One last thing I'd like to clarify after re-reading my previous post.
The correct send string I entered in the terminal is without trailing ";" - like it was supposed before. As mentioned, the problem has been the BAUD rate of 156k with 8MHz crystal..
So the correct command which will change the PWM -Dimmer level on node 3 to 50% is:
3;0;1;0;3;50\n
Hmm ok, without the last semicolon nothing works - it does not try to send.
I forgot to mention that I use a Arduino mini pro 3.3V @ 8MHz. Somewhere I read that the gateway should have 16Mhz- but because everything else (i.e. receiving) worked, I thought 8MHz would also work..
Because of that I tried an Arduino Nano running on 16MHz -> and THIS WORKS.
If one changes the MySensors.h Baudrate to e.g. 38400 than everything also works fine with the 8MHz.
However I think it is a very bad behaviour that receive works 100% fine but send not, evil computers 
BTW, can I also change the lib files when working in a cloned codebender sketch?
Thanks for your support!
Ok I tried to send the suggested messages:
3;0;1;0;4;50 (without semicolon) : nothing happnes, i.e. the gateway does not even try to send (tx led also not blinking, although rx light on ftdi usb->ttl chip is blinking)
3;0;1;0;4;50; (with semicolon) returns "0;0;3;0;9;send: 0-0-3-3 s=0,c=0,t=0,pt=0,l=1,st=ok:" on gateway and "read: 0-0-3 s=0,c=0,t=0,pt=0,l=1:\n" on the dimmer node
Exaclty the same readings for 3;0;1;0;3;50; in case you menat 3 instead of 4 (the latter 3)
3;0;1;1;3;5 does not work (does not work with semicolon at the end and does not work without it)
3;0;1;1;3;50; retruns the same messages as the 3;0;1;0;4;50;
Thanks for your efforts, I really hope that we can find the mistake. However may I assume that in principle it should be possible to send from the serial gateway with a terminal program as I proposed?
Hello everybody,
I'm just trying the MySensors protocol stack. I thought the easiest way to get it work and understand would be to have to nodes: one serial gateway and one dimmer.
I then thought i could connect the serial gateway to my favorite terminal program and see what the nodes are talking, I also thought that i should be able to send commands.
So I set everything up and I get the incoming messages on the serial terminal program:
0;0;3;0;14;Gateway startup complete.
0;0;3;0;9;read: 3-3-0 s=255,c=0,t=17,pt=0,l=5:1.4.1
3;255;0;0;17;1.4.1
0;0;3;0;9;read: 3-3-0 s=255,c=3,t=6,pt=1,l=1:0
3;255;3;0;6;0
0;0;3;0;9;read: 3-3-0 s=0,c=0,t=4,pt=0,l=5:1.4.1
3;0;0;0;4;1.4.1
0;0;3;0;9;read: 3-3-0 s=255,c=3,t=11,pt=0,l=11:DimmableLED
3;255;3;0;11;DimmableLED
0;0;3;0;9;read: 3-3-0 s=255,c=3,t=12,pt=0,l=3:1.1
3;255;3;0;12;1.1
0;0;3;0;9;read: 3-3-0 s=0,c=2,t=3,pt=0,l=0:
3;0;2;0;3;
This looks quite good to me. However now I want to send something so I type
3;0;1;0;3;50;\n
(of cause the \n is sent by the terminal program, i.e. it is the linefeed)
I expect this means send to node 3, childid 0, set command (1), no ack (0), V_dimmer type (3); value : 50
Then the DImmer node also seems to receive something because it says
read: 0-0-3 s=0,c=0,t=0,pt=0,l=1:\n
However I cannot see any changes in the brightness of the conneced LED. I also dont understand why:
3;0;1;0;3;99; does not work??!
I think I have something clearly missunderstood about any of the concepts? I hope you can help me.
Thanks
Dirk_H