@ramoncarranza When I went and looked where the library manager installed the IRremote lib(for me C:\Users\User\Documents\Arduino\libraries), it had given it an odd name like arduino_294267. I renamed it to IRremote and the issue went away.

@mfalkvidd I didnt realize it was a vera specific flag. By the name it sounds like something that would be needed to include sensors on any platform. If not, fair point.

@anvil Are you kidding me! That was it. I don't have a problem fiddling with the files but I assumed the step-by-step instructions would have laid that critical step out. Or for that matter why isn't it in the source to begin with?

@blacey
I was using the serial gateway over a year ago with UI5. I decided to update to the new version and have tried UI5 and UI7 with both the serial-to-vera and raspi-as-ethernet gateways. Can't get the serial gateway to show up so I'm back to UI7 Ethernet trying to figure out what's getting lost in the messages. SHAs seem to match yours. I'm a little confused though. Aren't id's handed out by the controller only during inclusion? If I reboot my vera, start the gateway, and clear eeprom/upload a motion sketch, I get the output below. It looks like an id is handed out and I never touched the start button.

root@MiOS_35029342:~# sha1sum /etc/cmh-ludl/*_Arduino*
f9875310ea581c6384046dfd733dc5c9e436ef20  /etc/cmh-ludl/D_Arduino1.json.lzo
e3c4493c7dff216c152b8a4d50c169acf636b1fc  /etc/cmh-ludl/D_Arduino1.xml.lzo
8f0186c85c9a6ef6e0e8ba0755f88cbb5d326e30  /etc/cmh-ludl/D_ArduinoNode1.json.lzo
7d66187bb75beb01606f607ad1e82a6fa6b2a552  /etc/cmh-ludl/D_ArduinoNode1.xml.lzo
722b702937db7aedcb03346229fcc38363b2c378  /etc/cmh-ludl/D_ArduinoRelay1.json.lzo
05ea89a8d904f436c60bd326315724e79c5c47de  /etc/cmh-ludl/D_ArduinoRelay1.xml.lzo
ed15bfde68e6615b7615bd6230ca8040a50f5f28  /etc/cmh-ludl/I_Arduino1.xml.lzo
2f0603b6192006f88e3582788a13a168391ceee4  /etc/cmh-ludl/L_Arduino.lua.lzo
dc1e8a26833890f2d1f412c9b2e915724576cbd4  /etc/cmh-ludl/S_Arduino.xml.lzo
64f886de376e2d932cd55bdf8a6367ed7a394d55  /etc/cmh-ludl/S_ArduinoNode.xml.lzo
root@MiOS_35029342:~#

mysgw: TSF:MSG:READ,255-255-0,s=255,c=3,t=3,pt=0,l=0,sg=0:
mysgw: Client 0: 255;255;3;0;4;1
mysgw: TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:1
mysgw: Client 0:
mysgw: TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
mysgw: TSF:MSG:PINGED,ID=1,HP=1
mysgw: TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=OK:1
mysgw: TSF:MSG:READ,1-1-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
mysgw: TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
mysgw: TSF:MSG:READ,1-1-0,s=255,c=0,t=17,pt=0,l=5,sg=0:2.1.0
mysgw: TSF:MSG:READ,1-1-0,s=255,c=3,t=6,pt=1,l=1,sg=0:0
mysgw: TSF:MSG:READ,1-1-0,s=2,c=0,t=1,pt=0,l=0,sg=0:
mysgw: TSF:MSG:READ,1-1-0,s=255,c=3,t=26,pt=1,l=1,sg=0:2
mysgw: TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=27,pt=1,l=1,sg=0,ft=0,st=OK:1
mysgw: TSF:MSG:READ,1-1-0,s=2,c=1,t=16,pt=0,l=1,sg=0:0
mysgw: TSF:MSG:READ,1-1-0,s=2,c=1,t=16,pt=0,l=1,sg=0:0
mysgw: TSF:MSG:READ,1-1-0,s=2,c=1,t=16,pt=0,l=1,sg=0:0

@marceloaqno Well that fixed the connection issue. Now I'm just back to square one where pressing start doesn't do anything. Why do I not need to specify my controllers ip? That is the ip for my veralite. Whats the use case for that option.

@marceloaqno
Ran as root and made sure I didn't have mysgw already running:

