Modbus Flex FC shows "broken" without map defined

[unclej84]

Which node-red-contrib-modbus version are you using?

5.43.0

What happened?

When creating a new Flex FC node with only server and unitId defined but maps just filled with {} (empty) for use with maps defined on incoming messages, all mobdus nodes get status broken shortly after deploy. Maybe this is related to #508 as it tries to process empty request? This can only be fixed by having some map defined in the node even when not needed.

Server

Other/External server

How can this be reproduced?

create a new node, enter server and unitId without defining any map (default {}) and deploy

What did you expect to happen?

Default map without configuration should not break the modbus nodes / communication

Other Information

No response

[grewek]

Yes that seems like a bug, will put this on the list for things todo.
Thank you for the report!
This is also probably related to another bug i am currently working (our internal state-machine).
I will check this after Vacation.

Happy Holidays :)

[grewek]

Hey, sorry for the waiting time hope you had great holidays :)

The bug that all clients go into a broken state is probably the same as #487. I am currently working on it but can't give you an exact estimate when the fix will be ready. There is however a workaround described in #487 maybe that helps
for now.

Thank you for your patience

[github-actions]

This issue is stale because it has been open 60 days with no activity. It will be closed in 30 days, but can be saved by removing the stale label or commenting.

[unclej84]

just to remove stale label

[github-actions]

This issue is stale because it has been open 60 days with no activity. It will be closed in 30 days, but can be saved by removing the stale label or commenting.

[unclej84]

just to remove stale label