Fix door sensor endpoint #105

New Issue

Closed

opened 2026-01-09 19:04:36 +01:00 by oysteikt · 7 comments

oysteikt commented

2026-01-09 19:04:36 +01:00

Owner

There is likely a mismatch between the expected schema and the schema used in the prod database

Screenshot sent by @berntjd in maintenance discord channel

There is likely a mismatch between the expected schema and the schema used in the prod database Screenshot sent by @berntjd in maintenance discord channel

Screenshot_20260108-163503.png

253 KiB

oysteikt added the bug crash report labels 2026-01-09 19:04:36 +01:00

felixalb commented

2026-01-11 21:43:38 +01:00

Owner

It looks like the correct payload format for https://git.pvv.ntnu.no/Projects/nettsiden/src/branch/main/www/door/index.php#L64-L81, and used to work fine.

There is likely a mismatch between the expected schema and the schema used in the prod database

Has the door table been dropped or altered, and if so, why? Taking a look.

It looks like the correct payload format for https://git.pvv.ntnu.no/Projects/nettsiden/src/branch/main/www/door/index.php#L64-L81, and used to work fine. > There is likely a mismatch between the expected schema and the schema used in the prod database Has the door table been dropped or altered, and if so, why? Taking a look.

felixalb commented

2026-01-11 21:48:10 +01:00

Owner

MariaDB [www-data_nettside]> SELECT * FROM door ORDER BY time DESC LIMIT 3;
+------------+------+
| time       | open |
+------------+------+
| 1767079800 |    0 |
| 1767078900 |    0 |
| 1767078000 |    0 |
+------------+------+
3 rows in set (0.000 sec)

Well, the table exists and looks sane, and stops at 1767079800, which is Tuesday, December 30, 2025 8:30:00 AM (Norwegian time)

``` MariaDB [www-data_nettside]> SELECT * FROM door ORDER BY time DESC LIMIT 3; +------------+------+ | time | open | +------------+------+ | 1767079800 | 0 | | 1767078900 | 0 | | 1767078000 | 0 | +------------+------+ 3 rows in set (0.000 sec) ``` Well, the table exists and looks sane, and stops at 1767079800, which is `Tuesday, December 30, 2025 8:30:00 AM` (Norwegian time)

oysteikt commented

2026-01-12 06:39:11 +01:00

Author

Owner

No, I think it's the code that queries the database, I suspect I switched out INT for DATETIME or something similar

oysteikt commented

2026-01-12 13:28:46 +01:00

Author

Owner

Did some more research, everything seems to match in the code and the production db, I wonder what's up...

If the door sensor stops at december 30, and we don't have any data since then, could it be that the php code crashes when it queries 0 rows?

Did some more research, everything seems to match in the code and the production db, I wonder what's up... If the door sensor stops at december 30, and we don't have any data since then, could it be that the php code crashes when it queries 0 rows?

oysteikt commented

2026-01-12 13:29:15 +01:00

Author

Owner

No wait, I'm dummedumm, this is the other part of the code that sends in timestamps. uuuuuuh, lemmesee