Some entities returning showing incorrect data while others correctly updating #398
-
I am opening a discussion rather than a bug because I'd like to know how to gather reliable data to troubleshoot this - is this the addon holding incorrect states or the API handing out garbage data. I do not want to waste ekutner's time. My have a long running issue (currently on 1.1.7 but has existed for some time previously) where during a cycle, some sensor elements seem to get stuck on incorrect data. The device is a WAX32K41AU washing machine. The attached image is a screenshot of the history of 4 different loads over a weekend. On the first load the top line Prior to wash 1 - idos1 is shown as off from 12:06 (arguably it's on as it's selected) How do I gather the data to troubleshoot this as the debug button has been removed. Thank you. Edit: Better image with sensor labels more visible. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
I appreciate the effort to avoid opening an issue but in this case it's not clear to me if this is a bug in the integration or HC. Please open an issue and attach a debug log with Log Level 7 (check the README) and specify the time of relevant events, like you did here. |
Beta Was this translation helpful? Give feedback.
-
Brief update, I will upload some debug logs and overview when I have a chance however key points:
Co-incidentally - I received my first 'washing machine software update' notification - which did and it updated 'version' 3.4125-2.10.1.13125 (3.0) to (3.4125-2.15.1.13325 (3.0). The next 3 cycles, idos and speedperfect were correct. However I noticed that temperature was incorrect for one of two cycles (cold instead of 40c). |
Beta Was this translation helpful? Give feedback.
-
So the current status is that this issue is a HC problem of reporting the wrong values? |
Beta Was this translation helpful? Give feedback.
I appreciate the effort to avoid opening an issue but in this case it's not clear to me if this is a bug in the integration or HC. Please open an issue and attach a debug log with Log Level 7 (check the README) and specify the time of relevant events, like you did here.