UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[dippi]

Hallo

ich hab das Update auf 0.1.9 gemacht und bekomme jetzt folgende Fehlermeldungen.

auch die Einstellmöglichkeit im Adapter fehlt bei mir auch.

gruß

Dippi
2772_log.png

[Matzebhv]

@Dutchman:

@Matzebhv:

Moin,

der Adapter wirft im Log immer wieder folgendes aus:

! ````
sourceanalytix.0 2019-01-20 12:10:48.767 error Case error : value received for calculation with unit : hPa which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:48.767 error Case error : value received for calculation with unit : % which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:48.767 error Case error : value received for calculation with unit : °C which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:43.760 error Case error : value received for calculation with unit : hPa which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:43.760 error Case error : value received for calculation with unit : % which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:43.758 error Case error : value received for calculation with unit : °C which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:38.755 error Case error : value received for calculation with unit : hPa which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:38.755 error Case error : value received for calculation with unit : % which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:38.755 error Case error : value received for calculation with unit : °C which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:33.752 error Case error : value received for calculation with unit : hPa which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:33.752 error Case error : value received for calculation with unit : % which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:33.752 error Case error : value received for calculation with unit : °C which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:28.746 error Case error : value received for calculation with unit : hPa which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:28.746 error Case error : value received for calculation with unit : % which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:28.746 error Case error : value received for calculation with unit : °C which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:23.740 error Case error : value received for calculation with unit : hPa which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:23.740 error Case error : value received for calculation with unit : % which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:23.740 error Case error : value received for calculation with unit : °C which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:18.744 error Case error : value received for calculation with unit : hPa which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:18.744 error Case error : value received for calculation with unit : % which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:18.744 error Case error : value received for calculation with unit : °C which is currenlty not (yet) supported
sourceanalytix.0 2019-01-20 12:10:16.429 error Sorry unite type hPa not supported yet
sourceanalytix.0 2019-01-20 12:10:16.429 error Sorry unite type % not supported yet
sourceanalytix.0 2019-01-20 12:10:16.427 error Sorry unite type °C not supported yet

Geloggt wird derzeit nur der Stromverbrauch über den Smartmeter-Adapter.

Ein Neustart des Adapters behebt das für eine kurze Weile, allerdings macht sich der Adapter dabei jedes mal lang:

