Micasaverde (Vera) also uses DCERouter, but all the plugins and devices have been rewritten. If you ask me it is one of the best z-wave stacks available (yes, it is better than our Z-Wave device).

br Hari

I guessed as much, because some time ago in their forums they stated it would be simple to add X10 support because LMCE supports it.

I'm seriously considering getting one of these things. I do like the web DT control of LMCE though, and I would certainly miss that. If there is some rest interface or similar to the box I might consider diving in and making a GSD driver for LMCE.

BTW, has anyone looked at openzwave?

1. It would be nice to have a page in the orbiter which displays a list of all devices which have either failed to start or have died and not restarted. At the moment I have problems whereby the zwave device dies but I never know unless I try to switch some lights on/off.

2. If a device is not started then more verbose logging should be provided somewhere, and it should be easily accessible. I have some GSD devices which no not start, are not disabled, but nothing is logged to any logs (grepped for the device name and also id in the log dir with no results). The /var/log/pluto/<device_id> log should be opened as early as possible so it can be logged into. I have devices which do not start but  never even have a log file created.

3. If the core dcerouter crashes then the media players and orbiters etc should continue running and try to reconnect in the background. The current behaviour has the effect of making the system quite infuriating sometimes (and as a result I have moved all media playback to dedicated devices - such as Xtreamers - under IR control)

My zwave lights stopped responding, so I check in the device logs and see this:

Code:

dcerouter_1009446:~# tail -f /var/log/pluto/49_ZWave.log

1 04/22/10 14:14:41 49 (spawning-device) Found /usr/pluto/bin/ZWave
05 04/22/10 14:14:42.883 Connect() failed, Error Code 111 (Connection refused)) <0xb71426c0>
05 04/22/10 14:14:43.882 Connect() failed, Error Code 111 (Connection refused)) <0xb71426c0>
05 04/22/10 14:14:44.882 Connect() failed, Error Code 111 (Connection refused)) <0xb71426c0>
05 04/22/10 14:14:45.882 Connect() failed, Error Code 111 (Connection refused)) <0xb71426c0>
05 04/22/10 14:14:46.882 Connect() failed, Error Code 111 (Connection refused)) <0xb71426c0>
Return code: 255
3 04/22/10 14:14:48 49 (spawning-device) Device died... count=50/50 dev=49
Thu Apr 22 14:14:48 BST 2010 died
3 04/22/10 14:14:59 49 (spawning-device) Aborting restart of device 49...

Seems a bit odd. Any ideas how to debug?

Regards,

Chris

Is Micasaverde based on pluto?

I have added a USB-UIRT to 810 beta and it is all there in the web interface but does not start at all. There is nothing about it in the App_Server log, and the devices are not disabled. Where else could I look?

Starting /usr/pluto/bin/USB_UIRT_0038 manually works and I can learn codes etc.

Regards,

Chris

1. Install snapshot DVD of 810

Did you select the bottom choice "LinuxMCE Install" when you installed kubuntu?

PS! I did a successful install of snapshot 22876 in VirtualBox some days ago.

Yes. Problem is that the full-install.sh script does not call pre-install-from-DVD.sh unless you modify it. From my investigations I see that unless pre-install is called the Linux MCE sources are never added to /etc/apt/sources.list, so the install will never succeed - it simply fails as soon as it tries to install the first pluto specific package. If it is supposed to work differently then I am interested to hear how, hence my post here.

Regards,

Chris

Ok, here is the diff for the /root/new-installer/full-install.sh file:

Code:

diff new-installer/full-install.sh new-installer-2/full-install.sh
1a2,3
> echo "Starting pre-install-from-DVD.sh"
> bash pre-install-from-DVD.sh

Here is the full modified file:

Code:

#!/bin/bash
echo "Starting pre-install-from-DVD.sh"
bash pre-install-from-DVD.sh
echo "Starting mce-install.sh"
echo "deb http://packages.medibuntu.org/ intrepid  free non-free">/etc/apt/sources.list.d/medibuntu.list
bash mce-install.sh
echo "Running post-install.sh"
bash post-install.sh
echo "Done!"

This seems to work!

Before you run the desktop LinuxMCE link, please run the following:

