Implicitly assumes `service_path = '/'`

[Kleinjohann]

All entities created in entirety have service_path='/', and entities with with service_path!='/' are not shown in the entities tab. Is this intentional / am I missing a setting for this somewhere?

[djs0109]

Hi @Kleinjohann that is good notice! Yes, it is our intention not to use/support service_path. Previous experience showed that service_path brings more problems than value.

[SBlechmann]

We have had this discussion for several years and we decided to go with the support of just "/" as servicepath for the moment.

Orion offers the possibility to use wildcards in servicepaths in get queries, so that all servicepaths can be queried with "/#". I believe I have already opend an internal discussion 2 weeks ago with the core developers because orion supports this.

Nevertheless, iota and orion's subscription endpoint (in contrast to the documentation!) do not support wildcards yet, check this issue which will bring inconsistencies.
While we can still discuss whether reading entities from all servicepaths is a good solution, the servicepath itself is not part of the response. This way you do not know in which servicepath the entity originates when querying /#.
Thus, you can't use this information to query the iota for device information or the subscription endpoint.

Maybe this clears some things up why entirety currently only supports "/" for now.