Timed out waiting for command: TT, value: 14.0. #11
Comments
|
Thanks for the report.
From the logs, it looks like there's an issue with the message processing task. The fact that the queue size decreased in size halfway through indicates that the queue processing task is still running. It seems to be blocked most of the time though. This does not necessarily mean that the problem lies with pyotgw or the OpenTherm Gateway integration in Home Assistant. If you're willing to tinker a bit to find the issue, the first thing you could try is to disable all other integrations to see if the problem persists. If it does, post another debug log of all components, not just To make your own life a bit easier, you can make a backup of your config dir (and database if separate) first to restore later. |
|
Thanks for the fast response!
I am definitely willing to help to debug this and tinker. I will try to run everything on a different HA installation where I do not have any integrations tonight! |
|
@mvn23, I have moved the integration to a Hass.io, RPi 3, without any other integrations running. I am still experiencing many problems. For example from the HA UI logs: Then the full log can be found here. I don't know how to proceed. I have also found this post on the community forum, which might be a related problem. |
|
The main issue now is that there are a lot of connection drops/interruptions |
|
The only thing I had running on that RPi3 was https://www.home-assistant.io/integrations/dsmr/ which uses I have another Pi on which I can try to install HA without anything else. I will do that tonight to see if I can learn anything more. I am relatively sure it's a software issue. After I restart HA, the |
|
I've uploaded my log here BTW. |
|
The command timeout defaults to 3 seconds. This should be enough, but for testing purposes you could try to increase it a bit. The easiest way to change it globally would be to increase the |
|
I do have problems, no matter where I run the integration. I have set up a completely new Home Assistant install (former Hass.io) on a RPi3. I am now trying to install the Thanks a lot for helping! |
|
Using a completely fresh HA install with only I have doubled Here are the log-files, I wish I would know where to start. I did get and once. |
|
Have you check the ping/signal strenght of the gateway? |
|
I do not think it's related to the signal's strength. I am currently trying @mvn23, I don't think I am the only one experiencing these problems, this (in Dutch) person has a similar setup to mine and has the same problems. He fixed it by going to the following route "OTGW -> OTMonitor -> OTMonitor MQTT -> MQTT Broker -> HA" instead of the default integration. |
I expected as much. Messages seem to actually get lost somewhere. We will have to analyze network traffic to find out where exactly.
I've seen this in logs before, but my own setup does not have these messages (maybe not supported by my boiler). It's unrelated to the timeouts and I expect it's a way to communicate the fact that the boiler's power mode has changed. Could you test and verify this? Then we can implement these messages as well.
There have indeed been similar reports in the past. So far I've never been able to reproduce, but it always seems to be related to WiFi versions of the gateway (or WiFi somewhere else in the link). However, even with WiFi, any failed transmissions/missing packets should normally be corrected on the TCP level. I will hook up a NodeMCU to my gateway this afternoon and run a Home Assistant instance on a raspberry pi to see if I can reproduce. Are there any specific steps I could take to trigger the issue? |
|
The otmonitor tool reports that it has 0 errors, so I have the impression that it doesn't encounter them. Unless it silently corrects errors. To get the errors I don't do anything else than changing the set temperature a few times and waiting. |
|
What firmware do you use on the NodeMCU? I am using The setup I use for testing is a raspberry pi 2B (raspbian, venv, default config with only |
|
It has been running like above for 20 hours now. In the mean time I have changed the temperature several times, both from HA and from the thermostat. |
|
I have made a HassIO add-on with However, I do prefer the native implementation. Since I have no connection errors at all using |
|
Unfortunately, I am not able to upgrade my R147 firmware to the I (believe) I would have to take the NodeMCU out of its case and do it via a cable which I do not have the time for ATM (including the hours of debugging a faulty upgrade). |
|
The earliest opportunity for me to try R147 is next weekend. In the mean time I will look into more debugging output when a connection reset is triggered. |
|
Latest master should give some more insight in the state of the serial connection when a reconnect is triggered. |
|
Just tested ESPEasy R147 and I do indeed see erratic behavior on there as well. I suggest you try the |
|
Oh, that's great news, thanks a lot for trying! I will try it ASAP and report back 👍 |
|
I have just installed I wasn't 100% sure about the settings for my NodeMCU, but this is what I have done. I did get this error twice: |
This is probably caused by the serial log messages from ESPEasy. Try setting |
|
That indeed seemed to have fixed it! 👍 I will try it out for a few days and then hopefully close this issue. |
|
I did get these error messages since yesterday: |
|
Can you provide a debug log of errors like that? From your screenshot it looks like some data gets lost somewhere. |
Got it, they probably don't affect each other then. Thanks for the log. It looks like all commands after |
|
Unfortunately, the original error started happening again (consistently). With logs http://files.nijho.lt/home-assistant-errors-again.log Could you perhaps tell me how to use |
Where is the network interface you're using to communicate with the gateway, the gateway ip and the gateway port for serial traffic. The dump will be placed in your working directory as To analyze the dump, you can either use |
|
The last response is now almost 1 year ago and there have been a few new releases since this issue was filed. Please file another bug report if you're still experiencing this issue with the latest release. |
|
Unfortunately, I never got it to work properly, so instead I am using the official For convenience, I have created a Home Assistant Supervisor Add-on: https://github.com/basnijholt/addon-otmonitor |
|
Kind of offtopic, but I've migrated OTGW integration from direct connection to OTGW->otmonitor addon->gateway and I like it. |
I keep getting the following error in HA
0.104:This is when setting the temperature to 14, which doesn't happen.
This is proceeded by the following (large, sorry) excerpt of my log
click here to expand the log
Not sure how to debug this. Could you perhaps give me some suggestions?
The text was updated successfully, but these errors were encountered: