Is there any way to use the IR codes that I already have in my Ocelot without having to relearn them? It took me a while to get them correct and some of them are learned and some of them were entered using ADI's IRMax utility. It is going to be a big pain to go through that whole process again.
Also is there a way to use the same command for more than one zone. I have the SEC-16IR and am currently using only one zone but in the near future I will have multiple zones and would like to reuse the same code for each zone.
Thanks,
Eric
Ocelot and IR
Unfortunately, you will need to re-learn the Ocelot IR codes with HouseBot. When learning the codes through HouseBot, HouseBot will prompt for additional information that is not stored natively in the Ocelot (like a descriptive name for the Code that is used to identify the Code later).
Unfortunately (again), the zone is tied to the IR code in the interface. The design figured that each zone would be physically associated with one or more pieces of IR equipment. I didn't really see a case for having the exact same equipment connected on multiple zones. It does, however, make it easier to switch between zones, as all you need to do is change the setting for the IR code in the Ocelot configuration.
Unfortunately (again), the zone is tied to the IR code in the interface. The design figured that each zone would be physically associated with one or more pieces of IR equipment. I didn't really see a case for having the exact same equipment connected on multiple zones. It does, however, make it easier to switch between zones, as all you need to do is change the setting for the IR code in the Ocelot configuration.
Scott
Scott,
That's a bummer. I really don't want to have to relearn all my codes. Any way you could change the plug-in so that you could link to an existing code and add the additional info that HouseBot needs?
I can give you a good example of using the same IR code in multiple zones. Say you have multiple DirecTV receivers, the only way to control them independently is by using multiple zones. Unless I'm missing something here you would have to duplicate all the IR commands for the DirecTV receivers to use different zones. It is scenarios like this is why there are multiple zones. If all your equipment used different IR codes then you wouldn't need multiple zones.
I may be overlooking something here. I'm going to play with the Ocelot plug-in more.
Eric
That's a bummer. I really don't want to have to relearn all my codes. Any way you could change the plug-in so that you could link to an existing code and add the additional info that HouseBot needs?
I can give you a good example of using the same IR code in multiple zones. Say you have multiple DirecTV receivers, the only way to control them independently is by using multiple zones. Unless I'm missing something here you would have to duplicate all the IR commands for the DirecTV receivers to use different zones. It is scenarios like this is why there are multiple zones. If all your equipment used different IR codes then you wouldn't need multiple zones.
I may be overlooking something here. I'm going to play with the Ocelot plug-in more.
Eric
It might be possible for you to create the records in the DB manually and then hit the 'Transfer to Library' button. That will send the Ocelot IR code to HouseBot. You will need to make sure that the positions (IRPosition) in the database (IRCodes table) matches the CMax IR position. I've never done this, so I can't guarantee it will work, but it's worth a shot. Backup you HBData.mdb file first.ericvic wrote:Any way you could change the plug-in so that you could link to an existing code and add the additional info that HouseBot needs?
Your example of having the exact same equipment was the one I never though of. My assumption was that you would use zones for similar equipment. For example, maybe you had an RCA TV and VCR that used the same Power On/Off codes and therefore they needed separated.
I can't think of an easy solution to this off of the top of my head. I do see your point and it would be nice to be able to, somehow, tie the SECU16 zone and module to the Device. I'm afraid it might involve an architectural change that would take some careful consideration. I'm off working on another project right now, while the beta settles. When I come back to it, maybe I can find an easier solution.
Scott
Scott,
If IRPosition was not the primary key (so it could have duplicates) you could define two remotes that used the same IR code. Not sure what effect that would have internally to HouseBot. Also there would be no way currently to use the GUI to manage the IR codes but it would allow the same code to be used in multiple zones. Just a thought.
Eric
If IRPosition was not the primary key (so it could have duplicates) you could define two remotes that used the same IR code. Not sure what effect that would have internally to HouseBot. Also there would be no way currently to use the GUI to manage the IR codes but it would allow the same code to be used in multiple zones. Just a thought.
Eric
Possibly. Still you'd have to duplicate things. There may be a simple surgical solution. I just haven't looked into it at all.ericvic wrote:Scott,
If IRPosition was not the primary key (so it could have duplicates) you could define two remotes that used the same IR code. Not sure what effect that would have internally to HouseBot. Also there would be no way currently to use the GUI to manage the IR codes but it would allow the same code to be used in multiple zones. Just a thought.
Eric
Scott