pali [Sun, 20 Jun 2021 18:07:12 +0000 (21:07 +0300)]
[ihc] Support for TLSv1.2 (#10856)
* [ihc] Support for TLSv1.2
So far IHC controller have supported only TLSv1. As TLSv1 is already
deprecated and upcoming IHC controller FW version will introduce support
for TLSv1.2.
This change introduce TLSv1.2 support for the binding. TLS version is
selectable to be backward compatible for older controller versions.
Communication error handling is also improved e.g. because of wrong
password or if Java environment doesn't support required TLS version.
When fatal communication error occurs, binding will not hammer
controller with retries as it need user actions.
Signed-off-by: Pauli Anttila <pauli.anttila@gmail.com>
* [ihc] Introduced auto mode and other improvements
Signed-off-by: Pauli Anttila <pauli.anttila@gmail.com>
* [ihc] introduced default constant
Signed-off-by: Pauli Anttila <pauli.anttila@gmail.com>
Wouter Born [Sun, 20 Jun 2021 17:59:46 +0000 (19:59 +0200)]
[nest] Add support for Smart Device Management (SDM) API (#8947)
* [nest] Add support for Smart Device Management (SDM) API
* Reworks WWN implementation so that the thing types have a wwn_ prefix and the classes have a WWN prefix and reside in a 'wwn' package
* Adds an SDM implementation which is also based on: https://github.com/bhigg-code/openhab-addons/tree/2.5.x/bundles/org.openhab.binding.nestdeviceaccess
* Adds unit tests for (de)serialization of the SDM and Pub/Sub API requests and responses
* Updates the binding documentation for the changes and additions
Fixes #8664
Also-by: Brian Higginbotham <brianhigginbothamtx@gmail.com> Signed-off-by: Wouter Born <github@maindrain.net>
* Fix and improve documentation
Signed-off-by: Wouter Born <github@maindrain.net>
* Always use UTF8 when decoding SDM events
James Hewitt [Sat, 19 Jun 2021 09:29:58 +0000 (10:29 +0100)]
[rfxcom] Add firmware type, avoid crashing on unknown. (#10879)
New firmware type reported from the community that's not in the SDK. Also,
we don't actually _use_ the firmware type or device type for anything, so
lets not crash if we don't match the bytes - lets just flag it unknown.
Markus Michels [Tue, 15 Jun 2021 22:00:56 +0000 (00:00 +0200)]
[shelly] 1PM/1L/2.5: New device#supplyVoltage; Motion: Missing channel for vibration; UNI: Unit for ADC voltage; PF for EM; Bulb: fix range for color temp (#10815)
* fixes #10738, #10799
Signed-off-by: Markus Michels <markus7017@gmail.com>
* - Feature #10090 New device#supplyVoltage channel for Shelly 2.5, 1PM
and 1L
- Change #10039 Info on "not reachable / timeout" should be warning,
not info
- Fix #10799 Missing Channel Definition for Vibration Events
- Fix #10738 Shelly UNI - ADC Voltage units of measure missing
- Fix #10111 Creating Equipment from Shelly Bulb Duo causes wrong
min/max
- README updated
Signed-off-by: Markus Michels <markus7017@gmail.com>
* #10737 Shelly EM - add powerFactor channel support
Signed-off-by: Markus Michels <markus7017@gmail.com>
* README updated
Signed-off-by: Markus Michels <markus7017@gmail.com>
* channel powerFactor (EM+EM3) is now of type Number:Dimensionless
Signed-off-by: Markus Michels <markus7017@gmail.com>
* Fix for #10864: Do not trigger same alarm within 5 minutes
Signed-off-by: Markus Michels <markus7017@gmail.com>
* better logic for alarm filter
Signed-off-by: Markus Michels <markus7017@gmail.com>
James Hewitt [Tue, 15 Jun 2021 17:37:07 +0000 (18:37 +0100)]
[rfxcom] Update interface message support (#10844)
Based on both the SDK and experimentation, this commit correctly identifies the
firmware and hardware version. A warning has been added for people with really
old firmware that may be different, but we didn't handle those different cases
well anyway.
Also includes updated firmware types and device types and support for pretty-
printing of the device and firmware type.
Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com>
James Hewitt [Mon, 14 Jun 2021 07:05:03 +0000 (08:05 +0100)]
[rfxcom] Add support for receiving RAW messages (#10833)
This is a new feature in the Pro firmwares that provides the real raw RF
pulse lengths as shorts. Good for being able to parrot switches that aren't
otherwise supported, once we add the tx support as well.
Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com>
James Hewitt [Sat, 12 Jun 2021 11:22:00 +0000 (12:22 +0100)]
[rfxcom] Read multiple bytes at a time over serial connection (#10832)
There's no reason not to read multiple bytes at a time (that I could find) so
for best practice, set the read limit to be the maximum size of an rfxcom
message. Tested fine on my system.
Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com>
James Hewitt [Thu, 10 Jun 2021 12:30:08 +0000 (13:30 +0100)]
[rfxcom] Convert unsigned byte to int properly for message length (#10830)
Without this, any message over 127 bytes reports a negative length and
fails the message start test, which puts the code out of sync with the
rfxcom leading to lots of errors, and eventually, complete loss of
connection.
Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com>
Martin Herbst [Sun, 6 Jun 2021 16:53:51 +0000 (18:53 +0200)]
[homematic] Smaller fixes and conversion of properties files to UTF-8 (#10813)
* Prevent possible NPE
Signed-off-by: Martin Herbst <develop@mherbst.de>
* Spotless
Signed-off-by: Martin Herbst <develop@mherbst.de>
* Fixes missing unit information (especially for HmIP devices)
For some HmIP devices the "valueunit" attribute is empty and thus no
default unit type could be derived. Using the data point name solves
this problem (at least for the relevant data points).
Fixes #10533
Signed-off-by: Martin Herbst <develop@mherbst.de>
* Condition result was wrong because of missing brackets
Signed-off-by: Martin Herbst <develop@mherbst.de>
* Regenerated and reorganized descriptions
Signed-off-by: Martin Herbst <develop@mherbst.de>
* Encoding changed to UTF-8 and some smaller text corrections
Signed-off-by: Martin Herbst <develop@mherbst.de>
* Use default value as maximum if is greater than received max value
For some devices the data point definition retrieved from the CCU
contains default values that are higher than the maximum value. In order
to allow the configuration of these config options the allowed maximum
value needs to be set to the default value.
Signed-off-by: Matthew Davies
matthew.davies@skynet.be Signed-off-by: raveydavies <84205523+raveydavies@users.noreply.github.com>
* VENSTAR THERMOSTAT AWAY MODE AFTER INITIAL COMMIT FEEDBACK
This code includes the Away mode of the Venstar thermostat. It is
updated following initial feedback and suggestions on my first version
from @digitaldan.
Signed-off-by: Matthew Davies <matthew.davies@skynet.be> Signed-off-by: raveydavies <84205523+raveydavies@users.noreply.github.com>
* VENSTAR THERMOSTAT BINDING - INCLUDE AWAY MODE
Removed the updateThermostat function, now have updateSettings and
updateControls corresponding to local API URLs.
Signed-off-by: Matthew Davies
<matthew.davies@skynet.be> Signed-off-by: raveydavies <84205523+raveydavies@users.noreply.github.com>
* VENSTAR THERMOSTAT AWAY MODE - Modification updated as per feedback 1
June 2021
Fix bug:
The channels names were not correctly assigned to the thing properties. The last channel had the default name, not the one retrieved from the module.
Also-by: cedricboon <cedric.boon@hotmail.com> Signed-off-by: Daniel Rosengarten <github@praetorians.be>
Björn Lange [Tue, 25 May 2021 20:06:49 +0000 (22:06 +0200)]
[mielecloud] Initial contribution of the Miele Cloud binding (#9146)
Also-by: Bert Plonus <bert.plonus@miele.com> Also-by: Martin Lepsy <martin.lepsy@miele.com> Also-by: Benjamin Bolte <benjamin.bolte@itemis.de> Signed-off-by: Björn Lange <bjoern.lange@itemis.de>
Thomas Weißschuh [Sun, 23 May 2021 19:08:56 +0000 (21:08 +0200)]
[linuxinput] use correct channelTypeUID for key-press channels (#10742)
Previously there was a mismatch between the UIDs used by the handler and
the one actually registered from the XML-file.
This lead to channels not showing up in the UI.
(See https://github.com/openhab/openhab-webui/issues/406 )
lolodomo [Sun, 23 May 2021 17:48:15 +0000 (19:48 +0200)]
[homeconnect] Let the binding update item state when handling a command (#10749)
To avoid the core framework updating automatically an item state while a
command is sent to this item but its handling by the binding is failing
or ignored
Korbinian Probst [Wed, 19 May 2021 20:18:15 +0000 (22:18 +0200)]
[SenecHome] Catch and ignore malformed JSON (#10657)
* SENEC Home: Add SocketTimeoutException and MalformedJsonException
Signed-off-by: Korbinian Probst <kp.droid.dev@gmail.com>
* SENEC: Revert last commit
Signed-off-by: Korbinian Probst <kp.droid.dev@gmail.com>
* SENEC: Implement a counter that keeps the device online for random errors
Signed-off-by: Korbinian Probst <kp.droid.dev@gmail.com>
* Implement a print of the faulty response
Signed-off-by: Korbinian Probst <kp.droid.dev@gmail.com>
* Improve print of faulty response
Signed-off-by: Korbinian Probst <kp.droid.dev@gmail.com>
* Print all responses for debugging, catch MalformedJsonException explicitly
Signed-off-by: Korbinian Probst <korbinian.probst@gmx.de>
* Add Infor print if JSON is wrong. Catch JsonSyntaxException. Remove errorCounter
Signed-off-by: Korbinian Probst <korbinian.probst@gmx.de>
* Remove most debug code, move remaining messages to trace log level
Signed-off-by: Korbinian Probst <korbinian.probst@gmx.de>
* Bring back catch of MalformedJsonException. Avoid null pointer exception in case response is null.
Signed-off-by: Korbinian Probst <korbinian.probst@gmx.de>
* Collect error to print it in one message
projects / openhab-addons.git / log