I have had a Slink-e for more than 2 years now.
I never had a problem running CDJ and switching
between 3 megaplayers, controlling the receiver
and a 4x1 Toslink switch.
However, I was never able to make it work
with HomeSeer.
Initially, I was laboring with a Slink-e and an
expansion module connected via a long cable.
Then I tried not using the expansion module.
Then I bought a second Slink-e. All along,
there was Xantech components thrown in.
First I learned everything using EZ-Learn.
Then I tried generating .cde files from codes
obtained with the JP1 tools. Now I am attempting
to learn the IR codes directly into HomeSeer
because I recently read something on this
board about that being preferable. But I can no
longer find this thread (Whoever said the
seach function was greatly improved).
In any event I am now learning IR commands
into the Nirvis plugin for Homeseer. While most
command appear to learn OK only some test
right. Sometimes, when I get an error on test,
the same error repeats when I retest a previously
OK- testing command.
For exemple, I learn the digits on TV, they test OK.
I learn volume up. It appears to learn OK. But on
testing I get a message like "Error: vol is not a
recognized command for the device XXXX". If
I then retest a digit command I get the same message
about "vol".
The use of "vol" is by itself interesting. When I first
started on this endless journey, the commands
were referenced as vol_up and vol_dwn etc.
So I thought maybe the underscore is illegal
so I replaced that with an hyphen and finally went with
no divider at all. Now the commands are referenced as
volup and voldwn in the cde file. They are called
vol_up and vol_dwn in the HomeSeer configuration
window. They appear to learn OK but upon testing
there is an error message refering to "vol"
All the above is for a Sony TV.
With the cable box from Scientic Atlanta, the issue
is different : nothing learns.
Can anybody help me make this work so that I can
enjoy IR automation before I die (Actuarial tables
and family history suggest that I may not have
more than 15-20 years left - if I am lucky)
JCT
I never had a problem running CDJ and switching
between 3 megaplayers, controlling the receiver
and a 4x1 Toslink switch.
However, I was never able to make it work
with HomeSeer.
Initially, I was laboring with a Slink-e and an
expansion module connected via a long cable.
Then I tried not using the expansion module.
Then I bought a second Slink-e. All along,
there was Xantech components thrown in.
First I learned everything using EZ-Learn.
Then I tried generating .cde files from codes
obtained with the JP1 tools. Now I am attempting
to learn the IR codes directly into HomeSeer
because I recently read something on this
board about that being preferable. But I can no
longer find this thread (Whoever said the
seach function was greatly improved).
In any event I am now learning IR commands
into the Nirvis plugin for Homeseer. While most
command appear to learn OK only some test
right. Sometimes, when I get an error on test,
the same error repeats when I retest a previously
OK- testing command.
For exemple, I learn the digits on TV, they test OK.
I learn volume up. It appears to learn OK. But on
testing I get a message like "Error: vol is not a
recognized command for the device XXXX". If
I then retest a digit command I get the same message
about "vol".
The use of "vol" is by itself interesting. When I first
started on this endless journey, the commands
were referenced as vol_up and vol_dwn etc.
So I thought maybe the underscore is illegal
so I replaced that with an hyphen and finally went with
no divider at all. Now the commands are referenced as
volup and voldwn in the cde file. They are called
vol_up and vol_dwn in the HomeSeer configuration
window. They appear to learn OK but upon testing
there is an error message refering to "vol"
All the above is for a Sony TV.
With the cable box from Scientic Atlanta, the issue
is different : nothing learns.
Can anybody help me make this work so that I can
enjoy IR automation before I die (Actuarial tables
and family history suggest that I may not have
more than 15-20 years left - if I am lucky)
JCT
Comment