Hello,
Just wanted to know how could I do this:
Just because I do not see the option in the covers documentacion.
Let me know,
Pedro
Hello,
Just wanted to know how could I do this:
Just because I do not see the option in the covers documentacion.
Let me know,
Pedro
I think this depends on your hardware… does your hardware allow incremental changes to the orientation of your blinds? If so, what is the nomenclature?
FYI scrollbars are called input_number
It is mqtt blind, but the addon does not seem to have this feature
I’m not sure where you got your info from, but from the mqtt cover component page, your request appears to be possible:
tilt_min (integer)(Optional)The minimum tilt value. Default value: 0 tilt_max (integer)(Optional)The maximum tilt value Default value: 100 tilt_closed_value (integer)(Optional)The value that will be sent on a close_cover_tilt command. Default value: 0 tilt_opened_value (integer)(Optional)The value that will be sent on an open_cover_tilt command. Default value: 0
You just need to specify a tilt to the mqtt topic. That tilt angle is what you link to the slider.
I have run into the same issue before.
The open/close slider does not appear as it does with other covers such as zwave cover.
The tilt slider does appear and does work once you assign a topic to it.
If thats the case, you just need to map the tilt to a slider, something like this:
- alias: Set Zone 1 Slider
trigger:
- platform: state
entity_id: media_player.yamaha_receiver
condition:
- condition: template
value_template: >
{% if is_state('media_player.yamaha_receiver','off') %}
true
{% else %}
{% if is_state_attr('media_player.yamaha_receiver', 'volume_level', states('input_number.yamaha_receiver') | int / 100) %}
false
{% else %}
true
{% endif %}
{% endif %}
action:
- service: input_number.set_value
entity_id: input_number.yamaha_receiver
data_template:
value: >
{% if trigger.to_state.state == 'on' %}
{% set n = trigger.to_state.attributes.volume_level | float %}
{{ (n - 1.0)*100.0 | int }}
{% else %}
-80
{% endif %}
- alias: Set Zone 1 Volume
trigger:
- platform: state
entity_id: input_number.yamaha_receiver
condition:
- condition: template
value_template: >
{% if is_state('media_player.yamaha_receiver', 'on') %}
{% if not is_state_attr('media_player.yamaha_receiver', 'volume_level', states('input_number.yamaha_receiver') | int / 100) %}
true
{% else %}
false
{% endif %}
{% else %}
false
{% endif %}
action:
- service: media_player.volume_set
entity_id: media_player.yamaha_receiver
data_template:
volume_level: >
{% set n = states('input_number.yamaha_receiver') | float %}
{{ n / 100 + 1 }}
The difference is that you would trigger off the mqtt device changes instead of what I have listed in this automation. You could even convert your slider from 0-100 to whatever the min/max of the device is.