Closed Mangomc closed 11 months ago
Hello, if this is a temporary log message don't worry it is well managed. You should have this only at restart. I don't understant the 75000 log messages. This should have only one or two. If not, you may have a problem on your side.
This is warning log and not error if I remember well.
There is already a tempo because VTherm waits that HA is totally started to start searching for the underlying climate. This means HA is started but not connected to the broker and I guess this is not how its works.
I'm seeing this error (it's not warning but error) about 60 times on each startup, as a thread network needs a few minutes to make all devices available to HA.
I will change this to a Warning level as it is only a warning if it is temporary. But this can be also a misconfiguration if this persists.
I reinstalled my HA today because everything was crashing and HA rebooted all the time on its own. Now the 75.000 log entries are gone :D Now only a few. 2-10. Sorry for the report. I will Mark it as resolved. Thanks for the Quick Support
Hey. Im using your Integration to control my climate device. But whenever i restart my home Assistant the whole System gets unresponsive for a while because its spamming the anove error into my log. 75.105 Times the same error
Cannot find the underlying climate entity. The error comes because it takes a while for HA to connect to the mqtt Broker and list all devices.
Maybe u can add a Pause of 30secs or something and try then again to Start the integration
Thanks in advance