Get I/O Pin Value/Status On the MQTT Response

Networking Solutions
24

Hi there,

You need to use a custom modbus register because there is no modbus address for getting the DIN value.

Regards,

25

Hello,

Do we have any option to close this form earlier and review etc? or we don’t have anything here like this?

Regards

Zain

26

Hi there,

Please refer to the above comment :

You need to use a custom modbus register because there is no modbus address for getting the DIN value.

We are unable to offer you any other workarounds.

Regards,
Arturas

27

okay

I have discuss this matter with my company. They said if this is very complicated then we don’t have to follow the DIN we just need any pin in order to have this external power check. Using which we can see in MQTT whether we are getting the power on the tower from external cable or not.

Can you tell what is the easiest way to do it? Using Analogue Pin? Relay output?

Regards

Zain

28

I am still waiting for a reply.

29

Hi there,

In your instance, as an alternative you can use the analogue pin modbus address that can be found in this link : RUT956 Monitoring via Modbus RUTOS - Teltonika Networks Wiki

Simply set up your configuration following the instructions in the link, and choosing the correct modbus value.

Regards,

Arturas

30

For Teltonika routers like the RUT956, the digital I/O status is usually not published automatically over MQTT unless it’s explicitly configured as a monitored parameter. You typically need to map the I/O values to an event or periodic publish using RMS, Event Juggler, or a custom MQTT publish rule that reads the GPIO state at intervals. Otherwise, MQTT will only report system or network metrics.

Also, make sure you’re checking whether the I/O status is exposed as telemetry data versus event-based data, as MQTT clients like MQTTX may only receive updates on state changes, not the current state on connection. RUT956 Input/Output - Teltonika Networks Wiki

In similar setups where device status is later visualized or included in recorded content (for example, creating short technical demos or status explainer videos edited with lightweight tools like InShot Pro APK having consistent and periodic status updates instead of event-only messages makes integration much easier.