# Automation Professionals' Image Streamer Driver Module

**URL:** <https://forum.inductiveautomation.com/t/automation-professionals-image-streamer-driver-module/29371>\
**Category:** 3rd Party Modules\
**Tags:** ignition79, ignition80, ignition83, ignition81\
**Created:** [October 24, 2019, 6:11pm UTC](https://forum.inductiveautomation.com/t/automation-professionals-image-streamer-driver-module/29371 "2019-10-24T18:11:49Z")\
**Posts on this page:** 10\
**Page:** 6

<div class="post-metadata">

**Author:** ![KIM\_SUNG\_HOO](https://avatars.discourse-cdn.com/v4/letter/k/977dab/32.png) [@KIM\_SUNG\_HOO](https://forum.inductiveautomation.com/u/KIM_SUNG_HOO)\
**Post date:** [July 17, 2023, 1:20pm UTC](https://forum.inductiveautomation.com/t/automation-professionals-image-streamer-driver-module/29371/101 "2023-07-17T13:20:47Z")

</div>

> [@pturmel](#):
>
> I recommend checking each camera's last frame timestamp (OPC item) in a gateway timer event, and calling [system.device.restart()](https://docs.inductiveautomation.com/display/DOC81/system.device.restart) to restart just that camera if it stalls.

I will try it tommorrow.

thank you!

---

<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:** [July 17, 2023, 1:26pm UTC](https://forum.inductiveautomation.com/t/automation-professionals-image-streamer-driver-module/29371/102 "2023-07-17T13:26:55Z")

</div>

Note that restarting a device can also be accomplished in the gateway web interface simply by opening the device's settings (edit) and saving without any actual changes.

---

<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:** [February 8, 2024, 1:36pm UTC](https://forum.inductiveautomation.com/t/automation-professionals-image-streamer-driver-module/29371/103 "2024-02-08T13:36:02Z")

</div>

Hmmm. I released a bugfix back in May for a client, but forgot to post it here.

For Ignition v8.1+: ~~v0.5.3.231501708~~

Fixed a regression in OPC item subscriptions.

---

<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:** [June 9, 2025, 7:14pm UTC](https://forum.inductiveautomation.com/t/automation-professionals-image-streamer-driver-module/29371/104 "2025-06-09T19:14:06Z")

</div>

Automation Professionals is pleased to announce a new production release of this module. The major change here is the removal of the Wicket-based configuration pages for JAR and JNI location overrides. That functionality has been moved to a pair of environment variables to simplify deployment. As a side effect, the need for Vision Client and Designer RPC was eliminated, greatly simplifying the code. (And greatly simplifying the conversion to v8.3.)

The [documentation](https://www.automation-pros.com/streamer/doc/) has been updated to reflect this change, and to add installation guidance for Ubuntu 24.04 LTS.

For Ignition v8.1.7+: [v1.0.0.251601902](https://www.automation-pros.com/ignition/Image%20and%20Video%20Streaming%20Driver-1.0.0.251601902-v81.modl)

---

<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:** [September 29, 2025, 8:32pm UTC](https://forum.inductiveautomation.com/t/automation-professionals-image-streamer-driver-module/29371/105 "2025-09-29T20:32:21Z")

</div>

Automation Professionals is pleased to announce the production release of this module for Ignition v8.3: [v1.0.0.252721937](https://www.automation-pros.com/ignition/Image%20and%20Video%20Streaming%20Driver-1.0.0.252721937-v83.modl).

This is functionally identical to the corresponding v8.1 release above.

---

<div class="post-metadata">

**Author:** ![Kyle\_Morris](https://avatars.discourse-cdn.com/v4/letter/k/ecd19e/32.png) [@Kyle\_Morris](https://forum.inductiveautomation.com/u/Kyle_Morris)\
**Post date:** [December 5, 2025, 10:38pm UTC](https://forum.inductiveautomation.com/t/automation-professionals-image-streamer-driver-module/29371/106 "2025-12-05T22:38:28Z")

</div>

Good afternoon Mr. Turmel.

We’re encountering an error with previously working video streams after upgrading from 8.1.32 to 8.1.49.

The highly abbreviated error we’re getting in the gateway log is `java.lang.NoClassDefFoundError: org/eclipse/jetty/server/HttpOutput`, and I see from the ignition release notes for 8.1.49 has `Upgraded Jetty from version `10.0.20` to `12.0.17``.

Am I correct in concluding that this module is not currently compatible with 8.1.49?

---

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [December 5, 2025, 11:00pm UTC](https://forum.inductiveautomation.com/t/automation-professionals-image-streamer-driver-module/29371/107 "2025-12-05T23:00:07Z")

</div>

Ignition 8.1.49 has a major Jetty upgrade with api change.  
Jetty is the internal Ignition webserver.

This is the cause of incompatibility.

---

<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:** [December 6, 2025, 3:10am UTC](https://forum.inductiveautomation.com/t/automation-professionals-image-streamer-driver-module/29371/108 "2025-12-06T03:10:27Z")

</div>

Well, shoot. I'll have to make a release for 8.1.49+.

Looks like the same Jetty as in v8.3, so I can backport the fix from my v8.3 release.

---

<div class="post-metadata">

**Author:** ![afawole](https://avatars.discourse-cdn.com/v4/letter/a/34f0e0/32.png) [@afawole](https://forum.inductiveautomation.com/u/afawole)\
**Post date:** [January 26, 2026, 6:40pm UTC](https://forum.inductiveautomation.com/t/automation-professionals-image-streamer-driver-module/29371/109 "2026-01-26T18:40:14Z")

</div>

Good day Mr. Turmel,  
Have you released the update yet?

---

<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:** [January 26, 2026, 6:46pm UTC](https://forum.inductiveautomation.com/t/automation-professionals-image-streamer-driver-module/29371/110 "2026-01-26T18:46:39Z")

</div>

I have not. Won't be before next week.

[Previous page](https://forum.inductiveautomation.com/t/automation-professionals-image-streamer-driver-module/29371.md?page=5)