>! ````
Caught	2019-01-20 11:35:19.305	error	by controller[18]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.304	error	by controller[18]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.304	error	by controller[18]: at <anonymous>
Caught	2019-01-20 11:35:19.304	error	by controller[18]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.304	error	by controller[18]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.304	error	by controller[17]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.304	error	by controller[17]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.304	error	by controller[17]: at <anonymous>
Caught	2019-01-20 11:35:19.304	error	by controller[17]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.304	error	by controller[17]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.304	error	by controller[17]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.304	error	by controller[17]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.304	error	by controller[17]: at <anonymous>
Caught	2019-01-20 11:35:19.304	error	by controller[17]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.304	error	by controller[17]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.304	error	by controller[17]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.304	error	by controller[17]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.304	error	by controller[17]: at <anonymous>
Caught	2019-01-20 11:35:19.304	error	by controller[17]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.304	error	by controller[17]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.304	error	by controller[17]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.304	error	by controller[17]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.304	error	by controller[17]: at <anonymous>
Caught	2019-01-20 11:35:19.304	error	by controller[17]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.304	error	by controller[17]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.304	error	by controller[17]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.304	error	by controller[17]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.304	error	by controller[17]: at <anonymous>
Caught	2019-01-20 11:35:19.304	error	by controller[17]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.304	error	by controller[17]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.304	error	by controller[17]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.304	error	by controller[17]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.303	error	by controller[17]: at <anonymous>
Caught	2019-01-20 11:35:19.303	error	by controller[17]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.303	error	by controller[17]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.303	error	by controller[17]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.303	error	by controller[17]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.303	error	by controller[17]: at <anonymous>
Caught	2019-01-20 11:35:19.303	error	by controller[17]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.303	error	by controller[17]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.303	error	by controller[17]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.303	error	by controller[17]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.303	error	by controller[17]: at <anonymous>
Caught	2019-01-20 11:35:19.303	error	by controller[17]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.303	error	by controller[17]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.303	error	by controller[16]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.303	error	by controller[16]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.303	error	by controller[16]: at <anonymous>
Caught	2019-01-20 11:35:19.303	error	by controller[16]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.303	error	by controller[16]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.303	error	by controller[15]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.303	error	by controller[15]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.303	error	by controller[15]: at <anonymous>
Caught	2019-01-20 11:35:19.303	error	by controller[15]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.303	error	by controller[15]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.303	error	by controller[15]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.303	error	by controller[15]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.303	error	by controller[15]: at <anonymous>
Caught	2019-01-20 11:35:19.303	error	by controller[15]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.303	error	by controller[15]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.303	error	by controller[14]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.303	error	by controller[14]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.303	error	by controller[14]: at <anonymous>
Caught	2019-01-20 11:35:19.303	error	by controller[14]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.303	error	by controller[14]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.302	error	by controller[14]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.302	error	by controller[13]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.302	error	by controller[13]: at <anonymous>
Caught	2019-01-20 11:35:19.302	error	by controller[13]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.301	error	by controller[13]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.301	error	by controller[13]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.301	error	by controller[13]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.301	error	by controller[13]: at <anonymous>
Caught	2019-01-20 11:35:19.301	error	by controller[13]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.301	error	by controller[13]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.301	error	by controller[13]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.301	error	by controller[13]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.301	error	by controller[13]: at <anonymous>
Caught	2019-01-20 11:35:19.301	error	by controller[13]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.301	error	by controller[13]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.301	error	by controller[13]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.301	error	by controller[12]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.301	error	by controller[12]: at <anonymous>
Caught	2019-01-20 11:35:19.301	error	by controller[12]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.301	error	by controller[12]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.301	error	by controller[12]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.301	error	by controller[12]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.301	error	by controller[12]: at <anonymous>
Caught	2019-01-20 11:35:19.301	error	by controller[12]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.301	error	by controller[12]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.301	error	by controller[11]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.301	error	by controller[11]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at <anonymous>
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.300	error	by controller[11]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.300	error	by controller[11]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at <anonymous>
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.300	error	by controller[11]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.300	error	by controller[11]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at <anonymous>
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.300	error	by controller[11]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.300	error	by controller[11]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at <anonymous>
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.300	error	by controller[11]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.300	error	by controller[11]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at <anonymous>
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.300	error	by controller[11]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.300	error	by controller[11]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at <anonymous>
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.300	error	by controller[11]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.300	error	by controller[11]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at <anonymous>
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.300	error	by controller[11]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.300	error	by controller[11]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.300	error	by controller[11]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.299	error	by controller[11]: at <anonymous>
Caught	2019-01-20 11:35:19.299	error	by controller[11]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.299	error	by controller[11]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.299	error	by controller[11]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.299	error	by controller[11]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.299	error	by controller[11]: at <anonymous>
Caught	2019-01-20 11:35:19.299	error	by controller[11]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.299	error	by controller[11]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.299	error	by controller[10]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.299	error	by controller[10]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.299	error	by controller[10]: at <anonymous>
Caught	2019-01-20 11:35:19.299	error	by controller[10]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.299	error	by controller[10]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.299	error	by controller[10]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.299	error	by controller[10]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.299	error	by controller[10]: at <anonymous>
Caught	2019-01-20 11:35:19.299	error	by controller[10]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.299	error	by controller[10]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.299	error	by controller[10]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.299	error	by controller[10]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.299	error	by controller[10]: at <anonymous>
Caught	2019-01-20 11:35:19.299	error	by controller[10]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.299	error	by controller[10]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.299	error	by controller[10]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.299	error	by controller[10]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.299	error	by controller[10]: at <anonymous>
Caught	2019-01-20 11:35:19.299	error	by controller[10]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.299	error	by controller[10]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.299	error	by controller[10]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.299	error	by controller[10]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.299	error	by controller[10]: at <anonymous>
Caught	2019-01-20 11:35:19.299	error	by controller[10]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.299	error	by controller[10]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.298	error	by controller[10]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject
Caught	2019-01-20 11:35:19.298	error	by controller[10]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught	2019-01-20 11:35:19.298	error	by controller[10]: at <anonymous>
Caught	2019-01-20 11:35:19.298	error	by controller[10]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:324:19)
Caught	2019-01-20 11:35:19.298	error	by controller[10]: (node:12800) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state_type' of undefined
Caught	2019-01-20 11:35:19.298	error	by controller[10]: (node:12800) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by reject</anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous>
```` `  

die Fehlermeldungen sind logisch, wie soll man Statistiken von verbrauch über Prozent werte machen ? (unit = not supported !) `

Moin,

