Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Devices and group config prevalence and priority #1662

Open
mapedraza opened this issue Oct 8, 2024 · 0 comments
Open

Devices and group config prevalence and priority #1662

mapedraza opened this issue Oct 8, 2024 · 0 comments

Comments

@mapedraza
Copy link
Collaborator

The problem

When data from a non provisioned device (I.E: DEV001) arrives to the IoTA through a certain group and APIKEY, automatically a devices is created with an specific entity_id associated based on entity_type and device_id

If the group is edited by adding a new parameter, entityNameExp then, new entities will be created, according to the new group expression, but device will contain the old entityID, wich leads to confussion.

The actual behavior is the desired, but, in case a device need to be remaped, it should not work (being used the entityNameExp instead the forced value)

This can be solved by removing the entityId value when creating the device. This should mean the group parameter, no matter if the entityNameExp is defined, or the default patter (<entityType>:<deviceId>) is going to be used. If entityId is defined in the device configuration, it should be used instead of the expression.

Be aware that, if the preference is solved, but the IoTA still keep copiying the entityId into the device, it could be incompatible with running deployments.

To be discussed in call
CC: @danielvillalbamota

@mapedraza mapedraza changed the title Devices and group config prevalence Devices and group config prevalence and priority Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant