sia-app/lib/data.dart, branch spellcheckIoT apphttps://cgit.xengineering.eu/sia-app/atom?h=spellcheck2026-04-08T12:16:28ZAdd plug control2026-04-08T12:16:28Zxengineeringme@xengineering.eu2026-04-08T12:16:28Zurn:sha1:18cbbf877b171fc23950e64dac5fa6abda6fb02b
This allows the user to turn Wi-Fi plugs on and off.
Add cover control with up / stop / down2026-04-08T09:28:51Zxengineeringme@xengineering.eu2026-04-08T08:58:29Zurn:sha1:e4c61d1b669a43d292be1f40d5b36dbcb93500a4
This allows the user to move covers with the Sia app.
Add AppState.covers2026-04-07T14:49:20Zxengineeringme@xengineering.eu2026-04-07T13:26:25Zurn:sha1:38705a8c1825638750cbee3e03bd182db1445020
This set contains all the covers the server offers. This commit does not
include displaying it.
Refactor message routing2026-04-07T14:48:45Zxengineeringme@xengineering.eu2026-04-07T12:53:37Zurn:sha1:129c825a77fb3cc039ab978785d72f92023ef1ab
This allows to route incoming MQTT messages in the _onMessage() method
and handle it in different handlers per topic.
Empty contacts cache on disconnect2026-04-07T12:18:01Zxengineeringme@xengineering.eu2026-04-07T12:18:01Zurn:sha1:c2110a2098d475c5fa06d265833e229fad938e8d
The cache of server data must be cleared on any disconnect. This avoids
a bug when devices from another server are displayed after connecting to
a different server or displaying outdated states on re-connect.
Implement setting server_fqdn2026-04-06T14:57:58Zxengineeringme@xengineering.eu2026-04-06T14:57:58Zurn:sha1:fcfb2a17733a38b690f4e034c78bc414be5527ef
This persists the used server_fqdn on connection. This makes sure the
user does not need to specify the FQDN every time.
Introduce class DB2026-04-03T19:42:15Zxengineeringme@xengineering.eu2026-04-03T19:29:39Zurn:sha1:2dc31225e08260a4a8f84fd61623e28f1c8c001e
This centralises database related code in one class.
Add *_futures to analysis_options.yaml2026-04-03T19:42:08Zxengineeringme@xengineering.eu2026-04-03T17:49:29Zurn:sha1:a406df320080bf31e32cb181136928793cb5d37b
These options should avoid making typical mistakes in asynchronous code.
Add DB schema version check2026-03-20T20:10:12Zxengineeringme@xengineering.eu2026-03-20T20:10:12Zurn:sha1:09c34e0f373d48f5993598c76fa176c8ed2fd4cd
This version is only compatible with the schema version 0. No migrations
are implemented. Thus the DB is only accessed if the schema version
saved as user_version is as expected.
Add reading server domain name from SQLite3 DB2026-03-20T19:48:52Zxengineeringme@xengineering.eu2026-03-20T16:02:39Zurn:sha1:09330228991b73ede49ed186f74a2c4f306d2e20
It is annoying to type the server domain name on every app start. This
should be way more ergonomic.
As a minimal first step reading from the database is implemented and
tested with an externally injected database.
Implement server selection2026-03-08T16:53:53Zxengineeringme@xengineering.eu2026-03-08T16:53:53Zurn:sha1:6ee59e8c2aaf69951f6f80003c23f9cd44976ce1
This lets the user select the fully qualified domain name (FQDN) of the
MQTT broker.
The FQDN is not yet preserved after a manual disconnect.
Switch completely to connection state machine2026-03-08T16:27:52Zxengineeringme@xengineering.eu2026-03-08T16:27:52Zurn:sha1:4bc034c7ab627c50aba7e2ce4da360c14465c150
This makes use of the state machine in the UI and implements all states
and transitions planned so far.
Add manual disconnect2026-03-08T15:49:42Zxengineeringme@xengineering.eu2026-03-08T15:49:16Zurn:sha1:ef8877ccffe0ebcc8f9f1c0bb6db372fa0886c2a
This allows going back to the connection page and to choose a different
server. Furthermore it might be useful to force a new connection attempt
while auto-reconnect might be in a delay state.
Remove automatic initial connection2026-03-07T15:35:59Zxengineeringme@xengineering.eu2026-03-07T15:35:13Zurn:sha1:796a2b21e8b5989187bfc7d4ddb7ba648038cbca
The user should provide the fully qualified domain name (FQDN) of the
MQTT broker manually and then press connect to actually connect
including automated re-connects.
As a first step the initial connect is bound to the manual button in the
bottom bar. To reduce the scope the disconnect button is labeled
"(disabled)" to make clear this is not expected to work.
Label button with '(dis)connect'2026-03-07T12:03:24Zxengineeringme@xengineering.eu2026-03-07T12:03:24Zurn:sha1:2e15dd323b7c3198e2af10f35f1186d91cc6cfaf
This does not yet work but the correct text based on the page is
displayed.
This is based on a state machine based implementation suitable to
implement the state handling cleanly.
Start by default on ConnectionPage2026-03-07T10:53:18Zxengineeringme@xengineering.eu2026-03-07T10:53:18Zurn:sha1:a46cb6e94688a65a31248bc4585bccfbc22242f0
This prepares starting connection attempts on manual action only.
Allow switching between pages2026-03-07T10:45:34Zxengineeringme@xengineering.eu2026-03-07T10:45:34Zurn:sha1:e75d23db9960c6060fd2b530f5878727e0caaf37
This prepares manually starting the connection after server name
insertion.
Add class ConnectionPage2026-03-07T10:07:53Zxengineeringme@xengineering.eu2026-03-06T20:45:43Zurn:sha1:6cb5a471a1bb18de802006c1017839c00d1871ad
This is a second page to offer a form to set the Sia server name.
Indicate disconnected Sia server2026-01-17T20:12:25Zxengineeringme@xengineering.eu2026-01-17T20:12:25Zurn:sha1:b38f887c0ed04e32ae62f097288fd318b4d3c8f2
There are now three instead of two status states:
- "Connected" / MQTT connected, Sia server connected
- "Connection issue" / MQTT connected, Sia server disconnected
- "Disconnected" / all other cases (Sia server connection unknown)
Add automatic reconnecting2026-01-17T19:56:55Zxengineeringme@xengineering.eu2026-01-17T19:53:07Zurn:sha1:f083de5a7d4bbc296e5fa07707a4a179f780f85b
This allows to use the app after a temporary disconnect between app and
MQTT broker.
Display MQTT connection status2026-01-17T19:56:45Zxengineeringme@xengineering.eu2026-01-16T20:49:22Zurn:sha1:1dc47d1991910d95b4472ed3e415adb0d46a6617
The user otherwise cannot trust the state of the contacts because the
app could just be disconnected from the broker.
Set contact states based on MQTT2026-01-15T20:25:45Zxengineeringme@xengineering.eu2026-01-15T20:25:45Zurn:sha1:7cdfe307fa3ae2de5326321cae74495fe0680d46
This is already the minimal viable product (MVP) for this app.
Add const MQTT connection options2026-01-11T19:51:27Zxengineeringme@xengineering.eu2026-01-11T19:51:27Zurn:sha1:38b49eb626ab0b3fdd634e82d21dacc593dd6629Switch to Map address to state for contacts2026-01-11T19:26:03Zxengineeringme@xengineering.eu2026-01-11T19:26:03Zurn:sha1:ad86cd926d5da6031930de79cbe85df7ff40df1c
This map should be empty in the future and updated based on the incoming
MQTT messages.
A list was not the correct data structure for that since it requires to
iterate over the whole list to find the entry with a certain address.
But this is required to update the state of an already known contact.
Fix indentation2026-01-11T18:56:21Zxengineeringme@xengineering.eu2026-01-11T18:56:21Zurn:sha1:0692db03e155054c8732da49eefba44d9c7ea549Re-introduce timer-based state toggling2026-01-10T20:37:51Zxengineeringme@xengineering.eu2026-01-10T20:37:51Zurn:sha1:f8cf9dc0a8b7e67e4c0f7e2d40b0b4ab26a5ed0a
This is now done with the refactored code organization and a strict UI /
data split.
Move state to data.dart2026-01-10T20:29:45Zxengineeringme@xengineering.eu2026-01-05T13:48:50Zurn:sha1:ee38d5671e0d6b8d0e1d3708a37b43a65682329f
The UI should not store the application logic state.
Split code into three Dart files2026-01-05T13:08:11Zxengineeringme@xengineering.eu2026-01-05T13:08:11Zurn:sha1:14d7ef0101400f531092ee4abfc42e9a0dfd218e
This follows recommendations [1] from the flutter documentation.
[1]: https://docs.flutter.dev/app-architecture/concepts