ifconfig | grep eth | wc -l

Output should be 2

and

ping avenard.org

If the ping fails then the install will fail.

Regards,

Chris

I'm fine with bash scripting so think I can fix this - but I just wanted someone to explain why things are as they are - is there a reason or is the DVD install untested?

I tried running the following:

1. pre-install-from-DVD.sh
2. mce-install.sh

but it fails when installing pluto-orbiter with unmet dependencies. Strange thing is "dpkg -l | grep pluto-orbiter" shows it as installed! I have noticed the avenard.org was down at the time, but is back now. This could be the issue! I will try the install again tonight and update you all.

Chris

Problem:

1. Install snapshot DVD of 810
2. Run the Desktop shortcut to /root/new-installer/full-install.sh
3. After installing a few packages I am asked to reboot
4. After reboot nothing happens - presented with a login prompt (KDE no longer starts as the symlinks were remove by the installer)
5. Manually run /root/new-installer/full-install.sh again
6. Install of pluto-dcerouter fails as linuxmce sources have not been added to apt sources.list

I did some digging around and found a function in mce-install-common.sh which adds the LinuxMCE sources called Setup_Apt_Conffiles, which seems to add either remote or local sources based on whether the core currently has internet connectivity (neat!). However, the part of mce-install.sh where this is called from is commented out:

Code:

Core_PK_Device="0"

if [[ "$c_netExtKeep" != "true" ]] ;then
        Setup_Network_Intefaces
fi

Setup_NIS

#trap 'RemoveOfflineSource' EXIT
#Setup_Apt_Conffiles
PinMythTVAt22

Setup_Pluto_Apt_Conf
./mce-install-preseed.sh
apt-get update

I did find however that the pre-install-from-DVD.sh script adds some repos, but this is not called at all from the full-install.sh script which is included in the DVD distribution.

Is there a reason for this? I assume this script is working for other users? How can it work for everyone else? I would go ahead an post a Trac ticket but it seems odd that nobody else would have run into this issue.

Regards,

Chris

ps. my setup is a VMware virtual machine with 2 network interfaces (both appear in ifconfig output and are working)

Oh, yes, it does look short! Any ideas how this has happened? Is this a common problem? Should I file a ticket to improve logging in this situation?

Can you send me yours? It's worth a go...!

Thanks,

Chris

I have used the active USB over cat5 converters you get on ebay but they only provide a USB 1 connection, not USB2, so you'll not be able to use them for a hard drive. I also found that on my setup I would experience USB disconnects and eventually my machine would lock up... so I don't really recommend them.

I'm not really sure anymore that there is a good solution for a setup where the MD is in a cupboard somewhere. Andrew?

Chris

All you have to do now is go into the mythtv frontend, press setup from the menu (when you are in the TV screen press Esc to go back to the menu), and find the setting for video playback. Change this to VDPAU. There are 3 profiles of increasing quality, and depending on your GPU you will be able to use at least one of them. Start with the lowest to be safe.

Yesterday my system filled up to 100% on the root partition and stopped working. I cleared out some files and rebooted, but when I tried to access the web admin I got:

Fatal error: mysql error: [1044: Access denied for user ''@'localhost' to database 'pluto_main'] in CONNECT(, '****', '****', pluto_main) in /var/www/lmce-admin/include/adodb/adodb-errorhandler.inc.php on line 77

This seemed very odd! I went into mysql and added permissions:

grant all on pluto_main.* to  ''@'localhost';
flush privileges;

The webadmin then gave me a similar message for pluto_media, so I repeated the above for that database.

Now the web admin worked! Phew. But, when I restarted the system again the DCERouter does not start. I see the following in the Launch Manager log:

Code:

