Closed snipah closed 1 year ago
Thanks for the logs. I am looking into the issue. It appears that logging is a blocking operation. So when a log is send via Wifi it takes too long. And the Lin listener is using an interrupt which than takes too long.
I developed and tested only via USB connection which has no issue.
I should have an update in a day or two.
Hi, I have uploaded a new version which should fix this issue. Can you please test again?
I have the feeling, that once I activate logging, the connection breaks. If I deactivate logging, everything works without problems. But I just tested the Truma part. Will keep on testing.
Try setting refresh on the component to ensure you have the latest version e.g.
- source: github://Fabian-Schmidt/esphome-truma_inetbox
components: ["truma_inetbox", "uart"]
refresh: always
Thanks!
Hi Fabian,
Just switched from inetbox2mqtt to your implementation because I prefer the hassle free config/update-procedure via Wireguard from everywhere! Everything is working as expected! Thanks for your great work!
I understood, that I might be able to run your Truma and Victon-Implmentation on one ESP! I currently have https://github.com/KinDR007/VictronMPPT-ESPHOME running on a separate 8266 for a Shunt and Smart Solar. Can I run the victrun-stuff to the same ESP your Truma-implementation is running on?
I expanded my Truma.yaml-file with the Victron-config. Truma is working initially but does the ESP even connect to the Victron-devices via BLE? Not sure... and then everything crashes... see log below.
Is it due to memory constraints? Am I doing something wrong?
and the ESP starts up fine and connects to Home Assistant but then throws and error and disconnects...