# Beaconing Device Status in Gateway **URL:** \ **Category:** Ignition\ **Created:** [October 1, 2014, 7:10pm UTC](https://forum.inductiveautomation.com/t/beaconing-device-status-in-gateway/9130 "2014-10-01T19:10:41Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![srosbury](https://avatars.discourse-cdn.com/v4/letter/s/a88e57/32.png) [@srosbury](https://forum.inductiveautomation.com/u/srosbury)\ **Post date:** [October 1, 2014, 7:10pm UTC](https://forum.inductiveautomation.com/t/beaconing-device-status-in-gateway/9130/1 "2014-10-01T19:10:41Z")
When using the “Is Connected” tag for showing device up/down status in gateway util in 7.7… If the IP of the connection to the PLC is not valid I get a broken link overlay showing a tag and information symbol and the status in the gateway shows a cycling “Connecting…Connecting: Determining Protocol” then “Disconnected:Defining Protocol” message. I do not see the “0” state which should show a red transparent overlay and conversely a state of “1” which would showing the green transparent overlay if the connection was complete. Question 1: Is it possible to get or reference a tag which will show all Six states possible for the connection (i.e. Connecting: Determining Protocol, Disconnected: Determining Protocol, Connected, Disconnected, Unknown) as shown in the Gateway-\>Configure-\>Devices table? Question 2: If the connecting process cannot complete due to an invalidor incomplete IP address say and the cycling of “Connecting: Determining Protocol” and “Disconnected: Determining Protocol” does not have a “state” assigned to it, is this what triggers the Broken Tag overlay with the information symbol? Cordially, Steven Rosbury Miller-Eads Automation ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [October 2, 2014, 6:06pm UTC](https://forum.inductiveautomation.com/t/beaconing-device-status-in-gateway/9130/2 "2014-10-02T18:06:26Z")
The quality of the “Is Connected” tag shouldn’t be going bad when the connection drops, that’s likely a bug. That being said, the tag having bad quality is probably just as good an indicator that it’s not connected as value=False and good quality. So you could watch for (value=False || Bad Quality) wherever you need the status right now. There’s no enumeration of states because it’s just a free-form String that each driver implementation is free to use however it wants. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [December 20, 2018, 8:05pm UTC](https://forum.inductiveautomation.com/t/beaconing-device-status-in-gateway/9130/3 "2018-12-20T20:05:12Z")
Split this topic on December 20, 2018, 8:05pm UTC 3 posts were split to a new topic: [Bad Quality Tags from Logix Devices](https://forum.inductiveautomation.com/t/bad-quality-tags-from-logix-devices/21550)