Content
# #rancho-ynecita — 2026-02-18
**06:27 [Kevin](https://slack.com/archives/C09D358F91R/p1771424844394749):** The system powered down last night. On startup this morning the alarm setpoints were at 0, the wells think they are in TOU disable even though the time and setpoints are correct, and now they won't call via setpoints. Do you have time to take a look?
**06:27 [Kevin](https://slack.com/archives/C09D358F91R/p1771424858536319):** @Mason Radke
**07:04 [Mason Radke](https://slack.com/archives/C09D358F91R/p1771427048200869):** ok fixed.
**07:04 [Mason Radke](https://slack.com/archives/C09D358F91R/p1771427054804579):** two things
**07:05 [Mason Radke](https://slack.com/archives/C09D358F91R/p1771427101864809):** TOU was always enabled, i needed to add a bypass rung for when its un checked.
**07:05 [Mason Radke](https://slack.com/archives/C09D358F91R/p1771427125107279):** and the TOU mode.. (TOU off vs TOU on) needed to be hard set for our application.
**07:05 [Mason Radke](https://slack.com/archives/C09D358F91R/p1771427130982869):** both fixed.
**08:36 [Kevin](https://slack.com/archives/C09D358F91R/p1771432575401549):** Thank you!
**08:36 [Kevin](https://slack.com/archives/C09D358F91R/p1771432603776419):** Did you check the alarm setpoints to see if they are retentive?
**08:42 [Mason Radke](https://slack.com/archives/C09D358F91R/p1771432974534739):** No. Driving now to my appointment.
**08:43 [Mason Radke](https://slack.com/archives/C09D358F91R/p1771432980249769):** I can check later