Topics

136

Users / Off Topic: How to easily create (flash) web based GUI for home automation?

« on: February 20, 2008, 08:53:58 am »

Hi,

sorry for being offtopic, but I know that there are many guys that will know about this and have no idea where to ask this elsewhere...

I'd like to add some simple web based (perhaps in Flash ?) GUI for basic operations with home automation system and media players.

Maybe something similar to this : http://misterhouse.wikispaces.com/Timo

It should be skinnable as possible (like example above that reads xml file for definition of devices, backgrounds, etc...) and also support live update of shown data over tcp (above example uses XMLSocket)...

I don't know anything about Flash, but have heard of it and also for OpenLaszlo, but I do wonder how would one start working on such project ? What tehcnology, what tools ? Any similar projects out there ?

Thanks in advance,

regards,

Bulek.

137

Developers / Why my device driver cannot register with DCERouter (works if run from cmd.line)

« on: February 14, 2008, 12:26:38 am »

Hi,

I wrote device driver that connects to DCERouter via 2 tcp ports (one for receiving command and other one for sending events to DCErouter). I've created template for that device driver and added name of binary file that actually runs the driver. I've added driver to Interface category - it has several child devices....

I have problems when I want the device driver to be started by LMCE. From log I write in device driver I can see that app was started, but the problem is that on web page it says that it hasn't registered with DCErouter, so I suppose that all messages/events it sends are ignored by DCERouter. The funny thing is that if I kill that LMCE started app and start it from command line it registers immediately...

I see nothing suspicious in DCERouter's logs. I have this :
/var/log/pluto/290_Cybrotech_Integra_BM.log :

========== NEW LOG SECTION ==========
1   02/12/08 09:21:52   290 (spawning-device)   Starting... 1
1   02/12/08 09:21:52   290 (spawning-device)   Found /usr/pluto/bin/Cybrotech_Integra_BM

/var/log/pluto/LaunchManager.log (it reports timeout waiting for device registration ):

05   02/12/08 9:21:52.370      Starting device 290 Cybrotech Automation <0xb68388e0>
05   02/12/08 9:21:52.370      Starting device 290 Cybrotech Automation: /usr/bin/screen -d -m -S Cybrotech_Automation-290 /usr/pluto/bin/Spawn_Device.sh 290 localhost Cybrotech_Integra_BM <0xb68388e0>
05   02/12/08 9:22:05.631      Timeout waiting for device registration <0xb68388e0>

Any hint, what might be going wrong ?

Thanks in advance,

regards,

Bulek.

138

Developers / Strange DCE message: does anyone know what it means ?

« on: February 07, 2008, 11:58:47 pm »

Hi,

occasionaly I receive weird DCE message from DCERouter. I have home automation driver written in Perl that has a lot of child devices under LMCE. All messages, events are processed in parent interface device.

Weird DCE message is : 0 290 9 0 "&" 316 -1000 2 9 25 "0"

290 ID of my interface
9 obviously something new (beside command,event...)
316 -1000 2 9 25 "0"   .. is first message that was sent from my interface to DCERouter.

At the same time this is in DCERouter's log :
01      02/08/08 0:00:21.813            Socket::ReceiveData-a 0x8ddae00 failed ret 0 <0x92ea2b90>
01      02/08/08 0:00:21.814            Socket 0x8ddae00 failure waiting for response to message from device 290 type 9 id 0 <0x92ea2b90>
07      02/08/08 0:00:26.886            Event #9 has no handlers <0x92ea2b90>

I suspect this is somekind of rejection DCE message, cause it happens when my device can't register with DCERouter (it says non-registered on WebAdmin) and first message being sent to DCERouter is repeated...

Although this could also be the result of some stupidity in my code 

Anyone know more about this message or knows if it is real ?

Thanks in advance,

regards,

Bulek.

139

Developers / How to properly make udev rule for touch screen device controller ?

« on: January 31, 2008, 12:44:31 am »

