[GELÖST] Eigene Objekt Einstellung für Sourceanalytix
-
Hallo,
ich habe mir einen Datenpunkt erstellt, den ich gern weiter in Sourceanalytix aufgenommen hätte.
Leider wird mir mein Datenpunkt dort nicht angezeigt.
Kann mir jemand sagen wo mein Fehler ist?Ich Denke es liegt daran das der Datenpunkt die Richtige Einheit haben muss.
Meine Objekteinstellung lautet:
{ "common": { "name": "6-WattVerbrauch-Minus-SolarWatt", "desc": "Manuell erzeugt", "role": "value", "type": "number", "read": true, "unit": "W", "write": true, "def": "", "custom": { "history.0": { "enabled": true, "aliasId": "", "debounceTime": 0, "blockTime": 0, "changesOnly": true, "changesRelogInterval": "0", "changesMinDelta": 0, "ignoreBelowNumber": "", "disableSkippedValueLogging": false, "retention": "31536000", "customRetentionDuration": 365, "maxLength": 10, "enableDebugLogs": false, "debounce": 0 }, "sourceanalytix.0": { "enabled": true, "selectedUnit": "Detect automatically", "deviceResetLogicEnabled": true, "threshold": 1, "start_day": 0, "start_week": 0, "start_month": 0, "start_quarter": 0, "start_year": 0, "consumption": true, "meter_values": true, "costs": true } } }, "type": "state", "_id": "0_userdata.0.Strom.6-WattVerbrauch-Minus-SolarWatt", "acl": { "object": 1636, "state": 1636, "owner": "system.user.admin", "ownerGroup": "system.group.administrator" }, "from": "system.adapter.admin.0", "user": "system.user.admin", "ts": 1678655648088 }zum Vergleich hier der Code von einem Objekt einer Fritz Steckdose die in Sourceanalytix schon vorhanden ist:
{ "type": "state", "common": { "name": "actual Power", "type": "number", "min": 0, "max": 4000, "unit": "W", "read": true, "write": false, "role": "value", "desc": "actual Power", "custom": { "history.0": { "enabled": true, "changesOnly": true, "debounce": "1000", "maxLength": "960", "retention": "7948800", "changesRelogInterval": 0, "changesMinDelta": 0, "aliasId": "", "debounceTime": 0, "blockTime": 1000, "ignoreBelowNumber": "", "disableSkippedValueLogging": false, "customRetentionDuration": 365, "enableDebugLogs": false }, "sourceanalytix.0": { "enabled": true, "selectedUnit": "Detect automatically", "deviceResetLogicEnabled": true, "threshold": 1, "start_day": 6.280789244477779, "start_week": 5.307458237233332, "start_month": 5.307458237233332, "start_quarter": 5.307458237233332, "start_year": 5.307458237233332, "costs": true, "consumption": true, "basicRate": false, "meter_values": false, "alias": "Pool", "selectedPrice": "ElectricityDay", "valueAtDeviceInit": null, "valueAtDeviceReset": null, "cumulativeValue": 6.280789244477779 } } }, "native": {}, "_id": "fritzdect.0.DECT_087610178347.power", "acl": { "object": 1636, "state": 1636, "owner": "system.user.admin", "ownerGroup": "system.group.administrator" }, "from": "system.adapter.sourceanalytix.0", "user": "system.user.admin", "ts": 1678575600067 } -
@yoda sagte in Eigene Objekt Einstellung für Sourceanalytix Aufnahme:
Leider wird mir mein Datenpunkt dort nicht angezeigt.
wo?
laut Screenshot hast du ihn doch zum konfigurieren?!
-
@homoran
der Datenpunkt wird angezeigt soweit ok, aber der Punkt fehlt in Sour... Liste
-
@yoda sagte in Eigene Objekt Einstellung für Sourceanalytix Aufnahme:
aber der Punkt fehlt in Sour... Liste
und im log steht nix?
auch nicht dass du eine Preisdefinition eintragen musst? -
@homoran
die Fehler die ich dort finde kommen von der Fritz Steckdosen warum kann ich nicht wirklich nachvollziehen.Es waren aber noch einige andere Fehler vorhanden - die ich beseitigen konnte.
Wobei eigentlich kein Fehler mit meinem Objekt direkt zu tun hatten.
Keine Ahnung aber nun sind meine neuen Objekte 6-WattVerbrauch-Minus-SolarWatt vorhanden:
Danke dir für den tip mit dem Log - da hatte ich nicht reingeschaut - sind noch andere Fehler um die ich mich mal kümmern müsste ....
sourceanalytix.0 2023-03-12 23:20:50.456 info Initialization of 0_userdata.0.Strom.6-WattVerbrauch-Minus-SolarWatt successfully sourceanalytix.0 2023-03-12 23:20:47.274 info Initialising (36 of 36) "0_userdata.0.Strom.6-WattVerbrauch-Minus-SolarWatt"sourceanalytix.0 2023-03-12 23:20:10.286 error Initialization of sourceanalytix.0.fritzdect__0__DECT_087610178347__power.currentYear.consumed.02_previousWeek failed, check warn messages ! sourceanalytix.0 2023-03-12 23:20:10.286 error Cannot handle calculations for sourceanalytix.0.fritzdect__0__DECT_087610178347__power.currentYear.consumed.02_previousWeek, check log messages and adjust settings! sourceanalytix.0 2023-03-12 23:20:10.281 error No cost type defined for sourceanalytix.0.fritzdect__0__DECT_087610178347__power.currentYear.consumed.02_previousWeek, please Select Type of calculation at state setting sourceanalytix.0 2023-03-12 23:20:10.272 error Initialization of sourceanalytix.0.fritzdect__0__DECT_087610178347__power.currentYear.consumed.01_previousDay failed, check warn messages ! sourceanalytix.0 2023-03-12 23:20:10.272 error Cannot handle calculations for sourceanalytix.0.fritzdect__0__DECT_087610178347__power.currentYear.consumed.01_previousDay, check log messages and adjust settings! sourceanalytix.0 2023-03-12 23:20:10.271 error No cost type defined for sourceanalytix.0.fritzdect__0__DECT_087610178347__power.currentYear.consumed.01_previousDay, please Select Type of calculation at state setting sourceanalytix.0 2023-03-12 23:20:10.261 error Initialization of sourceanalytix.0.fritzdect__0__DECT_087610178347__power.currentYear.consumed.05_currentYear failed, check warn messages ! sourceanalytix.0 2023-03-12 23:20:10.261 error Cannot handle calculations for sourceanalytix.0.fritzdect__0__DECT_087610178347__power.currentYear.consumed.05_currentYear, check log messages and adjust settings! sourceanalytix.0 2023-03-12 23:20:10.260 error No cost type defined for sourceanalytix.0.fritzdect__0__DECT_087610178347__power.currentYear.consumed.05_currentYear, please Select Type of calculation at state setting sourceanalytix.0 2023-03-12 23:20:10.202 error Initialization of sourceanalytix.0.fritzdect__0__DECT_087610178347__power.currentYear.consumed.03_currentMonth failed, check warn messages ! sourceanalytix.0 2023-03-12 23:20:10.201 error Cannot handle calculations for sourceanalytix.0.fritzdect__0__DECT_087610178347__power.currentYear.consumed.03_currentMonth, check log messages and adjust settings! sourceanalytix.0 2023-03-12 23:20:10.201 error No cost type defined for sourceanalytix.0.fritzdect__0__DECT_087610178347__power.currentYear.consumed.03_currentMonth, please Select Type of calculation at state setting sourceanalytix.0 2023-03-12 23:20:10.192 error Initialization of sourceanalytix.0.fritzdect__0__DECT_087610178347__power.currentYear.consumed.02_currentWeek failed, check warn messages ! sourceanalytix.0 2023-03-12 23:20:10.191 error Cannot handle calculations for sourceanalytix.0.fritzdect__0__DECT_087610178347__power.currentYear.consumed.02_currentWeek, check log messages and adjust settings! sourceanalytix.0 2023-03-12 23:20:10.191 error No cost type defined for sourceanalytix.0.fritzdect__0__DECT_087610178347__power.currentYear.consumed.02_currentWeek, please Select Type of calculation at state setting sourceanalytix.0 2023-03-12 23:20:10.179 error Initialization of sourceanalytix.0.fritzdect__0__DECT_087610178347__power.currentYear.consumed.01_currentDay failed, check warn messages ! sourceanalytix.0 2023-03-12 23:20:10.179 error Cannot handle calculations for sourceanalytix.0.fritzdect__0__DECT_087610178347__power.currentYear.consumed.01_currentDay, check log messages and adjust settings! sourceanalytix.0 2023-03-12 23:20:10.179 error No cost type defined for sourceanalytix.0.fritzdect__0__DECT_087610178347__power.currentYear.consumed.01_currentDay, please Select Type of calculation at state setting sourceanalytix.0 2023-03-12 23:20:04.041 error Initialization of tuya.0.bf8e70a10eeb5baa2aycrz.19 failed, check warn messages ! sourceanalytix.0 2023-03-12 23:20:04.038 error Cannot handle calculations for tuya.0.bf8e70a10eeb5baa2aycrz.19, check log messages and adjust settings! sourceanalytix.0 2023-03-12 23:20:04.038 error No cost type defined for tuya.0.bf8e70a10eeb5baa2aycrz.19, please Select Type of calculation at state setting
