-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unknown entity state after restart. #55
Comments
Thank you for asking this question. I have got the same problem. I think I know what the problem is and that currently there is no solution in this code. As I understand that comfoair-esp32 just listens for messages on the can-bus. The ventilation unit only sends the values when they change. A quick "fix" would be to restart the ventilation unit or you wait until the value changes... While writing this comment there is currently the possibility to send raw hex commands like described below. But a real solution would be that the esp32 could ask the ventilation unit for some/all sensor values like described here:
The ESP could know that there are unknown values and ask specific for these or it could ask for all values. |
Same here; + 1 on this issue. |
Hi, I was wondering if this issue has already been addressed by someone? If so, would you mind to share? Thanks |
Hey all, as far as I know nobody addressed this. tbh i still struggle to understand the usecase of this. I've mine up and running for weeks and apart from esphome updates my esp32 never reboots... maybe some of you cuts power to their VMC unit? |
Can u guys let me know if this is working for u? |
Where is the PDOID list? |
https://github.com/vekexasia/comfoair-esp32/blob/master/components/comfoair/__init__.py#L26 Also can u please take a look @ #74 I am trying to build a compatibility list |
Hello, I have a question about the entity state after ESP reset. All entities are in an unknown state until they are replaced or updated. Is there any way to make entities show their current state after a reset/update?
The text was updated successfully, but these errors were encountered: