Telldus Driver Download

  • 5Electrical Characteristics


Sonoff RF Bridge 433 is an ultra low power consumption device that can convert 433.92MHz (433MHz) to WiFi. It's a bridge between 433MHz RF and WiFi, which can be added to iOS & Android App eWeLink. Users can firstly pair 433MHz devices with the RF Remote, then add their RF Remote to the App. Therefore, users can control the 433MHz devices through App eWeLink. It's specially designed for mobile device and IoT application.

I Recently got interested in home automation, and set up OpenHab, first on a PC, then On a Raspberry Pi. It all worked well, after a fairly steep learning curve, my Harmony hub and Tradfri Lights were easy to set up. Hi I just installed a new comuputer with Windows 10 and need to install the Telldus Center user interface. I must be blind but I can't find any way to download in from the Telldus site.

From the picture, you can see the relations among the devices clearly. Firstly, you pair the 433MHz RF Remote controller with 433MHz device. Secondly, you add RF Bridge to App eWeLink. Thirdly, add the 433MHz RF Remote controller to RF Bridge via App, pair the buttons one by one. Then you can press the button on the App to turn on/off the 433MHz device remotely. One RF Bridge supports to add up to 4 RF Remote controllers.

You can add not only 1-4 buttons ordinary RF Remote to the RF Bridge on App, but also curtain RF Remote and Alarm. Please note that you can't see device status changes on the App.

Go shopping Sonoff RF Bridge 433 (SKU:IM170619001)

RF Bridge Diagram

WIFI 2.4G Characteristics

  • Support wireless 802.11 b/g/n/d/e/i/k/r standard
  • Support STA/AP/STA+AP working modes
  • Support WPA/WPA2, PSK and WP
  • Built-in TCP/IP protocol stack
  • Support multi-channel TCP client connection
  • Support Wi-Fi Direct (P2P)
  • Multi-queue management, make full use of 802.11e-compliant QoS priority
  • Adaptive rate fallback algorithm sets the optimum transmission rate and Tx power based on actual SNR and packet loss information.

433.92MHz Wireless Characteristics

  • Complete monolithic UHF receive/transmit
  • Receive & transmit frequency: 433.92MHz
  • Receive sensitivity: -107dBm
  • Max transmit power: 17dBm
  • Transmission speed: 10kbps
  • Autotune without manual adjustment
  • Ultra low RF antenna radiation
  • The receiving supports fixed code encoding, like PT2260, PT2262, PT2264, EV1527, etc.
  • Not support to learn rolling code and dynamic code

Electrical Characteristics

The device is powered by micro USB cable. The power is supplied to the system through 3.3V LDO chip.

Rated Parameters

Power supplyMicro USB:+5V
I/O voltageVSS - 0.3 ~ VDD + 0.3
Node Temp.+150℃
Storage Temp.-40℃ ~ +125℃
Operating Temp.-40℃ ~ +125℃
Soldering Temp.260℃

Technical Parameters

Wi-FiWireless StandardIEEE 802.11b/g/n/d/e/i/k/r
Transmit Power802.11b: +20±2dBm (@11Mbps)
802.11g: +17±2dBm (@54Mbps)
802.11g: +14±2dBm (@HT20,MCS7)
Receiving Sensitivity802.11b: -91 dBm (@11Mbps ,CCK)
802.11g: -75 dBm (@54Mbps, OFDM)
802.11n: -72 dBm (MCS7)
Antenna2.4G onboard antenna
433.92MWorking Frequency 433.92MHz
Demodulation Bandwidth5000Hz
Transmit PowerTransmitting mode: 12.5mA
Idle mode: 3mA
Standby mode: 1uA
Receive CurrentContinuous receiving mode: 3.9 ~ 4.5mA
Idle mode: 390uA
Standby mode: 0.9uA
HardwareOperating Voltage3.0 ~ 3.6V
GPIO drive of main chip Max:12mA(ESP8285),12.5mA(EFM8BB1)
Operating CurrentContinue sending:70~200mA
Normal working:30~200mA
Stand-by mode:<200uA