da ist aber nix in Prozent. aktiviert ist der Adapter auf dem DP: Zählerstand 1 Summe Wirkarbeit Bezug + (Total) -> value. Dort steht der Zählerstand in kWh drin. Der Adapter läuft ja nach neustart komischweise für ca. 30 Minuten. Danach ballert er wieder das Log voll.

Gruß

Matze

[Dutchman]

@ Dippie, Matze,

Gebt mir noch ne stunden für version 0.2.0 ;-)

[stern525]

@Dutchman:

@stern525:

Wenn ich jetzt z.B. bei Tagesverbrauch den logg aktiviere dann legt er wieder eine neue Zeile an. `

du musst den state aktivieren wo der wert rein kommt und nicht wie object welche SourceAnalytix liefert ! `

Ich hab es jetzt wieder neu angelegt aber Werte sind keine da. :idea:

Gibt es vielleicht irgendwo eine verständliche Anleitung für Leute die hier noch nicht so fit sind wo man was eintragen muss?

[Dutchman]

@stern525:

Gibt es vielleicht irgendwo eine verständliche Anleitung für Leute die hier noch nicht so fit sind wo man was eintragen muss? `

hup wird alles kommen wir befinden uns gerade im beta test, Version 0.2.5 wird voraussichtlich die erste stable und dan kommt auch die komplette doku.

Es veranderd sich im moment noch zu schnell zu viele Sachen um die wiki direkt fertig zu haben bitte um Verständnis.

~ Dutch

[stern525]

Kein Problem, er funktioniert bei mir noch nicht aber das wird er noch.

Das Teil voll cool denn es ist von der Idee her genau das was ich suchte.

Ich finde Du machst hier eine super Arbeit, RESPEKT!!

Vielen Dank!

[Dutchman]

So Freunde ! Ich habe soeben version 0.2.0 auf GitHub und NPM veröffentlicht, leider konnte ich nicht alle Sachen die ich Wollter direct mitnehmen.

Wollte aber auch nicht länger warten mit der 0.2.0 da doch erhebliche basis Sachen fehlten.

0.2.0 ist ein Major update, ich wurde euch empfehlen das loggen der states ab zu schalten, den adapter zu löschen und dan neu anfangen.

Installation : per GitHub oder NPM (npm i iobroker.sourceanalytics)

Fixes gegenüber der vorigen version :

Eine komplette Übersicht von fixes gegenüber der 0.1.0 release.

• (Dutchman) rebuild logic to calculate values (beta testing)

• (Dutchman) implement logic to automatically reset values by start of new day, week, month, year etc (beta testing)

• (Dutchman) changed logic from intervall polling to handle calculations based on state updates (beta testing, not if suitable for all situations)

• (Dutchman) fix issue incorrect states are added to monitoring

• (Dutchman) fix issue calculation not stopped when state removed from monitoring

• (Dutchman) always store all current meassurements to values of cathegorie regardless setting year etc

• (Dutchman) code cleanup and optiomalisation

• (Dutchman) added logging option "satus notification"

• (Dutchman) implement new translation mechanism

• (Dutchman) Adapter moved to community development tree

• (Dutchman) added npm version and test-status to readme

• (Dutchman) finalized new konfiguration screen & translations

• (Dutchman) adding/removing objects from analytix does not need adapter reboot anymore ! :-)

• (Dutchman) rebuild logic how data is handled as basic for new calculation logic (Experimental)

• (Dutchman) added options to year analytics to choose values (days,weeks,years etc)

• (Dutchman) option added for Developer logging

• (Dutchman) Basic price is currently not considered in cost calculations !

• (Dutchman) konfiguration pages completly redesigned : Please do not enter values yet !

• (Dutchman) master konfiguration added to globally define costs

• (Dutchman) intervall settings moved to global setting instead of each state seperated

• (Dutchman) instead of cost-price in each state use drop down menu to choose values from global settings

• (Dutchman) fix naming and translations

Diese Übersicht findet ihr auch hier : https://github.com/iobroker-community-a … /tag/0.2.0

Na dan viel spass, freue mich über Testberichte, wünsche und Fehlermeldungen !

[Kueppert]

Wow dutch, Respekt. Da ich nun auch node 8 drauf habe, werde ich den Adapter wegen der tuya Dosen auch Mal in Angriff nehmen ;)

Gesendet von meinem HUAWEI RIO-L01 mit Tapatalk

[Dutchman]

@Kueppert:

Wow dutch, Respekt. Da ich nun auch node 8 drauf habe, werde ich den Adapter wegen der tuya Dosen auch Mal in Angriff nehmen ;) `

