Skip to content
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

ESPNow gateway: outstanding issues #116

Open
peterhinch opened this issue Jul 7, 2023 · 0 comments
Open

ESPNow gateway: outstanding issues #116

peterhinch opened this issue Jul 7, 2023 · 0 comments

Comments

@peterhinch
Copy link
Owner

peterhinch commented Jul 7, 2023

@glenn20 I have pushed an update that supports ESP8266. This aspect works in my testing. I'd appreciate feedback on the following.
[EDIT]

Port scanning (nodes)

This is now working on my PC but the code needs refining.

Error reporting (gateway)

Now implemented by publishing to a user-definable topic.

ESPNow message send integrity (gateway and nodes)

Currently the gateway implements the ACK mechanism to enable node publications to meet the qos==1 guarantee. This is predicated on the assumption that ESPNow.send() might return success when it has in fact failed. It is possible that, when sync==True, this condition cannot occur and that the node will always "know" if a send had succeeded. It would be good to lose ACK. What is your view?

Encryption

I haven't studied this in detail but it's on my todo list. I don't foresee any particular problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant