Zwave fixes. (#2373)
* Fix move_up and move_down I managed to switch up the zwave move_up and move_down commands. This PR fixes it. Thank you @nunofgs for bringing this to my attention :) * Fix for aeotec 6 multisensor
This commit is contained in:
parent
7b02dc434a
commit
21381a95d4
2 changed files with 4 additions and 3 deletions
|
@ -60,11 +60,11 @@ class ZwaveRollershutter(zwave.ZWaveDeviceEntity, RollershutterDevice):
|
||||||
|
|
||||||
def move_up(self, **kwargs):
|
def move_up(self, **kwargs):
|
||||||
"""Move the roller shutter up."""
|
"""Move the roller shutter up."""
|
||||||
self._node.set_dimmer(self._value.value_id, 0)
|
self._node.set_dimmer(self._value.value_id, 100)
|
||||||
|
|
||||||
def move_down(self, **kwargs):
|
def move_down(self, **kwargs):
|
||||||
"""Move the roller shutter down."""
|
"""Move the roller shutter down."""
|
||||||
self._node.set_dimmer(self._value.value_id, 100)
|
self._node.set_dimmer(self._value.value_id, 0)
|
||||||
|
|
||||||
def stop(self, **kwargs):
|
def stop(self, **kwargs):
|
||||||
"""Stop the roller shutter."""
|
"""Stop the roller shutter."""
|
||||||
|
|
|
@ -108,7 +108,8 @@ DISCOVERY_COMPONENTS = [
|
||||||
TYPE_BOOL,
|
TYPE_BOOL,
|
||||||
GENRE_USER),
|
GENRE_USER),
|
||||||
('binary_sensor',
|
('binary_sensor',
|
||||||
[GENERIC_COMMAND_CLASS_BINARY_SENSOR],
|
[GENERIC_COMMAND_CLASS_BINARY_SENSOR,
|
||||||
|
GENERIC_COMMAND_CLASS_MULTILEVEL_SENSOR],
|
||||||
[SPECIFIC_DEVICE_CLASS_WHATEVER],
|
[SPECIFIC_DEVICE_CLASS_WHATEVER],
|
||||||
[COMMAND_CLASS_SENSOR_BINARY],
|
[COMMAND_CLASS_SENSOR_BINARY],
|
||||||
TYPE_BOOL,
|
TYPE_BOOL,
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue