IoT Bridge 23.3.11

Created by Tartabit Support, Modified on Thu, 9 Mar, 2023 at 3:25 PM by Tartabit Support

We are excited to announce the availability of version 23.3.11 of the IoT Bridge.  As always, the official release notes can be found here:  https://docs.tartabit.com/en/ReleaseNotes


23.3.11

  • notes
    • private deployments are now supported in Google Kubernetes Engine (GKE)
    • single-signon is now available for Google
    • refer to the upgrade instructions here for special instructions applying this update
    • significant helm chart improvements to aid deployment and debugging
  • core-google 1.0.0
    • new service for single-signon with Google
  • core-proxy 0.9.4
    • new service for enabling single deployments of the IoT bridge to span multiple Kubernetes clusters in different regions.
  • core-trigger 1.3.10
    • added convert.binReader()to read arbitray binary buffers.
      • supports big/little endian buffers
      • supports multiple different data types such as integers, floats, bools, strings, and byte arrays.
    • added convert.bitReader()to read bit-packed structures like ASN.1 UPER encodings
      • reads primitive values from arbitrary bit offsets
    • added api.post()api.put()api.delete(), and api.get() functions to allow calling APIs within the IoT Bridge to automate provisioning and configuration of the platform
    • added datetime format for date.format() function to support SQL syntax
    • added hash.crc32()hash.crc64()hash.crc64signed(), and hash.sha256() functions to allow for inline hash generation on input data.
    • added statusDetails object to the service and endpoint objects in trigger events
  • core-ui 1.4.11
    • added trigger auto-completions for trigger variables
    • improved lwm2m object browser to better visualize in-flight requests and device message queue
    • updated underlying nginx image for security fixes
    • added Google SSO to login page
    • added option to send welcome email when creating a new user
  • svc-azure-iot 1.3.4
    • major change devices now connect to IoT Hub through shared AMQP connections instead of individual MQTT connections. this change reduces the number of connections to IoT Hub from 1:1 to 995:1.
    • updated TLS certificate for new root CA published by Microsoft
    • added on-createon-connect, and on-disconnect events do better expose the connection lifecycle of a device
    • increased timeout from 5 seconds to 30 seconds for all synchronous trigger actions
  • svc-cdp-1nce 1.0.2
    • new service for integrating with the 1NCE API, data streams, and 1NCE OS
    • daily synchronization of SIM utilization
    • events for usage, device events, and cloud data
    • trigger functions to edit, activate, send sms, and more.
  • svc-lora 1.0.9
    • added support for NetMore LNS.
    • updated device decoders with 75 new device decoders
  • svc-lwm2m 1.6.7
    • fix for crash due to race condition when registering
    • allow FOTA on instances other than instance 0 (technically not supported by the specification)
    • added last known timestamp for lastKnown() data. Now variables with a ~ will contain a timestamp when a resource was last updated
    • blockwise data transfer fixes for out of sequence block requests
    • DTLS library enhanced with full support for RFC-9146 (DTLS with connection ID)
    • continued support for older draft-ietf-tls-dtls-connection-id-05 connection ID support
  • svc-mqtt 1.1.0
    • added support for mqtt client mode in addition to the existing mqtt broker mode
    • client supports publishing and subscribing to topics on external message brokers
    • client supports unencrypted and tls encrypted communications
  • svc-queclink 1.3.11
    • added GTVGL, GTIGL, GTVGN, GTVGF, and GTMPN events for the GV53 devices
  • svc-sql 1.0.0
    • new service for communicating with SQL databases
    • initial support for Microsoft SQL Server
    • coming soon: MySQL, and PostgreSQL
    • added functions sql.execute() and sql.select() to interact with remote SQL databases

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article