iobroker-community-adapters / ioBroker.km200

ioBroker Buderus KM200 adapter *DEPRECATED*
Other
24 stars 16 forks source link

Compatibility check to js-controller 3.3 and Admin5 React UI #59

Closed ioBrokerChecker closed 1 year ago

ioBrokerChecker commented 3 years ago

Dear Adapter developer,

with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.

If something is not correct this is logged as 'warning' or 'info' log.

Please take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to https://github.com/ioBroker/ioBroker.js-controller/issues/1301

Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.

More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui

Please close the issue after you checked it.

Thank you very much for your support!

meikel-g commented 3 years ago

js-controller 3.3 is now in stable and the data type mismatch starts affecting regular users: `

2021-08-11 17:37:16.339 - info: km200.0 (22247) State value to set for "km200.0.heatSources.info" has to be type "string" but received type "object" -- 2021-08-11 17:37:16.347 - info: km200.0 (22247) State value to set for "km200.0.heatSources.info" has to be type "string" but received type "object" 2021-08-11 17:37:19.553 - info: km200.0 (22247) State value to set for "km200.0.heatingCircuits.hc1.currentOpModeInfo" has to be type "string" but received type "object" 2021-08-11 17:37:19.556 - info: km200.0 (22247) State value to set for "km200.0.heatingCircuits.hc1.currentOpModeInfo" has to be type "string" but received type "object" 2021-08-11 17:37:32.461 - info: km200.0 (22247) State value to set for "km200.0.recordings.heatSources.actualPower._Months" has to be type "string" but received type "object" 2021-08-11 17:37:32.463 - info: km200.0 (22247) State value to set for "km200.0.recordings.heatSources.actualPower._Months" has to be type "string" but received type "object" `
Hini2001 commented 2 years ago

Same here... any further ideas to fix this problem?

mcm1957 commented 1 year ago

outdated

If you still receive such messages with current version, please oben a new issue