Node-RED Plugin v1.8.0-1: Fields in nodes not displaying

Hi,

After updating the Node-RED Plugin to version 1.8.0-1, I noticed an issue where the fields in existing nodes (such as for reading or writing device properties) appear blank:

However, when I export the nodes, the fields are still populated, for example:

        "assetId": "{{device}}",
        "property": "property_X",

Currently, the only way I can create new nodes is by importing and manually filling the fields, as they do not display correctly in the node window.

Does anyone have a solution to make the content of these fields visible again?

Hi,

I have noticed the same behaviour, the nodes does not displays the resources to pick them up.

I guess dev team will figure it out how to recover this feature.

@jaimebs , is it easy to fix this bug?

Thanks for the report, I will take a look at this during the week

Hi!

We’ve released a fix in the latest development version. The official release is scheduled for next week (to avoid releasing on Fridays! :beetle:).

You can install it like any other upgrade:
nr

and can make sure of the version through Node-RED palette settings:
nr2

1 Like

Hello again!

An official release is now available with version 1.9.0! Let me know if you find any issues.

Best regards

Thank you! The node fields are now visible after the upgrade.

I’ve noticed another thing when modifying the device name in the property write node. Specifically, when changing the device name, the property name and value fields are being cleared. For example, in this scenario:

  1. Initial node configuration:
    1

  2. Upon changing the device name:
    2024-11-06_11h25_57

  3. The fields are then cleared:
    2024-11-06_11h26_41

I’m not certain if this behavior is intentional, but if a custom node name is used it becomes less visible or apparent at a glance.

Hi @aeromek

The node dialogs are designed to remove the subresource fields (property and value in this case) when the main resource changes (device), as well as retrieving the value of the selected property when it exists for example. However I understand that in your case in which you are using a placeholder it may not be desirable.

I’ve created an issue in the GitHub repo in order to approach it for the next release of the plugin, while also give some time for other users to participate in what would be a desirable solution.

1 Like