# system.device.listDevices() doesn’t return device settings — intentional? (8.3)

**URL:** <https://forum.inductiveautomation.com/t/system-device-listdevices-doesn-t-return-device-settings-intentional-8-3/117711>\
**Category:** Ignition\
**Tags:** scripting, ignition83, perspective\
**Created:** [November 3, 2026, 2:03pm UTC](https://forum.inductiveautomation.com/t/system-device-listdevices-doesn-t-return-device-settings-intentional-8-3/117711 "2026-11-03T14:03:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gustavo\_Cardoso](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/gustavo_cardoso/32/85783_2.png) [@Gustavo\_Cardoso](https://forum.inductiveautomation.com/u/Gustavo_Cardoso)\
**Post date:** [November 3, 2026, 2:03pm UTC](https://forum.inductiveautomation.com/t/system-device-listdevices-doesn-t-return-device-settings-intentional-8-3/117711/1 "2026-11-03T14:03:47Z")

</div>

I’m trying to retrieve a list of all devices of a specific type, along with their settings, from a Perspective project. However, `system.device.listDevices()` only returns _Name_, _Enabled_, _State_ and _Driver_.

Context: I developed a custom communication driver that exposes a Device Connection Type, and I need to read a few of its settings in a device list in Perspective.

On the other hand, the new Gateway API in Ignition 8.3 exposes  
`http://<gateway>/data/api/v1/resources/list/com.inductiveautomation.opcua/device`,  
which returns all the settings and much more.

Since both serve a similar purpose, why do they return such different information? I’d expect the scripting function, which runs inside the gateway, to expose at least as much as the external API.

Is this intentional, and are there plans to expose device settings through `system.device.*`?

_Note: I’ve already worked around it by implementing a `system.<module>.listDevices()` function in my module, I’m just curious about the reasoning._

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [November 3, 2026, 2:07pm UTC](https://forum.inductiveautomation.com/t/system-device-listdevices-doesn-t-return-device-settings-intentional-8-3/117711/2 "2026-11-03T14:07:26Z")

</div>

The settings for a particular driver are defined and controlled by the module, not standardized across different driver types. The scripting function only exposes the standard properties.

Access to the rest only became possible in v8.3, due to the architecture of the new resource model. I wouldn't expect much to be done with legacy script functions.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [November 3, 2026, 5:26pm UTC](https://forum.inductiveautomation.com/t/system-device-listdevices-doesn-t-return-device-settings-intentional-8-3/117711/3 "2026-11-03T17:26:49Z")

</div>

> **[system.config.getResources | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.3/appendix/scripting-functions/system-config/system-config-getResources)**
>
> Returns all resources of the specified type.

Use the new `system.config` API and you can get full configuration of any resource.