# OPC-UA driver for Ignition 8: New "Device" interface?

**URL:** <https://forum.inductiveautomation.com/t/opc-ua-driver-for-ignition-8-new-device-interface/25046>\
**Category:** Module Development\
**Tags:** sdk, ignition80\
**Created:** [May 16, 2019, 1:53am UTC](https://forum.inductiveautomation.com/t/opc-ua-driver-for-ignition-8-new-device-interface/25046 "2019-05-16T01:53:38Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**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:** [April 21, 2020, 1:44pm UTC](https://forum.inductiveautomation.com/t/opc-ua-driver-for-ignition-8-new-device-interface/25046/7 "2020-04-21T13:44:31Z")

</div>

Ah, and just as a warning to you and anyone else who might be using this new Device API, there are some breaking changing coming down the line ☹

Whenever Milo 0.5.0 is released and Ignition updates to it there will be some required changes to your Device implementations. You can get a feel for what’s changing here: [Update opc-ua-device example for upcoming Device API changes by kevinherron · Pull Request #43 · inductiveautomation/ignition-sdk-examples · GitHub](https://github.com/inductiveautomation/ignition-sdk-examples/pull/43)

and the corresponding change in Milo here: [Remove AbstractLifecycle from ManagedAddressSpace class hierarchy by kevinherron · Pull Request #627 · eclipse/milo · GitHub](https://github.com/eclipse/milo/pull/627)

---

_[View the full topic](https://forum.inductiveautomation.com/t/opc-ua-driver-for-ignition-8-new-device-interface/25046)._