gerade bemerkt das ich 2 kleine Sachen vergessen habe, ist funktional aber kein problem… Es wird noch ne minor 0.2.1 kommen heute aber lasst euch bitte nicht abhalten ich brauche feedback damit ich issues abarbeiten kann ! :mrgreen:

[Homer.J.]

Hallo Dutchman,

Es wird keine Tagesvariable bei mir angelegt.

Grüße
5373_3cc833e7-3c58-4817-a6a8-2e27e05fb7b1.png

[Issi]

ja bei mir auch nicht berechnen tut er sie aber und es kommen bei mir immer solche Meldungen

sourceanalytix.0	2019-01-20 17:14:57.061	info	state : zigbee.0.00158d000237acf1.no_motion removed from SourceAnalytix
sourceanalytix.0	2019-01-20 17:14:55.920	info	state : netatmo.0.Büro-Alex.Außensensor removed from SourceAnalytix
sourceanalytix.0	2019-01-20 17:14:55.889	info	state : netatmo.0.Büro-Alex.Indoor removed from SourceAnalytix
sourceanalytix.0	2019-01-20 17:14:52.437	info	state : zigbee.0.00124b0018ed36ae.state removed from SourceAnalytix
sourceanalytix.0	2019-01-20 17:14:52.437	info	state : zigbee.0.00124b0018ed36ae.link_quality removed from SourceAnalytix
sourceanalytix.0	2019-01-20 17:14:52.437	info	state : zigbee.0.00124b0018ed36ae.link_quality removed from SourceAnalytix
sourceanalytix.0	2019-01-20 17:14:47.033	info	state : zigbee.0.00158d000237acf1.no_motion removed from SourceAnalytix
sourceanalytix.0	2019-01-20 17:14:37.020	info	state : zigbee.0.00158d000237acf1.no_motion removed from SourceAnalytix 

[Dutchman]

@Homer1976:

Hallo Dutchman,

Es wird keine Tagesvariable bei mir angelegt.

Grüße `

issue : https://github.com/iobroker-community-a … /issues/25

fix : https://github.com/iobroker-community-a ... fc98ef4c29

bitte nochmal von GitHub installieren ! Danke

[Dutchman]

@Issi:

ja bei mir auch nicht berechnen tut er sie aber und es kommen bei mir immer solche Meldungen

sourceanalytix.0	2019-01-20 17:14:57.061	info	state : zigbee.0.00158d000237acf1.no_motion removed from SourceAnalytix
sourceanalytix.0	2019-01-20 17:14:55.920	info	state : netatmo.0.Büro-Alex.Außensensor removed from SourceAnalytix
sourceanalytix.0	2019-01-20 17:14:55.889	info	state : netatmo.0.Büro-Alex.Indoor removed from SourceAnalytix
sourceanalytix.0	2019-01-20 17:14:52.437	info	state : zigbee.0.00124b0018ed36ae.state removed from SourceAnalytix
sourceanalytix.0	2019-01-20 17:14:52.437	info	state : zigbee.0.00124b0018ed36ae.link_quality removed from SourceAnalytix
sourceanalytix.0	2019-01-20 17:14:52.437	info	state : zigbee.0.00124b0018ed36ae.link_quality removed from SourceAnalytix
sourceanalytix.0	2019-01-20 17:14:47.033	info	state : zigbee.0.00158d000237acf1.no_motion removed from SourceAnalytix
sourceanalytix.0	2019-01-20 17:14:37.020	info	state : zigbee.0.00158d000237acf1.no_motion removed from SourceAnalytix 
```` `  

Danke ! : https://github.com/iobroker-community-a … /issues/26

hohle ich in 0.2.1 raus

[Homer.J.]

@Dutchman:

@Homer1976:

Hallo Dutchman,

Es wird keine Tagesvariable bei mir angelegt.

Grüße `

issue : https://github.com/iobroker-community-a … /issues/25

fix : https://github.com/iobroker-community-a ... fc98ef4c29

bitte nochmal von GitHub installieren ! Danke `

Funktioniert.

Grüße

[Kueppert]

@Kueppert:

Wow dutch, Respekt. Da ich nun auch node 8 drauf habe, werde ich den Adapter wegen der tuya Dosen auch Mal in Angriff nehmen ;)

