orvibo icon indicating copy to clipboard operation
orvibo copied to clipboard

Emit RF signal command will also emit the last IR signal

Open supakdee opened this issue 8 years ago • 5 comments

Hi,

I found that if I call IR emitter then call RF emitter, when it emits RF, at the same time, the last IR will be emitted as well.

Can you help to check?

Commands & Results below.

Thanks.

pi@raspberrypi:~ $ python3 /home/pi/orvibo/orvibo/orvibo.py -i MYIP -m MYMAC -x irda -e /home/pi/orvibo/orvibo/Toggle_Box.ir Orvibo[type=irda, ip=MYIP, mac=MYMAC] Emit IR done. pi@raspberrypi:~ $ python3 /home/pi/orvibo/orvibo/orvibo.py -i MYIP -m MYMAC -x irda -e /home/pi/orvibo/orvibo/Light.rf -r -s on Orvibo[type=irda, ip=MYIP, mac=MYMAC] Emit RF done.

supakdee avatar Nov 20 '16 01:11 supakdee

Hi, thank you for reporting this. Before emiting RF signal orvibo.py tries to wake up AllOne via sending empty IR signal. I wonder if it can lead to sending the recent emitted IR signal as well :) You can try to avoid this by deleting line 737 in the latest version of orvibo.py

cherezov avatar Nov 20 '16 16:11 cherezov

Hi,

If I create a file called "Blank.ir" with nothing inside, once I emit this file as IR signal - it will also emit the previous IR signal.

I'm now using the work around by recording another IR for button with unimportant command e.g. number then emit this at the end of IR so that even through it emit this IR, it will not turn on / off anything.

By the way, what do you mean by "deleting line 737"? (I see line 737 is "d.emit_rf433(o.switch, o.emitFile)", I guess deleting this line will not emit RF signal at all). I believe the issue is one line above "d.emit_ir(b' ')" but if this is the case, will orvibo wake up?

For clean issue resolution, is it possible to clear up the signal inputs at the end after IR is emitted so that it will not interfere with next command?

supakdee avatar Nov 21 '16 14:11 supakdee

I believe the issue is one line above "d.emit_ir(b' ')" but if this is the case, will orvibo wake up?

line 736, right.

I'm now using the work around by recording another IR for button with unimportant command e.g. number then emit this at the end of IR so that even through it emit this IR, it will not turn on / off anything.

This is what I actually tried to do in this line d.emit_ir(b' '), but magically it works like you've described in your issue. I guess your work around can be applied here via replacing d.emit_ir(b' ') with d.emit_ir(b'dummy bytes')

For clean issue resolution, is it possible to clear up the signal inputs at the end after IR is emitted so that it will not interfere with next command?

Since there is no documentation in open sources I can't confirm is there such a command or not :)

cherezov avatar Nov 21 '16 14:11 cherezov

After replacing d.emit_ir(b' ') by d.emit_ir(b'dummy bytes'), it's still the same issue :(

supakdee avatar Nov 21 '16 15:11 supakdee

the d.emit_ir(b'dummy bytes') also doesn't work for me. I used the blank IR as describe above as a work around.

mojo818 avatar Dec 25 '16 17:12 mojo818