Useful Links

Wi-Fi Socket/Switch Fail to be Controlled Troubleshooting

Features wanted, bug report and discuss in Itead Smart Home Forum

Retrieved from 'https://www.itead.cc/wiki/index.php?title=Sonoff_RF_Bridge_433&oldid=6381'

I Recently got interested in home automation, and set up OpenHab, first on a PC, then On a Raspberry Pi.

It all worked well, after a fairly steep learning curve, my Harmony hub and Tradfri Lights were easy to set up.

I was particularly impressed by the easy installation and configuration of OpenHab compared to other systems I have tried.

Then I remembered that I have a couple of Orange Pi Ones left over from my eBay trading period, so decided to try it on one of those, as I have other uses for my RPi.

The Orange pi One has a 4 core ARM processor and 512Mb of memory.

I also have an Orange pi lite, which has built in wifi, so that will be the next experiment.

First I downloaded Armbian from:

I chose this image:


Unzipped it, and copied it onto an SDcard using Etcher from Resin.io

Booted up and configured Armbian.

The default user is root with a password of 1234 which you are asked to change after installation is completed.


Then I logged in via SSH. (I use Linux on all my PCs, so command line from here only I’m afraid ).

Telldus Driver Download Pc

ssh <[email protected] orangepi>

First update:

sudo apt update

sudo apt upgrade

a while later….

sudo reboot

Install Java (OpenHab runs on Java)

sudo addaptrepository ppa:webupd8team/java

sudo apt update

sudo apt install oracle-java8-installer

sudo reboot

Install OpenHab following the instructions here for Debian:

Telldus Driver Download


15 minutes later, I had OpenHab running on OPi1 IPaddress:8080

I installed some bindings, and everything started appearing in my inbox.


Next step was to install and configure my Tellstick USB stick.

The Tellstick is a USB 433MHz transmitter for controlling a variety of proprietary power sockets.

I have one of the original Tellstick units, (The newer Tellstick duo is a transceiver version) and several EasyHome 433MHz sockets.

To install the Tellstick on Armbian: (updated as the original commands are outdated)

sudo sh -c ‘echo “deb http://s3.eu-central-1.amazonaws.com/download.telldus.com unstable main’

sudo wget http://download.telldus.se/debian/telldus-public.key

sudo apt-key add telldus-public.key

sudo apt update

sudo apt install -y telldus-core libftdi1 libconfuse-dev

The following steps may not be necessary, if the service is enabled by the installer.

Start the service:

sudo systemctl start telldusd.service

Check it is running:

sudo systemctl status telldusd.service

should show something like this:

● telldusd.service – Tellstick service daemon
Loaded: loaded (/lib/systemd/system/telldusd.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2017-12-24 10:19:33 UTC; 1h 24min ago
Process: 2190 ExecStart=/usr/local/sbin/telldusd (code=exited, status=0/SUCCESS)
Main PID: 2191 (telldusd)
CGroup: /system.slice/telldusd.service
└─2191 /usr/local/sbin/telldusd

Dec 24 10:19:33 orangepione systemd[1]: Starting Tellstick service daemon…
Dec 24 10:19:33 orangepione telldusd[2191]: telldusd daemon starting up
Dec 24 10:19:33 orangepione systemd[1]: Started Tellstick service daemon.
Dec 24 10:19:34 orangepione telldusd[2191]: Connecting to TellStick (1781/C30) with serial A6008hvI



Telldus driver download windows 7

sudo systemctl enable telldusd.service

Will set it up to start at boot time.

Telldus Driver Download Windows 10

it should show this:

Synchronizing state of telldusd.service with SysV init with /lib/systemd/systemd-sysv-install…
Executing /lib/systemd/systemd-sysv-install enable telldusd

Telldus Driver Download Torrent

That’s it!

You can now configure your devices by editing /etc/tellstick.conf

sudo nano /etc/tellstick.conf

Add the Tellstick binding and the Tellstick and its devices should start appearing i n your in-tray.