I have an up-to-date beta2 core/hybrd with an Onkyo TX-SR805 that works with the Onkyo/Integra receiver pnp script. The way the system sets it up after I answer 'Yes' to using it as my receiver and what room it's in (Home Theater), and which input (AV1) it leaves the field "COM Port on PC" as -Please Select-. Without changing anything from how the system sets it up it works fine, that is until I make a change that has nothing to do with the receiver and reload the router. The latest example is I created a lighting scenario last night and reloaded the router, the system stopped sending commands to the receiver. I switched the "COM Port on PC" field to one of my options (pl2303 dongle):
/dev/ttyUSB0 (pci0000:00/0000:00:02.0+1:1.0)
/dev/ttyUSB1 (pci0000:00/0000:00:04.0+1:1.0)
/dev/ttyUSB2 (pci0000:00/0000:00:04.0+5:1.0
reloading the router after each change but none of them worked. I had to delete the A/V equipment, reboot the core/hybrid, wait for it to ask me if i wanted to use the receiver and go through the setup again (which is a pain since i use webdt 366 and don't have a mouse attached to the core and the core is in a closet). Then the receiver started working again. Until I did a quick reload router again this morning to see if it would break, and it did. I'm not making any changes in the admin site from when it was working fine, so not sure what's going on. Looking at the 'Errors in log' for this A/V Equipment I get the following:
01 01/04/10 19:17:10.503 Lost connection device: 70 <0xb77988d0>
01 01/04/10 19:17:26.118 Paritybit/Stopbit 8N1 NOT supported. <0xb5f94b90>
01 01/04/10 19:25:30.339 GSD Port is not specified. Instantiating non-IO Wrapper. <0xb6017b90>
01 01/04/10 19:30:07.711 Paritybit/Stopbit 8N1 NOT supported. <0xb5ff9b90>
01 01/04/10 19:30:48.481 Paritybit/Stopbit 8N1 NOT supported. <0xb6114b90>
01 01/05/10 7:18:03.055 GSD Port is not specified. Instantiating non-IO Wrapper. <0xb603db90>
01 01/05/10 7:38:16.991 Error while calling method: Cannot call class method: cmd_193
01 01/05/10 7:38:16.991 For obscure reasons could not handle the message <0xb583cb90>
Any help would be appreciated. Thanks
