sia-app/lib, branch v0.1.0IoT apphttps://cgit.xengineering.eu/sia-app/atom?h=v0.1.02026-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.
Fix missing SafeArea for Android2026-04-08T09:58:06Zxengineeringme@xengineering.eu2026-04-08T09:58:06Zurn:sha1:5171ef6557c3f38a32e68313e51c4ca1e866835a
The start of the DevicesPage could be below a notch or header bar in
Android.
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.
Display available covers2026-04-08T08:45:21Zxengineeringme@xengineering.eu2026-04-07T15:09:45Zurn:sha1:5dc62a59bf12dcc0190c26eb3712c1b7eec3cfcd
This does not yet allow control of the covers but existence is shown.
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.
Implement SQL migrations2026-04-06T14:37:36Zxengineeringme@xengineering.eu2026-04-06T09:04:53Zurn:sha1:34d52bf961071348d8262e6d08d1703530ff8556
This allows to update the SQL schema incrementally.
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.
Make ConnectionPage a StatefulWidget2026-03-10T16:53:34Zxengineeringme@xengineering.eu2026-03-10T16:53:34Zurn:sha1:0f32a2c2aab78b882fff10a6b81ddd271bcb17b0
This allows to store the fully qualified domain name (FQDN) of the MQTT
broker and display it if the user visits the page again.
The old behaviour was that the text input field was empty.
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.
Make ConnectionStatus a SafeArea by default2026-03-07T10:14:34Zxengineeringme@xengineering.eu2026-03-07T10:13:26Zurn:sha1:b6f6dc481606d0ffb8c06ffb549cb0221b0c6167
This removes the need to write a SafeArea on each use of
ConnectionStatus and replaces it by exactly one occurrence.
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.
Move MaterialApp up to class Sia2026-03-06T11:49:29Zxengineeringme@xengineering.eu2026-03-06T11:49:29Zurn:sha1:12d36a7457759fdd9a0b3c600dfc81fef36ea37f
This makes sure there is only one class instance of MaterialApp.
Rename to class DevicesPage2026-03-06T11:39:38Zxengineeringme@xengineering.eu2026-03-06T11:39:38Zurn:sha1:2ff436b069564690b204763bc135c3df9611ef0f
The old name class UI was not adding much information and is not well
suited to be differentiated to upcoming other *Page classes.
Add `class Sia` as top-level widget2026-03-06T11:26:18Zxengineeringme@xengineering.eu2026-03-06T11:26:18Zurn:sha1:5b7084cf9de8f43cdc771f0b5ce92fc15d9e74af
This simplifies the main function and adheres more to Flutter
conventions.
Protect bottom bar with SafeArea2026-01-17T20:47:47Zxengineeringme@xengineering.eu2026-01-17T20:47:47Zurn:sha1:4b5843336970c8386702191a36ee7e57839b8fd3
On Android the bottom bar with the connection state used to be hidden by
the three Android navigation buttons.
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.