Welcome to EnviroDIY, a community for do-it-yourself environmental science and monitoring. EnviroDIY is part of WikiWatershed, a web toolkit designed to help citizens, conservation practitioners, municipal decision-makers, researchers, educators, and students advance knowledge and stewardship of fresh water. New to EnviroDIY? Start here

Reply To: logging to mmw with GPRSbee rev.7, issue wake/sleep and server response 504

Home › Forums › Monitor My Watershed › logging to mmw with GPRSbee rev.7, issue wake/sleep and server response 504 › Reply To: logging to mmw with GPRSbee rev.7, issue wake/sleep and server response 504

2019-08-13 at 3:52 AM #13065
Bernard
Participant

    Dear all, a brief follow up on this issue. I have redone the same system to log to MMW. I am sending 4 measurements Bat_volt, MaximDS3231_Temp, Modem_RSSI, Modem_SignalPercent. After enabling debugging I do not get any disturbing messages about the functioning of the Sodaq GPRSbee rev7, however I am still getting the response code 504 (gateway timeout), related to the server.

    The same systems does send data to ThingSpeak. I receive about 40% of the data online (so I expect the modem work correctly). After enabling debugging for logging to ThingSpeak I do not get any disturbing messages. Signal strength is about 50% and seems good enough.
    Unfortunately both options (MMW and ThingSpeak) still don’t get me at the level I would like to be. If someone has the same experience or any Ideas how to improve the reliability, please let me know.