Topics

1

Users / Quick Reload Loop

« on: September 07, 2012, 01:14:44 am »

Hi All

I had a problem in 8.10 that has now also come about in 10.04. Whenever an orbiter loads it tells me that it wants to reload the router because I have recently added/removed a device. I say "Yes, do it now" and as soon as the orbiter opens back up, it wants to reload again. It doesn't matter what orbiter, I load, the first thing it says is that it wants to reload the router.

Is there any way I can find out what is triggering the reload? Could it be that whatever flags the system as needing a reload isn't being cleared?

Is there some extra logging that I can turn on to see when the request to reload is being set, if so, which log file do I watch...DCERouter.log? If I can see when it is happening, I may be able to work out what device is causing it.

Or is there something I can lookup in MySQL to see what device is requesting a reload?

I was hoping for something a bit less brute-force than removing devices until it stops, but if I have to, I'll give that a go.

Thanks
Phil

2

Users / ATA Doorbell/Doorphone

« on: May 02, 2011, 09:14:15 am »

I've been trying to set up an analogue telephone adapter as a doorphone/doorbell as per this page in the wiki:

http://wiki.linuxmce.org/index.php/Doorbell

I haven't been able to get the Doorbell event to trigger. What I don't understand is this line:

"After this is done, whenever the extension is triggered, it will ring mobile orbiters and any cell phone orbiters listed in the webadmin. "

How does an extension "trigger". Is this just the analog phone going off-hook? A call being initiated? A certain code being dialed? I've tried a few things but have never been able to get a Doorbell event. It doesn't appear in the logs and I tried adding a "Respond to Event" for Doorbell, but the action never gets executed.

Is anyone doing this successfully in 8.10 with an ATA on extension 994? If so, how does a phone extension "trigger".

Thanks

3

Users / Intrepid distribution gone from archives

« on: November 04, 2010, 08:20:37 am »

My apt-get update is failing because the intrepid distribution seems to have gone from the archives...

I went to au.archive.ubuntu.com, us.archive.ubuntu.com, archive.ubuntu.com and none of them have intrepid showing in the dists list? Have I missed something?

What should my sources.list look like now for 8.10?

Thanks

4

Users / Yamaha Receiver stuck in Detect/Disable loop

« on: May 11, 2009, 03:14:36 am »

Hi All

I have just got a yamaha rx-v1900 and thought I'd take the time to do a system reinstall with the latest 8.10 alpha release (2.18). Up until now I have been running an early alpha2 release which has been working great.

When I plugged the receiver into the core it detected it, added the rx-v1x00 device and child devices and jumped into the setup wizard to set it up, which was great. I went through and set it up and all was good. Then about 2 minutes after completing, I noticed the serial detection scripts running again and it jumped back into the setup wizard. It then proceeded to do this continually. Fortunately it wasn't adding a new device each time.

I watched the yamaha device in web admin at various stages through the detect process and noticed that when the detection script ran, it was enabling the device and assigning the serial port correctly (/dev/ttyS0), but as soon as the setup wizard completed it cleared the serial port setting and the device was set to disabled. Then the serial port detection would find the active serial port and do the detection and setup all over again because the serial port wasn't assigned to a device. I also noticed that the correct configuration value wasn't being set, so I modified it to match my device. (R0240 instead of R0177).

I tried manually assigning the serial port and enabling the device before the next detection and this seemed to work. The detection stopped and the device was working. But as soon as I turned the receiver off (manually with the remote) and back on, the detection loop started again.

I assume I don't have to leave the receiver turned on 24/7 just because the core is. And I can understand the core enabling and disabling the device when I turn it on and off, but I thought it would remember my serial port assignment and not go into the setup wizard for every detection. And then not get stuck in a loop of redetecting the device.

Does anyone have any suggestions as to what might be going wrong?

Cheers

5

Users / Advanced event criteria options

« on: June 07, 2008, 09:15:37 am »

Hi all,

I'm sure this must be documented somewhere, but I'm struggling to find it. Can anyone point me to where I can find the values that are accepted by the event criteria, specifically:

House Mode
User Mode
Room Mode
Time of Day

I've tried various combinations of numbers, words (armed, away etc). I managed to work out Daytime and Night for the time of day..but I assume there are more.

