make sure we don't just hope that pointer logic works

some swserial migrations
also make sure we use pstrs

simplify the internals and allow to use multiple instances

possibly fix comparison issue with raw int vs. float, when checking for
errors. division may not actually succeed

migrate to the new structure

stronger time types, overrides

init underlying lib object as a member
this might be changed to unique_ptr, in case we really want begin() to
be idempotent and being able to re-init things
(which might not be actually possible?)

structure, overrides, strong time types

actually use the analog sensor base to read
(and fixing yet another pinmode accident)

fixed structure, overrides. strong time types

updated structure, overrides. strong time type
testing timesource changes. this should work, but might need to tweak
things if it starts to fail b/c of flash code loads

conversion is not working for signed ints, only unsigned

do not force to implement constructor, just update vtable
continue testing with bme280 class, update structure

make sure there's an option for direct address setup
sensor updates are wip, since base sensor code is also changing

use bitset when locking, avoid manual index & mask calculation
update check() to use boolean logic instead of returning int status
remove wip address-range, just use the {begin, end} pair
uint8_t instead of unsigned char when dealing with data

Avoid confusion between ref and pointer when looping over sensors
Re-use helper class in the magnitude object as well

Remove custom code related to filter movement, just use unique_ptr
Plus, updates filter code to use stl vector where possible

Experimening with dynamic cls id. Perhaps this should be something
else... but, at least there are no longer any header-defined values.

preemptive fix for the issue resolved in the 3.1.0

As mentioned in the #2491
Hides parent element when these groups are empty

IKEA Vindriktning Air Quality Sensor
https://www.ikea.com/gb/en/p/vindriktning-air-quality-sensor-80515910/

Added support for Itead Sonoff POW R3 (https://itead.cc/product/sonoff-powr3/)

This device is essentially the same as the POW R2, except:
- the relay is a normally closed type,
- the current and power ratings of the device are higher.

fixes #2491

While I am still hesitant to call this an improvement,
at least this makes part of the installation slightly faster

since it won't decide between String and StringView,
manually direct it to the StringView

also normalize token values of particle measurements

Bumps [minimist](https://github.com/substack/minimist) from 1.2.5 to 1.2.6.
- [Release notes](https://github.com/substack/minimist/releases)
- [Commits](https://github.com/substack/minimist/compare/1.2.5...1.2.6)

---
updated-dependencies:
- dependency-name: minimist
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

clangd does not like integer SUPPORT flags and `||`

amends e51e259f02
fixing incorrect conversion from kelvin, and also add full
conversion from possible farenheit source (if that ever happens)

experimenting with the idea of unit conversion... while a table-like
approach will work and will be slightly shorter, it would not have the
specific type checks and constexpr still does not play well with lambdas

plus, any conversion function referenced as a pointer will not really
be a constexpr (...and still require c++17 to work correctly when iterating)

cursor no longer calculates 'offset' but stores the absolute position
this also helps not introducing that specific math to the outside code

more const-correctness fixes and general accessors instead of plain structs
access and modification, where specific ctor or helper method should've
been used instead

Restore behaviour from dd12251e43
7ba1283024 unintentionally removed it
Instead of reverting to the 'atof' code, just use the provided string
as-is via RawJson (aka `serialized()` in the v6)

Note that the old approach may have caused some silent data loss b/c the
data could have been stored in 'double' or 'u64', where the ArduinoJson
only stores 'u32' and 'float' in it's internal buffer and does not (really)
warn us about any type incompatibilities.
(at least by default. but, the alternative is to store all floating point
numbers as 'double' internally, see ArduinoJson/Configuration.hpp)

resolves #2503