# New Ignition module and strange message

**URL:** <https://forum.inductiveautomation.com/t/new-ignition-module-and-strange-message/11554>\
**Category:** Ignition\
**Created:** [April 21, 2016, 4:00pm UTC](https://forum.inductiveautomation.com/t/new-ignition-module-and-strange-message/11554 "2016-04-21T16:00:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![thierry38](https://avatars.discourse-cdn.com/v4/letter/t/919ad9/32.png) [@thierry38](https://forum.inductiveautomation.com/u/thierry38)\
**Post date:** [April 21, 2016, 4:00pm UTC](https://forum.inductiveautomation.com/t/new-ignition-module-and-strange-message/11554/1 "2016-04-21T16:00:57Z")

</div>

Hi,

We’re working to developp a new Ignition driver module and we’re trying to solve an issue whose effect is to display a lot of strange “[DeviceSubscriptionItem] : No node set!” 😢

It’s occured after the following action:  
[ul]

- Start Ignition system
- Edit metadata and enable one device managed by our new driver module. We don’t have any problem and no strange message.
- Edit again the metadata of this device.  
[list]
- The “disconnect” method of the driver is called.
- A new instance of our driver is created and connect method is called.  
[/ul]  
[/list:u]

A this time, we’ve a lot of “[DeviceSubscriptionItem] : No node set!” messages which are written in the Ingition console. The problem is clearly linked to our code because if I disable the device, no other message is displayed.

When a message is displayed, the stack is the following.  
[ul]  
Logger(Category).warn(Object) line: 1039   
LoggerEx.warn(String) line: 302   
DeviceSubscriptionItem.setValue(DataValue) line: 77   
AggregateSubscriptionItem.setValue(DataValue) line: 54   
ReadRequest.receiveMessage(Integer, Object) line: 54   
ReadRequest.receiveMessage(Object, Object) line: 16   
ScheduledRequest.receiveMessage(M, Object) line: 85   
BasicRequestCycle.deliverMessage(M, Object, PendingRequest) line: 184   
BasicRequestCycle.messageArrived(M, Object) line: 166   
EcoSpecDriver(AbstractDriver).messageArrived(M) line: 708   
EcoSpecDriver(NodeMapDriver).messageDone(Integer) line: 76   
ReadRequest$1.run() line: 74   
Executors$RunnableAdapter.call() line: 511   
ScheduledThreadPoolExecutor$ScheduledFutureTask(FutureTask).run() line: 266   
ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor$ScheduledFutureTask) line: 180   
ScheduledThreadPoolExecutor$ScheduledFutureTask.run() line: 293   
ScheduledThreadPoolExecutor(ThreadPoolExecutor).runWorker(ThreadPoolExecutor$Worker) line: 1142   
ThreadPoolExecutor$Worker.run() line: 617   
Thread.run() line: 745   
[/ul]

In bold are the two lines which correspond to our driver but it’s in fact the standard NodeMapDriver.messageDone and AbstractDriver.messageArrived methods (not overrided). We’re trying to understand why the problem occurs and which actions / part of code in our driver code can explain this problem. ![:scratch:](https://us1.discourse-cdn.com/inductiveautomation/original/1X/76d1620bec252bfac07050c889ff5a91dc8a9c25.gif ":scratch:")

Note that I didn’t find any sendMessage call in our code !!!

Anybody has an idea and could help us ?

Thanks

---

<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, 2016, 4:05pm UTC](https://forum.inductiveautomation.com/t/new-ignition-module-and-strange-message/11554/2 "2016-04-21T16:05:18Z")

</div>

You don’t need to worry about this - it’s some logging in DeviceSubscriptionItem that is no longer relevant and needs to be re-worked on our side. I’ve gone ahead and fixed this for 7.8.4.

---

<div class="post-metadata">

**Author:** ![thierry38](https://avatars.discourse-cdn.com/v4/letter/t/919ad9/32.png) [@thierry38](https://forum.inductiveautomation.com/u/thierry38)\
**Post date:** [April 22, 2016, 7:08am UTC](https://forum.inductiveautomation.com/t/new-ignition-module-and-strange-message/11554/3 "2016-04-22T07:08:09Z")

</div>

Ok

Thanks for this quick answer. 😉

Thierry

---

<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:** [July 2, 2016, 7:47am UTC](https://forum.inductiveautomation.com/t/new-ignition-module-and-strange-message/11554/4 "2016-07-02T07:47:46Z")

</div>

Is the fix for this message in the 7.8.4-beta1.20160630-1229 ?

---

<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:** [July 2, 2016, 1:56pm UTC](https://forum.inductiveautomation.com/t/new-ignition-module-and-strange-message/11554/5 "2016-07-02T13:56:37Z")

</div>

Yes, it should be