Moritz Heusinger
Moritz Heusinger
We already have the state `${this.instanceId}.plugins.sentry.enabled` for this… isn’t it redundant?
Yes it makes no sense to have it as per instance we already have the state from my point of view. Please no redundancy here
> If needed as info for e.g. the UI then we could create a system.-adapter.name.X.disabledReporting state which is set correctly, so that a UI do not need to search the...
I see, admin uses this when clicking on the UI so instead of setting the state it uses this self defined flag. We should change admin behavior to get rid...
> I can not move it ... please recreate Because i already moved it. you references the same issue 😂 i guess it was late
I think we had this discussion started internally but not finished, we will take it into the next core refinement meeting.
Yes, that was also my idea and why I started the discussion and did not change schema right away, will discuss with @GermanBluefox and @Apollon77 next week.
IF not yet working as intended please raise an issue at https://github.com/ioBroker/ioBroker.vis-2
Then please open the issue at vis 2 repo because implementation needs to be done there. Schema is correct as stated so nothing we can do in controller
@oweitman nein bluefox muss es anpassen und was die reaction soll verstehe ich nicht. Du darfst auch gerne den Vis 2 PR erstellen