Losing virtualWrite values

structure7 / hvacMonitor

Monitoring supply/return air temps, run status, and on/off durations.

MIT License

10 stars 6 forks source link

Losing virtualWrite values #106

Closed structure7 closed 8 years ago

structure7 commented 8 years ago

Having issues with the following:

Pin------Local variable
110------hvacTodaysStartCount in void totalRuntime()
111------todaysAccumRuntimeSec in void countRuntime() (NOW COUNTS ALONG WITH VARIABLE)
112------yesterdayRuntime in void countRuntime() (NOW COUNTS ALONG WITH VARIABLE)
11-------currentFilterSec in void countRuntime() (NOW COUNTS ALONG WITH VARIABLE)

Ideas:

[x] Removing year() != 1970 from line 153. Why would it make any difference if the year isn't 1970? This might be holding things up.
[x] Are local variables writing back for Blynk.syncVirtual happens? I think yes. These syncs either need to happen immediately, or local variable recording delayed until sync is successful. Trying these syncVirtuals in the main loop where they'll run only once.

structure7 commented 8 years ago

Bah... the above didn't work. Maybe:

[x] Add ten second start delay to all routines writing to the above local variables. (made it 30)

structure7 commented 8 years ago

Didn't work, but.... I need to time how long from confirmed reset to clearance of variables. That might tell me something. Seems like it was 60 sec.

structure7 commented 8 years ago

Back to the drawing board on this. Nothing seems to be working.

structure7 commented 8 years ago

Maybe use data.sparkfun to write to all of these (in lieu of virtualWrite) then see if there is a way to pull down the info back into variables at startup.

structure7 commented 8 years ago

I'm having a logic issue: Let's say I reset the unit and every zeros out. Oh darn. So I plug everything back into vPins via Postman. HOWEVER, while they show in the app, I need to initiate something that actually writes this back to the local variable. Will have to play with this.

structure7 commented 8 years ago

After much back and forth, looks like there's something wrong with V112 (yesterday's runtime of all things).

Hey, this is just a string into V14. Why am I adding V112 when I can just call back the string at V14?

structure7 commented 8 years ago

Well, after it all, it seems Blynk just doesn't like much more than 2 blynk.syncVirtuals together. I grouped 2, spaced by 5 seconds... worked like a charm!