# How to listen to Websocket URI in Ignition

**URL:** <https://forum.inductiveautomation.com/t/how-to-listen-to-websocket-uri-in-ignition/58273>\
**Category:** Ignition\
**Created:** [April 11, 2022, 7:45am UTC](https://forum.inductiveautomation.com/t/how-to-listen-to-websocket-uri-in-ignition/58273 "2022-04-11T07:45:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marouene\_Dakhlaoui](https://avatars.discourse-cdn.com/v4/letter/m/9de053/32.png) [@Marouene\_Dakhlaoui](https://forum.inductiveautomation.com/u/Marouene_Dakhlaoui)\
**Post date:** [April 11, 2022, 7:45am UTC](https://forum.inductiveautomation.com/t/how-to-listen-to-websocket-uri-in-ignition/58273/1 "2022-04-11T07:45:04Z")

</div>

I have set up a server transmitting live video feed through Websocket, I would like to know can I listen to the WebSocket URI and display the feed in Ignition, I did the same thing through HTTP, and now I am testing WebSocket, thank you!

---

<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:** [April 11, 2022, 3:14pm UTC](https://forum.inductiveautomation.com/t/how-to-listen-to-websocket-uri-in-ignition/58273/2 "2022-04-11T15:14:48Z")

</div>

Not easily.

I would say a custom module is required.

---

<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:** [April 11, 2022, 4:04pm UTC](https://forum.inductiveautomation.com/t/how-to-listen-to-websocket-uri-in-ignition/58273/3 "2022-04-11T16:04:19Z")

</div>

I thought I saw you recently show how to upgrade to websocket using httpClient?

---

<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:** [April 11, 2022, 4:32pm UTC](https://forum.inductiveautomation.com/t/how-to-listen-to-websocket-uri-in-ignition/58273/4 "2022-04-11T16:32:34Z")

</div>

Sure, you could probably open a WS via httpClient. I don’t know how you’d emit that data to render in a component (Vision would be _easier_, Perspective would be harder) after that, though.

---

<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:** [April 11, 2022, 5:04pm UTC](https://forum.inductiveautomation.com/t/how-to-listen-to-websocket-uri-in-ignition/58273/5 "2022-04-11T17:04:57Z")

</div>

Presumably you’d run a long-lived thread to manage the websocket connection and publish incoming information in tags. Or “publish” to script module top-level objects of some form. Or use Perspective session messages to distribute the content.

{Not necessarily a comprehensive list.}