Is there a definitive list of all the event criteria and the values they expect?

Thanks
Phil

6

Users / IR Transmitter Help

« on: March 08, 2008, 08:05:35 am »

Hi All,

I'm trying to set up a device that I want to control through the LIRC Embedded Transmitter. Its a fan, not an A/V device, so I assume I don't use the Add A/V Equipment option. I created a new device under the Climate Category with the "Controlled via" set to "LIRC Embedded Transmitter"

I have the LIRC Embedded Transmitter device set up and I have added the new fan device as a child to the transmitter.

I've create an LIRC conf file for the device which was trained using irrecord and the fan devices remote. It shows up when I run:

linuxmce@dcerouter:~$ irsend LIST "" ""
irsend: ev100
irsend: mceusb

So I have the standard MCE remote and the ev100 (fan) remote configured.

I can run:
linuxmce@dcerouter:~$ irsend SEND_ONCE ev100 On
linuxmce@dcerouter:~$ irsend SEND_ONCE ev100 Off

and my fan turns on and off.

What I don't understand is what my next step in LinuxMCE is. I have tried Manually adding the On and Off commands to the devices command list, but I don't understand how it knows to use the ev100 remotes configuration for On to turn the fan on. I have tried to send a command to the device, but my transmitter doesn't even flash to indicate that it is transmitting, like it does when I use irsend.

All the help I have found is related to A/V devices and talks about going to AV Properties to configure the IR Commands...does this mean I have to set my fan up as an AV device?

I'll include some of my ev100.conf file below in case that helps.

Any help would be greatly appreciated.

Thanks
Phil


begin remote

  name   ev100
  flags RAW_CODES|CONST_LENGTH
  eps            30
  aeps          100

  ptrail          0
  repeat     0     0
  gap    81098

      begin raw_codes

          name On
              750    1800     750    1750    2000     550
             1950     600     700    1800     700    1850
             1950     600    1950     550     700    1850
              700    1850    1950     550    1950     600
             1950     600     650    1900    1900     600
              700    1850     650    1900     650    1850
             1950     600    1900     650    1900     600
              650    1900    1950     600     650

          name Speed
              750    1800     750    1750    2000     550
             2000     550     700    1850     650    1850
             1950     600    1950     600     650    1850
              700    1850    1950     600    1950     550
             1950     600     650    1900    1900     600
              700    1850     650    1900     650    1850
             1950     600    1950     600    1900     600
              700    1850    1950     600     650

7

Users / Adding support for newer tv tuner

« on: March 04, 2008, 12:37:10 am »

Hi all,

I'm fairly new to LinuxMCE and was just wondering what the best option for adding support for a newer tv tuner is. I have the Winfast DTV2000H card. I had read up before buying it to check that it was supported only to find out afterwards that there was a revision update and I have the type J which isn't natively supported.

While I can force it to work using the "option cx88xx card=51" switch in the module options file, this only offers limited support. That is, the digital tuner works but analogue and the composite/s-video inputs don't (analogue kinda does, without sound).

I did try to patch the module using a patch found here : http://lkml.org/lkml/2008/2/6/289, but I only had limited success with it. I tried to cheat by just downloading the kernel source 2.6.22 and only doing a "make modules" and copied over the .ko files without recompiling and installing a whole new kernel, so maybe this is why. The card autodetected and loaded without errors after the patch and it did show the extra input options. I was initially able to tune and watch digital tv in MythTV, but as soon as I added the analogue tuner to MythTV it seemed to kill the digital tuner. After adding the analogue tuner I couldn't get a lock on a digital channel in MythTV (only showed l _ _ lock and not L M S) and the bit error (BE) went up to 13000ish and MythTV would freeze after a few seconds. If I deleted all the tuners from MythTV and added just the digital back in, it would work again. Also, trying to use the composite video source from outside MythTV would kill the digital tuner again and I would have to delete it from Myth and add it back in again to get it working.

So, my question is, what is the best way for me to add support for the newer card? Do I do a full recompile of the kernel with the patch? Install a newer kernel that supports the card or is there some other way to add it in? If I do have to recompile a new kernel, are there any implications for running LinuxMCE and is there a recommended source version to use.

I'm now running a fresh install with LinuxMCE 0710 b4.

Cheers
Phil