Messages

A few words of warning... I bought one of these and the HDMI is via a DVI to HDMI adapter and there is no SPDIF connector.... so no digital sound output options!

Ok, eBaying right now... But what is the ideal behaviour? Disable temporarily then try again later? I guess if so then it goes beyond the device template.

Can anyone explain why this part exists in the code to disable the device? I am using X10 and zwave with USB-serial (zwave adapter contains one) and there is never an issue there. I don't see why the code for these 2 AV receivers shouldn't support USB-serial adapters!

@wombiroller that has happened a few times - in fact my video watching was interrupted 3 times last night by the bloody wizard! It mostly happens though that it gets disabled and then i have to manually enable again from the advanced page for that device in the web admin

@ladekribs I didn't think this problem was caused by the pnp engine, but could be wrong. It seemed this is caused by the templates themselves.

Chris

I have had a problem with my Denon AVC and Onkyo AV Receivers in that every once in a while (days or weeks) the serial port settings are removed and the devices set to disabled. This has followed me through 710, 810, 3 motherboards, PCI based serial, USB based serial, so there doesn't seem to be any hardware issue.

I have seen the following in the Process Initialize section of both the Denon and Onkyo device templates:

if initok==false
   DisableDevice( device_.devid_, true )
   print "The device wouldn't respond. Disabling it.\n"
   return
end


I have 2 questions:

1. Why is this done? If nobody knows what do you think about me changing it to not disable the device?
2. Does the DisableDevice clear the serial port settings? Is this the desired behaviour if something is temp unavailable?

Thanks in advance,

Chris

No, they don't support WPA. I just setup a second WLAN with WEP only encryption and locked down the subnet a bit (firewalled it and passed through only orbiter ports).

EDIT: Postage at cost - guess around £9 for UK (parcel2go.com)

I spent a while looking at it but did not get anywhere. Suddenly, one day last week it worked after a reboot, but then since the last reboot it has not worked. So still no wiser...

UK. Yes, work fine with 810. You can find instructions on this forum should you wish to install the orbiter image from scratch.

Chris

I find the same thing. It started happening a few days ago when I did an apt-get update. Will try to retrace my steps and get it working.

Advanced Linux Sound Architecture Driver Version 1.0.23.
Compiled on May 24 2010 for kernel 2.6.27-17-generic (SMP).

Code Select Expand

# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 0: VT1708S Analog [VT1708S Analog]
  Subdevices: 2/2
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
card 0: NVidia [HDA NVidia], device 1: VT1708S Digital [VT1708S Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 3: NVIDIA HDMI [NVIDIA HDMI]
  Subdevices: 1/1


From my experience you can not add squeezbox to a room that already has core/MD, you need to select a room that is not in use example "Garage" then you can go to the floorplan and place the squeezebox Icon.

I wonder if it is possible to add a squeezebox to a room with an MD, then have the squeezebox used for music playback in that room rather than the MD. I'm trying this but it doesn't seem to work...

Any sensible offer accepted...

I did a clean install from DVD snapshot on an Asus AT3N7A-I which I know a lot of people are using.

Don't see anything odd in dmesg. I just rebooted and this started happening immediately after the device starts up.

I have a couple of USB-serial adapters, a USB-UIRT, and a WinTv Nova USB attached. Maybe I will try removing these.

Problem with removing alsa-modules-`uname -r` is that this then means there is no support for my main soundcard! (hda nvidia)

I have the tricklestar one. Is that the same?

If it's a hardware issue then how come doing a software reset of the LMCE Zwave device from the web interface fixes it? Couldn't the driver do this reset itself after a bunch of these errors are recognised?

Thanks,

Chris

What was "that command"?

I have upgraded my core to a new motherboard and now also see the No callback received errors.

Sending the reset command to the zwave interface form the web admin fixes it for a while:

Code Select Expand

1 07/27/10 20:06:11.627 ERROR: Dropping command, no callback received after three resends <0xb727cb90>
05 07/27/10 20:06:14.826 No callback received: await_callback: 156 timer: 31 <0xb727cb90>
05 07/27/10 20:06:18.026 No callback received: await_callback: 156 timer: 31 <0xb727cb90>
05 07/27/10 20:06:21.226 No callback received: await_callback: 156 timer: 31 <0xb727cb90>
01 07/27/10 20:06:21.227 ERROR: Dropping command, no callback received after three resends <0xb727cb90>
05 07/27/10 20:06:54.552 No callback received: await_callback: 157 timer: 31 <0xb727cb90>
05 07/27/10 20:06:57.750 No callback received: await_callback: 157 timer: 31 <0xb727cb90>
05 07/27/10 20:07:00.950 No callback received: await_callback: 157 timer: 31 <0xb727cb90>
01 07/27/10 20:07:00.951 ERROR: Dropping command, no callback received after three resends <0xb727cb90>
05 07/27/10 20:07:04.151 No callback received: await_callback: 158 timer: 31 <0xb727cb90>
05 07/27/10 20:07:07.354 No callback received: await_callback: 158 timer: 31 <0xb727cb90>
05 07/27/10 20:07:10.559 No callback received: await_callback: 158 timer: 31 <0xb727cb90>
01 07/27/10 20:07:10.559 ERROR: Dropping command, no callback received after three resends <0xb727cb90>
05 07/27/10 20:07:43.867 No callback received: await_callback: 159 timer: 31 <0xb727cb90>
05 07/27/10 20:07:47.066 No callback received: await_callback: 159 timer: 31 <0xb727cb90>
05 07/27/10 20:07:50.267 No callback received: await_callback: 159 timer: 31 <0xb727cb90>
01 07/27/10 20:07:50.268 ERROR: Dropping command, no callback received after three resends <0xb727cb90>
05 07/27/10 20:07:53.467 No callback received: await_callback: 160 timer: 31 <0xb727cb90>
05 07/27/10 20:07:56.666 No callback received: await_callback: 160 timer: 31 <0xb727cb90>
05 07/27/10 20:07:59.867 No callback received: await_callback: 160 timer: 31 <0xb727cb90>
01 07/27/10 20:07:59.868 ERROR: Dropping command, no callback received after three resends <0xb727cb90>
05 07/27/10 20:08:13.082 No callback received: await_callback: 161 timer: 31 <0xb727cb90>
05 07/27/10 20:08:16.282 No callback received: await_callback: 161 timer: 31 <0xb727cb90>
05 07/27/10 20:08:19.483 No callback received: await_callback: 161 timer: 31 <0xb727cb90>
01 07/27/10 20:08:19.484 ERROR: Dropping command, no callback received after three resends <0xb727cb90>
05 07/27/10 20:08:52.811 No callback received: await_callback: 162 timer: 31 <0xb727cb90>
05 07/27/10 20:08:56.012 No callback received: await_callback: 162 timer: 31 <0xb727cb90>
05 07/27/10 20:08:59.215 No callback received: await_callback: 162 timer: 31 <0xb727cb90>
01 07/27/10 20:08:59.215 ERROR: Dropping command, no callback received after three resends <0xb727cb90>
05 07/27/10 20:09:02.410 No callback received: await_callback: 163 timer: 31 <0xb727cb90>
05 07/27/10 20:09:03.046 Got a reload command from 0  <0xb627ab90>
05 07/27/10 20:09:03.297 void ClientSocket::Disconnect() on this socket: 0x96f7090 (m_Socket: 7) <0xb727d6c0>
Return code: 2
2 07/27/10 20:09:03 40 (spawning-device) Device requests restart... count=1/50 dev=40
Tue Jul 27 20:09:03 BST 2010 Restart
========== NEW LOG SECTION ==========
1 07/27/10 20:09:11 40 (spawning-device) Starting... 1
1 07/27/10 20:09:11 40 (spawning-device) Found /usr/pluto/bin/ZWave
05 07/27/10 20:09:12.103 Creating child 41 <0xb71b16c0>
05 07/27/10 20:09:12.103 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb71b16c0>
05 07/27/10 20:09:12.103 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb71b16c0>
05 07/27/10 20:09:12.103 Creating child 42 <0xb71b16c0>
05 07/27/10 20:09:12.103 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb71b16c0>
05 07/27/10 20:09:12.103 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb71b16c0>
05 07/27/10 20:09:12.104 Creating child 43 <0xb71b16c0>
05 07/27/10 20:09:12.104 Note: Device manager has attached a device of type 1945 that this has no custom event handler for.  It will not fire events. <0xb71b16c0>
05 07/27/10 20:09:12.104 Note: Device manager has attached a device of type 1945 that this has no custom handler for.  This is normal for IR. <0xb71b16c0>
05 07/27/10 20:09:12.104 Creating child 44 <0xb71b16c0>
05 07/27/10 20:09:12.104 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb71b16c0>
05 07/27/10 20:09:12.104 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb71b16c0>
05 07/27/10 20:09:12.104 Creating child 45 <0xb71b16c0>
05 07/27/10 20:09:12.104 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb71b16c0>
05 07/27/10 20:09:12.104 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb71b16c0>
05 07/27/10 20:09:12.104 Creating child 46 <0xb71b16c0>
05 07/27/10 20:09:12.104 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb71b16c0>
05 07/27/10 20:09:12.104 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb71b16c0>
05 07/27/10 20:09:15.199 No callback received: await_callback: 147199752 timer: 31 <0xb71b0b90>
05 07/27/10 20:09:15.419 Got reply to ZW_MEMORY_GET_ID, Home id: 0x00d8c4d8, our node id: 1 <0xb71b0b90>
05 07/27/10 20:09:15.633 Got reply to GET_SUC_NODE_ID, node: 1 <0xb71b0b90>
05 07/27/10 20:09:16.225 Finished building node list: <0xb71b0b90>
05 07/27/10 20:09:16.225 Node: 1 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 1945 <0xb71b0b90>
05 07/27/10 20:09:16.225 Node: 9 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb71b0b90>
05 07/27/10 20:09:16.225 Node: 11 basic: 0x3 generic: 0x11 specific: 0x0 pluto: 38 <0xb71b0b90>
05 07/27/10 20:09:16.225 Node: 14 basic: 0x3 generic: 0x11 specific: 0x0 pluto: 38 <0xb71b0b90>


If this is a bug I will put in a trac ticket. Anyone know if this is already known?