rm -r MySensors/
git clone https://github.com/mysensors/MySensors.git --branch master
cd MySensors/
./configure --my-controller-ip-address=192.168.1.136 --my-port=5003 --my-rf24-irq-pin=15
make

root@raspberrypi:~/downloads/MySensors# ./bin/mysgw -d
mysgw: Starting gateway...
mysgw: Protocol version - 2.1.1
mysgw: MCO:BGN:INIT GW,CP=RNNG--Q,VER=2.1.1
mysgw: TSF:LRT:OK
mysgw: TSM:INIT
mysgw: TSF:WUR:MS=0
mysgw: TSM:INIT:TSP OK
mysgw: TSM:INIT:GW MODE
mysgw: TSM:READY:ID=0,PAR=0,DIS=0
mysgw: MCO:REG:NOT NEEDED
mysgw: connect: Connection refused
mysgw: failed to connect
mysgw: Eth: connect

@marceloaqno I should have specified, I'm getting the connection errors with the ethernet gateway.

@lakshmc Make sure you don't have the daemon running already

If not, I'm getting the same problem on the 2.1.1 that was just released. 2.1.0 was working "fine"(besides my suspecting a bug that doesn't let any inclusion happen, hence I tried the new version). Time to go back to the serial gateway right into the vera.

I've got nowhere. Unless someone happens to pop up with somewhere to look I guess I'll be going back to see if the serial gateway will work. As the problems exists after valid data already comes through I'd think the problem will still exist but who knows.

I've tried going back to UI5 as well but no change. I'd really like to know for starters why the start button in the UI doesnt have any visible effect but aparently starts things behind the scenes.

I've been banging my head against this for hours and I can't figure out why my veralite won't add my sensors. I've used this exact sensor before on UI5 and I can see the gateway acknowledging my movement. For starters I have done a factory reset and added only the gateway device and the "start inclusion" button never seems to do anything in the UI. I can see however that it calls the start procedure because something comes through to the gateway but the stop never happens either. I've been running the start, then the stop, then manually reload lua for good measure. The only thing I can find that seems relevant is copied below. Discarded seems bad.

If I'm reading correctly near the middle it goes like this:
0;0;3;0;5;1 get the gateway version
255;255;3;0;4;1 here, have node id 1
1;255;0;0;17;2.1.0 responds with version
1;255;3;0;6;0 request for config
1;255;3;0;11;Motion Sensor I'm a motion sensor
1;255;3;0;12;1.0 Sketch version
and then the node sending data again

Any help would be appreciated.

@hek It looks like development is the default branch in the repository. I was following the build instructions and couldn't figure out why I kept getting "connection refused". Just typing up a troubleshooting post when I saw my log said 2.2.0-beta. Sure enough when I grabbed master(2.1.0) instead it ran fine. Should probably add a checkout in the instructions.

@BartE Wow that's great. Thanks!

@BartE As I'm already using a sensor that I just control with light switch buttons in vera, I'd like to not have to add a IR receiver to the current board. Does this have the ability to let me just add the hex codes I already have?

Either way this is awesome.

@Tmaster I'm actually using a LG Exceed 2 that comes on sale for $8 at Best Buy every once in a while.

@Dwalt Oooo. Exactly what I was looking for. I'd prefer to sent my own codes but that's a good start. Thanks.

I've got a couple sensors with IR LEDs attached to them and can control things like my projector/receiver/AC through "light switch" widgets on my veralite. With enough devices the interface gets to be quite messy and cumbersome. Is there an existing "Device" for Veras that I could use to have some sort of remote panel with multiple buttons. Something where you would put your IR codes in the settings and each button would send a different payload to the sensor.

If not, any suggestions for good tutorials on creating my own?

I've been wanting to incorporate some 433mhz weather sensors. I'll be using this!

Sorry this isnt a helpful post, but is 100000mah a typo? 100 amp hours out of something that fits in a mail box? Seems very high.

You can certainly have a node set up but it would just sit there asking for a node ID all day. If you want to be able to control it until you get a controller set up, slap a NRF24Lo1 on another arduino and use it plugged into a computer as a serial gateway. You'll need to send the node id manually(no controller to do it for you) through the serial consol and then it will start sending the mysensors encoded messages. You can also send commands in the same format so you'll need to read up on the API.

Once you get a controller remember for flash the eeprom clear sketch so it can request a new node ID.