# Custom Node: collect & store runTime (mqtt) data in configuration note and access it from a node

**URL:** https://discourse.nodered.org/t/custom-node-collect-store-runtime-mqtt-data-in-configuration-note-and-access-it-from-a-node/14176
**Category:** Developing Nodes
**Created:** [9 August 2019 16:11 UTC](https://discourse.nodered.org/t/custom-node-collect-store-runtime-mqtt-data-in-configuration-note-and-access-it-from-a-node/14176 "2019-08-09T16:11:21Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [9 August 2019 22:36 UTC](https://discourse.nodered.org/t/custom-node-collect-store-runtime-mqtt-data-in-configuration-note-and-access-it-from-a-node/14176/2 "2019-08-09T22:36:48Z")

</div>

So without studying your code fully, am I right in saying your node will subscribe to a specific MQTT topic (`homie/#`) and provide a kinda store to permit uses to access values whenever they want?

If so, users could achieve this with standard nodes but I do admire the efforts to simplify it for users.

However, you should be more generic. For example, hard coding `homie/#` will seriously limit usability for a lot of people. This should be a setting property on your nodes configuration.

Forgive me if I am reading this wrong.

Let me know and I will try to help as best I can

---

_[View the full topic](https://discourse.nodered.org/t/custom-node-collect-store-runtime-mqtt-data-in-configuration-note-and-access-it-from-a-node/14176)._