Hi,

under Pluto it was enough to put this rule into /etc/udev/rules.d :

BUS=="usb", KERNEL=="event[0-3]*", SYSFS{product}=="GeneralTouch USB Touchscreen", SYMLINK=="input/gtouch"

and my touchscreen device always appeared at /dev/input/gtouch. Under LMCE same thing doesn't work. As I see (I don't know Linux so well), rules are now defined in 3 parts : first in 20-names.rules, then in 40-permissions.rules and at last on the spot I was adding my rule before : 60-symlinks.rules .

Currently I'm, getting this in dmesg :

dmesg | grep input
[   20.699985] input: Macintosh mouse button emulation as /class/input/input0
[   20.752388] input: AT Translated Set 2 keyboard as /class/input/input1
[   33.113212] input: PC Speaker as /class/input/input2
[   34.662851] input: ImPS/2 Logitech Wheel Mouse as /class/input/input3
[   35.248511] input: General Touch Co. Ltd.  GeneralTouch USB Touchscreen as /class/input/input4
[   35.248588] input,hiddev96: USB HID v1.10 Mouse [General Touch Co. Ltd.  GeneralTouch USB Touchscreen] on usb-0000:00:1d.7-3.4
[   35.248604] drivers/usb/input/hid-core.c: v2.6:USB HID core driver
[   53.983763] input: Power Button (FF) as /class/input/input5
[   54.028533] input: Power Button (CM) as /class/input/input6

Does anyone know how to define proper rules, so touchscreen device will be under it's own device hook ?

Thanks in advance,

regards,

Bulek.

140

Developers / Thinking about whole house multichannel audio solution in SW for LMCE ...

« on: January 28, 2008, 11:02:52 am »

Hi,

I'm thinking about possible ways of implementing whole house multichannel audio system under lmce.

What do I imagine under such system :
- black box with multiple inputs and outputs
- audio sources on inputs and audio sinks (audio cards) on outputs.

audio sources under LMCE:
- currently limited number - most known is Xine player wrapper and speech announcements (they can be separate audio source)
- the problem is cause you cannot run more media players on one Core, I vision that Audio only xine player thing is a good solution to this, so one can start more media players on core and get more sources on one machine (using more MDs to just get more audio sources is inefficient IMHO)...
- currently the problem is cause you cannot easily add another Xine player to LMCE system - I mean on creation of new audio zone and automatic creation of scenarios for control of such media player...

audio sinks:
- currently xine player is directly connected to sound output - aka sound card

Black box :
- I have found interesting project that could be what I'm looking for :
http://pulseaudio.org/ (I spotted it when Jim on MH mailing used it to connect Asterisk and PocketSphinx easily with it for speech recognition)

Maybe als Jack is candidate ? not sure, don't know much about it....

Black box in functionality must allow all kinds of switching,routing,mixing of audio inputs into several audio outputs. In this way we could much better implement also speech announcements, that are currently pretty unusable (media play is interrupted, not pause or faded out, after announcement, play is not restored from previous possition but with next song etc.. - the right way should be to fade out, pause media, make announcement and then fade in slowly to continue with media). I also spot that some applications under lmce are still trying to have exclusive acces of sound card (Embedded Phone used to do that if I remember correctly).... Using above mentioned project I think this could be helped a lot...


Any opinions, ideas ?

Regards,

Bulek.

141

Users / How to deal with kernel oops and Core Hardlocks... ?

« on: January 23, 2008, 01:31:22 pm »

Hi,

I'm getting a lot of kernel oops and sometimes also my LMCE 704 Core hardlocks (only HW reset helps)....

I'm spotting one weird problem :
1. I see kernel Oops or Eeek messages only if I'm connected via ssh at that time. if I search in syslog,messages or dmesg logs aftewards, I can't find any kernel messages Oops or Eeek in them. Do we have some setting to prevent this ? I get 1-2 lockups per day on my core but can't see kernel messages that describe cause of hard lockup... How to deal with this ?

