# Device Communications State

**URL:** <https://forum.inductiveautomation.com/t/device-communications-state/2761>\
**Category:** Ignition\
**Created:** [March 14, 2011, 1:59pm UTC](https://forum.inductiveautomation.com/t/device-communications-state/2761 "2011-03-14T13:59:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kjwilde](https://avatars.discourse-cdn.com/v4/letter/k/0ea827/32.png) [@kjwilde](https://forum.inductiveautomation.com/u/kjwilde)\
**Post date:** [March 14, 2011, 1:59pm UTC](https://forum.inductiveautomation.com/t/device-communications-state/2761/1 "2011-03-14T13:59:59Z")

</div>

What is the best way to determine the state (i.e good/bad) of communications at the device (not tag) level? I’d like to keep track of this for all devices on the network and report problems as they occur. Thanks

Kurt

---

<div class="post-metadata">

**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\
**Post date:** [March 14, 2011, 5:35pm UTC](https://forum.inductiveautomation.com/t/device-communications-state/2761/2 "2011-03-14T17:35:56Z")

</div>

The typical strategy is to have a tag for each device that you use for this purpose by monitoring that tag’s quality.

In the future each device will have a special folder of diagnostic tags, but in the meantime, use the strategy above.