Feedback

configure at run-time through web console: enable/disable Modbus feature expose both the Modbus Master & Modbus Slave tables to allow adds/changes. change Modbus Poll frequency, including to zero (see point below) add a Modbus Poll block, which manually polls all the defined registers in a specified Master (or Slave)

allows structured data storage and manipulation in apps without the performance overhead (and wear) of using flash writes. should allow the ability to 'manually' copy a table from memory to flash (or reverse direction).

enables client deployments in small business/residential environments where there is no existing MQTT server, nor an appetite to purchase/host another appliance to do so.

When new platform updates are rolled out, it should include a link which lists bug fixes and/or new features so we know if changes have been made that enable outcomes for us.

Be able to enable/disable MQTT client at runtime through Web Console/Settings

I am using SIO-16TC devices, each with 16 sequential input registers (512–527). Currently, I need to read each register individually, but it would be very helpful if the system could batch Modbus requests so that all registers from one device can be read in a single request. Requested features: Batching support : Allow one Modbus read request per device when registers are sequential (e.g., 512–527). Increased register length :– Please increase the maximum “Length (Number of registers)” limit up to 25 to support devices with larger blocks of registers. Output formatting : Option to display all channel values of one device in a single row for clarity, for example: Device1: CH0=27.9, CH1=28.0, CH2=27.8,.... Device2: CH0=27.9, CH1=28.0, CH2=27.8,....

Would it be possible to unify my accounts? I have an 'email' account and a Google OAuth-setup account tied to the same email address (however, the Google OAuth authentication is broken for me current)