Esphome component related updates #274
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As the title says - my esphome component allows for ethernet connectivity as well, therefore I propose the following rework.
Mostly just renaming from wifi to network and add ethernet logic & symbol.
Also, display backlight value was added to response-content and I changed default baud to 19200 after intensive changes (please just deny that change of course if you dont agree)
Removed the status code change and rather changed my esphome component to be fully backwards compatible, no need to reflash if someone doesnt need display backlight in query response etc.
Esphome component finished now as well, last remaining point is to create a nice HA custom card
ESPHome component features:
to read fw bin file from
As esphome can deal with ethernet/wifi + mqtt + api connections (ha & custom) -> these features are automatically available as well when replacing the esp8266 wifi-serial- proxy with an esphome based device using my opendps component
Hope this helps =)