# More status options for devices
**URL:** https://forums.losant.com/t/more-status-options-for-devices/5307
**Category:** Help
**Tags:** dashboard
**Created:** [October 24, 2023, 3:54am UTC](https://forums.losant.com/t/more-status-options-for-devices/5307 "2023-10-24T03:54:43Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@Braian\_Pita](https://forums.losant.com/u/Braian_Pita)
#### Post date: [October 24, 2023, 3:54am UTC](https://forums.losant.com/t/more-status-options-for-devices/5307/1 "2023-10-24T03:54:43Z")
Good evening,
I am currently working on a dashboard with a “Device List” content block. I was wondering if there is a way to add additional options to the connection status. In my use case, we need to differenciate between “Connected”, “Disconnected”, and “Communication Errors”. I want to be able to show the green icon for connected and red icon for disconnected as it is on the device list on my image, but I also want a “gray” icon for connection errors.
Is there a way to achieve this? Or any workarounds to get a similar result?
Thank you in advance
---
### Author:  [@Dylan\_Schuster](https://forums.losant.com/u/Dylan_Schuster)
#### Post date: [October 24, 2023, 2:37pm UTC](https://forums.losant.com/t/more-status-options-for-devices/5307/2 "2023-10-24T14:37:46Z")
Actually there is a workaround! The Losant API supports [setting a device’s connection status](https://docs.losant.com/rest-api/device/#set-connection-status), which you could use to set the device as “disconnected” with a custom reason (i.e. “Communication Errors”).
When it comes to the block, you could add a [custom column](https://docs.losant.com/dashboards/blocks/device-list/#custom) that renders your own custom icon and the “reason” in the case of the third status.
---
### Author:  [@Braian\_Pita](https://forums.losant.com/u/Braian_Pita)
#### Post date: [October 30, 2023, 12:55am UTC](https://forums.losant.com/t/more-status-options-for-devices/5307/3 "2023-10-30T00:55:10Z")
Thank you for the help,
I managed to do most of this, but I am having issues with accessing the custom reason inside the custom column. As far as I can tell, there is no “disconnectReason” attribute inside the connectionInfo object. And I could not find it anywhere inside the device object give in the custom column.
Also, is there a way to control the size of the image? I used the format ![image]() but I can only change the image size by manually altering the image instead of inside the template.
Thanks again!
---
### Author:  [@Dylan\_Schuster](https://forums.losant.com/u/Dylan_Schuster)
#### Post date: [October 30, 2023, 12:55pm UTC](https://forums.losant.com/t/more-status-options-for-devices/5307/4 "2023-10-30T12:55:08Z")
Huh, you’re right. The disconnectReason is available in the [connection log block](https://docs.losant.com/dashboards/blocks/device-connection-log/) but not the device list. Let me see if we can get that added to the device list block response.
---
### Author:  [@Braian\_Pita](https://forums.losant.com/u/Braian_Pita)
#### Post date: [October 30, 2023, 11:03pm UTC](https://forums.losant.com/t/more-status-options-for-devices/5307/5 "2023-10-30T23:03:30Z")
Thank you for the confirmation. Let me know of any updates, and if possible, when to expect this to be added if you plan on doing so. In the meantime, I think I will try to find a different workaround.
---
### Author:  [@Dylan\_Schuster](https://forums.losant.com/u/Dylan_Schuster)
#### Post date: [October 31, 2023, 12:00am UTC](https://forums.losant.com/t/more-status-options-for-devices/5307/6 "2023-10-31T00:00:55Z")
I was hoping it would be a quick fix to get that in before our November release but unfortunately it isn’t as easy to expose that property as I had hoped.
An alternative would be to store your custom disconnection reason as a [device tag](https://docs.losant.com/devices/overview/#device-tags).
---
### Author:  [@Braian\_Pita](https://forums.losant.com/u/Braian_Pita)
#### Post date: [November 1, 2023, 1:45am UTC](https://forums.losant.com/t/more-status-options-for-devices/5307/7 "2023-11-01T01:45:08Z")
Thank you for the help,
I managed to create a workaround solution by directly using the device latest state instead, but I hope this gets added soon as a supported feature. Have a good day!