Arduino MKR 1010 with humidity and temperature sensors coded to only post when one or other of these change significantly - held in different tables. Everything starts ok and in the serial monitor the EXECUTE call to the stored procedure returns TRUE. This value checked in the code and if returns FALSE then retry until TRUE.
Initially this was to a new Raspberry CM4 and lead me to believe that the new CM4 was faulty or my beginner setup was not as it should be. Now posts to both the new CM4 and an old secondhand 4B holding a full clone of the original database. CM4 now always (up till now) receives the data and the intermittent stopping of data storage has moved to the 4B. Dug out an old MKR 1010 and temperature sensor and this posts to both without problem.
When the data posting stops, it stops for good and needs a reboot to restart.
All software / firmware is up to date on all the Arduino's and Raspberry Pi's
They use MYSQL Connector to post the new data to a MYSQL stored procedure on the Raspberry Pi's that works out whether to insert a new row or update the last row. Both Raspberry's are 8 gb, not over-clocked and run cool 30/40 deg C. Arduino's are powered by Apple USB phone chargers and not on any breadboard in a cool basement.
The logging stops are random at approx. 21:00; 18:00 and 16:00 hours.
All devices are genuine not clones.
None are running any S/w other than the Pi's downloading the latest weather every hour and posting it for comparisons - which works without problem on both Pi's.
This Yorkshire man has reluctantly and hastily ordered another MKR 1010 to replace and test - should I have gone for another model?
What do I test next?
Many Many thanks in advance
Steve
"Solution" being tested is to close the connection after every insert and NOT leave it open to be used again.
Until we can come up with a solution for the "ERROR: Timeout waiting for client." and whether this cures all
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.