# What is the most correct way of linking old nodes to work with Dashboard 2

**URL:** <https://discourse.nodered.org/t/what-is-the-most-correct-way-of-linking-old-nodes-to-work-with-dashboard-2/86280>\
**Category:** Dashboard\
**Tags:** dashboard-2\
**Created:** [8 March 2024 16:12 UTC](https://discourse.nodered.org/t/what-is-the-most-correct-way-of-linking-old-nodes-to-work-with-dashboard-2/86280 "2024-03-08T16:12:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Soiski](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/soiski/32/88848_2.png) [@Soiski](https://discourse.nodered.org/u/Soiski)\
**Post date:** [8 March 2024 16:12 UTC](https://discourse.nodered.org/t/what-is-the-most-correct-way-of-linking-old-nodes-to-work-with-dashboard-2/86280/1 "2024-03-08T16:12:24Z")

</div>

So lets take a sample of a person who's great in linking lines etc. (I consider quite my self quite good on it 😁) but is unable yet to write any new code / widget/ nodes to Dashboard2 .  
I have a a ui-scheduler build for D1 and loved moving majority of my items into D2 but this I have not been able. So what I did is the keeping this "widget" still in D1 and I just called it via iFRAME function. Is this the way or any smarter way to do it (for us simple folks)

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/e/3e09cf66796898dd491ea613b712a1919a101dab.png)

Now in D2 via iFrame, works but....

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/3/634dd5ce68929eb1063c9120a4001826b402a6bb.png)

Thank you

---

<div class="post-metadata">

**Author:** ![joepavitt](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/joepavitt/32/59722_2.png) [@joepavitt](https://discourse.nodered.org/u/joepavitt)\
**Post date:** [8 March 2024 16:27 UTC](https://discourse.nodered.org/t/what-is-the-most-correct-way-of-linking-old-nodes-to-work-with-dashboard-2/86280/2 "2024-03-08T16:27:14Z")

</div>

Hi @Soiski - because D2.0 is completely Vue-based, and D1.0 is Angular-based, they're not front-end compatible, so there would need to be a new, D2.0-friendly `ui-scheduler` built.

If you are the author of `ui-scheduler`, or fancy the challenge anyway, and want to get it ported over, then we do have a Contribution Guide for third-party widgets [here](https://dashboard.flowfuse.com/contributing/widgets/third-party.html#getting-started) which points to an [example third party widget repo](https://github.com/FlowFuse/node-red-dashboard-2-ui-example).

We also have:

- UI LED: [GitHub - FlowFuse/node-red-dashboard-2-ui-led: A simple LED status indicator for the Node-RED Dashboard 2.0](https://github.com/FlowFuse/node-red-dashboard-2-ui-led)
- UI Webcam (built by @sumitshinde-84): [GitHub - sumitshinde-84/node-red-dashboard-2-ui-webcam: The ui-webcam node for Node-RED Dashboard 2.0 enables users to integrate webcam functionality into Node-RED Dashboard 2.0. It allows users to capture images, select different cameras, and control webcam features through an intuitive user interface within the Node-RED Dashboard.](https://github.com/sumitshinde-84/node-red-dashboard-2-ui-webcam)

---

<div class="post-metadata">

**Author:** ![Soiski](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/soiski/32/88848_2.png) [@Soiski](https://discourse.nodered.org/u/Soiski)\
**Post date:** [8 March 2024 16:48 UTC](https://discourse.nodered.org/t/what-is-the-most-correct-way-of-linking-old-nodes-to-work-with-dashboard-2/86280/3 "2024-03-08T16:48:07Z")

</div>

Hi Joe, unfortunately not the author. Just enjoying other genius peoples hard work 🤩

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [7 April 2024 16:48 UTC](https://discourse.nodered.org/t/what-is-the-most-correct-way-of-linking-old-nodes-to-work-with-dashboard-2/86280/4 "2024-04-07T16:48:32Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.