I added some updates
- logging should be fixed now
- you can select rolling average for graphs
- you can reorder the tiles for the current statistics via drag and drop (I might add an edit button later)

Yeah, I noticed that too. I'll take a look at it when I can find some time.

Yeah, I had it on the settings page but then moved it to the logs page. Felt more useful to have it right there.

Changes are added. I also optimized the logging method; it shouldnt hang anymore.

You can change the log level only in the yaml directly at the moment. I'll add a fastAPI hook to allow setting it from the settings page.

That looks like a nice setup. I'll see if I can add some information to the readme.

Code updated, you should now be able to trigger a data pull via mqtt. Set the payload in the lua script to:

Yeah, that shouldn't be too hard. I'll add that.

Code changes are added now. You can now change the settings using MQTT. The Example is updated in the readme.
You can send messages to the basetopic + /command (by default: mytoyota/command)

I added the code, but want to do some more refactoring before I push the changes. Something this weekend.

Good idea, didn't think about that option. Ill have a look at it.

Making a domoticz only plugin would remove a lot of functionality I was looking for when I created the dashboard. The current method offers a lot of flexibility how to integrate and use it with domoticz or other automation systems.

Ah, thanks for clarification. I'll add that option.

Any ideas about how this will function?


The feature is added now.
you can use curl to create the POST request for testing and you can find an example lua script in the readme to trigger it in Domoticz when a specific event occurs.

The ...

My plan is to add the option to change settings via http post requests. Then you can have domoticz change the polling interval whenever needed.

It works on my iphone and the the python backend, but not my Android phone. I updated Android 16 QPR2 Beta 1, maybe it's related to that.

Same here. Can't login through the app.

Ah, thanks for clarification. I'll add that option.

That's not a problem at all. I have that on my to-do list.

Not sure how feasible a dynamic polling interval for the battery charging is, as we don't know when you are charging, but I'll add it and you can see if it works for you.

That's interesting, for me the app is usually is correct.
But I noticed that pytoyoda sometimes doesn't return a true or false, but a none, and it's not consistent if the none is open or closed. It should look like this (locked is actually none, but I added logic to set the status to closed if the ...

Depending on your server you night have to wait 10 seconds or so until it connects to the log stream. I haven't had the time up optimize that part. You could also run the server outside the docker, then you get the logs in the terminal.