No error with creating node topic

[Postaria]

I am using iobroker with node red.
by creating a iobroker in node there is a field called topic.
in this field i put the path to my object.
for exsample : gruenbeck.0.softliQ.D/BS40040337.*
this doesnt work at all like the debug shows me nothing
as i put this in : gruenbeck.0.softliQ.*
i can read the changes in debug.
I think the slash causes this problem. but i dont know how to fix this.

[zenofmud]

@Postaria Welcome to the forum!

Could you provide the full name of the node you are using? (i.e. node-red-contrib-????)
Can you create a small example flow that shows the issue and export it and attach it to a reply. Thanks

In order to make code readable and usable it is necessary to surround your code with three backticks (also known as a left quote or backquote ```)

``` 
   code goes here 
```

You can edit and correct your post by clicking the pencil icon.

See this post for more details - How to share code or flow json

[Postaria]

hi zenofmud,
thanks for your reply.
the full name of the node i am using in iobrocker is:

ioBroker in

ioBroker input node. Connects to a ioBroker and subscribes to the specified topic. The topic may contain redis wildcards (*).

Outputs an object called msg containing msg.topic, msg.payload, msg.timestamp, msg.lastchange and msg.acknowledged.

The ack-flag determines whether only States with ack == true(updates) or ack == false(commands) or all events are forwarded.

In default the Node outputs the topic in MQTT format. This can be changed to the ioBroker database Format (with .)

The select box Mode offers further filtering options. The options are compareble to the RBE node. Both filter options can be configured to pre-initialize with the value on start or not - with this it behaves different if the filter options are in effect directly fot the first value change, or if the first change is always sent out.

this is the code of my flow just simple:

[
    {
        "id": "d846fb2b658527c7",
        "type": "ioBroker in",
        "z": "08e23d6952d2aca7",
        "name": "Soft Water",
        "topic": "gruenbeck.0.softliQ.D/BS40040337.*",
        "payloadType": "object",
        "onlyack": "",
        "func": "all",
        "gap": "",
        "fireOnStart": "true",
        "outFormat": "ioBroker",
        "x": 280,
        "y": 1220,
        "wires": [
            [
                "7c4eff4dd7c52c10"
            ]
        ]
    },
    {
        "id": "7c4eff4dd7c52c10",
        "type": "debug",
        "z": "08e23d6952d2aca7",
        "name": "debug 10",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": false,
        "complete": "payload",
        "targetType": "msg",
        "statusVal": "",
        "statusType": "auto",
        "x": 620,
        "y": 1220,
        "wires": []
    },
    {
        "id": "ae1e802d56e03e19",
        "type": "ioBroker in",
        "z": "08e23d6952d2aca7",
        "name": "Gruenbeck",
        "topic": "gruenbeck.0.softliQ.*",
        "payloadType": "object",
        "onlyack": "",
        "func": "all",
        "gap": "",
        "fireOnStart": "false",
        "outFormat": "ioBroker",
        "x": 280,
        "y": 1080,
        "wires": [
            [
                "6a7c5ea7e77aa747"
            ]
        ]
    },
    {
        "id": "6a7c5ea7e77aa747",
        "type": "debug",
        "z": "08e23d6952d2aca7",
        "name": "debug 12",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": false,
        "complete": "payload",
        "targetType": "msg",
        "statusVal": "",
        "statusType": "auto",
        "x": 620,
        "y": 1080,
        "wires": []
    }
]

and this is the complete path to the object:

i hope this helps understanding my issue.

[zenofmud]

Is that ioborker part of HomeAssistant or something else. It is not a standard node or any I can find in the flow library.

If it is a HomeAssistant node then you should ask the question on the HomeAssistant forum. You will have a better chance of getting it answered there.