@billgoolsby the gateway could probably be called event-driven but that's not why there is no need for additional code. The concepts are described in the getting started guide, which starts at https://www.mysensors.org/about

@brettzky84 said: Im using the serial gateway on u17 and have it working fine. i have the same problem as you when my vera is rebooted or powered off, but found 2 solutions. 1 with the vera on disconnect then reconnect the serial gateway. wait 10seconds refresh the dashboard page. Then go to app/ developer apps/ serial connection. Reset your baud rate to 115200??... Thansk. I ended up upgrading to the latst UI7 beta. My gateway is now working!!! Let's see how stable it is. (UI7 has fixed some of my other issue too)

Managed to find out a solution by myself. removed the three #define NO_PORTx_PINCHANGES removed the #include <PinChangeInt.h> changed PCintPort::attachInterrupt(pinInclusion, startInclusionInterrupt, RISING); to attachInterrupt(1, startInclusionInterrupt, RISING); Now I am able to use the Seeedstudip GPRS shield pins 7 and 8 with SoftwareSerial.

@catcher Thanks, I tried this Perl script and it is working out of the box with OpenHAB2! And I'm sending with MySensors 2.

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

No, youre right, that wouldnt work for battery powered. I chop the ends off old cell phone chargers and try to keep a room's sensors down to a single box. The only one I've considered being battery powered is the "Mailbox opened" one but thats another project. The polling is really just to allow getting realtime data when you want it. If I think about it more, Ill probably leave it out. I was just thinking out loud near the end.

@dzairo Can't help you with the project as it's way over my pay grade, but it sounds interesting. Good Luck!

Hi. It's long time .. but standard function is : gw.processRadioMessage(); and I make changes in source code in MyGateway.cpp to this : char MyGateway::processRadioMessage() { char isMessage=0; if (process()) { // A new message was received from one of the sensors isMessage=1; MyMessage message = getLastMessage(); if (mGetCommand(message) == C_PRESENTATION && inclusionMode) { rxBlink(3); } else { rxBlink(1); } // Pass along the message from sensors to serial line serial(message); } checkButtonTriggeredInclusion(); checkInclusionFinished(); return isMessage; } But in new library is not file MyGateway.cpp .. then I don't now .. using is : if (gw.processRadioMessage()==1) {..} regards.. there is possible make easy gateway .. controler .. to control only light for example.. then we don't need external controller .. etc..

Hi dzairo, Just wondering if you still monitor this thread. If so would love to know how to install the ComPort component so I can modify and use your terminal code. For some reason I don't have any luck with adding it to the IDE. thanks, Andy.

Hi all... This is important for all ... Hek I find problem with manual node ID setting .. Your code is optimized for ATmega328P 16Mhz - 115200 serial speed .. and here is problem ... big problem !! 16MHz -115200 is in normal speed : 3.549% ERROR , and in double speed : 2.124% ERROR with no calibrated 8Mhz internal RC oscilator is normal speed : 8.507% ERROR and in double speed : 3.549% then in fact .. no problem to send data from MCU to PC .. problem send data from PC to MCU .. solution : for sensor node or repeater .. we don't need received data from UART .. then can use 115200 with internal RC oscilator .. for serial gateway is need to send and received data from to MCU with controller .. then use scrystal 16Mhz (as orginal code ) or use better crystall : 7.3728Mhz , 11.0592Mhz , 14.7456Mhz ... with this crystall is ERROR 0% ... or use lower speed for serial gateway for example 38400bps ... sorry for all .. but I'm not thinking about it .. and problem was all time in hardware .. interesting is that if generate own bootloader for my node then first time I set 115200 bps speed and my software show error more then 8.5% ERROR ..and I must change speed to 38400 ... now it's working .. if node send request for new ID then I send it regards.

Hi. I do it .. change configuration in MyCOnfig.h (disable debug) and now gateway not send encoded message . But right now I test my serial board and have problem .. If send fast many packet from my sensor (INT0 and INT1) then serial gateway halt .. and no more data received from sensor and output string to uart .. I must reset MCU and all work again.. what is problem ?? Problem is in serial gateway .. after reset all work good .. any idea?? regards.

Original post is now updated (look at the bottom of it). (ping @bjornhallberg)

@Yveaux Ohh.. nice digging anyway.

Hi John, appLog.txt I also tried using datatype string but it doesen't work. Meanwhile I have studies the log files more detailed and found the following behavior: when defining the device skeletal and when updating the derived device (first approx. 25 lines in the log file V_STATUS is declared as string with values 51 resp. 52 as specified in the web interface. The entity is "Modul 433 MHz". Later on, when using the toggle switch in the web interface the value has changed in the decription in the log file (see line 164 or 185) value has been changed to on/off. With this definition it seem that the mysensors-Plugin is feeded has been changed from the specified values. My conclusion is that the change is taking place somewhere outside the mysensors-plugin. By the way, if I change the type to string do I have to use quotation marks in the web interface? Thanks a lot for your support. Martin

Hi all we are working on a new web client for our domotic framework. Here some screenshots It's a WIP so we need any help to complete it. The code is available at https://github.com/freedomotic/fd-vue-webapp/

I'm aware of the superiority of 1.4. Because I just started with building my custom controller I will go with the development branch for now. I really like the new protocol so far. I'm using very basic arduino sketches at the moment. The only thing I'm worried about is my custom controller that I'm building in Node-Red. Hopefully the feature changes will not have to much impact on that part.