Add openmediavault to latest

[Scrounger]

No description provided.

[github-actions]

ioBroker repository information about New at LATEST tagging

Thanks for spending your time and providing a new adapter for ioBroker.

Your adapter will get a manual review as soon as possible. Please stand by - this might last one or two weeks. Feel free to continue your work and create new releases. You do NOT need to close or update this PR in case of new releases.

In the meantime please check any feedback issues logged by automatic adapter checker and try to fix them. And please check the following information if not yet done:

• https://github.com/ioBroker/ioBroker.repositories?tab=readme-ov-file#requirements-for-adapter-to-get-added-to-the-latest-repository
• https://github.com/ioBroker/ioBroker.repositories?tab=readme-ov-file#development-and-coding-best-practices
• https://github.com/iobroker-community-adapters/responsive-design-initiative/tree/main#responsive-design-initiative

Important:

To verify the object structure of this adapter during REVIEW please export the object structure of a working installation and attach the file to this PR. You find a guide how to export the object struture here: https://github.com/ioBroker/ioBroker.repochecker/blob/master/OBJECTDUMP.md

You will find the results of the review and eventually issues / suggestions as a comment to this PR. So please keep this PR watched.

If you have any urgent questions feel free to ask.
mcm1957

@simatec Please take a look in respect to responsive design. Thanks

[mcm1957]

reminder 15.7.2025

[Scrounger]

@mcm1957:
What's the meaning of the flag obj-json missing. Can't find any info's for that

[mcm1957]

please see comment above:

To verify the object structure of this adapter during REVIEW please export the object structure of a working installation and attach the file to this PR. You find a guide how to export the object struture here: https://github.com/ioBroker/ioBroker.repochecker/blob/master/OBJECTDUMP.md

[Scrounger]

@mcm1957

seriously?
The object structure can also contain sensitive data such as Mac addresses, serial numbers, uuid's, names of people, etc.

If you have several hundred objects in the adapter that contain such data, for example, it takes a lot of effort to make this data available in a clean form.

And the object structure can also look slightly different for everyone, e.g. if you process an api and do not own all devices

Sorry, this is too much effort for an OpenSource project

[github-actions]

Automated adapter checker

ioBroker.openmediavault

-

👍 No errors found

• 👀 [W401] Cannot find "openmediavault" in latest repository

Add comment "RE-CHECK!" to start check anew

[mcm1957]

@mcm1957

seriously? The object structure can also contain sensitive data such as Mac addresses, serial numbers, uuid's, names of people, etc.

I would like to check the object structure created by the adapter especially hirarchy, roles, etc.
I understand your concerns about sensitive data. I would suggest to create an export WITHOUT state data. This should ensure that the structure is visible, but no sensitive content is exported.

reminder 23.7.2025

[Scrounger]

This should ensure that the structure is visible, but no sensitive content is exported.

Excluding the states is not the solution, object structure it self can contain sensitive data (e.g. mac's in id).
The hierarchy is predefined according to the dev docs channel -> device -> channel. All roles are set to states.
More details can be found through code review.

Sorry but I don't have the time to do the effort to bring the structure into a clean form.
It is your decision whether the adapter should go into the repository or not.