The B&O dealers just have the Beo5 Configuration Tool provided by B&O.

Many of them also visit the Beo5 Information & Resource pages

To my knowledge the dealers have to have B&O make the files for 3rd party products.

B&O has a tool for this, but the dealers do not get this tool for various reasons. One reason is that the B&O politic is to control most non-B&O products through the PUC to ensure the products are in sync. Stand-alone things like curtains, light and air-conditioning are the the aim for direct control by Beo5. Another reason is that B&O wants to guarantee the right user experience and therefore wants to make the XML for the dealers so that the operation of non-B&O products is made in the most correct B&O way.. :-)

Burnix wrote:

To my knowledge the dealers have to have B&O make the files for 3rd party products.

B&O has a tool for this, but the dealers do not get this tool for various reasons. One reason is that the B&O politic is to control most non-B&O products through the PUC to ensure the products are in sync. Stand-alone things like curtains, light and air-conditioning are the the aim for direct control by Beo5. Another reason is that B&O wants to guarantee the right user experience and therefore wants to make the XML for the dealers so that the operation of non-B&O products is made in the most correct B&O way.. :-)

You are correct that a dealer must request the addition of a 3rd party product be added to the PUC if it is a STB which B&O do not intend to support. The dealer and therefore the customer also has to pay a fee for this addition.

In my view there is nothing wrong with B&O's business policy related to using the PUC, what is a problem is the speed (or lack of it) of implementation of new STB's in the PUC which always takes many months and often years to be added after the general availability of a new STB.

It is excellent that B&O wishes to guarantee the right user experience which also means providing the complete solution when the customer receives their purchased Beovision and not have to wait for software updates many months (sometimes years) in the future. Can I use the Beovision 7 as an example !!

I actually meant that the dealer had to request the addition of a 3rd party product to the Beo5 Configuration Tool (aswell as with the addition to the PUC table) as the dealer to my knowledge do not have a tool nor the knowledge of the way B&O would like the a 3rd party product to be operated by Beo5. I too find the policy correct and I too find the speed much too slow at updating both PUC tables and products for the Beo5 Config Tool. Unfortunately these tasks are prioritized very low compared to developing new products and fixing more severe bugs.

Luckily it has been made somewhat easy to write you own XML files for the Beo5 enabling users (with access to the tool) to customize it to their own wishes. 🤒

Burnix wrote:

 

I actually meant that the dealer had to request the addition of a 3rd party product to the Beo5 Configuration Tool (aswell as with the addition to the PUC table) as the dealer to my knowledge do not have a tool nor the knowledge of the way B&O would like the a 3rd party product to be operated by Beo5. I too find the policy correct and I too find the speed much too slow at updating both PUC tables and products for the Beo5 Config Tool. Unfortunately these tasks are prioritized very low compared to developing new products and fixing more severe bugs.

 

Luckily it has been made somewhat easy to write you own XML files for the Beo5 enabling users (with access to the tool) to customize it to their own wishes. 🤒

How do you make your own XML files? As far as I know the software Keith is making is not yet available for software 2.2.

XML files are pure text files and can be created using Notepad! It's not all that difficult... 😐

Burnix wrote:

XML files are pure text files and can be created using Notepad! It's not all that difficult... 😐

😁  Right! Well the trick is to know WHAT to put in the XML files. I have a bunch of Pioneer codes I would like to get on my Beo5 . Would it be possible to get a few hints on how to carry this out?

eljefe wrote:

😁  Right! Well the trick is to know WHAT to put in the XML files. I have a bunch of Pioneer codes I would like to get on my Beo5 . Would it be possible to get a few hints on how to carry this out?

Hi,

maybe have a look at my Pioneer DVD player codes in the

beo4me wrote:

eljefe wrote:

😁  Right! Well the trick is to know WHAT to put in the XML files. I have a bunch of Pioneer codes I would like to get on my Beo5 . Would it be possible to get a few hints on how to carry this out?

Hi,

maybe have a look at my Pioneer DVD player codes in the link. You can also compare the old and new xml files. What format have you got the Pioneer codes in?

Cheers,
Frank

I have them converted into text files via. the lintronic software. Ill have a look at the files. Please let me know if you have any other tips.

beo4me wrote:

eljefe wrote:

😁  Right! Well the trick is to know WHAT to put in the XML files. I have a bunch of Pioneer codes I would like to get on my Beo5 . Would it be possible to get a few hints on how to carry this out?

Hi,

maybe have a look at my Pioneer DVD player codes in the link. You can also compare the old and new xml files. What format have you got the Pioneer codes in?

Cheers,
Frank

Just had a look at the 2 xml files and don't really know if I have the patience to go through them and look for differences. Not now anyways. Maybe Keith could tell us where the differences lie?