2. How to see if kernel message it just kernel error causing hardlock trouble and is not related to any HW failure ?

3. How would be the procedure to rule out HW failure causes for hard lockups ? I've tried to rum memtest for 1 day and no errors were found in memory. I'm not sure how to check if anything is wrong with disks ? My disks seem not to have support for SMART health check...

4. I've seen all my kernel messages already reported on proper places for that (https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/107325)
I need just to wait and try new kernels or is there anything else that needs to be done ?


Thanks in advance,

regards,

Bulek.

Code: [Select]

cerouter_42077:~#
Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] Eeek! page_mapcount(page) went negative! (-1)

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] page pfn = 23232

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] page->flags = 40000004

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] page->count = 1

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] page->mapping = 00000000

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] vma->vm_ops = 0x0

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] ------------[ cut here ]------------

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] invalid opcode: 0000 [1]

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] SMP

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] CPU: 0

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] EIP: 0060:[page_remove_rmap+224/240] Tainted: P VLI

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] EFLAGS: 00210246 (2.6.20-15-generic 2)

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] EIP is at page_remove_rmap+0xe0/0xf0

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] eax: 00000000 ebx: c1464640 ecx: 00200046 edx: 00000000

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] esi: de27f128 edi: b7800000 ebp: c1464640 esp: daaf5eb8

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] ds: 007b es: 007b ss: 0068

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] Process perl (pid: 29700, ti=daaf4000 task=eb80b030 task.ti=daaf4000)

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] Stack: c036966b 00000000 00000000 e6fc5000 c0163a8d 00000000 b7b63fff 00000000

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] de27f128 daaf5f44 00000000 00000001 b7b64000 f280fb78 cbe74200 c1806640

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] 00000000 ffffffff c14df8ac e6fc5000 f280fb78 23232323 c14df8ac 00362bf3

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] Call Trace:

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] [unmap_vmas+733/1472] unmap_vmas+0x2dd/0x5c0

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] [exit_mmap+119/240] exit_mmap+0x77/0xf0

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] [mmput+56/160] mmput+0x38/0xa0

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] [do_exit+242/2048] do_exit+0xf2/0x800

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] [do_page_fault+831/1520] do_page_fault+0x33f/0x5f0

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] [do_group_exit+38/128] do_group_exit+0x26/0x80

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] [sysenter_past_esp+105/169] sysenter_past_esp+0x69/0xa9

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] [xfrm_state_find+1251/1392] xfrm_state_find+0x4e3/0x570

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] =======================

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] Code: c0 74 0d 8b 50 08 b8 fc a1 36 c0 e8 3b ca fd ff 8b 46 48 85 c0 74 14 8b 40 10 85 c0 74 0d 8b 50 2c b8 1c a2 36 c0 e8 20 ca fd ff <0f> 0b eb fe 8b 53 0c eb 95 8d b4 26 00 00 00 00 55 57 56 89 d6

Message from syslogd@dcerouter at Mon Jan 14 23:39:48 2008 ...
dcerouter kernel: [14373.108000] EIP: [page_remove_rmap+224/240] page_remove_rmap+0xe0/0xf0 SS:ESP 0068:daaf5eb8

dcerouter_42077:~#





