Problem getting Modbus register updated by LoRaWAN

[Per Wirback]

Having setup an MS84-LR to read IO status from a LT22222-L over LoRaWAN and update Modbus registers to be read over Modbus/TCP, I have run into a strange problem. 

LoraWAN info can be read, no problem there.

Setting up the Modbus/TCP server works and defining what LoRA device to read and populate Modbus registers work also.

A Modbus client can then read the registers, 24 bytes starting at 0x0000.

But, any dynamic changes on the input status of the LT22222-L are not reflected in the Modbus registers!

The LR22222-L is setup to send updates every 10 seconds, and they arrive OK at the MS48. (unconfirmed payload with changed data)

"Show sensor History" under the Modbus tab shows the changed inputs, but when reading the Modbus registers from a client over TCP, nothing has changed.

After restarting the Modbus server in the MS84 with "Save&Apply", the Modbus registers get updated once, but then keeps its values. Restarting again updates the registers with the current LoRa received data, but nothing in the registers is ever changed without restarting.

It looks like the Modbus server implementation in the MS84-LR is a "one time shot" that read the LoRa values when starting up, but never gets updated by changed LoRa information.  

Or have I missed any config somewhere?

The Gateway is in a Stand alone setup, no connection to any Cloud, or MQTT or similar.

Node-Red is not running.

FW versions that I believe is up to date:

Name
Current Version

dragino-httpd :
2023-04-07

dragino-ui :
2025-10-21

draginomodbus :
2025-07-02

draginofwd :
2023-08-18

draginoups :
2025-04-17

dragino-fallback :
23.01.05

Brgds Per