10 03/29/10 10:53:54.662 Starting... <0xb71476c0>
10 03/29/10 10:53:54.662 =>initialize_Connections() <0xb71476c0>
10 03/29/10 10:53:54.675 Opening DB connection.. <0xb71476c0>
10 03/29/10 10:53:54.702 Successful <0xb71476c0>
05 03/29/10 10:53:54.713 Detected core as device #1 <0xb71476c0>
10 03/29/10 10:53:54.713 =>initialize_VideoSettings() <0xb71476c0>
10 03/29/10 10:53:54.713 =>initialize_AudioSettings() <0xb71476c0>
10 03/29/10 10:53:54.714 =>initialize_LogOptions() <0xb71476c0>
10 03/29/10 10:53:54.715 =>initialize_Start() <0xb71476c0>
10 03/29/10 10:53:54.715 Checking for mysql... <0xb71476c0>
10 03/29/10 10:53:54.715 Done checking for mysql...connection OK <0xb71476c0>
10 03/29/10 10:53:54.715 Checking for core services... <0xb71476c0>
10 03/29/10 10:53:54.715 Checking if core is up... <0xb71476c0>
10 03/29/10 10:53:54.741 No router lock file found, core is down <0xb71476c0>
10 03/29/10 10:53:54.741 Done checking for core services...core is not running <0xb71476c0>
10 03/29/10 10:53:54.741 AlarmManager::AddRelativeAlarm current time 1269856434 delay 5 type 2 <0xb71476c0>
10 03/29/10 10:53:54.742 AlarmManager::AddAbsoluteAlarm time 1269856439 type 2 <0xb71476c0>
21 03/29/10 10:53:54.742 lock(0x895737c) (>4) alarm: AlarmManager.cpp:185  <0xb71476c0>
21 03/29/10 10:53:54.742 acquired(0x895737c) #0 (>4) alarm AlarmManager.cpp:185  <0xb71476c0>
21 03/29/10 10:53:54.744 unlock(0x895737c) #0 (>4) alarm: AlarmManager.cpp:185  <0xb71476c0>
21 03/29/10 10:53:54.744 removed from map (0x895737c) #1 (>4) alarm: AlarmManager.cpp:185  was: 3 size, now 2 Rel: Y Got: Y <0xb71476c0>
21 03/29/10 10:53:54.744 end cond wait AlarmManager.cpp:102 (0x895737c)  <0xb7146b90>
21 03/29/10 10:53:54.754 start cond 0x89573b4 timed wait till 1269856439.0 now 1269856434.754391000 AlarmManager.cpp:102 (0x895737c)  <0xb7146b90>
21 03/29/10 10:53:54.755 end cond wait AlarmManager.cpp:102 (0x895737c)  <0xb6945b90>
21 03/29/10 10:53:54.755 start cond wait AlarmManager.cpp:102 (0x895737c)  <0xb6945b90>

Hmm. So I manually started the DCERouter and the App_Server in separate terminal sessions and a lot of stuff comes to life, however I see some stuff in their logs I have never seen before.

DCERouter:

Code:

This program is distributed according to the terms of the GNU Public License, available at:
http://www.fsf.org/licensing/licenses/gpl.html
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY;
without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See the GNU Public License for more details.
---------------

