Do you have any install documentation for it? Any docs for integrating into existing snips setup?

I am going to be checking this out. I have been working with snips on some other stuff, so this could be very interesting.

@zboblamont actually it was more of a "not completed" type of thing. i didn't finish the connection between the bottom part that houses the sensor and the top cap. so it got knocked over and water soaked in. so i will be redoing it and will just complete it this time

I made a sensor like this myself. i took a non-water proof one and drilled holes to match the sensor in some plexiglass. and sealed around it with silicone. This worked until florida tried to drowned me out and flooded my entire sensor housing lol

I ended up setting up some monitoring that if by some chance it does go belly up my monitoring will do a recovery action. But it does still happen from time to time, which is strange.

I recently had alot of issues with my pi gw too. One of the things I found REALLY helped was on my switch I set the speed and duplex to 100mb FULL. In my syslog around the time my GW stopped responding, I was seeing messages about the "carrier lost" on the nic. Not sure what caused that, but it seems like it was taking quite some time to renegotiate. Now that I have it set to 100 FULL my issues have gone from 1-2 a day to only once in 3 weeks.

Also, make sure you have plenty of power for your PI. I have noticed one of the first things that seems to flake out on me when i have a sub par power supply for the PI is the network.

Not sure it my experience will help but figured I would try

So here's the latest.

I checked and the PI was already set to static ip and not dhcp reservation. However, I made 2 changes and have been ok for 3 days now.

1. i changed ports on the switch. Not sure if it mattered, but i have plenty.
2. this is the one I think may have more impact. Since it seemed the carrier was dropping, but coming back, I started wondering if maybe something was triggering an auto renegotiation for nic speed. So I went in to the switch and have it hard set to 100 FULL instead of auto.

I still have the debug running and gonna let this run for quite some time just to make sure im feeling it's ok.

compiled with new (very noisy) options lol

Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17
Apr 03 13:50:48 DEBUG RF24:RBR:REG=23,VAL=17

No idea what that means, but it seems if i am seeing that, it's working lol.

@mfalkvidd compiling now. side question, can the ip address be put in the config later? i hate that i have to hard code it in at compile time.

@mfalkvidd do i need to modify the pi code and add that in and recompile? or can i add those in to the config file in /etc/mysensors.conf?