This project forked from davidramosweb/home-assistant-custom-components-cover-time-based
Time-based cover with customizable scripts or entity to trigger opening, stopping and closing. Position is calculated based on the fraction of time spent by the cover traveling up or down. State can be updated with information based on external sensors.
Cover state is assumed, so sometimes the Home Assistant cover status could be inconsistent with the real situation (for instance if someone used the old RF remote instead of using HA, or if the RF receiver fails before of bad quality signal).
I didn't found a way to "reset" the position to its actual value, i.e. overriding the cover position value in HA without sending any RF signal to the cover. Is there some special parameter or service to do that? Now I have to manually call my RF script to completely open the cover and then call the cover.open_cover service to align the HA position value to the actual position of the cover: it would be much more elegant to have some cover.reset_position to do the same
Could you please add support for TopDown - BottomUp shades. Now the top and bottom bar sometimes collide into each other. When that happens it stops/blocks and the cover-state is no longer correct. On top of that, to undo that you have to first send and inverted command (blocked going down -> send an up command and blocked going up -> send a down command) etc.
Hi,
Thanks for this - I'd made the tweaks to call my custom scripts and not send stop commands and then found your code, D'oh!
I was wondering if you'd consider introducing the other tweaks I'd made (happy to make a pull request):
An optional configuration for a sensor that indicates if cover is closed.
@property
def is_closed(self):
"""Return if the cover is closed."""
door_sensor = self.hass.states.get(self._closed_sensor)
return door_sensor is None or door_sensor.state == self._closed_sensor_state
I'm using this with a garage door where people will be opening / closing outside of HA controls this would help stop getting cover out of sync.
My other current tweak is to set assumed_state to False - leaving it as True means both Up and Down arrows are available e.g. when closed, which screws up underlying actions required to operate door.
Having that as an optional item defaulting to True would help - out of interest are you seeing any UI oddness like arrows being available when they shouldn't be with that set to True?
Thanks!
My roller shutter controller have two inputs that works in two modes:
First option can be only used when full open or close is requested. Second gives me extra 2.5sec delay that break position calculation - for example 2 x 20% UP is not the same as 1 x 40% UP.
Please consider adding delay option that can be optionally excluded from position calculation.
To allow configuration through the Home Assitant UI this variable it's necessary.
Please add it.
Thanks.
Hi,
I'm not sure if this is possible at all or if it is a limitation of my RF device (Broadlink RM PRO+) but I'm wondering if there could be an option to interrupt the previous script call to start the next one.
Reason/Use case:
If my blinds are closed and I want to open then very slightly, around 1%-3% for example. I notice that my broadlink will send the open command and only once that is done (once broadlink LED goes off), will it send the stop command. The issue is the stop command should have been set earlier, given the time it takes for my blinds to open completely.
Cheers!
Had a lot of updates recently and each time, the position of the cover is not maintained.
Normally, the position is maintained between server restarts.
Anyway to maintain the position when doing all these updates?
Hi Robi!
Congratulation about this great add-on.
May I suggest a feature?
I used this to control the shutters. But the shutters build up with slates.
There is a time when the lowest slate hits the ground, and there is an another time when all the slates closed.
It would be good if your solution can handle this functionality.
I mean when we set 50%, the shutter should cover the half of the window, when I set 100% the shutter lowest slate should reach the ground, and after it we should go forward, to completely close the shutter if we want.
So one timer for cover the whole window, and a 2nd timer after it to close the shutter.
I hope I was clear...
Thank you
László
"requirements": ["xknx==0.17.1"],
I set the known_position to compensate for the delay (app 1-2 secs) in sending the commands. I use the following code in the script. However the stop_script_entity_id-script is never called after using the cover_rf_time_based.set_known_position-service
- service: cover_rf_time_based.set_known_position
data:
confident: false
entity_id: cover.office
position: "{{ starting_position_calculated }}"
position_type: current
The last one today. 😄
Hope it's ok to request features in the issue tracker.
It would be nice to configure the travelling settings with an input_number or other templates.
For example:
travelling_time_up: "{{ states('input_number.cover_up') }}"
When using the position slider, it invokes the opposite script than it should.
cover:
- platform: cover_rf_time_based
devices:
study_curtains:
name: Study curtains
travelling_time_up: 11
travelling_time_down: 11
open_script_entity_id: script.curtain_study_open
stop_script_entity_id: script.curtain_study_stop
close_script_entity_id: script.curtain_study_close
device_class: curtainScenario:
Is this a config mistake on my end or is the component really invoking the wrong script?
In lovelace I click on up button and this integration call up script.
When cover is opened I would the integration call stop script
Is it possible?
Thanks
Hi,
As a feature request it would be nice to add Sunshade/Marquis mode which would basically reverse the directions of operation. By intuition sunshade is closed when it is rolled up and it is open when it rolls down and creates shade. Of course one can swap the RF codes but the position slider will go the wrong way
After the Update to newest HassOS and Integration, the cover.set_cover_position won`t work anymore for me.
After Setting the Position manually to 50, nothing happens, but the Entity says Its Done. Im Using it with custom.entity.slider.row
Setting:
service: cover.set_cover_position
target:
entity_id: cover.kuche_rollo
data:
position: 50
resulting in:
current_position: 50
travelling_time_down: 17
travelling_time_up: 18
unconfirmed_state: 'True'
friendly_name: Küche Rollo
assumed_state: true
supported_features: 15
Nothing is happing in real. Only the Cover-Buttons "up" Down" "Stop" are working right now within the UI.
The Scripts for MQTT publish to Sonoff Tasmota-Bridge are tested and working fine. No Errors in Log.
I cant`t say if it is a Problem with HA or with rf-Integration. It seems that the postions are reversed
right now: "0" is opened and "100" is closed.
Configuration.yaml
Script:
service: mqtt.publish
data:
topic: cmnd/RFBridge_Tasmota/backlog
payload: >-
RfRaw
AAB035050812DE05F0017202D02BC0481XXXXXXXXXXXXA3B2A3A3A3B2A3B2A3A3B2A3B2A3A3B2B2B2A3A3A3B2A3A3A3A3B2B2B2B2A3A55
Hi guys, I'm noticing some problem with this integration. I've installed it with HACS (version 1.0.8), and I'm using HASSIO on raspberry 3 (core version 2021.5.1, supervisor 2021.04.3, OS 5.13).
I've installed the custom component, rebooted, added script and configuration, rebooted.
My config is:
cover:
- platform: cover_rf_time_based
devices:
veneziane_soggiorno_dx_knx:
name: "Veneziane soggiorno dx knx"
travelling_time_up: 43
travelling_time_down: 43
close_script_entity_id: script.veneziane_soggiorno_dx_discesa
stop_script_entity_id: script.veneziane_soggiorno_dx_stop
open_script_entity_id: script.veneziane_soggiorno_dx_salita
send_stop_at_ends: False #optional
aliases: #optional
- veneziane_soggiorno_dx_knx
As I reboot, KNX is not working anymore. Different error is given, but seem to be kindly random.
The most common is:
Setup failed for knx: Unable to import component: No module named 'xknx.dpt'
Do you have some ideas where I can start from? Thank you.
I am getting the following error during HA startup. I'm using a raspberry pi 4 with Bullseye OS and HA in a docker environment. Until now I never had a problem with this component but suddenly this one popped up. I'm using a MQTT based cover.
home-assistant | 2022-08-06 11:56:09.193 ERROR (MainThread) [homeassistant.components.cover] Error while setting up cover_rf_time_based platform for cover home-assistant | Traceback (most recent call last): home-assistant | File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 281, in _async_setup_platform home-assistant | await asyncio.shield(task) home-assistant | File "/config/custom_components/cover_rf_time_based/cover.py", line 150, in async_setup_platform home-assistant | async_add_entities(devices_from_config(config)) home-assistant | File "/config/custom_components/cover_rf_time_based/cover.py", line 132, in devices_from_config home-assistant | device = CoverTimeBased(device_id, home-assistant | File "/config/custom_components/cover_rf_time_based/cover.py", line 178, in __init__ home-assistant | from xknx.devices import TravelCalculator home-assistant | File "/usr/local/lib/python3.10/site-packages/xknx/__init__.py", line 3, in <module> home-assistant | from .xknx import XKNX home-assistant | File "/usr/local/lib/python3.10/site-packages/xknx/xknx.py", line 9, in <module> home-assistant | from xknx.io import ConnectionConfig, KNXIPInterface home-assistant | File "/usr/local/lib/python3.10/site-packages/xknx/io/__init__.py", line 10, in <module> home-assistant | from .request_response import RequestResponse home-assistant | File "/usr/local/lib/python3.10/site-packages/xknx/io/request_response/__init__.py", line 6, in <module> home-assistant | from .authenticate import Authenticate home-assistant | File "/usr/local/lib/python3.10/site-packages/xknx/io/request_response/authenticate.py", line 6, in <module> home-assistant | from xknx.knxip import KNXIPFrame, SessionAuthenticate, SessionStatus home-assistant | ImportError: cannot import name 'SessionAuthenticate' from 'xknx.knxip' (/usr/local/lib/python3.10/site-packages/xknx/knxip/__init__.py)
Hi,
I'm having RFXTRX for Somfy RTS shutter.
RFXTRX integration create cover objects.
In order to have this custom component to work, I need to create via script the cover command open, close and stop.
Would it be possible to support also cover objects ?
It looks a little bit weird to create manual command for an already existing cover to make it working.
Thanks,
Pierre
rfxtrx:
device: /dev/ttyUSB1
devices:
# cover.bureau
xxxxxxxxxxxxxxx:
cover:
//script file
'open_shutter_bureau':
alias: 'Ouvre le volet du bureau'
sequence:
- service: cover.open_cover
data:
entity_id: cover.bureau
#option: open
'close_shutter_bureau':
alias: 'Ferme le volet du bureau'
sequence:
- service: cover.close_cover
data:
entity_id: cover.bureau
#option: closed
'stop_or_my_shutter_bureau':
alias: 'Fixe le volet du bureau'
sequence:
- service: cover.stop_cover
data:
entity_id: cover.bureau
#option: stop
Hello,
we recently had a bug report in HA core (home-assistant/core#76604) mentioning that a very old xknx version is used to run the KNX integration. After some analysis the issue creator found out that this custom integration is using xknx==0.9.4, which is from 3 years ago as a pinned dependency.
Can you please update to the latest version of xknx or even better - get rid of it altogether.
I think merging pull request #21 may have caused some unexpected behavior. The merge flipped the meaning of position 0 from closed to open and position 100 from open to closed. The problem is that Home Assistant uses the former convention, as seen in its Template Cover documentation. If you use a Cover Time Based Component within a Template Cover, things go awry unless you manually flip the positions back to the former convention.
Great component, and thanks for all your work!
The cover gets the entity_id from the friendly name, not from the devices key.
cover:
- platform: cover_rf_time_based
devices:
my_test_cover_time_based: # this should be the entity_id
name: Test CC # the name is used for the entity_id
travelling_time_up: 26
travelling_time_down: 24
send_stop_at_ends: True
close_script_entity_id: script.cover_test_cc_close
stop_script_entity_id: script.cover_test_cc_stop
open_script_entity_id: script.cover_test_cc_open
Hi,
Config example in the doc does not work, HA gives me this error :
cover_entity_id is an invalid option for cover.cover_rf_time_based
If the cover is in position 0% or 100% the buttons for up down stay active and also call the scripts.
So if the cover fully open, the up button should be inactive and not call the up script.
Hi, Im using the cover_rf_time_based to set my ZigBee shutters so I have position cover etc. One will work without faults open, close and set position, but the other will continue to run either to 0% or 100% and won't stop when set position. if i remove the cover and re add it for that one device will start working but then the issue swaps to the other.
I was struggling to find a way to make this work using counters, but found this awesome component. So firstly, THANKS!
I have a few things:
#Feature Request
close_script_entity_id: >
service: remote.send_command
data:
entity_id: remote.rmpro_remote
command: b64:sgD0AqIzDBk
#Questions
2. I have blinds where I can set them in privacy mode when they are at 50% position. I have a separate RF signal for this, but obviously this unique use case means I can just set them at 50% value manually. It just means that I won't have the "opening" or "closing" states that I would prefer.
Fully aware that question 2 and 3 are very specific to my use case, just curious if you might have some knowledge you could drop on me.
Again, amazing work as always nagyrobi!
I might be better doing my own counter and automations to address my specific needs, I'm just stumped though.
Hi,
Thank you for your work! Much appreciated.
I've set up my rollers and they're working great, thanks.
But I would like to have a small enhancement - to have the rollers show the open percentage synced with the percentage of the height of the window (ie if they show 75% they should be about 75% of the window height).
My rollers are spending quite a lot of time (about 5-6 seconds) to unroll and start lifting up, while getting to fully open takes about 24 seconds. This is translating to show 60% open when they are only 30-35% compared with the window height.
Maybe we can split the time traveling up/down into 3 parts and calculate the percentages for each of them, something like:
0 --- 3 ----------------- 97---100
| ----- | ------------------ | ----- |
t1 t2 t3
That would make the percentages more accurate, and we can allow for different timings on each different motor.
Do you think this can be easily achieved?
Thank you very much!
Florin
Hello,
Thank you for this integration!
I have an old shutter with a remote that only has the up/down buttons and when the shutter is moving a press on either one stops it.
This works fine, unless the shutter is not moving and I use the stop button in HASS.
So I'm trying to create a script to prevent the action if the shutter is not moving, I tried based on the state of the shutter opening/closing but it seems that these states are not managed. Do you confirm?
Any idea how to solve this case? Or a useful link?
Thanks in advance.
Hi,
is it possible to add the ability to call service instead of using script?
Thanks,
Hello and thanks for the script.
I have a problem using Alexa and this script. I constantly receive a message in error logs:
2022-07-21 23:00:31 ERROR (MainThread) [homeassistant.components.alexa.state_report] Error when sending ChangeReport for cover.rollo_wz_b to Alexa: THROTTLING_EXCEPTION: Request could not be processed due to throttling.
2022-07-21 23:00:31 ERROR (MainThread) [homeassistant.components.alexa.state_report] Error when sending ChangeReport for cover.rollo_wz_b to Alexa: THROTTLING_EXCEPTION: Request could not be processed due to throttling.
2022-07-21 23:00:31 ERROR (MainThread) [homeassistant.components.alexa.state_report] Error when sending ChangeReport for cover.rollo_wz_b to Alexa: THROTTLING_EXCEPTION: Request could not be processed due to throttling.
2022-07-21 23:00:32 ERROR (MainThread) [homeassistant.components.alexa.state_report] Error when sending ChangeReport for cover.rollo_wz_b to Alexa: THROTTLING_EXCEPTION: Request could not be processed due to throttling.
2022-07-21 23:00:32 ERROR (MainThread) [homeassistant.components.alexa.state_report] Error when sending ChangeReport for cover.rollo_wz_b to Alexa: THROTTLING_EXCEPTION: Request could not be processed due to throttling.
2022-07-21 23:00:32 ERROR (MainThread) [homeassistant.components.alexa.state_report] Error when sending ChangeReport for cover.rollo_wz_b to Alexa: THROTTLING_EXCEPTION: Request could not be processed due to throttling.
Possibly it is because of the “live state” information as it changes position.
Could a delay be added to “current_position”? Maybe 3 seconds or more.
mqtt:
cover:
- name: "MQTT Rollo Balkon"
object_id: mqtt_rollo_wz_b
state_topic: "schellenberg/device/value/2298"
command_topic: "schellenberg/device/value/update/2298"
qos: 1
retain: true
payload_open: "1"
payload_close: "2"
payload_stop: "0"
state_open: "1"
state_closed: "2"
state_stopped: "0"
optimistic: false
cover:
- platform: cover_rf_time_based
devices:
rollo_wz_b_based:
name: rollo_wz_b
travelling_time_up: 24
travelling_time_down: 24
cover_entity_id: cover.mqtt_rollo_wz_b
send_stop_at_ends: False #optional
always_confident: False #optional
device_class: shutter #optional
alexa:
smart_home:
filter:
include_entities:
- cover.rollo_wz_b
Thank you
When HA boots, it always says closed. Is there a way to override this and set default open 100% after restart?
HA Startup log:
2021-12-08 08:46:28 WARNING (MainThread) [homeassistant.helpers.entity] Entity cover.og_bad (<class 'custom_components.cover_rf_time_based.cover.CoverTimeBased'>) implements device_state_attributes. Please report it to the custom component author.
2021-12-08 08:46:28 WARNING (MainThread) [homeassistant.helpers.entity] Entity cover.og_nico_dach (<class 'custom_components.cover_rf_time_based.cover.CoverTimeBased'>) implements device_state_attributes. Please report it to the custom component author.
2021-12-08 08:46:28 WARNING (MainThread) [homeassistant.helpers.entity] Entity cover.og_schlafzimmer (<class 'custom_components.cover_rf_time_based.cover.CoverTimeBased'>) implements device_state_attributes. Please report it to the custom component author.
2021-12-08 08:46:28 WARNING (MainThread) [homeassistant.helpers.entity] Entity cover.test_cc (<class 'custom_components.cover_rf_time_based.cover.CoverTimeBased'>) implements device_state_attributes. Please report it to the custom component author.
Hi I randomly have a situation where a command is missed by a cover (window blind), not really sure what to do in this case, should I alter the script to send multiple rfraw commands to try and compensate?
Please can you add invert logical for the position?
With shutters Its not logical to get current_position: 100 when the shutter its fully open.
In other components this option exists:
thomasloven/lovelace-slider-entity-row#134
Thanks.
My roller shutter moves from full up to down in 20second, but there is extra 3sec move down that locks shutter. Those 50% is far away from 50% shutter clearance.
Tasmota for example allows to configure calibration points
https://tasmota.github.io/docs/Blinds-and-Shutters/#calibration
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.