21 03/29/10 9:23:43.550 lock(0x8887bac) (>2) messagequeue: DCERouter.cpp:1862  <0xb65a5b90>
21 03/29/10 9:23:43.551 acquired(0x8887bac) #0 (>2) messagequeue DCERouter.cpp:1862  <0xb65a5b90>
10 03/29/10 9:23:43.551 ProcessQueue going to sleep <0xb65a5b90>
21 03/29/10 9:23:43.552 start cond wait DCERouter.cpp:1862 (0x8887bac)  <0xb65a5b90>
10 03/29/10 9:23:43.633 Running as device: 2 installation: 1005237 using path: /usr/pluto/ <0xb65a66c0>
10 03/29/10 9:23:43.634 AlarmManager::AlarmManager 0x88a4dd8 <0xb65a66c0>
21 03/29/10 9:23:43.634 lock(0x88a4e1c) (>3) alarm: AlarmManager.cpp:87  <0xb65a66c0>
21 03/29/10 9:23:43.634 acquired(0x88a4e1c) #0 (>3) alarm AlarmManager.cpp:87  <0xb65a66c0>
21 03/29/10 9:23:43.634 unlock(0x88a4e1c) #0 (>3) alarm: AlarmManager.cpp:87  <0xb65a66c0>
21 03/29/10 9:23:43.634 removed from map (0x88a4e1c) #0 (>3) alarm: AlarmManager.cpp:87  was: 2 size, now 1 Rel: Y Got: Y <0xb65a66c0>
21 03/29/10 9:23:43.635 lock(0x88a4e1c) (>4) alarm: AlarmManager.cpp:102  <0xb5bffb90>
21 03/29/10 9:23:43.635 acquired(0x88a4e1c) #0 (>4) alarm AlarmManager.cpp:102  <0xb5bffb90>
21 03/29/10 9:23:43.635 start cond wait AlarmManager.cpp:102 (0x88a4e1c)  <0xb5bffb90>
21 03/29/10 9:23:43.635 lock(0x88a4e1c) (>6) alarm: AlarmManager.cpp:102  <0xb4bfdb90>
21 03/29/10 9:23:43.636 acquired(0x88a4e1c) #0 (>6) alarm AlarmManager.cpp:102  <0xb4bfdb90>
21 03/29/10 9:23:43.636 start cond wait AlarmManager.cpp:102 (0x88a4e1c)  <0xb4bfdb90>
21 03/29/10 9:23:43.636 lock(0x88a4e1c) (>7) alarm: AlarmManager.cpp:102  <0xb43fcb90>
21 03/29/10 9:23:43.636 acquired(0x88a4e1c) #0 (>7) alarm AlarmManager.cpp:102  <0xb43fcb90>
21 03/29/10 9:23:43.636 start cond wait AlarmManager.cpp:102 (0x88a4e1c)  <0xb43fcb90>
21 03/29/10 9:23:43.635 lock(0x88a4e1c) (>5) alarm: AlarmManager.cpp:102  <0xb53feb90>
21 03/29/10 9:23:43.646 acquired(0x88a4e1c) #0 (>5) alarm AlarmManager.cpp:102  <0xb53feb90>
21 03/29/10 9:23:43.646 start cond wait AlarmManager.cpp:102 (0x88a4e1c)  <0xb53feb90>
10 03/29/10 9:23:43.672 Executed query UPDATE Device SET Registered=0,psc_mod=psc_mod (39 rows) <0xb65a66c0>
10 03/29/10 9:23:43.678 Executed query UPDATE Device JOIN Device AS Parent ON Device.FK_Device_ControlledVia=Parent.PK_Device SET Device.FK_Installation=Parent.FK_Installation (0 rows) <0xb65a66c0>
10 03/29/10 9:23:46.084 Created the server device: 1 CORE <0xb65a66c0>

App Server:

Code:

App_Server, v.2.0.0.44.09112922522
Visit www.plutohome.com for source code and license information

