iobroker-community-adapters / iobroker.tesla-motors Goto Github PK
View Code? Open in Web Editor NEWioBroker Adapter for Tesla cars and powerwalls
License: MIT License
ioBroker Adapter for Tesla cars and powerwalls
License: MIT License
Version: stable=1.3.2 (349 days old) => latest=1.4.2 (15 days old)
Installs: stable=1153 (74.15%), latest=170 (10.93%), total=1555
Click to use developer portal
Click to edit
Note: This is an automatically generated message and not personally authored by bluefox!
Version: stable=1.3.2 (503 days old) => latest=1.4.5 (15 days old)
Installs: stable=1164 (70.76%), latest=153 (9.3%), total=1645
Click to use developer portal
Click to edit
Do not close this issue manually as a new issue will be created if condition for update still exists.
Please drop a comment if any reason exists which blocks updating to version 1.4.5 at this time.
Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence
Hallo,
Danke für den tollen Adapter!
Zwei Dinge würde ich mir wünschen:
Danke.
Der Folder token ( tesla-motors...tokens ) wächst enorm an und erzeugt mit der Zeit eine Unmenge an Datenpunkten.
Könnte man hier bitte einen regelmässigen cleanup durchführen ?
Ich hatte gestern pro Fahrzeug in dem Folder über 5000 Datenpunkte und heute nach ca 20h sind es bereits wieder fast 100
Meine aktuelle benutzte Version ist die 1.4.2
Hi, der Adapter legt verschiedene Folder mit einer history an. Dadurch entsteht über die Zeit ein riesiger, unübersichtlichen Datenbaum. Ich habe keine Option gefunden dies zu unterbinden.
Um den Objektbaum nicht unkontroliert vollaufen zu lassen, wäre eine Option die Sicherung historischer Daten abzustellen hilfreich. Damit die Tageswerte weiter in einer history erfasst werden können, wäre ein Art "Last day summary" eine Möglichkeit. Dort könnte sich ein hisotry adapter die Daten holen.
VG
the commands seems not to be working anymore:
tesla-motors.0 | 2023-07-05 01:20:47.458 | error | {"response":null,"error":"invalid_command","error_description":""} |
---|---|---|---|
tesla-motors.0 | 2023-07-05 01:20:47.458 | error | AxiosError: Request failed with status code 400 |
tesla-motors.0 | 2023-07-05 01:20:47.457 | error | https://owner-api.teslamotors.com/api/1/vehicles/STE20200906-00103/command/backup |
Adapter V1.3.2
NodeJS: 16.19.1
NPM: 8.19.3
JSController: 4.0.24
Nachdem ich meinen Tesla auf 2023.38.6 upgedated habe, musste ich den Adapter auf 1.35 Updaten, damit er überhaupt wieder funktioniert.
Aber der Datenpunkt tesla-motors.0.*.vehicle_state.odometer_km funktioniert nicht mehr.
Der Datenpunkt tesla-motors.0.*.vehicle_state.odometer zählt korrekt hoch.
keine Fehlerlogs vorhanden.
Versions:
It would be nice if this api endpoint could be added.
Hallo Zusammen,
Der Adapter lief jetzt einige Zeit sehr gut bei mir.
Gestern habe ich ein neues Auto bekommen und versuche das nun in ioBroker zu bekommen. Allerdings scheint der Login nicht zu funktionieren. Die URL habe ich der Anleitung nach eingefügt, und die enthält auch Access und Refresh Token.
Im Teslalogger hat die Neuanmeldung funktioniert.
Ich habe das jetzt mehrfach getestet und auch mal sowohl Instanz als auch Adapter gelöscht, aber ohne Erfolg. Anbei mein Log:
`
tesla-motors.0 | 2022-03-23 10:45:03.315 | info | Waiting for codeURL please visit instance settings and copy url after login |
---|---|---|---|
tesla-motors.0 | 2022-03-23 10:45:03.231 | info | starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.tesla-motors, node: v12.22.2, js-controller: 3.3.22 |
tesla-motors.0 | 2022-03-23 10:44:57.503 | info | Got terminate signal TERMINATE_YOURSELF |
tesla-motors.0 | 2022-03-23 10:44:57.498 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason |
tesla-motors.0 | 2022-03-23 10:44:57.497 | info | terminating |
tesla-motors.0 | 2022-03-23 10:44:57.472 | info | Save login session |
tesla-motors.0 | 2022-03-23 10:44:57.405 | info | Got terminate signal TERMINATE_YOURSELF |
tesla-motors.0 | 2022-03-23 10:44:57.369 | error | Please relogin in the settings and copy a new codeURL |
tesla-motors.0 | 2022-03-23 10:44:57.368 | error | {"error":"invalid_grant","error_description":"Internal server error","error_uri":"https://auth.tesla.com/error/reference/a53e5b95-bbff-47a8-bb63-80c81c0ae495-1648028697280"} |
tesla-motors.0 | 2022-03-23 10:44:57.368 | error | Error: Request failed with status code 403 |
tesla-motors.0 | 2022-03-23 10:43:57.136 | info | Login successful |
tesla-motors.0 | 2022-03-23 10:43:57.135 | error | Start relogin in 1min |
tesla-motors.0 | 2022-03-23 10:43:57.135 | error | {"error":"unsupported_grant_type","error_description":"The authorization grant type is not supported by the authorization server."} |
tesla-motors.0 | 2022-03-23 10:43:57.135 | error | Error: Request failed with status code 401 |
tesla-motors.0 | 2022-03-23 10:43:57.134 | error | own token failed |
tesla-motors.0 | 2022-03-23 10:43:56.961 | info | Start own Token Refresh |
tesla-motors.0 | 2022-03-23 10:43:56.594 | info | starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.tesla-motors, node: v12.22.2, js-controller: 3.3.22 |
tesla-motors.0 | 2022-03-23 10:43:51.703 | info | Got terminate signal TERMINATE_YOURSELF |
tesla-motors.0 | 2022-03-23 10:43:51.694 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason |
tesla-motors.0 | 2022-03-23 10:43:51.693 | info | terminating |
tesla-motors.0 | 2022-03-23 10:43:51.675 | info | Save login session |
tesla-motors.0 | 2022-03-23 10:43:51.671 | info | Got terminate signal TERMINATE_YOURSELF |
tesla-motors.0 | 2022-03-23 10:42:33.699 | info | Waiting for codeURL please visit instance settings and copy url after login |
tesla-motors.0 | 2022-03-23 10:42:33.611 | info | starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.tesla-motors, node: v12.22.2, js-controller: 3.3.22 |
Hat jemand eine Idee?
Hi,
it would be nice to get the "UnlockChargePort" function in the main package.
It seems it was already implemented in the fork by @dbweb-ch.
Thanks in advance
Sascha
In der Tesla App werden u.a die geladenen kWH pro Jahr angezeigt. Im Adapter unter den Datenpunkten...
Ist es möglich....
Version 1.4.2 (non-npm: iobroker-community-adapters/ioBroker.tesla-motors, node: v18.18.0, js-controller: 5.0.19
Seit gestern werden im Sekundentakt unter
tesla-motors.0.STE20200911-xxxxx.energy_history
tesla-motors.0.STE20200911-xxxxx.energy_history_lifetime
neue Ordner angelegt mit
tesla-motors.0.STE20200911-xxxxx.energy_history.time_series01
bis zum manuellen abschalten des Adapters
tesla-motors.0.STE20200911-00279.energy_history.time_series5000+x
gleiches für energy_history_lifetime
bis ich den Adapter ausschalten konnte hatte ich über 150.000 Objekte
dabei wird auch eine CPU Last von über 100% generiert.
Alle Objekte habe ich gelöscht, 1.4.2 neu installiert -> leider kein Erfolg, gleiches Verhalten
Woran kann das liegen?
Heute Nacht hat iobroker plötzlich nicht mehr die Werte aktualisiert obwohl er eine Verbindung hat. Ich habe dann den Adapter neu mit Tesla verbunden. Jetzt fällt mir auf, dass die Objekte in einem neuen Verzeichnis mit dem Namen des in ID verspeicherten Werts neu aufgebaut wurden ... somit funktionieren sowohl scripts wie auch vis nicht mehr weil sie auf die falschen Datenpunkte zugreifen.
Was ist die Ursache warum das neu aufgebaut ist und wie wird das verhindert ?
Versions:
Seit dem letzten Tesla-Update meines Model S vor ein paar Tagen aktualisieren sich die Positionsdaten nicht mehr. Ich habe einmal den Debug-Mode aktiviert und in das JSON reingeschaut, und tatsächlich sind dort auch keine mehr enthalten:
"drive_state": { "active_route_latitude": 51.XX, "active_route_longitude": 6.XX, "active_route_traffic_minutes_delay": 0, "power": 0, "shift_state": "P", "speed": 0, "timestamp": 1699810502840 },
Das letzte Update hat bewirkt, das im Tesla jetzt immer über ein Symbol angezeigt wird, das die App auf die Position-Daten zugreift. Ggf. wurde auch was an der API geändert?
Ein anderes Fahrzeug (Model 3), welches über den gleichen Account mit dem Controller verbunden ist, hat noch die Positionsdaten (und das entsprechende Update noch nicht).
Hi,
die Meldung erscheint bei mir immer. Habe schon versucht neu zu installieren und auch mehrmals den Login-Link eingefügt.
tesla-motors.0 | 2022-08-29 13:17:08.609 | error | Invalid codeURL please visit instance settings and copy url after login
Danke schon mal!
Version: stable=1.3.2 (309 days old) => latest=1.3.3 (15 days old)
Installs: stable=1162 (77.78%), latest=144 (9.64%), total=1494
Click to use developer portal
Click to edit
Note: This is an automatically generated message and not personally authored by bluefox!
The data point charger phases shows 2 although the car is charged with 3 phases.
The value is correct for one and two phases.
Version 1.3.2
No automatic Update of States in 1.4.0.
I updated cause of position fix. Now i get only new values when restarting the Adapter.
Tesla Adapter: V1.3.2
NodeJS: 16.19.1
NPM: 8.19.3
js-controller: 4.0.24
i changed the login credentials in the adapter and now i get periodically following error messages:
`
tesla-motors.0 | 2023-06-29 07:58:15.773 | error | {"response":null,"error":"https://powergate.prd.sn.tesla.services:443/api/v4/vehicle/charge_history => {:Message=>"Error getting charge history", :Status=>400}","error_description":""} |
---|---|---|---|
tesla-motors.0 | 2023-06-29 07:58:15.772 | error | AxiosError: Request failed with status code 400 |
tesla-motors.0 | 2023-06-29 07:58:15.772 | error | https://owner-api.teslamotors.com/api/1/vehicles/929761219325979/charge_history?vehicle_trim=5&client_time_zone=Europe/Berlin&client_country=DE¤cy_code=EUR&state=&time_zone=Europe/Vatican&state_label=&vehicle_model=2&language=de&country_label=Deutschland&country=DE |
tesla-motors.0 | 2023-06-29 07:58:15.771 | error | General error |
tesla-motors.0 | 2023-06-29 07:03:45.296 | error | TypeError: Cannot read properties of undefined (reading 'parseBase64') |
tesla-motors.0 | 2023-06-29 07:03:45.295 | error | Error extract keys: LRW3E7EL8NC605350 {"id":929761219325979,"user_id":1689261269605303,"vehicle_id":1689178486352666,"vin":"LRW3E7EL8NC605350","color":null,"access_type":"DRIVER","tokens":["13b83c5692bf189f","bee4da994e7cb3b0"],"state":"online","in_service":false,"id_s":"929761219325979","calendar_enabled":true,"api_version":58,"backseat_token":null,"backseat_token_updated_at":null,"ble_autopair_enrolled":false,"drive_state":{"active_route_latitude":47.407996,"active_route_longitude":8.595528,"active_route_traffic_minutes_delay":0,"gps_as_of":1688015024,"heading":274,"latitude":47.330871,"longitude":8.790783,"native_latitude":47.330871,"native_location_supported":1,"native_longitude":8.790783,"native_type":"wgs","power":0,"shift_state":null,"speed":null,"timestamp":1688015025403}} |
tesla-motors.0 | 2023-06-29 07:03:15.289 | error | TypeError: Cannot read properties of undefined (reading 'parseBase64') |
tesla-motors.0 | 2023-06-29 07:03:15.288 | error | Error extract keys: LRW3E7EL8NC605350 {"id":929761219325979,"user_id":1689261269605303,"vehicle_id":1689178486352666,"vin":"LRW3E7EL8NC605350","color":null,"access_type":"DRIVER","tokens":["13b83c5692bf189f","bee4da994e7cb3b0"],"state":"online","in_service":false,"id_s":"929761219325979","calendar_enabled":true,"api_version":58,"backseat_token":null,"backseat_token_updated_at":null,"ble_autopair_enrolled":false,"drive_state":{"active_route_latitude":47.407996,"active_route_longitude":8.595528,"active_route_traffic_minutes_delay":0,"gps_as_of":1688014994,"heading":274,"latitude":47.330871,"longitude":8.790783,"native_latitude":47.330871,"native_location_supported":1,"native_longitude":8.790783,"native_type":"wgs","power":0,"shift_state":null,"speed":null,"timestamp":1688014995383}} |
tesla-motors.0 | 2023-06-29 07:02:45.241 | error | TypeError: Cannot read properties of undefined (reading 'parseBase64') |
tesla-motors.0 | 2023-06-29 07:02:45.240 | error | Error extract keys: LRW3E7EL8NC605350 {"id":929761219325979,"user_id":1689261269605303,"vehicle_id":1689178486352666,"vin":"LRW3E7EL8NC605350","color":null,"access_type":"DRIVER","tokens":["13b83c5692bf189f","bee4da994e7cb3b0"],"state":"online","in_service":false,"id_s":"929761219325979","calendar_enabled":true,"api_version":58,"backseat_token":null,"backseat_token_updated_at":null,"ble_autopair_enrolled":false,"drive_state":{"active_route_latitude":47.407996,"active_route_longitude":8.595528,"active_route_traffic_minutes_delay":0,"gps_as_of":1688014963,"heading":274,"latitude":47.330871,"longitude":8.790781,"native_latitude":47.330871,"native_location_supported":1,"native_longitude":8.790781,"native_type":"wgs","power":0,"shift_state":null,"speed":null,"timestamp":1688014965346}} |
tesla-motors.0 | 2023-06-29 07:02:15.348 | error | TypeError: Cannot read properties of undefined (reading 'parseBase64') |
tesla-motors.0 | 2023-06-29 07:02:15.348 | error | Error extract keys: LRW3E7EL8NC605350 {"id":929761219325979,"user_id":1689261269605303,"vehicle_id":1689178486352666,"vin":"LRW3E7EL8NC605350","color":null,"access_type":"DRIVER","tokens":["13b83c5692bf189f","bee4da994e7cb3b0"],"state":"online","in_service":false,"id_s":"929761219325979","calendar_enabled":true,"api_version":58,"backseat_token":null,"backseat_token_updated_at":null,"ble_autopair_enrolled":false,"drive_state":{"active_route_latitude":47.407996,"active_route_longitude":8.595528,"active_route_traffic_minutes_delay":0,"gps_as_of":1688014934,"heading":267,"latitude":47.330867,"longitude":8.790793,"native_latitude":47.330867,"native_location_supported":1,"native_longitude":8.790793,"native_type":"wgs","power":2,"shift_state":"D","speed":3,"timestamp":1688014935459}} |
tesla-motors.0 | 2023-06-29 07:02:14.999 | info | State value to set for "tesla-motors.0.LRW3E7EL8NC605350.vehicle_state.tpms_last_seen_pressure_time_rr" has to be type "number" but received type "string" |
tesla-motors.0 | 2023-06-29 07:02:14.998 | info | State value to set for "tesla-motors.0.LRW3E7EL8NC605350.vehicle_state.tpms_last_seen_pressure_time_rl" has to be type "number" but received type "string" |
tesla-motors.0 | 2023-06-29 07:02:14.998 | info | State value to set for "tesla-motors.0.LRW3E7EL8NC605350.vehicle_state.tpms_last_seen_pressure_time_fr" has to be type "number" but received type "string" |
tesla-motors.0 | 2023-06-29 07:02:14.997 | info | State value to set for "tesla-motors.0.LRW3E7EL8NC605350.vehicle_state.tpms_last_seen_pressure_time_fl" has to be type "number" but received type "string" |
tesla-motors.0 | 2023-06-29 07:02:14.976 | info | State value to set for "tesla-motors.0.LRW3E7EL8NC605350.drive_state.speed" has to be type "string" but received type "number" |
tesla-motors.0 | 2023-06-29 07:01:45.259 | error | TypeError: Cannot read properties of undefined (reading 'parseBase64') |
tesla-motors.0 | 2023-06-29 07:01:45.258 | error | Error extract keys: LRW3E7EL8NC605350 {"id":929761219325979,"user_id":1689261269605303,"vehicle_id":1689178486352666,"vin":"LRW3E7EL8NC605350","color":null,"access_type":"DRIVER","tokens":["13b83c5692bf189f","bee4da994e7cb3b0"],"state":"online","in_service":false,"id_s":"929761219325979","calendar_enabled":true,"api_version":58,"backseat_token":null,"backseat_token_updated_at":null,"ble_autopair_enrolled":false,"drive_state":{"active_route_latitude":47.407996,"active_route_longitude":8.595528,"active_route_traffic_minutes_delay":0,"gps_as_of":1688014904,"heading":275,"latitude":47.332289,"longitude":8.791959,"native_latitude":47.332289,"native_location_supported":1,"native_longitude":8.791959,"native_type":"wgs","power":-8,"shift_state":"D","speed":22,"timestamp":1688014905349}} |
tesla-motors.0 | 2023-06-29 07:01:15.243 | error | TypeError: Cannot read properties of undefined (reading 'parseBase64') |
tesla-motors.0 | 2023-06-29 07:01:15.243 | error | Error extract keys: LRW3E7EL8NC605350 {"id":929761219325979,"user_id":1689261269605303,"vehicle_id":1689178486352666,"vin":"LRW3E7EL8NC605350","color":null,"access_type":"DRIVER","tokens":["13b83c5692bf189f","bee4da994e7cb3b0"],"state":"online","in_service":false,"id_s":"929761219325979","calendar_enabled":true,"api_version":58,"backseat_token":null,"backseat_token_updated_at":null,"ble_autopair_enrolled":false,"drive_state":{"active_route_latitude":47.407996,"active_route_longitude":8.595528,"active_route_traffic_minutes_delay":0,"gps_as_of":1688014874,"heading":256,"latitude":47.332215,"longitude":8.796515,"native_latitude":47.332215,"native_location_supported":1,"native_longitude":8.796515,"native_type":"wgs","power":14,"shift_state":"D","speed":19,"timestamp":1688014875352}} |
tesla-motors.0 | 2023-06-29 07:00:45.215 | error | TypeError: Cannot read properties of undefined (reading 'parseBase64') |
tesla-motors.0 | 2023-06-29 07:00:45.214 | error | Error extract keys: LRW3E7EL8NC605350 {"id":929761219325979,"user_id":1689261269605303,"vehicle_id":1689178486352666,"vin":"LRW3E7EL8NC605350","color":null,"access_type":"DRIVER","tokens":["13b83c5692bf189f","bee4da994e7cb3b0"],"state":"online","in_service":false,"id_s":"929761219325979","calendar_enabled":true,"api_version":58,"backseat_token":null,"backseat_token_updated_at":null,"ble_autopair_enrolled":false,"drive_state":{"active_route_latitude":47.407996,"active_route_longitude":8.595528,"active_route_traffic_minutes_delay":0,"gps_as_of":1688014844,"heading":252,"latitude":47.332482,"longitude":8.80143,"native_latitude":47.332482,"native_location_supported":1,"native_longitude":8.80143,"native_type":"wgs","power":3,"shift_state":"D","speed":35,"timestamp":1688014845324}} |
tesla-motors.0 | 2023-06-29 07:00:15.322 | error | TypeError: Cannot read properties of undefined (reading 'parseBase64') |
tesla-motors.0 | 2023-06-29 07:00:15.321 | error | Error extract keys: LRW3E7EL8NC605350 {"id":929761219325979,"user_id":1689261269605303,"vehicle_id":1689178486352666,"vin":"LRW3E7EL8NC605350","color":null,"access_type":"DRIVER","tokens":["13b83c5692bf189f","bee4da994e7cb3b0"],"state":"online","in_service":false,"id_s":"929761219325979","calendar_enabled":true,"api_version":58,"backseat_token":null,"backseat_token_updated_at":null,"ble_autopair_enrolled":false,"drive_state":{"active_route_latitude":47.407996,"active_route_longitude":8.595528,"active_route_traffic_minutes_delay":0,"gps_as_of":1688014814,"heading":298,"latitude":47.333003,"longitude":8.805947,"native_latitude":47.333003,"native_location_supported":1,"native_longitude":8.805947,"native_type":"wgs","power":0,"shift_state":"D","speed":5,"timestamp":1688014815425}} |
tesla-motors.0 | 2023-06-29 07:00:14.997 | info | State value to set for "tesla-motors.0.LRW3E7EL8NC605350.vehicle_state.tpms_last_seen_pressure_time_rr" has to be type "number" but received type "string" |
tesla-motors.0 | 2023-06-29 07:00:14.997 | info | State value to set for "tesla-motors.0.LRW3E7EL8NC605350.vehicle_state.tpms_last_seen_pressure_time_rl" has to be type "number" but received type "string" |
tesla-motors.0 | 2023-06-29 07:00:14.996 | info | State value to set for "tesla-motors.0.LRW3E7EL8NC605350.vehicle_state.tpms_last_seen_pressure_time_fr" has to be type "number" but received type "string" |
tesla-motors.0 | 2023-06-29 07:00:14.996 | info | State value to set for "tesla-motors.0.LRW3E7EL8NC605350.vehicle_state.tpms_last_seen_pressure_time_fl" has to be type "number" but received type "string" |
tesla-motors.0 | 2023-06-29 07:00:14.986 | info | State value to set for "tesla-motors.0.LRW3E7EL8NC605350.drive_state.speed" has to be type "string" but received type "number" |
tesla-motors.0 | 2023-06-29 07:00:06.194 | info | State value to set for "tesla-motors.0.LRW3E7EL8NC605350.vehicle_state.tpms_last_seen_pressure_time_rr" has to be type "number" but received type "string" |
tesla-motors.0 | 2023-06-29 07:00:06.194 | info | State value to set for "tesla-motors.0.LRW3E7EL8NC605350.vehicle_state.tpms_last_seen_pressure_time_rl" has to be type "number" but received type "string" |
tesla-motors.0 | 2023-06-29 07:00:06.193 | info | State value to set for "tesla-motors.0.LRW3E7EL8NC605350.vehicle_state.tpms_last_seen_pressure_time_fr" has to be type "number" but received type "string" |
tesla-motors.0 | 2023-06-29 07:00:06.192 | info | State value to set for "tesla-motors.0.LRW3E7EL8NC605350.vehicle_state.tpms_last_seen_pressure_time_fl" has to be type "number" but received type "string" |
tesla-motors.0 | 2023-06-29 07:00:06.182 | info | State value to set for "tesla-motors.0.LRW3E7EL8NC605350.drive_state.speed" has to be type "string" but received type "number" |
tesla-motors.0 | 2023-06-29 07:00:00.594 | error | {"response":null,"error":"not_found","error_description":""} |
tesla-motors.0 | 2023-06-29 07:00:00.594 | error | AxiosError: Request failed with status code 404 |
tesla-motors.0 | 2023-06-29 07:00:00.593 | error | https://owner-api.teslamotors.com/api/1/energy_sites/144759284921/backup |
tesla-motors.0 | 2023-06-29 06:59:45.203 | error | TypeError: Cannot read properties of undefined (reading 'parseBase64') |
tesla-motors.0 | 2023-06-29 06:59:45.202 | error | Error extract keys: LRW3E7EL8NC605350 {"id":929761219325979,"user_id":1689261269605303,"vehicle_id":1689178486352666,"vin":"LRW3E7EL8NC605350","color":null,"access_type":"DRIVER","tokens":["bee4da994e7cb3b0","561bc46d3938399d"],"state":"online","in_service":false,"id_s":"929761219325979","calendar_enabled":true,"api_version":58,"backseat_token":null,"backseat_token_updated_at":null,"ble_autopair_enrolled":false,"drive_state":{"active_route_latitude":47.407996,"active_route_longitude":8.595528,"active_route_traffic_minutes_delay":0,"gps_as_of":1688014784,"heading":280,"latitude":47.332614,"longitude":8.809552,"native_latitude":47.332614,"native_location_supported":1,"native_longitude":8.809552,"native_type":"wgs","power":16,"shift_state":"D","speed":30,"timestamp":1688014785309}} |
tesla-motors.0 | 2023-06-29 06:59:15.205 | error | TypeError: Cannot read properties of undefined (reading 'parseBase64') |
tesla-motors.0 | 2023-06-29 06:59:15.204 | error | Error extract keys: LRW3E7EL8NC605350 {"id":929761219325979,"user_id":1689261269605303,"vehicle_id":1689178486352666,"vin":"LRW3E7EL8NC605350","color":null,"access_type":"DRIVER","tokens":["bee4da994e7cb3b0","561bc46d3938399d"],"state":"online","in_service":false,"id_s":"929761219325979","calendar_enabled":true,"api_version":58,"backseat_token":null,"backseat_token_updated_at":null,"ble_autopair_enrolled":false,"drive_state":{"active_route_latitude":47.407996,"active_route_longitude":8.595528,"active_route_traffic_minutes_delay":0,"gps_as_of":1688014754,"heading":271,"latitude":47.332708,"longitude":8.813146,"native_latitude":47.332708,"native_location_supported":1,"native_longitude":8.813146,"native_type":"wgs","power":-12,"shift_state":"D","speed":32,"timestamp":1688014755310}} |
tesla-motors.0 | 2023-06-29 06:58:45.212 | error | TypeError: Cannot read properties of undefined (reading 'parseBase64') |
tesla-motors.0 | 2023-06-29 06:58:45.211 | error | Error extract keys: LRW3E7EL8NC605350 {"id":929761219325979,"user_id":1689261269605303,"vehicle_id":1689178486352666,"vin":"LRW3E7EL8NC605350","color":null,"access_type":"DRIVER","tokens":["bee4da994e7cb3b0","561bc46d3938399d"],"state":"online","in_service":false,"id_s":"929761219325979","calendar_enabled":true,"api_version":58,"backseat_token":null,"backseat_token_updated_at":null,"ble_autopair_enrolled":false,"drive_state":{"active_route_latitude":47.407996,"active_route_longitude":8.595528,"active_route_traffic_minutes_delay":0,"gps_as_of":1688014724,"heading":250,"latitude":47.331895,"longitude":8.817651,"native_latitude":47.331895,"native_location_supported":1,"native_longitude":8.817651,"native_type":"wgs","power":1,"shift_state":"D","speed":0,"timestamp":1688014725321}} |
tesla-motors.0 | 2023-06-29 06:58:15.125 | info | State value to set for "tesla-motors.0.LRW3E7EL8NC605350.vehicle_state.tpms_last_seen_pressure_time_rr" has to be type "number" but received type "string" |
tesla-motors.0 | 2023-06-29 06:58:15.124 | info | State value to set for "tesla-motors.0.LRW3E7EL8NC605350.vehicle_state.tpms_last_seen_pressure_time_rl" has to be type "number" but received type "string" |
`
Since some days I'm receiving the following error. It happens every time when an API update is being processed.
Any ideas? Let me know if you need more information ...
tesla-motors.0
2023-10-08 09:12:46.994 error {"response":null,"error":"https://powergate.prd.sn.tesla.services:443/api/powerwalls/1152100-13-E--**************/status => Gone","error_description":""}
tesla-motors.0
2023-10-08 09:12:46.994 error AxiosError: Request failed with status code 410
tesla-motors.0
2023-10-08 09:12:46.994 error https://owner-api.teslamotors.com/api/1/powerwalls/****************-00108/status
tesla-motors.0
2023-10-08 09:12:46.994 error General error
tesla-motors.0
2023-10-08 09:09:46.715 info Found 1 devices
tesla-motors.0
2023-10-08 09:09:45.771 info Receive device list
tesla-motors.0
2023-10-08 09:09:45.770 info Login successful
tesla-motors.0
2023-10-08 09:09:44.288 info Initial login
tesla-motors.0
2023-10-08 09:09:44.267 info starting. Version 1.3.2 in /opt/iobroker/node_modules/iobroker.tesla-motors, node: v18.17.1, js-controller: 5.0.12
Version: stable=1.3.2 (325 days old) => latest=1.3.5 (15 days old)
Installs: stable=1167 (76.37%), latest=157 (10.27%), total=1528
Click to use developer portal
Click to edit
Note: This is an automatically generated message and not personally authored by bluefox!
Auch in Version 1.3.3 sind im Log kontinuierlich folgende Errors zu sehen?
tesla-motors.0. 2023-10-18 10:13:22.853 error TypeError: data.time_series is not iterable
tesla-motors.0. 2023-10-18 10:13:22.853 error https://owner-api.teslamotors.com/api/1/energy_sites/1689312975048004/calendar_history?kind=energy&start_date=2016-01-01T00%3A00%3A00%2B01%3A00&time_zone=Europe/Berlin&period=lifetime&end_date=2023-10-18T10:13:19.932Z
tesla-motors.0. 2023-10-18 10:13:22.853 error General error
tesla-motors.0. 2023-10-18 10:13:21.580 error {"response":null,"error":"https://powergate.prd.sn.tesla.services:443/api/v2/energy_site/backup_history => No valid dins were present in the request [[ /api/v2/energy_site/backup_history?kind=backup&site_id=STE20230916-01074&dins=&asset_site_id=8cee82ec-0e18-49c2-8a13-d1d0cd481986 ]]","error_description":""}
tesla-motors.0. 2023-10-18 10:13:21.579 error AxiosError: Request failed with status code 400
tesla-motors.0. 2023-10-18 10:13:21.579 error https://owner-api.teslamotors.com/api/1/energy_sites/1689312975048004/history?kind=backup
tesla-motors.0. 2023-10-18 10:13:21.579 error General error
The adapter creates a lot of logs about incorrect data types received for the energy gateway/powerwall. The values are updated as expected.
To Reproduce
Poll data from a tesla account with a powerwall in it.
Expected behavior
There should be no warnings.
Screenshots & Logfiles
tesla-motors.0 | 2022-02-14 14:34:18.835 | info | State value to set for "tesla-motors.0.STE2021XXX.percentage_charged" has to be type "string" but received type "number" |
---|---|---|---|
tesla-motors.0 | 2022-02-14 14:34:18.834 | info | State value to set for "tesla-motors.0.STE2021XXX.energy_left" has to be type "string" but received type "number" |
tesla-motors.0 | 2022-02-14 14:34:18.432 | info | State value to set for "tesla-motors.0.STE2021XXX.components.battery" has to be type "boolean" but received type "number" |
tesla-motors.0 | 2022-02-14 14:34:18.431 | info | State value to set for "tesla-motors.0.STE2021XXX.components.solar" has to be type "boolean" but received type "number" |
tesla-motors.0 | 2022-02-14 14:34:18.287 | info | State value to set for "tesla-motors.0.STE2021XXX.percentage_charged" has to be type "string" but received type "number" |
tesla-motors.0 | 2022-02-14 14:34:18.287 | info | State value to set for "tesla-motors.0.STE2021XXX.energy_left" has to be type "string" but received type "number" |
Versions:
The object in iobroker for energy_left is already of type number.
Even after deleting the object and restarting the adapter it is recreated as number with the correct value in it. The log still complains about it :(
Dear Adapter developer,
with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.
If something is not correct this is logged as 'warning' or 'info' log.
Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!
Please spent some 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 or info log there from these checks please adjust the adapter and fix the relevant cases.
For questions please refer to ioBroker/ioBroker.js-controller#1749
Please close the issue after you checked it.
Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!
Hi
wrong datatype reported:
`
2022-10-27 09:59:27.217 | info | State value to set for "tesla-motors.0.XXXXXX.vehicle_state.media_info.now_playing_source" has to be type "string" but received type "number" |
---|
`
Ladeverlust von ca. 5% pro 24h.
'Auto für jedes Update aufwecken' ist OFF.
Mein Setup beinhaltet sowohl Tesla Powerwall, als auch ein Model X 2019 (Raven)
Wenn ich den Adapter tesla-motors pausiere, gibt es praktisch keine Entladung der Batterie im Auto
Versions:
Der Adapter funktioniert aus meiner Sicht wunderbar.
Hin und wieder habe ich im Log die "Error 408" Meldungen. Du hattest mal erwähnt, dass sie eigentlich rausgefiltert werden?
`
tesla-motors.0 | 2021-09-24 15:25:51.567 | error | {"response":null,"error":"https://mothership-api-europe.vn.teslamotors.com:443/vehicles/557279701 => operation_timedout with 10s timeout","error_description":""} |
---|---|---|---|
tesla-motors.0 | 2021-09-24 15:25:51.566 | error | Error: Request failed with status code 408 |
tesla-motors.0 | 2021-09-24 14:28:51.497 | error | {"response":null,"error":"https://mothership-api-europe.vn.teslamotors.com:443/vehicles/1091727681 => operation_timedout with 10s timeout","error_description":""} |
tesla-motors.0 | 2021-09-24 14:28:51.496 | error | Error: Request failed with status code 408 |
tesla-motors.0 | 2021-09-24 12:36:51.472 | error | {"response":null,"error":"https://mothership-api-europe.vn.teslamotors.com:443/vehicles/1091727681 => operation_timedout with 10s timeout","error_description":""} |
tesla-motors.0 | 2021-09-24 12:36:51.460 | error | Error: Request failed with status code 408 |
`
Hallo. Ich suche Datenpunkte für Average Watt/100 km für Trip und Total Watt für Trip. Gibt es die nicht? Und könnte man die einbauen? Nikola für Tesla kennt diese Punkte..
Danke!
My Model 3 is a leased vehicle, therefore I have not full access to alle data of the car. For example, I can't view my charing history. Normaly there is menu point in the Tesla App, but I don't have it. I already called with Tesla and my Leasing provider, they say I have not access because I'm not the primary vehicle owner.
Because of this fact I get regularly "access denied" errors from the Tesla adapter. For users like me, it would be nice if we could disable known error logs. Would that be conceivable?
Hi,
der Adapter funktionierte bisher immer gut. Nur bekomme ich keine Verbindung mehr..... Habe nichts gemacht, kein Update nichts.
Das Protokoll gibt folgendes aus:
Nun habe ich versucht, die Verbindung (auth.tesla.com) zu erneuern. Da kommt aber keine ID mehr oder Login Möglichkeit.
Habe auch schon den Cache und Cockies gelöscht, keine Veränderung. Wenn ich auf Tesla.com gehe, kann ich mich normal einloggen.
Passwort habe ich auch mal zurückgesetzt, wurde im Forum empfohlen. Leider ebenfalls nichts.
Jemand eine Idee?
Grüße
Seitdem mir das bestellte Fahrzeug zugewiesen wurde, kann es der Adapter ebenfalls auslesen.
Da vermutlich nicht alle erwartenden Daten verfügbar sind, werden diverse Fehler generiert und Objekte die eigentlich für die Powerwall relevant sind erzeugt:
`
tesla-motors.0 | 2022-08-05 10:53:30.296 | error | {"response":null,"error":"not_found","error_description":""} |
---|---|---|---|
tesla-motors.0 | 2022-08-05 10:53:30.296 | error | Error: Request failed with status code 404 |
tesla-motors.0 | 2022-08-05 10:53:30.296 | error | https://owner-api.teslamotors.com/api/1/energy_sites/undefined/live_status |
tesla-motors.0 | 2022-08-05 10:53:30.296 | error | General error |
tesla-motors.0 | 2022-08-05 10:53:30.294 | error | {"response":null,"error":"not_found","error_description":""} |
tesla-motors.0 | 2022-08-05 10:53:30.291 | error | Error: Request failed with status code 404 |
tesla-motors.0 | 2022-08-05 10:53:30.291 | error | https://owner-api.teslamotors.com/api/1/energy_sites/undefined/history?kind=backup |
tesla-motors.0 | 2022-08-05 10:53:30.290 | error | General error |
tesla-motors.0 | 2022-08-05 10:53:30.282 | error | {"response":null,"error":"not_found","error_description":""} |
tesla-motors.0 | 2022-08-05 10:53:30.282 | error | Error: Request failed with status code 404 |
tesla-motors.0 | 2022-08-05 10:53:30.281 | error | https://owner-api.teslamotors.com/api/1/energy_sites/undefined/site_info |
tesla-motors.0 | 2022-08-05 10:53:30.281 | error | General error |
tesla-motors.0 | 2022-08-05 10:53:30.279 | error | {"response":null,"error":"not_found","error_description":""} |
tesla-motors.0 | 2022-08-05 10:53:30.279 | error | Error: Request failed with status code 404 |
tesla-motors.0 | 2022-08-05 10:53:30.279 | error | https://owner-api.teslamotors.com/api/1/energy_sites/undefined/calendar_history?kind=self_consumption&start_date=2016-01-01T00%3A00%3A00%2B01%3A00&period=lifetime&time_zone=Europe%2FBerlin&end_date=2022-08-05T10:53:30.035Z |
tesla-motors.0 | 2022-08-05 10:53:30.278 | error | General error |
tesla-motors.0 | 2022-08-05 10:53:30.273 | error | {"response":null,"error":"not_found","error_description":""} |
tesla-motors.0 | 2022-08-05 10:53:30.273 | error | Error: Request failed with status code 404 |
tesla-motors.0 | 2022-08-05 10:53:30.272 | error | https://owner-api.teslamotors.com/api/1/energy_sites/undefined/calendar_history?kind=energy&start_date=2016-01-01T00%3A00%3A00%2B01%3A00&time_zone=Europe/Berlin&period=lifetime&end_date=2022-08-05T10:53:30.035Z |
tesla-motors.0 | 2022-08-05 10:53:30.272 | error | General error |
tesla-motors.0 | 2022-08-05 10:53:30.264 | error | {"response":null,"error":"not_found","error_description":""} |
tesla-motors.0 | 2022-08-05 10:53:30.264 | error | Error: Request failed with status code 404 |
tesla-motors.0 | 2022-08-05 10:53:30.264 | error | https://owner-api.teslamotors.com/api/1/energy_sites/undefined/calendar_history?kind=energy&period=day&time_zone=Europe%2FBerlin&end_date=2022-08-05T10:53:30.035Z |
tesla-motors.0 | 2022-08-05 10:53:30.264 | error | General error |
tesla-motors.0 | 2022-08-05 10:53:30.259 | error | {"response":null,"error":"not_found","error_description":""} |
tesla-motors.0 | 2022-08-05 10:53:30.259 | error | Error: Request failed with status code 404 |
tesla-motors.0 | 2022-08-05 10:53:30.258 | error | https://owner-api.teslamotors.com/api/1/energy_sites/undefined/calendar_history?kind=self_consumption&period=day&time_zone=Europe%2FBerlin&end_date=2022-08-05T10:53:30.035Z |
tesla-motors.0 | 2022-08-05 10:53:30.258 | error | General error |
tesla-motors.0 | 2022-08-05 10:53:30.251 | error | {"response":null,"error":"not_found","error_description":""} |
tesla-motors.0 | 2022-08-05 10:53:30.251 | error | Error: Request failed with status code 404 |
tesla-motors.0 | 2022-08-05 10:53:30.251 | error | https://owner-api.teslamotors.com/api/1/energy_sites/undefined/site_status |
tesla-motors.0 | 2022-08-05 10:53:30.250 | error | General error |
tesla-motors.0 | 2022-08-05 10:53:30.245 | error | {"response":null,"error":"unknown site","error_description":""} |
tesla-motors.0 | 2022-08-05 10:53:30.245 | error | Error: Request failed with status code 404 |
tesla-motors.0 | 2022-08-05 10:53:30.245 | error | https://owner-api.teslamotors.com/api/1/powerwalls/undefined/status |
tesla-motors.0 | 2022-08-05 10:53:30.244 | error | General error |
Versions:
*Adapter version: 1.3.0
*JS-Controller version: 4.0.23
*Node version: 16.16.0
*NPM version: 8.11.0
*Operating system: bullseye
Der Tesla Adapter läuft bei mir seit mehreren Monaten fehlerfrei und liefert auch richtige Werte die mit Grafana dargestellt werden. Seit einiger Zeit verändert sich aber der Tesla Powerwall Wert "energy_left" nicht mehr. Die letzte Aktualisierung fand am 21.03. um 00:30 statt. Wie muss ich vorgehen um das Problem zu lösen?
Describe the bug
When I click on the button for open trunk in ioBroker, nothing happens. Only the following error message appears:
{"response":null,"error":"Tesla Vehicle Command Protocol required, please refer to the documentation here: https://developer.tesla.com/docs/fleet-api#2023-10-09-rest-api-vehicle-commands-endpoint-deprecation-warning","error_description":""}
tesla-motors.0
2024-01-14 15:27:45.358 error AxiosError: Request failed with status code 403
tesla-motors.0
2024-01-14 15:27:45.357 error https://owner-api.teslamotors.com/api/1/vehicles/929890198683643/command/actuate_trunk
However, data from the Tesla is retrieved and displayed, so the connection must be there
Greetings
Holger
Version: stable=1.3.1 (126 days old) => latest=1.3.2 (15 days old)
Installs: stable=675 (65.28%), latest=100 (9.67%), total=1034
Click to edit
i made a github update some days ago (V1.3.2) and i get a lot of error messages in the log
`
tesla-motors.0 | 2023-06-09 12:21:12.008 | warn | State "tesla-motors.0.5YJSA7E25HF205349.charge_history.charging_tips.text_sections01.paragraphs.Lernen Sie, wie Sie Geld sparen, nachhaltiger laden und auf alles vorbereitet sein können, was das Leben Ihnen bietet" has no existing object, this might lead to an error in future versions |
---|---|---|---|
tesla-motors.0 | 2023-06-09 12:21:11.994 | error | Error: The id "5YJSA7E25HF205349.charge_history.energy_cost_breakdown.card.info.sections03.paragraphs.Alle Ladevorgänge außerhalb von Zuhause und Tesla Superchargers, dargestellt durch den durchschnittlichen Strompreis in Deutschland." is invalid. Ids are not allowed to end in "." |
tesla-motors.0 | 2023-06-09 12:21:11.994 | error | Error extract keys: 5YJSA7E25HF205349.charge_history.energy_cost_breakdown.card.info.sections03.paragraphs.Alle Ladevorgänge außerhalb von Zuhause und Tesla Superchargers, dargestellt durch den durchschnittlichen Strompreis in Deutschland. "Alle Ladevorgänge außerhalb von Zuhause und Tesla Superchargers, dargestellt durch den durchschnittlichen Strompreis in Deutschland." |
tesla-motors.0 | 2023-06-09 12:21:11.989 | error | Error: The id "5YJSA7E25HF205349.charge_history.energy_cost_breakdown.card.info.sections03.paragraphs.Alle Ladevorgänge außerhalb von Zuhause und Tesla Superchargers, dargestellt durch den durchschnittlichen Strompreis in Deutschland." is invalid. Ids are not allowed to end in "." |
tesla-motors.0 | 2023-06-09 12:21:11.986 | error | Error: The id "5YJSA7E25HF205349.charge_history.energy_cost_breakdown.card.info.sections02.paragraphs.Schätzwert anhand der Rechnungsdaten Ihres Tesla für den angegebenen Zeitraum." is invalid. Ids are not allowed to end in "." |
tesla-motors.0 | 2023-06-09 12:21:11.986 | error | Error extract keys: 5YJSA7E25HF205349.charge_history.energy_cost_breakdown.card.info.sections02.paragraphs.Schätzwert anhand der Rechnungsdaten Ihres Tesla für den angegebenen Zeitraum. "Schätzwert anhand der Rechnungsdaten Ihres Tesla für den angegebenen Zeitraum." |
tesla-motors.0 | 2023-06-09 12:21:11.983 | error | Error: The id "5YJSA7E25HF205349.charge_history.energy_cost_breakdown.card.info.sections02.paragraphs.Schätzwert anhand der Rechnungsdaten Ihres Tesla für den angegebenen Zeitraum." is invalid. Ids are not allowed to end in "." |
tesla-motors.0 | 2023-06-09 12:21:11.976 | error | Error: The id "5YJSA7E25HF205349.charge_history.energy_cost_breakdown.card.info.sections01.paragraphs.Die Berechnung erfolgt anhand der durchschnittlichen Stromkosten in Deutschland für den angegebenen Zeitraum." is invalid. Ids are not allowed to end in "." |
tesla-motors.0 | 2023-06-09 12:21:11.975 | error | Error extract keys: 5YJSA7E25HF205349.charge_history.energy_cost_breakdown.card.info.sections01.paragraphs.Die Berechnung erfolgt anhand der durchschnittlichen Stromkosten in Deutschland für den angegebenen Zeitraum. "Die Berechnung erfolgt anhand der durchschnittlichen Stromkosten in Deutschland für den angegebenen Zeitraum." |
tesla-motors.0 | 2023-06-09 12:21:11.973 | error | Error: The id "5YJSA7E25HF205349.charge_history.energy_cost_breakdown.card.info.sections01.paragraphs.Die Berechnung erfolgt anhand der durchschnittlichen Stromkosten in Deutschland für den angegebenen Zeitraum." is invalid. Ids are not allowed to end in "." |
tesla-motors.0 | 2023-06-09 12:21:11.967 | error | Error: The id "5YJSA7E25HF205349.charge_history.gas_savings.card.info.sections01.paragraphs.Die aktuelle Berechnung basiert auf geschätzten Kraftstoffkosten von 1,83 € pro Liter in Deutschland." is invalid. Ids are not allowed to end in "." |
tesla-motors.0 | 2023-06-09 12:21:11.966 | error | Error extract keys: 5YJSA7E25HF205349.charge_history.gas_savings.card.info.sections01.paragraphs.Die aktuelle Berechnung basiert auf geschätzten Kraftstoffkosten von 1,83 € pro Liter in Deutschland. "Die aktuelle Berechnung basiert auf geschätzten Kraftstoffkosten von 1,83 € pro Liter in Deutschland." |
tesla-motors.0 | 2023-06-09 12:21:11.964 | error | Error: The id "5YJSA7E25HF205349.charge_history.gas_savings.card.info.sections01.paragraphs.Die aktuelle Berechnung basiert auf geschätzten Kraftstoffkosten von 1,83 € pro Liter in Deutschland." is invalid. Ids are not allowed to end in "." |
tesla-motors.0 | 2023-06-09 12:21:11.960 | error | Error: The id "5YJSA7E25HF205349.charge_history.gas_savings.card.info.sections01.paragraphs.Berechnung durch Schätzung des Kostenunterschieds zwischen dem Aufladen Ihres Tesla und den Kraftstoffkosten für ein vergleichbares kraftstoffbetriebenes Fahrzeug in derselben Region." is invalid. Ids are not allowed to end in "." |
tesla-motors.0 | 2023-06-09 12:21:11.960 | error | Error extract keys: 5YJSA7E25HF205349.charge_history.gas_savings.card.info.sections01.paragraphs.Berechnung durch Schätzung des Kostenunterschieds zwischen dem Aufladen Ihres Tesla und den Kraftstoffkosten für ein vergleichbares kraftstoffbetriebenes Fahrzeug in derselben Region. "Berechnung durch Schätzung des Kostenunterschieds zwischen dem Aufladen Ihres Tesla und den Kraftstoffkosten für ein vergleichbares kraftstoffbetriebenes Fahrzeug in derselben Region." |
tesla-motors.0 | 2023-06-09 12:21:11.959 | error | Error: The id "5YJSA7E25HF205349.charge_history.gas_savings.card.info.sections01.paragraphs.Berechnung durch Schätzung des Kostenunterschieds zwischen dem Aufladen Ihres Tesla und den Kraftstoffkosten für ein vergleichbares kraftstoffbetriebenes Fahrzeug in derselben Region." is invalid. Ids are not allowed to end in "." |
`
arbeite in der version 1.3.0 und habe mich nun einige tage gespielt und den adapter einfach nicht zum laufen bekommen. scheint als würde die callback url seit einiger zeit die locales mit übergeben, siehe mein beispielurl:
https://auth.tesla.com/void/callback?**locale=de-DE&**code=xxx&state=xxx&issuer=https%3A%2F%2Fauth.tesla.com%2Foauth2%2Fv3
Nach entfernen der locale funktioniert der adapter
occassionally there is an info message in the log about a wrong data type like:
State value to set for "tesla-motors.0.5YJSA7E25HF205349.charge_history.charging_history_graph.data_points25.Gesamtausgaben.raw_value" has to be type "string" but received type "number"
so i think there is no forced data type while creating the DP and so depending on the value it will be interpreted as string or number.
I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:
Thanks,
your automatic adapter checker.
seit paar Wochen bekomme ich diesen Fehler im LOG:
tesla-motors.0 15379 2023-02-07 09:55:23.450 error General error
tesla-motors.0 15379 2023-02-07 10:00:14.226 error Error: socket hang up
The adapter fails to start on my Raspberry Pi 4.
The tesla adapter is installed in version 1.3.1, ioBroker version 4.0.23, js-controller 4.0.23, nodejs 15.14.0.
The issue is likely caused by the dependency axios-cookiejar-support. The version of this package is ^1.0.1 according to the package.json file, but the latest version 4 possibly fixed the issue. See my ioBroker log:
host.raspi4 | 2022-11-13 19:20:09.037 | error | instance system.adapter.tesla-motors.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
-- | -- | -- | --
host.raspi4 | 2022-11-13 19:20:09.036 | error | Caught by controller[0]: }
host.raspi4 | 2022-11-13 19:20:09.035 | error | Caught by controller[0]: code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
host.raspi4 | 2022-11-13 19:20:09.035 | error | Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/axios-cookiejar-support/lib/index.js:8:40) {
host.raspi4 | 2022-11-13 19:20:09.035 | error | Caught by controller[0]: at require (node:internal/modules/cjs/helpers:92:18)
host.raspi4 | 2022-11-13 19:20:09.034 | error | Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:996:19)
host.raspi4 | 2022-11-13 19:20:09.033 | error | Caught by controller[0]: at Function.Module._load (node:internal/modules/cjs/loader:769:27)
host.raspi4 | 2022-11-13 19:20:09.033 | error | Caught by controller[0]: at Function.Module._resolveFilename (node:internal/modules/cjs/loader:910:27)
host.raspi4 | 2022-11-13 19:20:09.032 | error | Caught by controller[0]: at Function.Module._findPath (node:internal/modules/cjs/loader:513:31)
host.raspi4 | 2022-11-13 19:20:09.032 | error | Caught by controller[0]: at resolveExports (node:internal/modules/cjs/loader:473:36)
host.raspi4 | 2022-11-13 19:20:09.031 | error | Caught by controller[0]: at packageExportsResolve (node:internal/modules/esm/resolve:562:3)
host.raspi4 | 2022-11-13 19:20:09.031 | error | Caught by controller[0]: at throwExportsNotFound (node:internal/modules/esm/resolve:337:9)
host.raspi4 | 2022-11-13 19:20:09.030 | error | Caught by controller[0]: at new NodeError (node:internal/errors:329:5)
host.raspi4 | 2022-11-13 19:20:09.030 | error | Caught by controller[0]: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/defaults' is not defined by "exports" in /opt/iobroker/node_modules/axios/package.json
host.raspi4 | 2022-11-13 19:20:09.029 | error | Caught by controller[0]: ^
host.raspi4 | 2022-11-13 19:20:09.028 | error | Caught by controller[0]: throw e;
host.raspi4 | 2022-11-13 19:20:09.028 | error | Caught by controller[0]: node:internal/modules/cjs/loader:479
I wonder whether I’m doing anything wrong as no one else reported the issue yet.
Für das Token Refresh Intervall wird aktuell das Feld "expire_time" von der letzten Token Abfrage verwendet. Das kann dazu führen, dass Requests, die zum Zeitpunkt dieses Token Refreshs ausgeführt werden, dies ggf. mit einem abgelaufenen Tokens tun.
Daher sollte ein zeitlicher Puffer eingebaut werden, z.B.
(expire_time - 30) * 1000
Version: stable=0.5.2 (133 days old) => latest=1.0.6 (15 days old)
Installs: stable=186 (40.26%), latest=91 (19.7%), total=462
Click to edit
Nutze aktuell die Version 1.0.7 mit 1 Fahrzeug & 1 PW2 Gateway
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.