-
-
Notifications
You must be signed in to change notification settings - Fork 113
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
ESPHome functionality #50
Comments
I also found a similar request going the other way. Not sure where the best place for this request should be. |
I don't know ESPHome. Are you creating a sketch when working with ESPHome ? |
ESPHome is a declarative framework for programing ESP32 and ESP8266 dev boards |
Can you import libraries ? |
I do not know for sure but depending on what you declare in the YAML config I believe this happens during the compile process before upload. |
I will have a look at their documentation, if they don't allow third party libraries, there is not much I will able to do |
ESPHome does allow importing external components using the 'external' component: @thelastoutpostworkshop : Would be great if I knew what to import. I am willing to test this and contribute to documenting. T. |
Thanks a lot for the info and sure I will need help for testing. |
It looks like the source needs to be rearrange in a specific format to allow ESPHome to import such a 'component', as per: Perhaps core developers of ESPHome are willing to contribute turning GPIOViewer into such a component. Fingers crossed |
Yes and some people open issues on it, on the ESPHome repository |
It appears, that IDF is needed for ESPHome, currently GPIOViewer library is based on the Arduino Framework. So a port to IDF is needed, I do not know at this point the amount of work this port will required. |
If i'd only knew what this means, but it seems possible to create a arduino based library as component in IDF. At least, that is what it looks like they done here: Perhaps a similar method can be used here ?? |
Thanks I will look into it |
Yes, you can. |
So, is it possible to use GPIO Viewer with ESPHome? |
I think so, if someone wants to submit PRs for it, you are welcomed. |
First, this is an awesome capability. |
Nobody submitted PRs for this yet, your are welcome to contribute. |
Going to give it a go, but got to get up to speed on ESPHome component development and then off to the races. |
Thanks, I do not know how much of a learning curve it is. |
I really like this functionality and I really hope someone makes it come to pass. Not much good on coding mysel sadly 🤔 |
+1 |
1 similar comment
+1 |
wow this would be so helpful |
Yes, GPIOViewer in ESPHome would be a perfect addition! |
This looks great, just found it and am also interested in the possibility with ESPHome. In the meantime, for a particular problem I’m having, I was thinking I’d temporarily re-flash the affected device. It’s not like the config for that device will go away in ESPHome. |
I was able to add this to ESPHome.
However, I don’t think this results in the “#include” being set and the Web server running on port 8080. I may be wrong, as the ESPHome device I was testing already had a Web server on port 80. (This also meant it had the other required libraries installed.) |
So you have this addon working in esphome just with 4 lines of code only? |
This example works only with inpit pins https://github.com/dvb6666/esphome-components/blob/main/examples/test-gpio-viewer.yaml |
Would it be possible to enable this within the ESPHome project?
https://www.esphome.io/
The text was updated successfully, but these errors were encountered: