You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The VitoWiFi library has been dormant for quite a while with no new updates nor bugfixes. Now I'm again working on the library with a new version. It will be simplified but radically different.
I understand that a new version will, while the current version is not even merged, again require a lot of work to integrate. But I still want to ask for input on how the API can be made "ESPHome-friendly".
Does it need to be blocking/non-blocking? Event driven?
Are only ESPxxxx devices targeted (with the Arduino framework)?
Any specifics on configuration?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I see there is interest in integrating Optolink/VitoWiFi (https://github.com/bertmelis/VitoWiFi) into ESPHome, as in this PR: #4453
The VitoWiFi library has been dormant for quite a while with no new updates nor bugfixes. Now I'm again working on the library with a new version. It will be simplified but radically different.
I understand that a new version will, while the current version is not even merged, again require a lot of work to integrate. But I still want to ask for input on how the API can be made "ESPHome-friendly".
Does it need to be blocking/non-blocking? Event driven?
Are only ESPxxxx devices targeted (with the Arduino framework)?
Any specifics on configuration?
I'd love to hear your thoughts.
Beta Was this translation helpful? Give feedback.
All reactions