ASP sub-type blinds with RFXtrx transceiver

ptitneo · March 16, 2019, 4:42pm

Hello! First post here as I’m spending the afternoon trying out OpenHab

I got the basics working pretty fast. Setting up the RFXtrx433e wasn’t exactly straightforward but I got it working thanks to this great forum. I also got my Somfy blinds working through the binding. And all of this through the Paper UI, pretty nice!

However my first major issue (which is one that also took me some time on Home Assistant, but a non-issue in Domoticz) is that I also have a BLINDS1 type blind that has a pretty rare subtype (ASP) :

Packettype = BLINDS1
subtype = ASP
Sequence nbr = 1
id1-3 = 0020AA decimal:8362
Command = Open
Signal level = 8 -56dBm

I assume the id I should use is 8362.0, but the problem is that ASP isn’t available in the subtype dropdown of the RFXCOM Blinds1 Actuator thing (which I assume is what I should be using here). I’ve tried all available subtypes without success.

I’m running a pkg install of v2.4.0 release build, on a raspberry pi 3 with raspbian stretch.

Thanks!

ptitneo · March 16, 2019, 11:42pm

Digging a little into the source in found the list of supported subtypes in the readme:

github.com

openhab/openhab2-addons/blob/master/addons/binding/org.openhab.binding.rfxcom/README.md#configuration-options-1

# RFXCOM Binding

This binding integrates large number of sensors and actuators from several different manufactures through [RFXCOM transceivers](http://www.rfxcom.com).

RFXCOM transceivers support RF 433 Mhz protocols like:

*   HomeEasy
*   Cresta
*   X10
*   La Crosse
*   OWL
*   CoCo (KlikAanKlikUit),
*   PT2262
*   Oregon
*   etc.

See the RFXtrx User Guide from [RFXCOM](http://www.rfxcom.com) for the complete list of supported sensors and devices as well as firmware update announcements.

## Supported RFXCOM Types

This file has been truncated. show original

The list is the same as here:

github.com

openhab/openhab2-addons/blob/master/addons/binding/org.openhab.binding.rfxcom/ESH-INF/thing/blinds1.xml

<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="rfxcom" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:thing="http://eclipse.org/smarthome/schemas/thing-description/v1.0.0"
	xsi:schemaLocation="http://eclipse.org/smarthome/schemas/thing-description/v1.0.0 http://eclipse.org/smarthome/schemas/thing-description-1.0.0.xsd">

	<thing-type id="blinds1">
		<supported-bridge-type-refs>
			<bridge-type-ref id="bridge" />
			<bridge-type-ref id="tcpbridge" />
			<bridge-type-ref id="RFXtrx433" />
			<bridge-type-ref id="RFXrec433" />
		</supported-bridge-type-refs>

		<label>RFXCOM Blinds1 Actuator</label>
		<description>A Blinds1 device.</description>

		<channels>
			<channel id="command" typeId="command" />
			<channel id="shutter" typeId="shutter" />
			<channel id="signalLevel" typeId="system.signal-strength" />

This file has been truncated. show original

But there are actually more subtypes in the enum here:

github.com

openhab/openhab2-addons/blob/master/addons/binding/org.openhab.binding.rfxcom/src/main/java/org/openhab/binding/rfxcom/internal/messages/RFXComBlinds1Message.java

/**
 * Copyright (c) 2010-2019 Contributors to the openHAB project
 *
 * See the NOTICE file(s) distributed with this work for additional
 * information.
 *
 * This program and the accompanying materials are made available under the
 * terms of the Eclipse Public License 2.0 which is available at
 * http://www.eclipse.org/legal/epl-2.0
 *
 * SPDX-License-Identifier: EPL-2.0
 */
package org.openhab.binding.rfxcom.internal.messages;

import static org.openhab.binding.rfxcom.internal.RFXComBindingConstants.*;
import static org.openhab.binding.rfxcom.internal.messages.ByteEnumUtil.fromByte;

import org.eclipse.smarthome.core.library.types.OpenClosedType;
import org.eclipse.smarthome.core.library.types.StopMoveType;
import org.eclipse.smarthome.core.library.types.UpDownType;

This file has been truncated. show original

… including the ASP subtype (T11).

I wonder why subtypes >T8 aren’t in the XML. Would it work if I used a thing file instead of Paper UI? And if so, I’d have to also declare the RFXtrx transceiver binding in the file too, would that conflict with it being in Paper UI already?

Thanks!