Post by jimkernsjr on Jan 17, 2017 2:46:35 GMT
Hello All...
I thought I'd share with you a couple month long struggle of mine that finally came to an end. I initially built the RFM Gateway/node system and it ran rock solid for months on end. All of a sudden, one day it was as unstable as Charles Manson on crack. Seems like the radio would work for a short while then give up the ship, the MQTT light was blinking off and on, amongst various other anomolies.
The first problem I found was that I accidentally discovered that there was 5 volts on the Bruno Uno 3v3 line when an Ethernet shield was attached. I called it to the attention of Papa, who you will find in his documentation a fix for such a problem. Even still, after fixing the problem, the whole system still never worked right again. I rebuilt the whole shield with the radio, tried 3 different Ethernet shields, Uno's, radios, and still the MQTT light was on and off, on and off. I lived with the problem until just the other day.
In the meanwhile, I discovered out in my detached garage, that my security camera system took a nasty lightening strike. I remember this happening during the summer, but never quite made the connection or got around to fixing it. I never figured where the lightening came in, but it took out a camera, the memory in the Geovision system (not the computer though!), the router, back into the house through an underground ethernet cable, and destroyed just one port in my managed 24 port gigabit Ethernet switch. Oddly, everything else seems to work OK on this switch, but I got a wild hare to just reconnect this RFM gateway to another switch, and bingo, works like a charm again! Figuring it must just be auto-negotiation problems, I put it back into the original switch and forced the port back down to 10mbps/half duplex and still solid. Strangely, I dont remember ever seeing the Ethernet link light drop while it renegotiated and before the MQTT LED lit back up.
I just though I'd share that, because apparently only this Ethernet shield is very sensitive to the auto-negotiate, because the 15 other devices are not having such a problem. Also, there are notes that exist not to run your openhab/MQQT on a WIFI that I saw somewhere, so it's wise to pay attention to that as well.
Good luck, hope it helps someone else...
I thought I'd share with you a couple month long struggle of mine that finally came to an end. I initially built the RFM Gateway/node system and it ran rock solid for months on end. All of a sudden, one day it was as unstable as Charles Manson on crack. Seems like the radio would work for a short while then give up the ship, the MQTT light was blinking off and on, amongst various other anomolies.
The first problem I found was that I accidentally discovered that there was 5 volts on the Bruno Uno 3v3 line when an Ethernet shield was attached. I called it to the attention of Papa, who you will find in his documentation a fix for such a problem. Even still, after fixing the problem, the whole system still never worked right again. I rebuilt the whole shield with the radio, tried 3 different Ethernet shields, Uno's, radios, and still the MQTT light was on and off, on and off. I lived with the problem until just the other day.
In the meanwhile, I discovered out in my detached garage, that my security camera system took a nasty lightening strike. I remember this happening during the summer, but never quite made the connection or got around to fixing it. I never figured where the lightening came in, but it took out a camera, the memory in the Geovision system (not the computer though!), the router, back into the house through an underground ethernet cable, and destroyed just one port in my managed 24 port gigabit Ethernet switch. Oddly, everything else seems to work OK on this switch, but I got a wild hare to just reconnect this RFM gateway to another switch, and bingo, works like a charm again! Figuring it must just be auto-negotiation problems, I put it back into the original switch and forced the port back down to 10mbps/half duplex and still solid. Strangely, I dont remember ever seeing the Ethernet link light drop while it renegotiated and before the MQTT LED lit back up.
I just though I'd share that, because apparently only this Ethernet shield is very sensitive to the auto-negotiate, because the 15 other devices are not having such a problem. Also, there are notes that exist not to run your openhab/MQQT on a WIFI that I saw somewhere, so it's wise to pay attention to that as well.
Good luck, hope it helps someone else...
