Thanks for the quick reply and explanation.
I was probably generalizing about documentation on the EEPROM and was really looking at UNO not UNO WiFi Rev2 documentation.
So i was probably the one making the bad assumption.
Just got my first Arduino product two weeks ago so just learning differences, etc.
Ill try and keep all my stored config data under the 256. If i start adding more features, etc and have the need for more, ill look into some external EEPROM solutions.
Im building a mist system for doing plant cuttings.
In the process of determing number of valves/relays i want to control. At the moment going with 4.
The trying to determine if i have only one program foreach or multiples. each program has start and stop times, cycle/duty times, etc. Plus allowing some char arrays for program name and valve names. So the data structure go fairly big.
I got the WiFi just to learn, and having a regular Uno coming for playing/testing so i might move the final version to Uno only. Just depends how much i decide to use the WiFi portion for AP phone hookup config/status, NTP time calls, web config/status hookup.
Also going to add in some sensors once i test a few. temp/humidity, rain, daylight, etc.
Plus love to use a local HMI with say a Nextion Display.
So with all that, i might go ahead and look at using the Uno Wifi at a closer location and communicate to another local Arduino Uno for the local sensors and relay protion.
Basically have a HMI/COMM Uno Wifi inside my house and then a Uno Only out in the greenhouse where i dont think i have WiFi anyway.
Thanks again!