🚀 Version History

🚀 Version 2.4

• Gateway redesign, supporting direct connection and binding of sub devices
• Add scene management, equivalent to device grouping, which integrates gateways, directly connected devices, or single sub devices, can configure input and operation variables, and can bind configuration and monitoring
• New data bridging, supporting HTTP push, Mqtt bridging, database storage functions, and supporting input and output sides
• New language internationalization has been added, with support for multiple languages on the web, mini programs, and apps, and the ability to configure different languages
• New data center has been added, supporting the display of data operation status for individual devices, as well as the display of historical data for multiple physical models of devices
• New data collection, data debugging, and command permission functions have been added to the equipment
• Bug fixes and code optimization
• Tip: After upgrading, the gateway device will no longer be effective. Remove the collection point template and backup the data before upgrading

🚀 Version 2.3

Details

• Multi tenant redesign, restructuring department management and transforming it into an institution, implementing multi tenant management based on the institutional dimension
• Role permissions can be flexibly allocated within the organization to support the management of subordinate organization data
• Configuration, rule engine, large screen, message notification, speaker, video support tenant isolation
• New batch import of devices has been added to device management, allowing for the selection of devices to be assigned to institutions, the recycling of devices from institutions, and the optimization of device binding and sharing
• System user isolation, distinguishing between end users and tenants
• Bug fixes and code optimization
• Tip: After upgrading, the old version departments and tenants will no longer be effective. Please backup your data before upgrading

🚀 Version 2.2

Details

• Add a rule engine, refactor device alerts and scene linkage
• Scene linkage adds product triggering and specified device triggering, multiple triggering conditions, silence time, and delayed execution, supporting object models and object array types
• Add rule scripts, support message resending, compatible with more device access
• Message notifications support email, Tencent SMS and voice, Alibaba SMS and voice, WeChat, enterprise WeChat, DingTalk and other alert notification methods
• Add SMS login
• Add positioning methods to the product, create default inherited positioning methods for devices, and allow for individual modification of devices
• Bug fixes and code optimization
• Tip: After upgrading, the old version alarm and scene linkage configuration will no longer be effective. Backup the data before upgrading

🚀 Version 2.1

Details

• Mqtt theme refactoring, unifying the object model theme into interface calls
• OTA upgrade optimization
• Upgrade Emqx to version 5.1
• Support WeChat login
• Add video center module, including video surveillance split screen display, recording management, channel management, and configuration management
• Device details optimized for lazy loading
• Device sharing supports sharing device specified functional attributes
• Modbus protocol is compatible with reading function codes 01, 02, and 04, and writing function codes 05
• Modbus parsing data type compatibility: bit, 16 bit unsigned, 16 bit signed, 32-bit signed (unsigned) (ABCD/CDAB), 32-bit floating-point number (ABCD/CDAB)
• Compatible with edge gateway solutions
• Fix scene linkage/alarm trigger command compatibility
• Fix shadow mode and integrate topics
• Device response loop, displaying details of the impact of instructions issued by the device
• Optimize the calculation, processing, and storage of data reported by devices
• Platform interface optimization, improvement, and bug fixing
• Mobile: New weather forecast, WeChat login, optimized homepage UI layout, improved user management

🚀 Version 2.0

Details

• New protocol management has been added, and the system supports custom communication protocol parsing using JSON, Modbus, and annotation methods.
• MqttBroker based on Netty, supports clustering, TCP server and UDP server built on Netty, and all protocol devices can be managed uniformly.
• Added gateway module, supporting device data forwarding, protocol decoding and encoding, data calculation, and rule engine
• Refactoring of the Emqx message processing module, Emq supports Modbus protocol and various hardware custom communication protocols on the original basis. Support data forwarding and data decoupling.
• OTA front-end and back-end upgrade and reconstruction, benchmarking enterprise level OTA upgrade process
• Supports two types of MQTTBroker, EMQ and Netty based MqttBroker, which can be freely switched.
• Support Modbus cloud polling
• Support Modbus device simulation
• Front end supporting backend business page update.

1.平台总览

图片1

2.平台架构

图片1

3.模块调整

图片1

🚀 Version 1.3.1

Details

• New object types and object array types have been added to the object model to support grouping of sub devices and object models
• Change the array type of the object model to: integer (replace int), decimal (replace double), string, object
• Remove is_top (top) from the object model, add is_deadonly (read-only) and order (sorted)
• Alarm/timing/scene linkage does not currently support object types, object array types, and arrays
• Simplify the device list page, remove object models, and improve page loading speed
• Integrating video surveillance into products and devices
• Add video configuration menu, dynamically configure streaming media servers and batch generate device channels
• Video surveillance supports live streaming, pan tilt control, and video playback
• Video surveillance uses an open-source player, a commercial player has been purchased, and version 2.0 has been released for use
• Mobile corresponding function support