🚀 Simple IoT Releases

v0.11.0

  • fix rule condition schedule processing (#547)
  • support high rate serial MCU data (#517)

Update 2023-05-30 – This release has issues with Shelly IoT device support (#552)

v0.11.2

  • fix race condition in Client Manager client startup (#552). This fixes a crash
    when detecting Shelly devices.
  • update point merge code to handle complex types
  • more fixes for rule condition schedule processing (#547)
  • fix issue with Shelly device discovery duplicating devices (#552)
1 Like

v0.11.3

  • serial client: add high rate rx count for debugging

image

v0.11.4

  • remove index field from Point data structure. See #565
  • add support for Shelly Plus2PM
  • change Shelly client to use Shelly API Component model

2pm

v0.12.0

  • support Dates in Rule schedule conditions
  • Rules are re-run if any rule configuration changes
  • Display error conditions in Rule nodes
  • hide schedule weekday entry when dates are active
  • hide schedule date entry when weekdays are active
  • support deleting (tombstone points) in NodeDecode and NodeMerge functions

image

1 Like

v0.12.1

  • fix control of Shelly lights
  • required that Point:Key field always be set (#580)
  • improvements in point decode and merge with arrays (not finished)

v0.12.2

v0.12.3

  • switch to elm-tooling to enable building on Linux and MacOS ARM machines
  • enable riscv builds in release

v0.12.4

  • Reworked and simplified decode and merge routines (#589). See
    documentation
  • UI: fixed issue with with paste node rule condition/actions (#600)
  • Can client: fixed various issues (#498)
  • Rule client: fix issue with error reporting (#599)
  • switch to forked mdns package to get rid of closing messages (#558)
  • update nats.go package from v1.20.0 => v1.28.0
  • update nats-server package from v2.9.6 => v2.9.21
  • default NATS server to 127.0.0.1 instead of localhost

v0.12.5

  • add supported for Linux temp sensors (#607)

image

v0.12.6

  • fix issue with email in user node UI (#609)
1 Like

v0.12.7

  • serial client decoding improvements

v0.13.0

  • implement siot install command (#527)
  • update frontend poll rate from 3s to 4s
  • fix siot store (was crashing due to Opened not being defined)

Simple IoT can now install itself, just run: siot install

https://docs.simpleiot.org/docs/user/installation.html#simple-iot-self-install-linux-only

v0.13.1

  • update client manager API to include list of parent node types
  • fix issue with duplicating nodes where there were two copies of Description
    points
  • display decode error count for high-rate serial packets
  • display rate for high-rate serial packets

image

nice and useful bits are trickling in, its doing great on my builder. Runs for days and only time it gets restarted is on new releases or system restart

1 Like

Great, thanks for the feedback!

@bminer and I brainstormed a dynamic point filter today and I think have a pretty good solution for being able to optionally insert filters at any point so that points will only be generated when things change.

1 Like
  • update to nats-server to v2.10.4
  • update to nats client package to v1.31.0
  • development: envsetup.sh sources local.sh if it exists
  • Go client API for export/import nodes to/from YAML
  • siot CLI export and import commands
  • simpleiot-js improvements
  • Network Manager Client (WIP)
  • NTP Client
  • serial client: allow configuration of HR point destination
  • serial client: add “Sync Parent” option
  • Signal generator client: add support for square, triangle, and random walk
    patterns. See docs
  • fix issue with batched points of the same type/key (#658)

Note, use v0.14.1 with updated frontend assets.

image

v0.14.3

  • UI: display unknown nodes as raw type and points
  • UI: add raw view button to node expanded view. This allows us to view the raw points in any node which is useful for debugging and development. (see docs for more information)

image

1 Like

v0.14.4

  • UI: in node raw view, you can now edit/add/delete points (#676)
  • UI: add custom node types

v0.14.5

  • simpleiot-js: Fixed bugs and improved README
  • Replace deprecated io/ioutil functions (#680)
  • fixed frontend bug where only custom node types could be added
1 Like

v0.14.6

  • verb → adjective changes in several types. This is more consistent and
    accurate with how things are done in this industry (HTML, etc). This is a
    breaking change in that nodes with disable or control flag set will need to be
    reconfigured.
    • disable → disabled
    • control → controlled
  • add modbus Float32ToRegsSwapWords()
1 Like

v0.14.7

  • add modbus swap words for Int32/Uint32 writes

v0.15.0

  • NTP client: Do not set configuration if servers are not specified. This allows
    timesyncd to use the default configuration if no servers are specified.
  • server: Args now accepts a *FlagSet to allow flags to be extended
  • Influx client when writing points from a given node also adds additional tags
    based on the node that emitted the point. Previously, nodeID tag was added,
    but this has been renamed to node.id. Also added is node.type and
    node.description (populated with the value of a point of type
    “description”).
  • For each Influx DB client, the user can specify an array of tag point types
    (via point type “tagPointType”). These point types are also copied as tags for
    each point emitted by the node. For example, if node A has two points tag:city
    (i.e. Point.Type is “tag” and Point.Key is “city”) and tag:state, then these
    point values are appended to every single point emitted by node A. In Influx,
    each point would have a tag node.tag.city and node.tag.state with their
    respective Point.Text values.
  • BREAKING CHANGE: Influx DB tag nodeID is now node.id
  • update frontend dependencies and fix various build issues
  • UI: add tag UI most clients so that custom tags can be added to each node.

image

Time to update distros recipes !

1 Like