pkuehnel
pkuehnel
@mkindahl I am using the container with `docker-compose up -d`. The docker-compose.yml looks like that: ``` services: database: image: timescale/timescaledb:latest-pg12 deploy: resources: limits: memory: 200M logging: driver: "json-file" options: max-file:...
1. Initial data is correct (when creating the aggregate), manual refresh does work (at least no error message). 2. I do not get any error when executing Begin, Delete, Rollback....
Ok, new test: I tried: ``` begin; CALL refresh_continuous_aggregate('tasmotalogs_summary_hourly', '2021-09-09', '2021-11-16'); commit; ``` Got the warning, that there is no transaction in progress and no updates in the continuous aggregate....
Can I help you anyhow? I could send you my whole container including all files. There is nothing private in the database.
Or do you have any ideas how I can resolve that issue?
As I am not that deep into timescaleDb I do not want to invest more time on this issue. As workaround I created a cronjob on my Docker host executing...
I got rid of Teslamateapi and implemented the new fleet api by myself (at least what I need), see [here](https://github.com/pkuehnel/TeslaSolarCharger/blob/master/TeslaSolarCharger/Server/Services/TeslaFleetApiService.cs) I created a Dev Account at Tesla as well and...
> The car will not sleep if an application (Tesla app, TeslaMate, other third-party Tesla loggers) are polling the car. This has been the case for years, but not anymore....
What I noticed is that TeslaMate is a bit freaking out, probably because it does not expect the car to go to sleep: ``` 2024-01-30 15:46:26.019 [info] Sent 200 in...
Yes. As I said, this only occurs when there is something wrong with the streaming API on drive/charge start. But your question has nothing to do with my issue. The...