Controller issueshttps://gitlab.cs.wallawalla.edu/elock/controller/-/issues2020-10-29T09:11:44-07:00https://gitlab.cs.wallawalla.edu/elock/controller/-/issues/10Dynamic Config2020-10-29T09:11:44-07:00Jacob PriddyDynamic ConfigStore all config options in NVS, and allow them to be dynamically updated from the server.Store all config options in NVS, and allow them to be dynamically updated from the server.Jacob PriddyJacob Priddyhttps://gitlab.cs.wallawalla.edu/elock/controller/-/issues/11Request metrics2020-10-29T09:13:13-07:00Jacob PriddyRequest metricsProvide some way to determine how long a request took, maybe send the length of the last request on the next one, or just send the time the request started and then add the time the total request took in on the server (this might be erro...Provide some way to determine how long a request took, maybe send the length of the last request on the next one, or just send the time the request started and then add the time the total request took in on the server (this might be error prone due to time differences on client and server)Jacob PriddyJacob Priddyhttps://gitlab.cs.wallawalla.edu/elock/controller/-/issues/12Use Websockets2021-03-11T21:45:11-08:00Jacob PriddyUse WebsocketsUse websockets since this is at it's core a real time application.Use websockets since this is at it's core a real time application.Jacob PriddyJacob Priddyhttps://gitlab.cs.wallawalla.edu/elock/controller/-/issues/13Open Mode not working2021-03-11T23:11:16-08:00Jacob PriddyOpen Mode not workingOpen mode for new doors is not working. Fix ASAP. It is however working for old doors hitting the API. This means that the API is sending correct open mode times but the new firmware is not processing the times correctly or at all.Open mode for new doors is not working. Fix ASAP. It is however working for old doors hitting the API. This means that the API is sending correct open mode times but the new firmware is not processing the times correctly or at all.Jacob PriddyJacob Priddyhttps://gitlab.cs.wallawalla.edu/elock/controller/-/issues/14Migration to IDF v4.4 and Catch2 v32024-02-25T05:49:51-08:00Ethan JansenMigration to IDF v4.4 and Catch2 v3Currently using IDF v4.2, migrate to v4.4 before migrating to v5 and beyond.
Also, current docker container pulls Catch2 v3 when v2 is expected. Change to supporting Catch2 v3.Currently using IDF v4.2, migrate to v4.4 before migrating to v5 and beyond.
Also, current docker container pulls Catch2 v3 when v2 is expected. Change to supporting Catch2 v3.Ethan JansenEthan Jansenhttps://gitlab.cs.wallawalla.edu/elock/controller/-/issues/15OTA Update Not Updating Version of Running Partition2024-03-05T11:45:47-08:00Ethan JansenOTA Update Not Updating Version of Running PartitionAfter locally flashing a door controller with version 1.0.3.0, the board will check for an update, notice that the remote version 1.0.5.0>1.0.3.0, update, and restart. Upon restarting the version is correctly displayed as 1.0.5.0, howeve...After locally flashing a door controller with version 1.0.3.0, the board will check for an update, notice that the remote version 1.0.5.0>1.0.3.0, update, and restart. Upon restarting the version is correctly displayed as 1.0.5.0, however the following night when the board checks for an update it still thinks that the running version is 1.0.3.0 instead of 1.0.5.0.
This causes nightly reflashes/restarts when no update should be applied if the controller is truly running version 1.0.5.0.