* Correct things definition in README.md
Add example of bridge and link thing to bridge.
---------
Signed-off-by: aliijm <44173819+aliijm@users.noreply.github.com>
* [mqtt.espmilighthub] use system channel types for color temp and brightness
closes#10096
also add absolute color temp channel. and remove level channel when we
already have a color channel (you can link a DimmerItem to a color
channel if your light doesn't happen to have color or you want direct
control of brightness only for some reason)
---------
Signed-off-by: Cody Cutrer <cody@cutrer.us>
* [mqtt.homeassistant] add support for Update component
This component is fairly non-standard - it doesn't add any channels.
Instead, it provides several properties to the thing, and also adds
a thing configuration allowing you to trigger an OTA update on a
Home Assistant device from MainUI.
---------
Signed-off-by: Cody Cutrer <cody@cutrer.us>
* [mybmw] fix not working binding due to API update
to make it work the code has been refactored and due to API changes some
improvements could be made. These include:
- (improvement) fingerprint generation: You can
take a look at the README how to create a
fingerprint more conveniently.
- (change) changed channel: charge-info has been
renamed to charge-remaining
- (improvement) added channels:
estimated-fuel-l-100km and estimated-fuel-mpg
which calculates the estimated fuel consumption
based on the range and remaining fuel liters
- unfortunately such a calculation is not available
for EVs as there is no information about the capacity of the battery.
- (improvement) added channel last-fetched:
the last-updated timestamp is showing by when
the last update of the vehicle happened. As right
now you can not see from the channels if a thing
is offline due to connection issues, you can check
now if last-fetched is more than 5 minutes ago to identify an issue
- (fixed) remote command typos fixed
Fixes#14065
Also-by: Mark Herwege <mark.herwege@telenet.be>
Signed-off-by: Martin Grassl <martin.grassl@digital-filestore.de>
* Add support for garage door transition status
Homekit requires a status for the garage door of OPEN, CLOSED, CLOSING,
OPENING. In order to report that, we must provide state transition
information. State transition information is inferred when the garage
door state is changed. For door_transition_time_seconds since the last
open/close command was issued, the binding reports the state as either
"closing" or "opening".
---------
Signed-off-by: Tim Harper <timcharper@gmail.com>
Co-authored-by: Laurent Garnier <lg.hc@free.fr>
* [knx] New modifier to set mainGA write-only
Co-authored-by: Florian Hotze <florianh_dev@icloud.com>
Signed-off-by: Holger Friedrich <mail@holger-friedrich.de>
* [mqtt.homeassistant] improve Cover support
* Add support for covers that report position
* Handle when command and state values for OPEN/CLOSE/STOP
differ (as they do by default)
* Expose the full cover state, since it can have tell you
if the cover is moving or not
* Handle covers that have a position only, but not a state
* add constants to clarify up/down values
* Be sure to parse percents from strings in RollshutterValue
---------
Signed-off-by: Cody Cutrer <cody@cutrer.us>
* [boschshc] Add support for motion detector illuminance sensor
- add channel and corresponding channel type
- add update description
- add state model
- implement service and handler
- add documentation
- add unit test
---------
Signed-off-by: David Pace <dev@davidpace.de>
* [pilight] Add option to disable background discovery for a given pilight bridge thing
Previously the background discovery updated periodically all channels of all
devices regardless whether they have sent an update or not. This behavior
makes it impossible to decide whether a device is still alive by observing
channel updates sent by a device itself. Especially for devices running on
battery, it is important to know, if it still sends updates.
Create ExecutorService during initialize
---------
Signed-off-by: Stefan Roellin <stefan@roellin-baumann.ch>
* [mqtt] Interpet incoming NaN as UNDEF for NumberValues
Since DecimalType and QuantityType don't support NaN, but
when you're linking to a topic that the device is using
floating point, NaN might happen.
---------
Signed-off-by: Cody Cutrer <cody@cutrer.us>