Gesendet von meinem HUAWEI RIO-L01 mit Tapatalk ` Beim tuya Adapter wird der Wert aktuell in Watt ausgegeben. Wird aktuell gem. Log noch nicht unterstützt.

Möchte nicht extra Skripte bauen, daher warte ich noch was… :)

Gesendet von meinem HUAWEI RIO-L01 mit Tapatalk

[Dutchman]

@Kueppert:

@Kueppert:

Wow dutch, Respekt. Da ich nun auch node 8 drauf habe, werde ich den Adapter wegen der tuya Dosen auch Mal in Angriff nehmen ;)

Gesendet von meinem HUAWEI RIO-L01 mit Tapatalk ` Beim tuya Adapter wird der Wert aktuell in Watt ausgegeben. Wird aktuell gem. Log noch nicht unterstützt.

Möchte nicht extra Skripte bauen, daher warte ich noch was… :) `

Dan kannste am besten Statistic Adapter benutzen um W nach Wh um zu rechnen.

Weiß noch nicht ob ich das hier integrieren kann/werde also bis Version 0.5 werden nach jetzigen Plan nur Energy Werte unterstützt und nicht Lasten.

Ich checke Mal intern warum tuya das nicht liefert

Edit : nicht möglich mit tuya die Geräte liefern keine wH bzw kWh Daten.

App kann es anzeigen weil die Geräte Werte an die Cloud schicken welche es berechnet.

Sent from my iPhone using Tapatalk

[FriMatze]

Hey, ich brauche jetzt wirklich mal eure Hilfe. Folgendes. Habe den Rat angenommen und vor der Installation von 0.2.0 alles wieder herunter geworfen; 0.1.6 war installiert. Dann Version 0.2.0 installiert. Die Installation läuft soweit ich das sehen kann ohne Probleme durch, siehe Bild. Nach der Installation kann ich unter den installierten Adaptern sehen das der SourceAnalytix Adapater 0.2.0 installiert wurde, aber unter Instanzen kann ich ihn nicht sehen.

Was ist hier los :?: Check ich nicht :!:

[Kueppert]

@FriMatze:

Hey, ich brauche jetzt wirklich mal eure Hilfe. Folgendes. Habe den Rat angenommen und vor der Installation von 0.2.0 alles wieder herunter geworfen; 0.1.6 war installiert. Dann Version 0.2.0 installiert. Die Installation läuft soweit ich das sehen kann ohne Probleme durch, siehe Bild. Nach der Installation kann ich unter den installierten Adaptern sehen das der SourceAnalytix Adapater 0.2.0 installiert wurde, aber unter Instanzen kann ich ihn nicht sehen.

Was ist hier los :?: Check ich nicht :!:

filename="3.png" index="0">~~ filename="1.png" index="2">~~ filename="2.png" index="1">~~ ` Hast ein Upload gemacht?

Gesendet von meinem HUAWEI RIO-L01 mit Tapatalk

[Kueppert]

@Dutchman:

@Kueppert:

@Kueppert:

Wow dutch, Respekt. Da ich nun auch node 8 drauf habe, werde ich den Adapter wegen der tuya Dosen auch Mal in Angriff nehmen ;)

Gesendet von meinem HUAWEI RIO-L01 mit Tapatalk ` Beim tuya Adapter wird der Wert aktuell in Watt ausgegeben. Wird aktuell gem. Log noch nicht unterstützt.

Möchte nicht extra Skripte bauen, daher warte ich noch was… :) `

Dan kannste am besten Statistic Adapter benutzen um W nach Wh um zu rechnen.

Weiß noch nicht ob ich das hier integrieren kann/werde also bis Version 0.5 werden nach jetzigen Plan nur Energy Werte unterstützt und nicht Lasten.

Ich checke Mal intern warum tuya das nicht liefert

Edit : nicht möglich mit tuya die Geräte liefern keine wH bzw kWh Daten.

App kann es anzeigen weil die Geräte Werte an die Cloud schicken welche es berechnet.

Sent from my iPhone using Tapatalk ` Alles klar dutch,

dann mache ich den auch drauf und teste das über den Weg.

Wird Zeit für js1.6 und der Möglichkeit, mit compact RAM zu sparen langsam :D

Gesendet von meinem HUAWEI RIO-L01 mit Tapatalk

[Dutchman]

@Kueppert:

@FriMatze:

Was ist hier los :?: Check ich nicht :!: `

Wen man über git installiert wird nie eine Instanzen erzeugt, das passiert nur bei Installationen aus dem Admin.

Also immer Manuel erstellen bzw Uploaden

Sent from my iPhone using Tapatalk `