dcerouter kernel: [100495.644000] Oops: 0002 [#1]

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000] SMP

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000] CPU:    0

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000] EIP:    0060:[cache_alloc_refill+298/1360]
Tainted: P      VLI

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000] EFLAGS: 00010046   (2.6.20-15-generic #2)

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000] EIP is at cache_alloc_refill+0x12a/0x550

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000] eax: df90bdc0   ebx: 00000006   ecx: 00000035
  edx: a7b4bbc0

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000] esi: 0000001d   edi: dbdfe000   ebp: df909c00
  esp: e545be68

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000] ds: 007b   es: 007b   ss: 0068

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000] Process fuser (pid: 13555, ti=e545a000 task=d5
4a5560 task.ti=e545a000)

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000] Stack: 00000010 000000d0 00000004 000000d0 df9
0e9c0 df908000 df90bdc0 00000000

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000]        479726af 0e3c60b5 e56b9560 c0189dba e56
b9560 dbdfe01c 00000246 000000d0

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000]        df90e9c0 da1657c8 c0172c00 00000000 000
00423 00000004 c018811b e545bf08

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000] Call Trace:

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000]  [alloc_inode+202/384] alloc_inode+0xca/0x180

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000]  [kmem_cache_alloc+128/144] kmem_cache_alloc+0
x80/0x90

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000]  [d_alloc+27/400] d_alloc+0x1b/0x190

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000]  [proc_fill_cache+257/320] proc_fill_cache+0x1
01/0x140

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000]  [filldir64+0/224] filldir64+0x0/0xe0

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000]  [proc_readfd+223/480] proc_readfd+0xdf/0x1e0

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000]  [proc_fd_instantiate+0/352] proc_fd_instantia
te+0x0/0x160

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000]  [filldir64+0/224] filldir64+0x0/0xe0

Message from syslogd@dcerouter at Wed Jan 23 12:36:15 2008 ...
dcerouter kernel: [100495.644000]  [filldir64+0/224] filldir64+0x0/0xe0



142

Users / Can I resize web Orbiter ?

« on: January 15, 2008, 09:21:46 pm »

Hi,

I'd love to try web orbiter on 640x480 3Com Audrey gadget. But I guess it would need that size of Orbiter with it, but I couldn't find web orbiter on Orbiters page to select screen size...

Also, since various devices can connect to Web Orbiter, is it somehow possible to change it's settings according to type of client that connects and can it be customized on any way (to somehow dictate web page template to get different position of buttons, etc...)


Thanks in advance,

regards,

Bulek.

143

Users / Playing with 2 x-lite clients and video calls under LMCE

« on: January 14, 2008, 04:00:11 pm »

Hi,

I'm working on telephony features in new house that is based on LMCE... I have 3 entry points in telephony : doorphone, GSM incoming line, and IP telephony. I will probably describe how to do such setup soon, but currently I'm trying to get/test video capabilities of current system.

I use 2 x-lite clients (thanks for recomendation from Andrew). Since video telephony is not supported on Orbiter phones, I'm trying to do it with windows clients (it would be nice to be able to make video call from work to home office with x-lite clients on both sides)...

In near future, I also sincerely hope, that we will be able to get video telephony going on embedded Orbiter phones (they are based on linphone already, and newer version of LinPhone supports Video !!!!)...

But in the mean time, I play with window clients, and I spot that video is transferred only in one direction - only from calling party to end point and not vice versa...

I have also posted to asterisk mailing list, but maybe there are also some experienced Asterisk guys in here....

Any advice, hint ?

Thanks in advance,

regards,

Bulek.

I have done following :
2 x-lite clients :
[201]
username=201
type=friend
secret=LMCE!201
record_out=Adhoc
record_in=Adhoc
qualify=yes
port=5060
nat=never
mailbox=201@device
host=dynamic
dtmfmode=rfc2833
disallow=all
context=from-internal
canreinvite=no
callerid=device <201>
allow=ulaw
allow=alaw
allow=gsm
allow=h263
allow=h263p

[204]
username=204
type=friend
secret=LMCE!204
record_out=Adhoc
record_in=Adhoc
qualify=yes
port=5060
nat=never
mailbox=204@device
host=dynamic
dtmfmode=rfc2833
disallow=all
context=from-internal
canreinvite=no
callerid=device <204>
allow=ulaw
allow=alaw
allow=gsm
allow=h263
allow=h263p


sip.conf :

; Note: If your SIP devices are behind a NAT and your Asterisk
;  server isn't, try adding "nat=1" to each peer definition to
;  solve translation problems.

[general]

