Support for Projector Screen iVisions Electro M

---

For my home cinema setup I use a Projector Screen "iVisions Electro M"
https://www.projectieschermen.com/electro-m-series-projectiescherm.html

It uses a single channel RF remote control AC123-01 which also seems to be available in a 2, 6 and 16 channel version. A Goolge search reveals the remote is also used by A-OK branded blinds.

The RF protocol is currently not supported, thus I’m giving it a try to implement the protocol. However, I’m not able to make it work.

The problem is that each time I send a command from the remote control, the code differs a bit.

For now I’m focussing on the stop command, the idea is that if I have one command working I will be able to make the other works as well.

These are codes I receive when I press the stop button on the remote:

221022102020221210202212121210202022121210221020221210202210212121212020212021221020212021212121212122102121221212112122121211212223
221022102020221210202212121210202022121210221020221210202210212020202120202121221020212121212121212122102121221212102122121211212223
221022102020221210202212121210202022121210221020221210202210212021202120202021221020212021212121212122102121221212102122121211212223
221022102020221210202212121210202022121210221020221210202210202020202120202021221020212020202121212122102021221212102122121211212223
221022102020221210202212121210202022121210221020221210202210212020202120202021221020212121212121212122102020221212102122121211212223
221022102020221210202212121210202022121210221020221210202210212020202120212121221020212121212120212122112121221212102122121211202223
221022102020221210202212121210202022121210221020221210202210202020202120202021221020212120202121212122102021221212102122121211212223
221022102020221210202212121210202022121210221020221210202210202020202120202021221020212021212120212122102020221212102122121211202223
221022102020221210202212121210202022121210221020221210202210202020202120202021221020212020202120202022102020221212102122121211202223
221022102020221210202212121210202022121210221020221210202210212020202120212021221020212121212121212122102121221212102122121211212223
221022102020221210202212121210202022121210221020221210202210202020202120202021221020212020202121202022102021221212102122121211212223

Pulse widths are [ 152, 211, 598, 5103 ]

As you can see, they differ all a bit. I tried to replay a message using the raw switch implementation I created earlier, but when I send one of the above messages the screen does not stop

Does anyone have a suggestion on how to solve this mystery?

@rrooggiieerr said in Support for Projector Screen iVisions Electro M:

The problem is that each time I send a command from the remote control, the code differs a bit.

May be it is rolling code like the hideki protocol. See also https://forum.pimatic.org/topic/807/hama-wheater-sensor-not-showing-up-in-debug-logs/5

It looks like the code only differs in the 0 and 1 pulses, thus the 152 and 211 length pulses. I think it’s safe to assume that the 0 and 1 pulses are actually the same pulses. If I replace the 1s for 0s all the commands are the same.

My current implementation is able to receive the commands and detect them as up, down and stop messages, however sending messages does not trigger any actions in the screen.

So, nine months later I finally have my Projector Screen working in Pimatic. Not by implementing an RF protocol, I couldn’t make that to work, but by using the serial interface of the screen. I use the following shell commands:
open:
/bin/echo -n -e "\xFF\xAA\xEE\xEE\xEE" > /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
close:
/bin/echo -n -e "\xFF\xAA\xEE\xEE\xDD" > /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0

So now I want to use a DummyShutter device in combination with some rules to open and close the screen. However, I can’t find any method to something like:

when cinema-screen is opened
then execute "/bin/echo -n -e \"\\xFF\\xAA\\xEE\\xEE\\xEE\" > /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0"

What is the right way to interact with the DummyScreen device?

Just an image to show off and share my setup:

what exactly does not work with your rule?
you can use a rule like WHEN position of cinema-screen = down THEN execute ...
at least it works for me this way

Yes, that works.

I would think that triggers a rule when the screen reaches the down state.