# Some MQTT tags stay Bad\_NotConnected

**URL:** <https://forum.cirrus-link.com/t/some-mqtt-tags-stay-bad-notconnected/413>\
**Category:** Ignition Modules\
**Created:** [August 30, 2023, 3:46pm UTC](https://forum.cirrus-link.com/t/some-mqtt-tags-stay-bad-notconnected/413 "2023-08-30T15:46:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fielies](https://avatars.discourse-cdn.com/v4/letter/f/d9b06d/32.png) [@Fielies](https://forum.cirrus-link.com/u/Fielies)\
**Post date:** [August 30, 2023, 3:46pm UTC](https://forum.cirrus-link.com/t/some-mqtt-tags-stay-bad-notconnected/413/1 "2023-08-30T15:46:29Z")

</div>

I keep on running into this odd issue. I have the following tags on the edge:

![image](https://canada1.discourse-cdn.com/flex028/uploads/cirrus_link/original/1X/e3b42f5e2af21a98c026e0f9ef6cc53ec1ad8078.png)

These tags are then transmitted with transmission module, here is the resulting tags under MQTT Engine provider:

![image](https://canada1.discourse-cdn.com/flex028/uploads/cirrus_link/original/1X/c2f68b0dce8d57b6dcd8ddc1cd2932221290b7e8.png)

On closer investigation it seems that the values that are not coming through have not changed since the last node offline event and the ones that are coming through, have changed.

I think what is happening is that some values rarely change (weeks/months) and then a node goes offline and online and everything is Bad\_NotConnected until it’s value changes. Only then does it update.

How does one get around this? I assumed that with the rebirth, the last known values would be published?

---

<div class="post-metadata">

**Author:** ![dan.potter](https://avatars.discourse-cdn.com/v4/letter/d/6de8d8/32.png) [@dan.potter](https://forum.cirrus-link.com/u/dan.potter)\
**Post date:** [August 30, 2023, 6:10pm UTC](https://forum.cirrus-link.com/t/some-mqtt-tags-stay-bad-notconnected/413/2 "2023-08-30T18:10:31Z")

</div>

Hello Fielies,

This may have been addressed in later versions of our modules. If you meet the minimum Ignition version requirements I would take Transmission and Engine up to our latest v4.0.18.

Compatibility listings:  
[https://docs.chariot.io/display/CLD80/Ignition+Compatibility+with+Cirrus+Link+Modules](https://docs.chariot.io/display/CLD80/Ignition+Compatibility+with+Cirrus+Link+Modules)

If this does not solve the issues please open a support ticket with us at [support@cirrus-link.com](mailto:support@cirrus-link.com)

Regards,

Daniel

---

<div class="post-metadata">

**Author:** ![Fielies](https://avatars.discourse-cdn.com/v4/letter/f/d9b06d/32.png) [@Fielies](https://forum.cirrus-link.com/u/Fielies)\
**Post date:** [September 5, 2023, 4:30pm UTC](https://forum.cirrus-link.com/t/some-mqtt-tags-stay-bad-notconnected/413/3 "2023-09-05T16:30:34Z")

</div>

Hi Daniel,

Thanks for the info. I updated all the Ignition GW’s transmission and engine modules as you stated. Now we wait and see.