Development

@MikeF I don't have access to the code now, but you are probably right. I need to copy the whole enum, selectively copying doesn't work.

thanks to all your contributions, it becomes clear for me.

I'm so sorry for such late reply... the reason i wanted no for loop was to see how the code for that would turn out... I have a project in mind with requires maybe 2 switches and if one is turned on then regardless of the message coming from controller for the second light it should stay off...

I verified a variable named Voltage DOES get created and is set on the Vera arduino node device if I create MyMessage with: MyMessage voltageMsg(255, V_VOLTAGE); and send value with: send(voltageMsg.set(12.1, 1));

Yes, that's what it for, to allow you to change the frequency... If you have interference, other networks or other devices in the band. In the US, the 915 MHz ISM band is 902 to 928Mhz, the 433MHz band is 433.05 to 434.79 (not very big, unless you have a Ham License, then its 420 to 450MHz)

Agree with @mfalkvidd and most of the times im even more ungentle (is that even a english word?). I just out my soldering iron, heat the led/regulator up and push them away with force.

Hi. I have some progress. I can see data coming in terminal ... [INFO] [ runtime.busevents ] - Arduino state updated to 0;0;1;0;4;1009.0 0;1;1;0;0;22.0 0;2;1;0;1;61.0 and keep updating... (only 3 nodes so far) However on website still nothing... I assume there is something wrong with openhab config. What I did... Added serial bindings from this link ( http://forum.mysensors.org/topic/655/serial-gateway-connection-to-openhab/3 and updated demo.rules accordingly and also had to remove ... @115200 from demo.items - { serial="/dev/ttyACM0@115200" }

@Stric Good to know! I don't have this kind of problem because I use a Atmega328 with external 16MHz clock. The Sensebender Micro uses internal clock and run as low as 1MHz, so there is your problem.

Sorry, I don't know why you added ,0. :stuck_out_tongue_winking_eye: For some of the msg setters, the second argument is used to specify length (buffer) or number of decimals (float). Please read through the API: http://www.mysensors.org/download/sensor_api_15#the-full-api

Mo ha ha... I will take over ALL your sensors. :) [image: 1456263063095-dr_evil-646x363.jpg]

My memory is sh*t.... i even replied to this relevant post! http://forum.mysensors.org/topic/812/realtimeclockdisplaysensor-ino-no-fetch-time-from-controller/6

Here are the defines I put in my sketches for the development library: //#define MY_NODE_ID 1 //#define MY_PARENT_ID 0 // Possible values for Arduino IDE: 9600, 19200, 38400, 57600, 74880, 115200, 230400, 250000 // The last three values are only possible if the mcu works at 16Mhz or more, not possible for 8MHz operation. //#define MY_BAUD_RATE 57600 //#define MY_RADIO_NRF24 //#define MY_RADIO_RFM69 // Enable serial gateway //#define MY_GATEWAY_SERIAL // Enabled repeater feature for this node //#define MY_REPEATER_FEATURE // Flash leds on rx/tx/err //#define MY_LEDS_BLINKING_FEATURE // Set blinking period //#define MY_DEFAULT_LED_BLINK_PERIOD 300 // 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 //#define MY_DEFAULT_ERR_LED_PIN 5 // Error led pin //#define MY_DEFAULT_RX_LED_PIN 6 // Receive led pin //#define MY_DEFAULT_TX_LED_PIN 7 // the PCB, on board LED // possible values: RF24_PA_LOW (is default on gateway), RF24_PA_MED, RF24_PA_HIGH, RF24_PA_MAX (is default on nodes) //#define MY_RF24_PA_LEVEL RF24_PA_HIGH // RF channel for the sensor net, 0-127. Channel 76 is the default in all library examples //#define MY_RF24_CHANNEL 76 //RF24_250KBPS for 250kbs (default), RF24_1MBPS for 1Mbps, or RF24_2MBPS for 2Mbps //#define MY_RF24_DATARATE RF24_250KBPS

No, I wasn't aware of the ESPEasyMySensors PoC. Nice. And if you implement a "super"-gateway that one would gather information from all of the others? Haven't really thought it through enough to say if it is realistic or worth the trouble. I mean data can flow directly from a ESP node to the controller. Why bother implementing another failure source by routing them through a single gateway. Unless you mean taking advantage of the Ad-hoc network features of WiFi to get more distance/coverage out of it.

@hek, I suspect that there is something wrong with this pull request. If you just returning true, then protocolParse() will not be called and gatewayTransportReceive() function in MyGatewayTransport.cpp will receive previously parsed message.

Hello folks. There is any plan to include into mysensors the LoRa RFM95 ,96? I am currently testing one those modules at 433mhz with RadioHead library. I had conducted some test in suburban environment and getting around 1.8 miles range. I pretend to apply this for remote water pump control monitoring in farms. I still want to try the rfm69 and see how much range I can cover . Any advice will be highly appreciated. Regards

@jeylites I just put mine into My Documents/Arduino/Libraries

@choffmann Thanks a lot! Please let us know you if the update solved your issue.

I'm in favor of this. I would add Item 6: Have (configurable) symbolic names for the values. I' using the gateway with FHEM where readings are automatically created and symbolic names are much easier to handle than the raw numbers. I've pacthed that in the version I'm using, but a general approach would be great.