-
Notifications
You must be signed in to change notification settings - Fork 21
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
Move Arduino code to platformIO based projects #136
Comments
I have no problem with platform io. I use it for other projects and agree with your comments |
@TylerReedMC I think we should add @ozarchie as member, so if needed we could tag his as reviewer. |
The arduino code was stable, and I can compare and test the revised PlatformIO on my system. Although I prefer more modular than monolithic block approach to the code, I will leave the PlatformIO code as you have coded. The final issues really related to integration with the Python code. |
@ozarchie Just to avoid confusion, the code in the hapifirmware folder is not equivalent to the one in hapinode. These seemed to be two different code bases, with hapifirmware being significantly smaller functionality wise. Is there a reason for the split between hapifirmware and hapinode? What I did was move the code in |
The hapifirmware codebase is based on an early implementation of the system, using a proprietary protocol and usb connection. The hapinode code was developed for mqtt and wireless. |
Cool and good to know 🙂 |
The reason's I would be interested in moving to PlatformIO projects is:
Other reasons include:
I have already converted the hapifirmware source code to the PlatformIO format so that it can be tested. Installation instructions can be found in the folder itself.
The text was updated successfully, but these errors were encountered: