Help for non existing states in iobroker-IN Nodes.

[mickym2]

If an iobroker-IN node references a non existing state the following info is logged:

`

node-red.0 | 2022-02-27 00:04:19.476 | info | Automatic objects creation is not enabled. You can enable it in the node configuration -- | -- | -- | --

`

It cost me some time to find out, that this message is created by iobroker-IN nodes referencing non existing states.

So 2 suggestions:

1. Change the message in the log - as the current message does not give the correct hint on the root cause of the message.
2. The log should mentioned that it is caused by an iobroker-IN Node to an not existing state - and the node-ID that the user is able to search for the iobroker-in node which referenced the non-existing state.

[GermanBluefox]

Changed in next version

[Bernd9000]

Sehr gut, endlich kann man den Fehlern auf den Grund gehen :-)

[mickym2]

Na schön wäre noch gewesen. wie ich angeregt hatte dass man die Node-ID in das Log aufgenommen hätte dann hätte man direkt danach suchen können.

Wenn man also in das Log noch die ID aufgenommen hätte:

dann kann man die Flows über diese ID durchsuchen und bekommt genau die entsprechende Node in den Flows angezeigt:

Das war das was ich unter 2. angesprochen hatte. :(

[Apollon77]

Can be added ... I will try to add node.id to kind of "all" logs now ...

[Apollon77]

GitHub updated with logged node-id

[mickym2]

Great this is working:

[Apollon77]

Cool, learned a lot :-)

[Apollon77]

Released in 3.0.0