Skip to content

3.10.0

Choose a tag to compare

View all tags
@jboulton jboulton released this 13 Oct 08:27
· 19 commits to master since this release
3.10.0
bb9ae37

Changed

  • History over local connections. For a TimeGraph, EventLog or Map with storage_enable(), the device now only answers history requests that come from the Dash server. The Dash server is the app's source of truth for that history: answered over TCP, the app took the device's history as complete and didn't fetch older data from the server. Live updates still go to every connection.
  • deviceSetup in the CFG now lists the device's connections (TCP for a TCPConnection, MQTT for a DashConnection, BLE), then the settings the Dash app can change. The options are upper case, as the app writes them, and the Dash login option is DASH (was dashio). Adding a connection changes the CFG, so work out cfgRev from get_cfg_hash() after adding the device's connections. The examples do this; expect cfgRev to go up once on their next start.
  • DashConnection reconnects with a growing wait after a refused login, up to 15 minutes, and doesn't try to connect without a username and password. Before, it retried about every second.

New

  • DashStore: local storage, and store and forward to the Dash server. Device(..., store=dashio.DashStore("device.db")) keeps the data of the device's TimeGraph, EventLog and Map controls in an sqlite database, with limits on the number of entries and their age. History requests are answered from it, including data from before a restart. When the device connects to the Dash server, it sends the server the data it missed, with the DashIO firmware's store and forward (SDU) protocol.
  • Devices that only connect now and then, e.g. on LTE to save power:
    • DashConnection(auto_connect=False), connect() and disconnect(). During a planned disconnect, device messages are dropped rather than sent as a backlog when the connection is made; requests to the server, such as STE, are kept.
    • device.set_store_sync_callback() is called when each sync with the Dash server ends, so the device can disconnect.
    • device.store_and_forward = True lets the Dash app turn on store and forward (SAF) for the device on the Dash server.
  • dashio.CaptionMode and dashio.DeviceViewStyle are exported.

Examples

  • Examples/intermittent_connection.py: a data logger that connects to the Dash server on a schedule and disconnects when its store has synced. The Dash app provisions it over TCP on the local network: its name, the Dash login, and the connection and record intervals.
  • The greenhouse keeps its history in a DashStore (greenhouse.db).

See Documentation.md, in particular Local Storage.

Assets 2
Loading