My thread on moving to DB-2 from the original one

[Trying_to_learn]

This is kind of a continuation of this thread - as it is closed/solved - and I don't want to steal it.

Dashboard 2 Migration using AI?

I have had a fair few issues with Dashboard 2. Some were bugs, some related to appearance, some to usability and some just down to me misunderstanding. But @BartButenaers has perfectly reasonably asked for specific examples where DB2 requires more coding than DB1. The first example that jumps to my mind is with the gauge - how to represent a value of 1234.56789 as 1,234.57%. Please note, I don't claim that this is a sensible thing to want to do. Nor am I asking for this widget to be fixed. …

When I started with NR - can't remember how long ago, but I'd put it at about 10 years ago - and I worked strictly with the editor screen.

NO GUI at all.

But because of the need creep of GUI things, I had to start using the Dashboard.

That had some problems for me as I tried to be too smart for my own good and had multiple dashboards which caused conflicts.

But when I got that confusion sorted out there were problems with the layout.

Not helped by the zoom level sometimes being ..... adjusted and so when I loaded the dashboard the layout was corrupted from the other time.

In the meantime, docker came along and I have only played with it a couple of times on another machine but haven't got into it.
I won't go on about it here as it is outside the scope.

I've been told I can have both dashboards installed on the same instance.
So I could (thinking hypothetically from here on) slowly migrate the dashboard nodes form V1 to V2.

But reading the afore mentioned thread: That isn't as easy as I would have thought.

There is a bit of discussion about the newer version being too...... difficult (too many options?) to be ...... conducive to not being used.

So that raises a question - from my position at this point in time:

Putting aside the GUI tweaks you can have on/in the items, can you just ignore them and have them vanilla and use them out of the box?

This way it wouldn't be too much work to get/migrate an existing dashboard to the newer one.

Then you can/could go back and add the fancy stuff later?

What I THINK:
You have a working ...... gauge.
No big.
You replace the v1 with v2 one. Then just before the new node, you can add the extra eye candy to take advantage of the new GUI stuff.

This would be done with something like a change node that would add extra structure to the message.

I think I've dug a fairly big/deep hole here and don't want to dig much more.

I hope this can grow to not only help me get my head around moving from the original dashboard to dashboard-2.

Thanks in advance.

[Paul-Reed]

@Trying_to_learn

I hope this can grow to not only help me get my head around moving from the original dashboard to dashboard-2

But please remember to start a new forum topic for each subject/issue, each with it's own descriptive title.

[Trying_to_learn]

Ok.

I read the mentioned thread and it opened a few questions I have about going from DB-1 to DB-2.

As there were a few questions mentioned there: I thought I'd start a new thread to cover them.

On the other hand, I didn't want to open..... a lot of threads, each one a question relating to the migration.

I'm not sure what you mean then.

Should I open a lot of different threads?

[Paul-Reed]

@Trying_to_learn

Should I open a lot of different threads?

Specific issues should be in their own respective thread, such as 'changing the input msg structure for DB2', 'how to personalize a DB2 node', 'changing the layout of widgets', etc.

It makes it easier to index topics, and easy for other people to search the forum for similar issues, which in turn avoids duplicity.

[Trying_to_learn]

I'm stuck between a rock and hard place.

I am trying to understand the bigger picture.

I have never used any DB-2 nodes.

Say they have extra needs (which, ok, I accept) I don't know how many more things are needed and by what nodes.

So - how I read it - I would have to start a new thread for each of the nodes in the new DB-2.
Which I think is a bit too much/many threads.

The original thread was discussing the difficulty of migrating.
It's closed - for it's answer.

But it left things open.
WHAT - I don't know as I accept I don't know what I don't know.

[Paul-Reed]

@Trying_to_learn

Say they have extra needs (which, ok, I accept) I don't know how many more things are needed and by what nodes.

There is extensive and well written DB2 guide which describes individual nodes, their requirements and limitations, so you could determine yourself how they fit into your new structure.
Have you read it, as that should be your starting place.

[TotallyInformation]

@Trying_to_learn

I'm stuck between a rock and hard place.

I am trying to understand the bigger picture.

I have never used any DB-2 nodes.

It would be really helpful if you could share which DB1 nodes you have used in your dashboards.

[Trying_to_learn]

Button, text, gauge, chart and template.

Level, LED.

There may be a couple of other ones.....

But as a start, they are the main ones I use.

ui-control - just remembered
multistate switch
week schedule
ui-scheduler
slider

[Trying_to_learn]

I think it is not nice of me if I accept this thread is resolved and then go and open a whole lot of new threads.

But taking on what was suggested and TRYING to get my head around some of the nodes:
text input is already a problem.

So it is an INPUT so I type stuff and that is then on sent in the message.

So I put it in a flow.

It is set to text input - single line
I DEPLOY it and this is what I get/see in the GUI side.

Clicking anywhere in/on the .... thing.... Nowhere do I see a blinking cursor.
So I am already failing on how to use the text input node.

I was - kind of - thrown by the instructions. But I'll cop that.

So what am I NOT doing to be able to input text - be it one line or otherwise?

I have since added a number and button node.
Same.
No change to what I am seeing.

[Trying_to_learn]

RESOLVED

I was using the wrong URL to see the newer style dashboard.