-
Notifications
You must be signed in to change notification settings - Fork 9
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
No creating und writing of values in object list #139
Comments
Please add version information: adapter: |
system-info 1.1.0 |
No tip for me ???
|
Tested version 1.0.0 and 1.1.0. Installation of 0.3.0 was not even possible due to errors. No objects are created under systeminfo, but debug logfile contains information that there are valid results. Error in logfile: "err from getObjectList: TypeError: Cannot read private member from an object whose class did not declare it". Loglevel info:
Example of debug logfile:
|
same error |
Since the last update of the systeminfo adapter, the system values are no longer read out or entered in the adapter's object list.
Even after installing a second systeminfo adapter, no more objects are created.
It is a Raspi 4, everything is up to date.
Iobroker, node-js and npm are the latest version recommended for PI 4.
Does anyone have a tip for me?
Last protokoll
2023-09-28 17:54:00.012 - debug: systeminfo.1 (20550) Aussentemp received '21.2'
2023-09-28 17:54:00.014 - debug: systeminfo.1 (20550) MS TypeError: this._extendObject is not a function at MyAdapter.extendObject (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:2051:21) at /opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:431:96 at new Promise () at MyAdapter.extendObject (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:430:20) at MyAdapter.makeState (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:667:21) at setItem (/opt/iobroker/node_modules/iobroker.systeminfo/systeminfo.js:467:14) at /opt/iobroker/node_modules/iobroker.systeminfo/systeminfo.js:594:58 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
The text was updated successfully, but these errors were encountered: