NR requires multiple browser refreshes to load flows

General
1

Hi,

I've had this pesky issue for months now. The only significant change has been that I have moved all my Environments from Windows to Debian 11 and Raspbian.

The issue is that quite often flows will not load fully load without manual refreshes. On loading a flow, I get this screen instead:
image

  • If I refresh the page as soon as I see it, I will then have to refresh 2x or 3x times in total before the progress bar fully completes and the flows are visible and ready to use.

  • If I wait for a while and come back to it, only 1 refresh is required.

  • Sometimes it looks like it has loaded after 2x refreshes, however the default editor does not show any syntax highlighting. After a 3rd reload the syntax highlighting works again.

I have checked the developer console and an incomplete load looks like this:

image
image1303Ă—332 32.4 KB

Versus a complete load, which looks like this:

image
image1294Ă—305 28.8 KB

This is happening on multiple Windows machines. I only use Chrome.

Does anyone understand what the error is that I am seeing on a partial load?

2

Turn off this chrome extension

image
image757Ă—59 4.38 KB

Also, try updating to node-red 2.2.2

2 Likes
3

That's the Grepper extension. I don't know if you use it, but it can be helpful when searching for code snippets.

Alas, it fixed the issue! Somehow I thought it would be more complex to resolve.

Thank you

:muscle: :+1:

4

What's in 2.2.2 that's worth the upgrade? Or where you just suggesting a path of things to try to resolve it.

5

What you said :point_up_2:

However, there were a couple of niggles solved by 2.2.2 (I forget what right now)

6

Will add it to the list of things to do, thanks!

I'm drowning in zwave right now.

I've just started the migration to 100% NR for all my home automation and have a tonne of things to fix/redo/configure.

Interestingly, moving from a 300 series to 500 series controller has surfaced issues that didn't exist on the 300 series controller e.g. wake up beams.

All of these issues take time to investigate and come up with a plan to resolve, in this case - replace the offending 300 series devices, as the manufacturer will never provide a firmware update to resolve the issue.

Anyway, I'm going off topic. Thanks for your help.

7

Grr, I hate grepper. It now pollutes all of my google searches and is just a site that scrapes everyone else's work.

8

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