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

Upgrade Adafruit_MPR121 library #684

Closed
TD-er opened this issue Jan 7, 2018 · 1 comment
Closed

Upgrade Adafruit_MPR121 library #684

TD-er opened this issue Jan 7, 2018 · 1 comment
Labels
Category: Plugin Related to supported sensors Type: Bug Considered a bug
Milestone

Comments

@TD-er
Copy link
Member

TD-er commented Jan 7, 2018

Where setThreshholds() is being used, the compiler gives "deprecated" warnings.

lib/Adafruit_MPR121/Adafruit_MPR121.cpp: In member function 'boolean Adafruit_MPR121::begin(uint8_t)':
lib/Adafruit_MPR121/Adafruit_MPR121.cpp:43:23: warning: 'void Adafruit_MPR121::setThreshholds(uint8_t, uint8_t)' is deprecated (declared at lib/Adafruit_MPR121/Adafruit_MPR121.h:87) [-Wdeprecated-declarations]
setThreshholds(12, 6);

Travis CI marks these warnings as error.

@Grovkillen Grovkillen added Type: Bug Considered a bug Category: Plugin Related to supported sensors labels Jan 8, 2018
@Grovkillen Grovkillen added this to the 2.0.0 milestone Jan 8, 2018
@psy0rz
Copy link
Member

psy0rz commented Jan 10, 2018

Those errors are actually errors that your struct initialisation code is triggering in cpp check. (i left a comment about this on the pull request i think:)

Only warnings in our own code are treated as errors, here's an example of a successfull build with those same ada fruit errors: https://travis-ci.org/letscontrolit/ESPEasy/builds/324883515

Warnings in libs are ignored most of the time. I only added a pragma-workaround in P065.

Nevertheless the deprecation warning should be fixed. :)

@psy0rz psy0rz closed this as completed Jan 10, 2018
psy0rz pushed a commit that referenced this issue Jan 10, 2018
* [switch] Fixed switch behavior and default settings. (#675)

As described in #673 .
The problem was partly related to the default values stored in flash ("0"), which was not a valid value for the switch type.

When upgrading from an older version of ESPeasy, make sure to check the switch type (normal switch or dimmer) and save the settings for the switch device again, even when nothing was changed.
Default configuration and new added switches will now work like intended.

When a controller is enabled (e.g. Domoticz MQTT or -HTTP) and the button is pressed multiple times, the ESP may reboot. See issue #674.

* ABC calibration feature added (#606)

* [Flash info] Detailed flash information (#678)

Last few days a number of issues and forum topic was about the type of flash used on the ESP boards.

This is an extension of the detailed information page.

Perhaps also merge with the newer and more clear layout of pull request #624?
That pull request was only merged to the mega branch.
I kept the changes local, but perhaps they should be placed in the "Storage" section introduced with #624.
Maybe also that pull request should get merged into the v2.0 branch.

* Bugfix/v2.0 crash switch (#682)

* [crashes] Added constructors to initialize all members in structs

Numerous structs are defined, but none of them have default constructors and there is no guarantee the members will be set when used. 
With these default constructors, the parameters at least have an initialized value.

* [PubSubClient] Add bound checks on the internal buffer

Not sure if this was really causing an issue, but proper bound checks are always a good thing.

* [Crash Switch] Disabled delayBackground and added yield() calls

Something really fishy is going on with the delayBackground function, which will result in crashes when pressing the switch multiple times, with Domoticz MQTT enabled as first controller.
Disabled for now and delay(1) added to give background tasks a chance to do their work and make sure the watchdog doesn't perform a reset.

* [CI build errors] Commented out some unused variables

Travis considers them as error and fails the checks.

* [CI check] Out-of-bounds check fix

* actually ignore MQTT messages that are too big.

* moved mqtt stuff outside of backgroundtasks(). fixes #683 in my test scenario

* [Adafruit MPR121] Change deprecated name setThreshholds to setThresholds (#685)

See #684

* fixed plugin id of "Communication - Kamstrup Multical 401". (accidental octal notation)

* changed devicecombobox handling to save a lot of memory on device page. fixes #654 #676 and could be triggered by #683 in some cases.

* [CPPcheck] v2.0 ControllerSettingsStruct some variables not initialized (#692)

Fixing these cppcheck errors:
101.43s$ cppcheck --enable=warning src/*.ino -q --force -I src --include=src/ESPEasy.ino --error-exitcode=1
[src/ESPEasy.ino:500]: (warning) Member variable 'ControllerSettingsStruct::HostName' is not initialized in the constructor.
[src/ESPEasy.ino:500]: (warning) Member variable 'ControllerSettingsStruct::Publish' is not initialized in the constructor.
[src/ESPEasy.ino:500]: (warning) Member variable 'ControllerSettingsStruct::Subscribe' is not initialized in the constructor.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Plugin Related to supported sensors Type: Bug Considered a bug
Projects
None yet
Development

No branches or pull requests

3 participants