Closed Matt77CHE closed 4 months ago
i18n attribute is only valid at top level and at custom component entry according to schema.md https://github.com/Excodibur/ioBroker.tahoma/blob/f6c12259fdfea1602a6473a8b39c8b6113b21275/admin/jsonConfig.json#L40 https://github.com/Excodibur/ioBroker.tahoma/blob/f6c12259fdfea1602a6473a8b39c8b6113b21275/admin/jsonConfig.json#L60
https://github.com/ioBroker/ioBroker.admin/blob/master/packages/jsonConfig/SCHEMA.md
So those two lines should be removed in my opinnion.
Thanks for reporting the issue and for the hint. It should be fixed with https://github.com/Excodibur/ioBroker.tahoma/releases/tag/v0.10.4 now. Please check if the issue still occurs.
After adapter installing, I recognized a warn message in Log file:
tahoma has an invalid jsonConfig: [{"instancePath":"/items/basicSettingsTab","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/8/then/additionalProperties","keyword":"additionalProperties","params":{"additionalProperty":"i18n"},"message":"must NOT have additional properties"},{"instancePath":"","schemaPath":"#/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"}]
Versions: