# 🎉 Node-RED 1.1.0-beta.1 released

**URL:** <https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761>\
**Category:** News\
**Created:** [4 June 2020 10:38 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761 "2020-06-04T10:38:31Z")\
**Posts on this page:** 20\
**Page:** 3

<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:** [5 June 2020 09:30 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/42 "2020-06-05T09:30:47Z")

</div>

The 'tool tip' for the info tab says 'Node information'  
 ![Screen Shot 2020-06-05 at 5.28.05 AM](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/b/8/b898ff6fb29826b42121877d983c0e02a126b75c.png)

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [5 June 2020 09:40 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/43 "2020-06-05T09:40:33Z")

</div>

> [@ristomatti](#):
>
> My report on duplicate debug log messages on Android was left out. I was able to pinpoint the issue to actually be duplicate inject node manual trigger on a single tap. Perhaps both `touchstart` and `onclick` events fire?

Thanks - have added to the list. Will investigate the edit behaviour - nothing has intentionally changed in this area, but the whole touch-screen experience doesn't get much testing from us and has always been a bit of an after thought.

> [@zenofmud](#):
>
> The 'tool tip' for the info tab says 'Node information'

Just like it always has... but it is a bit anachronistic, so will update.

---

<div class="post-metadata">

**Author:** ![ristomatti](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ristomatti/32/5857_2.png) [@ristomatti](https://discourse.nodered.org/u/ristomatti)\
**Post date:** [5 June 2020 10:14 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/44 "2020-06-05T10:14:32Z")

</div>

> [@knolleary](#):
>
> the whole touch-screen experience doesn't get much testing from us and has always been a bit of an after thought

Well, you will get more now as I tend to do all my forum reading/posting on a tablet and I'll often need to test some flows or ideas while I'm at it.

---

<div class="post-metadata">

**Author:** ![JGKK](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jgkk/32/18515_2.png) [@JGKK](https://discourse.nodered.org/u/JGKK)\
**Post date:** [5 June 2020 10:16 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/45 "2020-06-05T10:16:43Z")

</div>

> [@ristomatti](#):
>
> you will get more now

Yes now that devices such as the ipad pro are around i definitely think we will see more and more people using nodered from touch screen devices. I for one love using Nodered with one 🙈

---

<div class="post-metadata">

**Author:** ![ristomatti](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ristomatti/32/5857_2.png) [@ristomatti](https://discourse.nodered.org/u/ristomatti)\
**Post date:** [5 June 2020 10:28 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/46 "2020-06-05T10:28:53Z")

</div>

> [@JGKK](#):
>
> for one love using Nodered with one 🙈

Personally I find it quite a struggle on a 10" screen, having to occasionally rotate the screen to either fit the sidebars or node settings dialog. But I do it anyway for some reason. I guess I'm just too lazy to get up on my computer. But this is drifting off topic... 🙂

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [5 June 2020 10:42 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/47 "2020-06-05T10:42:38Z")

</div>

🙂 We look forward to some pull requests to go along with your new position of chief touch interface tester !

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [5 June 2020 10:43 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/48 "2020-06-05T10:43:34Z")

</div>

> [@dceejay](#):
>
> We look forward to some pull request

But I will hastily add that I've fixed all of your touch-related issues locally (not pushed to git yet) so we don't need PRs for them.

---

<div class="post-metadata">

**Author:** ![ristomatti](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ristomatti/32/5857_2.png) [@ristomatti](https://discourse.nodered.org/u/ristomatti)\
**Post date:** [5 June 2020 10:50 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/49 "2020-06-05T10:50:30Z")

</div>

> [@dceejay](#):
>
> We look forward to some pull requests to go along with your new position of chief touch interface tester !

But this would mean I'd need to leave the comfort of my tablet! I have been looking at the code with this in mind in the past to be honest. But so far it has seemed too intimidating to take a shot. Perhaps watching a few more of Nick's great live streams will give the required boost in confidence... 😄

---

<div class="post-metadata">

**Author:** ![dynamicdave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dynamicdave/32/96_2.png) [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)\
**Post date:** [6 June 2020 06:44 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/50 "2020-06-06T06:44:23Z")

</div>

Have I missed something?

I've installed Node-RED 1.1.0-beta.1 but still get missing configurations on nodes that are in groups.  
If I click on each node and update the ones that have a pink background and deploy, they all revert to unassigned state as soon as I 'stop' and 'restart' Node-RED.

NR is running on a RPI-4B 4GB and was previously running v.1.0.6

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [6 June 2020 06:47 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/51 "2020-06-06T06:47:28Z")

</div>

I dont think it was pushed to the beta.1 version

---

<div class="post-metadata">

**Author:** ![dynamicdave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dynamicdave/32/96_2.png) [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)\
**Post date:** [6 June 2020 06:50 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/52 "2020-06-06T06:50:55Z")

</div>

I thought it was... reading this line-item from Nick.

> [@tada Node-RED 1.1.0-beta.1 released](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/36):
>
> Already reported in this thread and fix : [tada Node-RED 1.1.0-beta.1 released](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/17) Already mentioned in the thread and on my list of things to fix.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [6 June 2020 06:59 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/53 "2020-06-06T06:59:01Z")

</div>

We haven't published a new version with those fixes in.

---

<div class="post-metadata">

**Author:** ![dynamicdave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dynamicdave/32/96_2.png) [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)\
**Post date:** [6 June 2020 07:01 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/54 "2020-06-06T07:01:36Z")

</div>

Thanks Nick for the clarification.  
I'll wait patiently and explore all the other 'goodies' in the new release.

Thanks for doing such a great job with the current release of Node-RED.

---

<div class="post-metadata">

**Author:** ![ristomatti](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ristomatti/32/5857_2.png) [@ristomatti](https://discourse.nodered.org/u/ristomatti)\
**Post date:** [6 June 2020 09:00 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/55 "2020-06-06T09:00:52Z")

</div>

The admin cli seems to throw an error. Running 1.1.0-beta.1 on a RPi 4 with the latest Raspbian. I've installed NR with `sudo npm install -g --unsafe-perm node-red@next`.

```auto
$ node -v
v14.3.0

```

```auto
$ node-red admin
Usage:
   node-red-admin <command> [args] [--help] [--userDir DIR] [--json]

Description:
   Node-RED command-line client

Commands:
   target - Set or view the target URL and port like http://localhost:1880
   login - Log user in to the target of the Node-RED admin API
   list - List all of the installed nodes
   info - Display more information about the module or node
   enable - Enable the specified module or node set
   disable - Disable the specified module or node set
   search - Search for Node-RED modules to install
   install - Install the module from NPM to Node-RED
   remove - Remove the NPM module from Node-RED
   hash-pw - Creates a hash to use for Node-RED settings like "adminAuth"

TypeError: Cannot read property 'catch' of undefined
    at Object.<anonymous> (/usr/lib/node_modules/node-red/red.js:20:57)
    at Module._compile (internal/modules/cjs/loader.js:1200:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1220:10)
    at Module.load (internal/modules/cjs/loader.js:1049:32)
    at Function.Module._load (internal/modules/cjs/loader.js:937:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)
    at internal/main/run_main_module.js:17:47

```

Edit: It seemed to run `node-red admin install <package>` just fine though.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [6 June 2020 09:36 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/56 "2020-06-06T09:36:09Z")

</div>

> [@ristomatti](#):
>
> The admin cli seems to throw an error.

`node-red-admin` 0.2.6 published with the fix.

---

<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:** [6 June 2020 09:51 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/57 "2020-06-06T09:51:55Z")

</div>

Previously the `node-red` command used to expect any parameter passed to be the name of a flows file to use. Isn't it potentially confusing that this has changed? I see that the old behaviour still exists, provided the name of the flows file is not `admin`. Is it going to be even more likely that users will expect to use `node-red start` to start node-red?

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [6 June 2020 10:09 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/58 "2020-06-06T10:09:32Z")

</div>

> [@Colin](#):
>
> Previously the `node-red` command used to expect any parameter passed to be the name of a flows file to use. Isn't it potentially confusing that this has changed?

Nothing has changed but for the _one_ exception of the word `admin`. I decided that, on balance, the risk was pretty low that someone would be using a flow file called just `admin`. In the unlikely case that does cause a clash, they can rename their flow file to `admin.json` or literally any other word.

> [@Colin](#):
>
> Is it going to be even more likely that users will expect to use `node-red start` to start node-red?

Running `node-red start` does start node-red - just not, in the specific case of the Pi, start it as a service. As a source of confusion, that already exists. This won't do anything to change that.

---

<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:** [6 June 2020 10:31 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/59 "2020-06-06T10:31:47Z")

</div>

> [@knolleary](#):
>
> Running `node-red start` does start node-red - just not, in the specific case of the Pi, start it as a service

Plus it looks for a flows file called `start`.

> [@knolleary](#):
>
> As a source of confusion, that already exists. This won't do anything to change that.

I am not entirely convinced, but time will tell.

---

<div class="post-metadata">

**Author:** ![ristomatti](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ristomatti/32/5857_2.png) [@ristomatti](https://discourse.nodered.org/u/ristomatti)\
**Post date:** [6 June 2020 10:42 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/60 "2020-06-06T10:42:35Z")

</div>

> [@knolleary](#):
>
> `node-red-admin` 0.2.6 published with the fix.

I reinstalled `node-red@next` and can confirm it's fixed, thanks. Fast fingers... and on Saturday(!), don't you guys ever rest? 🙂

---

<div class="post-metadata">

**Author:** ![Hypnos](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hypnos/32/7566_2.png) [@Hypnos](https://discourse.nodered.org/u/Hypnos)\
**Post date:** [6 June 2020 11:32 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761/61 "2020-06-06T11:32:23Z")

</div>

The used command is  
node-red admin

The help says as usage  
node-red -admin

 ![Screenshot_20200606-133026](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/9/d96b3dd7074e1366c0d7360499aaca68bd66850a.jpeg)

I may be wrong, but should the usage changed to the new way without the dash?

[Previous page](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761.md?page=2)

[Next page](https://discourse.nodered.org/t/node-red-1-1-0-beta-1-released/27761.md?page=4)
