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
FIRMATA WIFI ESP8266 #12
Comments
There is not currently. I would like to add it — perhaps over the summer — but graduate school has made development on this slow. I would also love a PR for this. hint, hint |
Any progress? I would also really want to control it from wifi or lan or bluettooth whatever is the easiest for you. |
this project is kinda dead, you could try to use something like p5.dom and johnny five. It would be a bit harder but that's the way it is |
Yes, I am pretty taken with other things these days. PRs welcome, tho. |
i did a little bit of research and it seems like the only thing we need to do is to use etherport.
That should be all we need to do, appart from making a way to select one of the two edit: the etherport is saying it does only support ethernet but according to firmata.js it isn't |
i don't know how johnny-five code is related to normal firmata but maybe we can also do it like this:
|
i will try to test it myself once i have an esp2866 but that will take some time. |
this should do the trick but we need to add a dependency for etherport and we need a good way to change between serial and wifi. |
are you okay with a comment "do this do enable wifi" or do you want a dedicated setting for the server? edit: if normal etherport doesn't work i/you should try etherport-client |
Thanks for looking into all this! I think it would be better to let people toggle between wifi and serialport with an optional flag. Once you have a chance to test that it works, open the PR and I can merge and update the new version on npm? |
hey there, is there a way to use this library with esp8266 running wifi firmata? I mean not using serial but instead use etherport client?
The text was updated successfully, but these errors were encountered: