Custom Component: Cover Time Based

robi · January 22, 2021, 8:23am

Hi Brandon,
It is possible with the trigger-script version of this component, which has the cover_rf_time_based.set_known_position service exactly for this
If you put a door sensor to the desired end or in the pathway, you can make it jump there every time it passes by it, so you get an auto-calibration each time.

Brandon_Beierle · January 23, 2021, 10:31pm

Thanks! I’ll look into that. I don’t think the travel distance is big enough for a door sensor (the contact zone is too wide), but perhaps an optical one or a 3d printer style limit switch would work

wanaka · February 14, 2021, 8:15am

Hi,

I am having problem to implment this using rfxcom. I have created a folder under config/cover_rf_time_based but for some reason still got his error.

Logger: homeassistant.components.hassio
Source: components/hassio/init.py:420
Integration: Hass.io (documentation, issues)

Platform error cover.cover_rf_time_based - Integration ‘cover_rf_time_based’ not found.

robi · February 14, 2021, 1:47pm

I suggest to install HACS first to your Home Assistant instance. It will make the management of your custom components a whole lot easier.

wanaka · February 15, 2021, 3:54am

Hi,

Thanks manage to solve my problem after install HACS. I am using the rfxcom integration. Next step to figure out how to integrate the state of the blind when someone use an external remote. I do have tasmota rf module as well. May be I should use to update the blind status when someone press the remote. The other simple option is to replace the external remote with opple scene switch (6 buttons)

cover:

platform: cover_rf_time_based
devices:
blind1_cover_time_based:
name: Test Blind 1
travelling_time_up: 68
travelling_time_down: 68
close_script_entity_id: script.rf_blind1_down
stop_script_entity_id: script.rf_blind1_stop
open_script_entity_id: script.rf_blind1_up
send_stop_at_ends: False #optional
aliases:
- Test Blind 1

‘rf_blind1_down’:
sequence:

device_id: b77fdf9bd4a916ca8c96fda9099efba3
domain: cover
entity_id: cover.unknown_type_0x19_0x06_010101_16
type: close
mode: single

‘rf_blind1_stop’:
sequence:

device_id: b77fdf9bd4a916ca8c96fda9099efba3
domain: cover
entity_id: cover.unknown_type_0x19_0x06_010101_16
type: stop
mode: single

‘rf_blind1_up’:

sequence:

device_id: b77fdf9bd4a916ca8c96fda9099efba3
domain: cover
entity_id: cover.unknown_type_0x19_0x06_010101_16
type: open
mode: single

wanaka · February 15, 2021, 5:28am

Hi,

homeassistant:
customize_domain: #for all covers
cover:
device_class: shutter
customize: #for each cover separately
cover.my_test_cover_time_based:
device_class: shutter

How to add a slider to the components so that I can adjust the percentage it open or close

robi · March 7, 2021, 7:11pm

With the latest update from HACS, we respect the changes introduced in XKNX version 0.12.0 where position 0 means “fully open”, 100 means “fully closed”.

After update you need to simply close all your covers from Lovelace to re-sync their position with the reality. From now on 0 means “fully open”, 100 means “fully closed” here too.
This was requested many times and it was impossible until now.

farmio · March 7, 2021, 7:37pm

Are you aware that the knx HA integration is inverting this again when interfacing with xknx?

github.com

home-assistant/core/blob/a066f8482866d69a38f69dd99cc20682565d9f4b/homeassistant/components/knx/cover.py#L81


            | SUPPORT_STOP_TILT
        )
    return supported_features

@property
def current_cover_position(self):
    """Return the current position of the cover.

    None is unknown, 0 is closed, 100 is fully open.
    """
    # In KNX 0 is open, 100 is closed.
    try:
        return 100 - self._device.current_position()
    except TypeError:
        return None

@property
def is_closed(self):
    """Return if the cover is closed."""
    # state shall be "unknown" when xknx travelcalculator is not initialized
    if self._device.current_position() is None:

This is done to avoid issues with other integrations. Eg. when you call Alexa to “open covers” it will send 100% to HA - which will be passed to other integrations then.

It was changed in xknx to stick to the KNX specifications, which are in this case the inverse of HAs.

robi · March 7, 2021, 9:15pm

It remains compatible. Many people asked for it as it’s more logic like this.

VDRainer · March 8, 2021, 8:06am

Thats a matter of taste.
Would be nice if this could be made optional.

robi · March 8, 2021, 8:10am

I’m not sure if it’s possible. But if you can submit a PR, I’d love to merge it…

starob · March 8, 2021, 3:29pm

Tasmota’s default is also 100=fully open. This means people who use Tasmota & HA covers will get confused (like myself) or need to change all Tasmota covers which could be a lot of work. Therefore I agree with VDRainer : make it configurable.

robi · March 8, 2021, 4:59pm

Let’s vote then, I can revert the change if many people complain.
I don’t have the time and priority now to make it configurable.

starob · March 8, 2021, 5:09pm

OK, I then vote for keeping 100 = fully open.

robi · March 9, 2021, 8:47pm

For people who use RF covers with Tasmota RF Brigde some new tips to improve reliability of code transmission.

eltonnascimento · March 10, 2021, 5:00pm

This is an excellent addon, but after the update I had problems with the graphics. The up arrow opens the curtain, but graphically it is closing. the same happens when I ask to close. the down arrow closes the curtain, but graphically it is opening. would you have any tips for me to solve? it worked very well before the update. thanks

VDRainer · March 10, 2021, 8:49pm

Scroll 9 posts up and start reading there.
Welcome to HA!

javicalle · March 11, 2021, 11:07am

Hi,
IMHO although in the documentation for the integration ‘cover’ it is not positioned in an OPEN / CLOSED criterion, within the code you can see several references about which value is OPEN/CLOSED:

Maybe the comments are out of date, but I think going against the base implementation can end up causing problems in the CC interoperatibility.

javicalle · March 12, 2021, 8:08am

Well, it seems that there is an ‘official’ documentation on this subject:

https://developers.home-assistant.io/docs/core/entity/cover#platform-properties-to-be-implemented-by-deriving-platform-classes

robi · March 12, 2021, 4:47pm

OK reverted. Toggle up and down each one to re-sync state to reality.