port = 5060           ; Port to bind to (SIP is 5060)
bindaddr = 0.0.0.0    ; Address to bind to (all addresses on machine)
disallow=all
allow=ulaw
allow=alaw
context = from-sip-external ; Send unknown SIP callers to this context
callerid = Unknown
videosupport=yes ; enable Asterisk video support

#include sip_nat.conf
#include sip_custom.conf
#include sip_additional.conf

144

Users / Adding softsqueeeze as LMCE's player

« on: January 14, 2008, 09:51:57 am »

Hi,

I just tried to add softsqueeze to fake LMCE to think it's HW player. I sent detection message and it got "detected", but it seems that it's not controllable through LMCE. Something is different, so it doesn't work. But it would be nice to have player on your laptop winPC, that could be synchronized with HW squeezeboxes and controlable from LMCE....

Anyone with more experience doing this  ?

Regards,

Bulek.

145

Users / Squeezebox not recognized plug'n'play

« on: January 11, 2008, 09:40:13 pm »

Hi,

I've aded brand new Squeezebox to LMCE's lan, it got ip address from DHCP, but after that nothing happened (neither on hybrid Orbiter, neither on other winxp PC with Orbiter running). I've done this :

1. Set squeezebox to dhcp
2. connect to LAN
3. it gets ip address of 192.168.0.191
4. then nothing happens (I'm expecting screen to appear on Orbiters)...

I'm attaching two logs below.... What is wrong ? (Have described here also : http://mantis.linuxmce.org/view.php?id=3802)

I have also another problem - in the meanwhile I'd like to add squeezebox to system manually - but don't know how to do it (is it Slimserver first, and then SB as child, or somehow different - can any user with squeezebox help in setting it up manually ?

Additional Information    dhcpd.log :
00 Fri, 11 Jan 2008 00:04:33 +0100 DHCP : MAC '00:04:20:12:52:c8' IP '192.168.0.191'
00 Fri, 11 Jan 2008 00:04:33 +0100 NEW DEVICE !!!


Plug'n'play plugin :

Received Message from 1 (CORE / Home Theater) to -1001 (unknown / ), type 2 id 65 Event:Device Detected, retry none, parameters: <0xb3cc7b90>
07 01/11/08 0:04:33.727 Parameter 5(Mac Address): 00:04:20:12:52:c8 <0xb3cc7b90>
07 01/11/08 0:04:33.727 Parameter 13(Text): <0xb3cc7b90>
07 01/11/08 0:04:33.727 Parameter 28(IP Address): 192.168.0.191 <0xb3cc7b90>
07 01/11/08 0:04:33.727 Parameter 49(PK_DeviceTemplate): <0xb3cc7b90>
07 01/11/08 0:04:33.727 Parameter 51(VendorModelID): <0xb3cc7b90>
07 01/11/08 0:04:33.727 Parameter 52(PK_CommMethod): 3 <0xb3cc7b90>
07 01/11/08 0:04:33.727 Parameter 53(PK_PnpProtocol): 2 <0xb3cc7b90>
07 01/11/08 0:04:33.727 Parameter 54(PNP Serial Number): <0xb3cc7b90>
07 01/11/08 0:04:33.727 Parameter 55(DeviceData): <0xb3cc7b90>
07 01/11/08 0:04:33.727 Parameter 56(Category): <0xb3cc7b90>
07 01/11/08 0:04:33.727 Parameter 59(Signature): <0xb3cc7b90>
05 01/11/08 0:04:33.767 Socket::ReceiveData 0x88b9818 failed, bytes left 0 start: 1340000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 119 Incoming_Conn Socket 119 127.0.0.1 <0xb3cc7b90>
05 01/11/08 0:04:33.767 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 119 127.0.0.1 <0xb3cc7b90>
05 01/11/08 0:04:33.767 TCPIP: Closing connection to -1003 (Router Dev 0) 0x88b9818 m_Socket: -1 <0xb3cc7b90>
05 01/11/08 0:04:33.767 Router::RemoveAndDeleteSocket 0x88b9818 -1003 <0xb3cc7b90>
07 01/11/08 0:04:40.263 Event 4 has no handlers <0x79eabb90>

146

Users / What softphone to use for external winxp client ?

« on: January 11, 2008, 01:06:11 pm »

Hi,

I'm slowly beggining to put new LMCE system in my new demo house with all needed functionalities. I'm about to work on adding telephony features.

I'm stuck with selection of best softphone to be used on laptop on remote locations, to be client for LMCE's Asterisk...

What I'd like to see is also video functionality. Currently I'm considering Linphone (it supports video and our Embedded Orbiter phones are based on that platform - so I guess we could eventually see also embedded video phone on MDs ? )...

But I have problem connecting it to Asterisk - it also has lack of support for phone books, etc...

What softphone do you you most easily inside and outside your local network ?

Thanks in advance,

regards,

Bulek.

147

Users / Asterisk not started under 704 ?

« on: January 11, 2008, 09:42:26 am »

Hi,

I have pretty untouched 704 installation.
I spot that Asterisk is not running at all (ticked that option on Core page)

Asterisk wrapper says :

01   01/11/08 9:32:26.284      failed connecting to asterisk manager <0xb68f8b90>
01   01/11/08 9:32:31.287      failed connecting to asterisk manager <0xb68f8b90>
01   01/11/08 9:32:36.291      failed connecting to asterisk manager <0xb68f8b90>

It seems that Asterisk is not started at all - if I run it from command line, then wrapper connects and seems to be fine...

Where can I check why Asterisk is not running by default settings ?

Thanks in advance,

regards,

Bulek.

148

Users / Transferring main hard disk content to bigger disk ?

« on: January 08, 2008, 07:07:46 pm »

Hi,

I have 320G IDE hard disk that my hybrid boots from. I have another fresh 500G ide hard disk and would like to transfer content to it, and replace smaller disk completely...

Any easy procedure to do that (regarding different size of disks - partitions) ?

Thanks in advance,

regards,

Bulek.

149

Developers / Implementing a way to show various device data on floorplan - need comunity help

« on: January 07, 2008, 12:13:44 pm »

Hi,

as promised here (http://forum.linuxmce.org/index.php?topic=3609.msg20529#msg20529), I talked to Chris (Pluto developer) and asked about current state of adding support for showing data for various devices on Orbiter floorplans. It seems that this interests more and more LMCE users, since currently only very limited number of devices can be properl shown and controlled from floorplans.

Chris agreed to help with necessary info - originally Eugene was meant to code this, but he cannot do that... Chris added few comments on this mantis thread for a start :

http://mantis.linuxmce.org/view.php?id=3456

I'd be glad for your comments and if there is anyone willing to contribute work in this direction. Chris will help with all info needed - he claims that it's pretty straight forward... He will respond to mantis thread notes...

The whole idea is pretty simple (no new events or whatever). Just ability to add another device data to device templates that would specify what will be shown on floorplan (if at all) - this could be another device data entry or just simply device state... Orbiters will refresh that info every few seconds and I think this is good enough...

I also described few more info about how Orbiters show info for devices on floorplan (but don't know if that info applies) :
http://wiki.linuxmce.com/index.php/Adding_support_for_floorplan_devices

Anyone willing to help and work with Chris ? Any other opinion ?

Thanks in advance,

regards,

Bulek.
 

150

Developers / How can I implement automatic light detection/configuration procedure-like Zwave

« on: December 26, 2007, 07:21:07 am »

Hi,

when you install lmce, you get to lighting section and if you have ZWave for instance, there is automatic procedure for determining proper location for all autodetected light modules...

I wonder about internals of that procedure... How is it implemented ? Is it "external" implementation or is standard procedure that you can use also from other automation devices ?

Anyone with more insight into this ?

Thanks in advance,

regards,

Bulek.