0.3.0

Added

• Device lifecycle message
• Low-code constructor
• Automatic description generation for spec properties (JVM only)

Changed

• Property caching moved from core Device to the CachingDevice
• DeviceSpec properties no explicitly pass property name to getters and setters.
• DeviceHub.respondHubMessage now returns a list of messages to allow querying multiple devices. Device server also returns an array.
• DataForge 0.8.0

Fixed

• Property writing does not trigger change if logical state already is the same as value to be set.
• Modbus-slave triggers only once for multi-register write.
• Removed unnecessary scope in hub messageFlow

What's Changed

• 0.3.0 by @SPC-code in #13

Full Changelog: v0.2.0...v0.3.0

0.2.0

• Core interfaces for building a device server
• Magix service for binding controls devices (both as RPC client and server)
• A plugin for Controls-kt device server on top of modbus-rtu/modbus-tcp protocols
• A client and server connectors for OPC-UA via Eclipse Milo
• Implementation of byte ports on top os ktor-io asynchronous API
• Implementation of direct serial port communication with JSerialComm
• A combined Magix event loop server with web server for visualization.
• An API for stand-alone Controls-kt device or a hub.
• An implementation of controls-storage on top of JetBrains Xodus.
• A kotlin API for magix standard and some zero-dependency magix services
• Java API to work with magix endpoints without Kotlin
• MQTT client magix endpoint
• RabbitMQ client magix endpoint
• Magix endpoint (client) based on RSocket
• A magix event loop implementation in Kotlin. Includes HTTP/SSE and RSocket routes.
• Magix history database API
• ZMQ client endpoint for Magix