10 03/29/10 9:25:01.470 Device: 0 starting.  Connecting to: dcerouter <0xb6fc56c0>
10 03/29/10 9:25:01.517 Setting timeout for socket 4 to 20 <0xb6fc56c0>
10 03/29/10 9:25:01.598 ALSA Master volume: 66% <0xb6fc56c0>
10 03/29/10 9:25:01.598 Starting signal handler thread <0xb6fc56c0>
10 03/29/10 9:25:01.598 Started signal handler thread <0xb6fc56c0>
21 03/29/10 9:25:01.599 lock(0x8cb3ab4) (>81) MessageQueue: Command_Impl.cpp:822  <0xb67c3b90>
21 03/29/10 9:25:01.599 acquired(0x8cb3ab4) #0 (>81) MessageQueue Command_Impl.cpp:822  <0xb67c3b90>
21 03/29/10 9:25:01.599 start cond wait Command_Impl.cpp:822 (0x8cb3ab4)  <0xb67c3b90>
10 03/29/10 9:25:01.613 Requesthandler 0x8cb3968 (device: 1) runThread now running <0xb5fc2b90>
10 03/29/10 9:25:01.613 Connect OK <0xb6fc56c0>
05 03/29/10 9:25:01.613 Creating child 2 <0xb6fc56c0>
10 03/29/10 9:25:01.613 Got CreateEvent for unknown type 1. <0xb6fc56c0>
05 03/29/10 9:25:01.613 Note: Device manager has attached a device of type 1 that this has no custom event handler for.  It will not fire events. <0xb6fc56c0>
10 03/29/10 9:25:01.613 Got CreateCommand for unknown type 1. <0xb6fc56c0>
05 03/29/10 9:25:01.613 Note: Device manager has attached a device of type 1 that this has no custom handler for.  This is normal for IR. <0xb6fc56c0>
05 03/29/10 9:25:01.613 Creating child 3 <0xb6fc56c0>
10 03/29/10 9:25:01.614 Spawning device: 3 File_Grids_Plugin on display:  ip: 192.168.80.1 <0xb6fc56c0>
10 03/29/10 9:25:01.598 SignalHandler_Thread: Started <0xb6fc4b90>
Linux signal handler: Started
Linux signal handler: Exited
10 03/29/10 9:25:01.639 SignalHandler_Action: Started <0xb6fc4b90>
21 03/29/10 9:25:01.639 lock(0x8cf2dac) (>88) MessageQueue: Command_Impl.cpp:357  <0xb6fc56c0>
21 03/29/10 9:25:01.639 acquired(0x8cf2dac) #0 (>88) MessageQueue Command_Impl.cpp:357  <0xb6fc56c0>
21 03/29/10 9:25:01.639 unlock(0x8cf2dac) #0 (>88) MessageQueue: Command_Impl.cpp:357  <0xb6fc56c0>
21 03/29/10 9:25:01.640 removed from map (0x8cf2dac) #0 (>88) MessageQueue: Command_Impl.cpp:357  was: 4 size, now 3 Rel: Y Got: Y <0xb6fc56c0>
05 03/29/10 9:25:01.640 Creating child 4 <0xb6fc56c0>
10 03/29/10 9:25:01.640 Spawning device: 4 General_Info_Plugin on display:  ip: 192.168.80.1 <0xb6fc56c0>
21 03/29/10 9:25:01.639 lock(0x8cb3b84) (>89) AppServer: SignalHandler.cpp:74  <0xb6fc4b90>
21 03/29/10 9:25:01.654 acquired(0x8cb3b84) #0 (>89) AppServer SignalHandler.cpp:74  <0xb6fc4b90>
10 03/29/10 9:25:01.654 SignalHandler_Action: Exited <0xb6fc4b90>
21 03/29/10 9:25:01.654 unlock(0x8cb3b84) #0 (>89) AppServer: SignalHandler.cpp:74  <0xb6fc4b90>
21 03/29/10 9:25:01.654 removed from map (0x8cb3b84) #0 (>89) AppServer: SignalHandler.cpp:74  was: 3 size, now 2 Rel: Y Got: Y <0xb6fc4b90>
Linux signal handler: Started
Linux signal handler: Exited

It looks to me like something odd is going on. Can anyone comment on this?

Thanks,

Chris

Yes, it was detected automatically, and I chose to use automatically and use lmce's dir structure. All the links etc are made.

The script simply does not pick that up as a valid share. I wondered if it is because the parent device of the share is the NAS itself, and not LMCE? If I remove the check on ControlledVia then it works fine.

Is this your script btw? I found another issue ;-)

Chris

The part in the code below which adds FK_Device_ControlledVia = '$PK_Device' as a condition for the found storage devices means that only storage devices which are controlled by a core or MD are picked up by the script. I have some shares attached to a NAS which are not picked up, as this final constraint does not permit it.

Does anyone know why it's like this? I'm also surprised that nobody else has noticed this, as it would mean they could not record to NAS. Am I doing something odd here?

Thanks,

Chris

Code:

## Get a list of storage devices that use the pluto dir structure
if ($CommaSeparatedDeviceList eq '') {
        print 'Finding devices in DB';
        $sql="
                SELECT
                Device.PK_Device,
                Device.Description
        FROM
                Device
                JOIN Device_DeviceData ON FK_Device = PK_Device
        WHERE
                FK_DeviceTemplate IN (" . join(",",@TPL_STORAGE_DEVICES) . ")
                AND
                FK_DeviceData = $DD_USERS
                AND
                IK_DeviceData LIKE '%-1%'
                AND
                FK_Device_ControlledVia = '$PK_Device'
        ORDER BY PK_Device
        ";
        @results=RunSQL($sql);
        foreach $row (@results) {
    push(@Devices,$row);
  }