Skip to content

Refactoring ArduinoIoTCloud #109

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

Merged
merged 54 commits into from
Apr 8, 2020

Conversation

aentinger
Copy link
Contributor

Over the course of the ArduinoIoTCloud development a lot of clutter has gathered which makes it more difficult to use the existing code base to add something new on top (technical debt). This PR is touching many areas of the code but still tries to keep atomic commits as much as possible.

…nt has been assigned a valid value - it should have the NULL value assigned at object construction
…in method to dedicated util class CryptoUtil for better readability
…uctCertificate' which allows for a similiar check/control flow in 'ArduinoIoTCloud::begin'
…loudTCP' since its not needed for LoRa boards
…irtual functions within the ArduinoIoTCloud base class

There is no need for this since the communication mechanism is different for TCP enabled and LoRa based boards.
Removing of both writeStdout and writeShadowOut since they are not required for LoRa boards (there isn't even MQTT in play)
…ClientBegin to begin which makes puts the change closer to where it actually matters
…method since they share most of the code except for a topic parameter which is an additional parameter to the new function 'write'
…TCP' since its not needed for 'ArduinoIoTCloudLPWAN'
@arduino-libraries arduino-libraries deleted a comment from TravisBuddy Mar 31, 2020
…nt since there is no need for the constant to be public
…erver like the TCP based boards do. Instead we only have a connection to the gateway and no control wether or not this connection extends to cloud. Therefore checking the connection to the gateway is the only thing we can do.
…cur on the board (e.g. connecting -> connected)
…an't know if there really is a connection to the cloud since this is conceptually impossible if we have only a connection to the gateway
@aentinger aentinger marked this pull request as ready for review April 1, 2020 08:46
@aentinger
Copy link
Contributor Author

Successfully tested on PROD with

  • MKR WAN 1310 ✔️
  • MKR GSM 1400 ✔️
  • MKR 1000 ✔️
  • MKR WiFi 1010 ✔️
  • ESP8266 ✔️

@AlbyIanna

  • Can you please test with MKR WAN 1300/1310 and MKR NB 1500?
  • Since this changes contains the changes of PR Refactor cryptologic initialisation code #108 it would be sufficient to check this PR and not check the old one. FYI: Since Provisioning.ino has been modified can you please check if the getting started process still works at it should (it should, but checking can't hurt).

@aentinger
Copy link
Contributor Author

@Rocketct can you please test this PR with MKR NB 1500?

@Rocketct
Copy link

Rocketct commented Apr 6, 2020

@aentinger yes 'l ask to our colleague in Malmo and report as as soon as we will get some results

@Rocketct
Copy link

Rocketct commented Apr 7, 2020

@aentinger our colleague test it and works properly, he test the things creation and data exchange between cloud and NB ad all works fine

@aentinger
Copy link
Contributor Author

@Rocketct Thank you very much 👍

@aentinger aentinger merged commit 2d60fea into master Apr 8, 2020
@aentinger aentinger deleted the add-formatting-elements-for-better-readability branch April 8, 2020 04:29
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

Successfully merging this pull request may close these issues.

2 participants