# Dashboard 2.0 Pre-Alpha Available

**URL:** https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142
**Category:** General
**Tags:** dashboard-2
**Created:** [28 July 2023 13:39 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142 "2023-07-28T13:39:33Z")
**Posts on this page:** 20
**Page:** 9

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [29 September 2023 07:45 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/161 "2023-09-29T07:45:54Z")

</div>

Could I put in a request please for some of the remaining basic issues with the core nodes to be cleared up, as they are preventing me from implementing my current dashboards in D2.  
In particular

> <https://github.com/FlowFuse/flowforge-nr-dashboard/issues/209>
>
> As with D1, the Button widget should have an option to emulate a button click if… a message is passed in. It should then send the received message, but with the configured topic and payload.
> However, if the message includes msg.enabled then this should not emulate a click.

> <https://github.com/FlowFuse/flowforge-nr-dashboard/issues/193>
>
> \### Description
> 
> Captures the "Dialog" functionality from \`ui-toast\` in Dashboar…d 1.0, that has not been ported to the \`ui-notification\` widget in D2.0
> 
> This should utilise 
> 
> \### Properties
> 
> \- Labelling:
> - Cancel
> - OK/Confirm
> \- Properties from Vuetify we could implement:
> - Full Screen (https://vuetifyjs.com/en/components/dialogs/#fullscreen)
> - Transitions (https://vuetifyjs.com/en/components/dialogs/#transitions)
> 
> 
> \### Events
> 
> \- \*\*on-action\*\*: On submitting/confirming the dialog, a \`msg\` should be sent on with relevant content.
> 
> 
> \### Controls
> 
> \_No response\_
> 
> \### Existing Examples
> 
> https://vuetifyjs.com/en/components/dialogs/
> 
> \### Have you provided an initial effort estimate for this issue?
> 
> I have provided an initial effort estimate

> <https://github.com/FlowFuse/flowforge-nr-dashboard/issues/210>
>
> \### Description
> 
> https://github.com/flowforge/flowforge-nr-dashboard/issues/141#…issuecomment-1725782775
> 
> 
> 
> \### Have you provided an initial effort estimate for this issue?
> 
> I have provided an initial effort estimate

---

<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: [29 September 2023 08:05 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/162 "2023-09-29T08:05:57Z")

</div>

Hi Colin, will be prioritising a day or two tackling these once I have [Third Party Widget Support by joepavitt · Pull Request #221 · FlowFuse/flowforge-nr-dashboard · GitHub](https://github.com/FlowFuse/flowforge-nr-dashboard/pull/221) tied up. I've also been having to work on Product work last week ahead of our release yesterday, so didn't actually get any Dashboard work done, and I only work 4 days a week - but will get to it all 😄

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [29 September 2023 09:16 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/163 "2023-09-29T09:16:27Z")

</div>

I wasn't meaning to pressurise, just making sure these had not got forgotten.  
Working on new stuff is always more interesting than tidying up loose ends 🙂

---

<div class="post-metadata">

### Author: ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)
#### Post date: [29 September 2023 09:42 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/164 "2023-09-29T09:42:46Z")

</div>

> [@Colin](#):
>
> I wasn't meaning to pressurise...

Of course not 😆😆😆

---

<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: [5 October 2023 15:39 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/165 "2023-10-05T15:39:26Z")

</div>

Thought the crowd here may be interested to know that I'll be running a [FlowFuse Webinar at the end of October](https://flowfuse.com/webinars/2023/dashboard-20/) all about Dashboard 2.0. Hope to see some of you there.

---

<div class="post-metadata">

### Author: ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [5 October 2023 16:45 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/166 "2023-10-05T16:45:14Z")

</div>

Thanks Joe, will it be recorded? I probably won't be able to make that time.

---

<div class="post-metadata">

### Author: ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)
#### Post date: [5 October 2023 16:51 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/167 "2023-10-05T16:51:50Z")

</div>

> [@TotallyInformation](#):
>
> will it be recorded? I probably won't be able to make that time.

Yes unfortunately I probably won't be able to attend. But all past webinar recordings are available [here](https://flowfuse.com/webinars/).

---

<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: [5 October 2023 17:23 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/168 "2023-10-05T17:23:23Z")

</div>

Yep, it will be recorded and posted to our YouTube Channel and "Webinars" page on our Website

---

<div class="post-metadata">

### Author: ![CONNECT](https://avatars.discourse-cdn.com/v4/letter/c/9fc348/32.png) [@CONNECT](https://discourse.nodered.org/u/CONNECT)
#### Post date: [5 October 2023 20:32 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/169 "2023-10-05T20:32:43Z")

</div>

@joepavitt  
Dashboard 2.0 nodes will be available only in FlowForge?  
I'm looking for monetization opportunities and one of the directions I was thinking about is making my UI nodes [iglass-nodes (node) - Node-RED](https://flows.nodered.org/node/iglass-nodes) work only in FlowForge?  
Is it possible to implement something like a widget store on the FlowForge?

---

<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: [6 October 2023 07:41 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/170 "2023-10-06T07:41:07Z")

</div>

> [@CONNECT](#):
>
> Dashboard 2.0 nodes will be available only in FlowForge?

Dashboard 2.0 is completely Open Source, and already available in the [Node-RED flow library](https://flows.nodered.org/node/@flowforge/node-red-dashboard). You can install it from the "Manage Palette" option in Node-RED as you would Dashboard 1.0.

If you would like to have your widgets working inside Dashboard 2.0, that is possible, as with the `0.6.0` release we made it possible to create third-party integrations, which you can read more about in the docs [here](https://dashboard.flowfuse.com/contributing/widgets/third-party.html). I'm also planning on writing a piece of content to the FlowFuse blog (hopefully today, maybe early next week) about this in more detail too.

On FlowFuse, we have also just released [Private NPM Catalogs](https://flowfuse.com/blog/2023/10/use-private-custom-nodes-with-flowfuse/) where you can configure your own Node-RED instances to use a set of private npm modules, which could include your own work. Making that accessible to others would be possible by sharing the link to your private npm registry, which would be down to you to manage access/sharing.

---

<div class="post-metadata">

### Author: ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)
#### Post date: [8 October 2023 11:34 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/171 "2023-10-08T11:34:31Z")

</div>

Is there any documentation for the chart node yet, I'm trying to get the x-axis to show time/date (instead of - is it a epoch timestamp?)

---

<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 October 2023 11:47 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/172 "2023-10-08T11:47:39Z")

</div>

@Paul-Reed May be a version update required, i added that into 0.5.0 iirc, we have the docs here: [Chart ui-chart | Node-RED Dashboard 2.0](https://dashboard.flowfuse.com/nodes/widgets/ui-chart.html)

You can set the x-axis type to "Timescale", which is also the default now for any new chart nodes added to the editor.

---

<div class="post-metadata">

### Author: ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)
#### Post date: [8 October 2023 11:55 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/173 "2023-10-08T11:55:13Z")

</div>

I'm already using v0.5.0 and its still showing the epoch timestamp.

Oh Wait... it was an existing flow, and I had to delete the chart node and re-add it again.  
Now I get time/date.

Thanks

---

<div class="post-metadata">

### Author: ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [16 October 2023 01:08 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/174 "2023-10-16T01:08:14Z")

</div>

The Radio Group node looks like it is not creating a fresh msg if you have sent a msg thru it previously and have the `If msg arrives on input, pass through to output: ` checked off.

I opened an issue on gitHub with a flow reproducing the issue: [http://localhost:1880/#flow/8a69c70383ca3f27](http://localhost:1880/#flow/8a69c70383ca3f27)

---

<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: [24 October 2023 16:35 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/175 "2023-10-24T16:35:56Z")

</div>

Hi All, just a nudge for anyone interested, I'll be doing a Dashboard 2.0 Webinar on Thursday: [Dashboard 2.0 - Where we are, and what’s next? • FlowFuse](https://flowfuse.com/webinars/2023/dashboard-20/)

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [24 October 2023 17:03 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/176 "2023-10-24T17:03:54Z")

</div>

The time in UTC is still not there, as far as I can see.

---

<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: [24 October 2023 18:30 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/177 "2023-10-24T18:30:58Z")

</div>

Hi Colin, it is still recorded as an open issue: [Text Input Widget timestamp and date input formats · Issue #147 · FlowFuse/node-red-dashboard · GitHub](https://github.com/FlowFuse/node-red-dashboard/issues/147)

---

<div class="post-metadata">

### Author: ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)
#### Post date: [24 October 2023 19:02 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/178 "2023-10-24T19:02:41Z")

</div>

> [@joepavitt](#):
>
> Hi Colin, it is still recorded as an open issue

I think Colin is referring to advertised start time for your webinar 😉  
As discussed previously a number of users suggested dropping CET time format, and replacing it with UTC.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [24 October 2023 19:09 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/179 "2023-10-24T19:09:26Z")

</div>

Or just adding UTC.

---

<div class="post-metadata">

### Author: ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)
#### Post date: [24 October 2023 19:22 UTC](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142/180 "2023-10-24T19:22:29Z")

</div>

@joepavitt for info, that discussion started [here](https://discourse.nodered.org/t/dashboard-2-0-where-we-are-and-what-s-next/81929/4).

[Previous page](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142.md?page=8)

[Next page](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142.md?page=10)