did you get this to work with the Beo4?

Unfortunately not. I couldn't find any help or figure it out so I gave up. If you succeed please let me know, thanks.

Hi,

several years ago i downloaded the 'correct' (= old format) Lirc file from lirc.org.

It's attached  as a zip file containing 'beo4.conf'.

Thanks. Did you also manage to successfully build a Raspberry PI receiver?

I have been playing with a Raspberry Pi with Lirc, and did not find any success.🙁

However I did see a link to a github repo for BeoMote which is a library for use with an Arduino. The original was designed for a B&O eye, and I am using a TSOP 7000. I have reworked a clone and have it working pretty reliably with an Arduino Uno. The circuit is the same as in this thread, but without the 4k7 resistor. I have it hooked up to the 3.3v and pin 3 of my Uno. Pressing remote buttons will result in translated commands being sent over the serial port. Initially it seemed excessive to use both a Pi and Arduino, but in retrospect it should be more reliable as the Arduino can do the time sensitive pulse processing, leaving the Pi to do other CPU intensive work without having to worry about the remote processing.

My git clone is at 

samsp wrote:

I have been playing with a Raspberry Pi with Lirc, and did not find any success.🙁

However I did see a link to a github repo for BeoMote which is a library for use with an Arduino. The original was designed for a B&O eye, and I am using a TSOP 7000. I have reworked a clone and have it working pretty reliably with an Arduino Uno. The circuit is the same as in this thread, but without the 4k7 resistor. I have it hooked up to the 3.3v and pin 3 of my Uno. Pressing remote buttons will result in translated commands being sent over the serial port. Initially it seemed excessive to use both a Pi and Arduino, but in retrospect it should be more reliable as the Arduino can do the time sensitive pulse processing, leaving the Pi to do other CPU intensive work without having to worry about the remote processing.

My git clone is at link. I also added the commands I could find in the BeoRemote One that were not already in the commands enum from Beo 4.

The loop function of the sketch writes the remote data via the USB serial connection. If I have the arduino hooked to a USB port of the Pi, then I can read the data via the USB serial port that is created over the USB connection. It seems like the Pi has the drivers included so it maps the arduino to /dev/ttyUSB0.

I will be hooking this up to OpenHab to control my TV, Receiver, Fire TV, PS4 etc via a combination of HDMI CEC and IP commands (Pioneer). Essentially an overly complex and expensive version of a Logitech Harmony, but with the egonomics of a B&O remote.

 

Raspberry PI is not by default running a realtime Linux kernel, and that is why it is very difficult/almost impossible to get the IR decoded correct on the PI.

I tried and almost got it working, but it still missed a lot of commands from the remote. 

An Arduino on the other hand works 100% perfect. I have build a totally LC2 compatible system that uses Arduino and Philips Hue, which is all controlled by Beo4.

Everything works and can be set up like LC2 lamps.

/Weebyx

You guys have made some VERY interesting and useful projects for the B&O world and I'm very curious about these solutions!

Would you mind sharing how you did it, what parts are required and what functionality is possible with your setups?

TWG wrote:

You guys have made some VERY interesting and useful projects for the B&O world and I'm very curious about these solutions!

Would you mind sharing how you did it, what parts are required and what functionality is possible with your setups?

I have made my Philips Hue control with an original B&O Ir Eye(because it is beautiful on the wall), connected to an Arduino Uno.

On the Uno is running the code that detects IR pulses, and decodes them the same way B&O does it.

Once the IR code is decoded to a command, the Arduino determines if it has something to do with the Light command, and if so, it creates a http webrequest to the Philips Hue bridge via the Hue API, that tells Hue which lights/groups to turn on/off/dim and so on.

It requires some coding experience, but it is not as hard as it sounds. Off course Arduino knowledge is required. The HW is very simple if you use the B&O IR eye.

It is also easy to use the old IR receiver from a Beomaster 35/4500.

/Weebyx

Hi! Sounds like one can control a Beovision motorstand with an IR-receiver and Arduino Uno?!

I have had a love of B&O hardware for decades, but could not justify the resources to buy it, particularly for TV/Video equipment where the price/functionality is not there. I have admired the integration of a complete B&O system and wanted to achieve the same thing in a heterogeneous environment. I wanted something similar to logitech harmony, but cleaner using a BEO 4 or BeoRemote One. 

I have now built it.

IR signals are received by an Arduino Nano together with a TSOP 7000 IR reciever, capacitor & resistor. This is running a custom version of BeoMote that processes the IR pulses, translates them into binary and sends codes via the built in serial port/USB connection.

I then have a Raspberry Pi running OpenHab2 as the control unit. The arduino is connected via USB which appears as a serial port to the Pi. OpenHab has bindings for Serial. PioneerReciever, Sonos, zwave and I extended an HDMI-CEC one posted on the forums. 

I am using HDMI-CEC to control my TV (Vizio), PS4 & FireTV Cube. CEC is great for this as its more reliable than IR, can power on devices that don't via IR (PS4) and don't support IR (FireTV). It will also do the source switching automatically without me having to figure out the inputs.

My reciever (Pioneer) is supposidly CEC capable, but its buggy. The IP binding works great for it.

I have rules that interpret the B&O commands, and then map them to CEC or other commands. I can select a source with the Beo Remote One, and it will switch it on, switch to it, and then send subsequent signals to that device.

I have it filtering out volume to the receiver, standby turns everything off, lighting maps to zwave devices etc.

Total cost of hardware (not including remote(s)) < $100. The biggest issue was getting small numbers of individual components, so I now have a collection of resistors, capacitors, diodes, Arduino Nanos (came as a pack of 3) etc.