Hi, guessed,
Thank you for your work. I have successfully setup the IR Transmitter and the Zenith TV device in Vera. Now I CAN see all commands in advance tab when creating new scenes. So I assume it should work.
Unfortunately, it didn't. Maybe it is because of my firmware version? Currently I am running at 1.1.1186.
Do I need to reset the firmware to an older version?
Yeap, you're on a Beta release.
A problem was intro'd into the Beta's where the normal UI "mechanism" for
associating an
IR Device, with the
IR Transmitter that it should use, it missing. They've since added it back, but we don't yet have access to that version.
It's normally a Drop-down menu, present in the Device's editing dialog that lets you do this, and the drop down shows "all" the
IR Transmitter devices you have installed into your system.
If you're on a Beta release, as you are, then this association needs to be setup
manually before the "Device" can start sending stuff (since, in any system, there might be more than one
IR Transmitter device, like I have)
Anyhow, here are the manual steps you need to perform to work-around the Beta bug:
a) Find the "Device #" of the
IR Transmitter device in your system
In the example screenshot (UI4_1.png) mine shows as "90" in the Device dialog. In the examples below, I'll use the value "90", but you should change this to the value from your system.
b) Open the Device Dialog for your
IR Device in your system (the ZenithTV in your case) and create a Variable called "IODevice".
The specifics of the Variable are as follows:
New service: urn:micasaverde-com:serviceId:HaDevice1
New variable: IODevice
New value: 90
These values are case-sensitive, and should be entered exactly as above, then click the (Add >) Button
c) Click (Save)
d) Validate the values in the Dialog.
If you go back into your Zenith TV dialog, after Vera restarts completely, you should see something like the attached screenshot (UI4_3.png)
At this point the
IR Device (Zenith TV) should be setup to send it's codes via your
IR Transmitter (SQBlaster Plugin)
again, this work-around shouldn't be needed going forward.