Troubleshooting

Ok, tried that but it doesnt work. Its like the recieve time variable doesnt empty and the first numbers is just overwritten: read: 0-0-105 s=255,c=3,t=1,pt=0,l=10,sg=0:1451249777 requesting time send: 105-105-0-0 s=8,c=2,t=47,pt=0,l=0,sg=0,st=ok: read: 0-0-105 s=8,c=2,t=47,pt=0,l=3,sg=0:5.5 Msg to Child: 8, Message: 5.51249777 So the variable with my time is 5.5 and 1249777 from time.

Thank you for your answer. I read a post indicating to change the speed of 1MB for L01 . I'll order L01 + . Congratulations on your achievement .

At the moment they use same Channel and base ID, as it´s, i have to confess, very complicated to change them each time in the file and to recompile everything. But i will try tomorrow to give them different ID´s / Channels. WHat confuses me even more, and i don´t expect to get help here, but as i use FHEM, i saw, that ID´s i deleted in the past were reasigned to new sensors, with some values from the old / deleted ones, maybe that´s already where the problems start.... I think the easiest for me would be to Switch either to the developer Version- as said it´s ot receiving all Messages, or use the MQTT Gateway, but how to get it in inclusion mode ? Do i understand it right that the MQTT ESP Gateway will handle the allowed childs by itself and broadcast the Messages of only These childs to the MQTT Broker ?

Thanks Maybe you also advice how to trick Master branch (not Development branch) on the same way to disable radio and achieve coexisting of the serial gateway and node on the same arduino connected to a controller via usb? Examples at the Development branch have explicit definitions for using radio, which I can comment out //#define MY_RADIO_NRF24 //#define MY_RADIO_RFM69 Meanwhile the master branch examples have no such definitions and assume the radio is always present, so I cannot disable it and it cause radio init errors for my case

HAAAAAAAAAAAAAAAAAA !!!!!! pffffffffffff !!!! so noob I am :( it's work now ! I have a lot of arduino in my network, and there are diffrent MAc address => normal ! But in arduino with my sensor there wasn't MY_MAC_ADDRESS defined. and... two arduino with the same MAC (default MAC) ... pffff ==> doesn't work fine!!!! now it's work perfectly ! I'm sorry for you waste time ! thanks !

Im not home right now but gateway is v 1.5 and almost all sensors is also 1.5 recept 1 or 2 at 1.4.. Distance vary alot between 1 to 50 meters from the gateway. I've traced the problem to the gateway though, it loses connection to my Vera for some unknown reson

ok i think this can be regarded as solved: have tested very many on/of roundtrips and with an 100nf and an additional 4,7nf cap it's rocking stable. Maybe this would be worth a sidenote here: http://www.mysensors.org/build/connect_radio

@drock1985 I guess your switch string should be as follows, #Switches (Lights) switch 1: platform: mqtt state_topic: "mygateway1-out/2/1/1/0/2" command_topic: "mygateway1-in/2/1/1/0/2" name: "test1" payload_on: "1" payload_off: "0"

@Cliff-Karlsson if you have an AC waveform it will probably be a lot of noise and/or a "sine like" wave of a certain frequency. [image: 1450881227189-upload-6c2f3ec0-fffc-4b45-b839-886304797eb9]. Connected to an optocoupler this will trigger very frequently. What I suggest you do is rectify the signal so that you get a "DC" signal to use as a trigger. [image: 1450881699785-upload-768f93c3-149b-4902-8fb3-628813e04a4f] thnx wiki Connect the +Vo and GND to your optocoupler (in series with a resistor of around 470 Ohm). C1 = 100uF & R1 = 1kOhm will do to get a reasonable clean signal. You can attach the optocoupler to the interrupt (D2 or D3) and do whatever you want with it using gw.sleep(...)

Thanks for your kindly reply

I have not been home so i am unable to change radios or add capacitors, but what i have done and has worked for 3-4 days now is just adding delays between switching the relays. Before i would switch 1 off and 1 on at the same time, now i have added 15 seconds between and it is working without issue (fingers crossed)

Yes, wait is totally fine.

MySensors 1.6 (still in development) is quite a lot smaller than 1.5. You cound try it and see if it is enough.

Yep, Either you create a rule in openhab to answer these requests or set a static id in your node. (someone else have to answer how to create rules in OH)

Found the error: As soon as in MyConfig.h die following is enabled, compiling fails: #define MY_GATEWAY_W5100 EDIT: #define MY_GATEWAY_W5100 is not nessecary at all? even the gatewayClient sketch compiles successful without it.

Sometimes clearing the EEPROM helps: http://www.mysensors.org/build/debug

Thank you for advices, I was trying but no success after several days, so I left the ideea of using the Serial Gateway and moved to the MQTT Gateway + Home Assistant, I made it to work! I have published my work at https://github.com/Mihai258/HomeAssistant-MySensors-MQTT , I hope it will help other people to quickly implement their own projects and save their time.

@cleight This issue came up with the iBoard under MyS 1.4 and could be fixed by uncommenting a line which expanded all the variables in the gw constructor. From: MyGateway gw(RADIO_CE_PIN, RADIO_SPI_SS_PIN, INCLUSION_MODE_TIME); to this: MyGateway gw(RADIO_CE_PIN, RADIO_SPI_SS_PIN, INCLUSION_MODE_TIME, INCLUSION_MODE_PIN, RADIO_RX_LED_PIN, RADIO_TX_LED_PIN, RADIO_ERROR_LED_PIN); This made the pin changes in the sketch stick. I do not know how it is constructed in MyS 1.5. Perhaps you can change line 11 in GatewayUtil.h to map the inclusion pin from pin 3 to pin 14 and recompile.

Hardware mod