Probably you already know this as the RIU automation specialist but maybe not
The raspberry is famous for corrupting of sd cards. Use the sd card only for booting and use a USB stick/drive for the read/write operations. Also make sure the the pi shuts down properly and provide enough current to the pi.
Don't pull the plug of the raspberry when not shut down properly. There is a change of corruption when the citys power blacks out.
I love raspberry but it is not stable enough to use in a project that has to run for 3 months with absolute no problems. My opinion only.
Banana pi have sata connectors but is a bit more expensive and maybe more stable.
I have a few corrupted sd cards. I use a 1TB hdd on mt rpi3 thru the USB port. I am hoping to get the good sata cable for the bpi, I have a 250GB hdd on that one. the bpi is not as bad on sd cards, but they all suck. I run my test work on a pc with openhab on it and I test until I am ready to download to the rpi3 and do hard testing. That allows me to run thru various scenarios and test different approaches and see what works best quickly. You can run openhab on a pc but there are no real inputs and outputs like switches and sensors. I have all that connected to the rpi3 and just run headless and copy and paste from text editor to nano. easier for work flow.
The aquarium controllers are famous for the blue screen. Wake up to no status and have to reset the controller. After two of those sessions, I decided I could build a better controller. I went thru the code of both hurircane and typhon, I have both and they both have serious short comings. A lack of channel controls, poor interface, too many buttons r not enough channel controls. pick one. I have a box of coralux and stevesleds controllers. All failed after maybe six months. I guess fish don's complain about no sunrise or sunset or lights on lights out, routine. I feel for folks buying those other controllers and learning the hard way like me.
The reason i was restricting access to eeprom is to stabilize and increase the life of the GrowGreen controller. Arduino recommends to access writing to eeprom an average of 20 times in the life of the unit
that is sensitive. I left out the 20 times and locked out routine, no need to restrict folks if they understand the consequences. My schedules have not changed for years. When I switched from HPS to LEDs it switched, I could have lights on in the daytime and work in teh garden in the daytime. lovely. Otherwise schedules do not change as plants ar finicky about their schedules, hence GrowGreen. namaste