Messages

46

Developers / Re: Sample code from the GSD/Ruby Webcast

« on: July 17, 2008, 09:51:05 pm »

Hi ddamron,

too bad I could not attend the webcast; I understand this sample code is for GSD, thus run from one of the lmce processes.

I would like to have a standalone ruby script (launched from command line) that connects to DCE to send messages and get events. Would you have some sample code for that ?

47

Users / Re: Problem when transferring larger files to LMCE public share

« on: July 07, 2008, 11:45:32 am »

bulek, just a shot in the dark: does it happen also after disabling Update Media (or the whole core processes altogether) ?

48

Feature requests & roadmap / Re: New Media Navigation Facility

« on: May 24, 2008, 09:24:58 pm »

For what it's worth, I had a similar problem: I could access /mnt/device/40/public but the media was not seen in the orbiter.
I found out that LMCE was setting the flag "Online" to off when it couldn't reach the server, and never switched it back on.
So going to the web admin, to the NFS share and enabling "online" again fixed it for me (after doing all the permission verifications explained earlier in this thread). Not sure if you have the same problem, but it's worth checking.

49

Users / Re: Responding to z-wave sensor events

« on: May 20, 2008, 09:31:51 am »

I used to send a Delay command to DCErouter but now I am just catching the "sensor triggered == 0" which is sent by the sensor when no movement is detected. On my zwave PIR sensors, it conveniently does it a few minutes after it's triggered. I didn't test whether the timer in the sensor itself was reset when more movement is detected.

50

Users / Re: Responding to z-wave sensor events

« on: May 19, 2008, 05:43:40 pm »

I'm successfully using the sensors to turn on the lamps now, but the "time of day" criteria does not work for me. First there was a mistake: "DAYTIME" does not exist so the condition was always true. The right one seems to be "Daytime". However, it seems that "time of day" is always set to "Daytime" which means the event is never triggered.

Any idea where that variable is supposed to be updated ?

51

Users / Re: Shared folders disappearing and network weirdness

« on: May 19, 2008, 05:40:56 pm »

Have you modified the template like Bulek suggested ?
I think it's the one in /usr/pluto/templates/smb.conf.template

I'm doing this for /etc/fstab and /etc/exports and it seems to work well.
Sam

52

Users / Re: Responding to z-wave sensor events - SOLVED

« on: May 15, 2008, 09:30:07 pm »

So the correct value for an event "sensor tripped ON" is 1 and not 255 as I had configured, which gives:
- Respond to events
- An sensor is tripped
- What device = "sensor hall"
- What time of day <> "DAYTIME"
- Event parameter "triggered" = 1
- action: switch on a light nearby

I have also added a handler for sensor tripped OFF (0) which turns off the line after a small timer. Neat.

The error

Code: [Select]

SendSensorTrippedEvents: wrong node ID:
remains, but it doesn't harm...

happy

53

Users / Responding to z-wave sensor events

« on: May 14, 2008, 12:11:20 am »

I have added two z-wave PIR sensors and defined the event handler as follows:

- Respond to events
- An sensor is tripped
- What device = "sensor hall"
- What time of day <> "DAYTIME"
- Event parameter "triggered" = 255
- action: switch on a light nearby

When I trigger the sensor I get this in the ZWave logs:

Code: [Select]

05      05/14/08 0:01:16.866            alarmPIRHandler : node: 18 report: 255 <0xb68f9b90>
05      05/14/08 0:01:16.867            SendSensorTrippedEvents: wrong node ID: 18, 19 <0xb68f9b90>
05      05/14/08 0:01:16.867            SendSensorTrippedEvents: wrong node ID: 18, 2 <0xb68f9b90>
05      05/14/08 0:01:16.867            SendSensorTrippedEvents: wrong node ID: 18, 3 <0xb68f9b90>
05      05/14/08 0:01:16.867            SendSensorTrippedEvents: wrong node ID: 18, 4 <0xb68f9b90>
05      05/14/08 0:01:16.867            SendSensorTrippedEvents: wrong node ID: 18, 5 <0xb68f9b90>
05      05/14/08 0:01:16.867            SendSensorTrippedEvents: wrong node ID: 18, 6 <0xb68f9b90>
05      05/14/08 0:01:16.867            SendSensorTrippedEvents: wrong node ID: 18, 8 <0xb68f9b90>
05      05/14/08 0:01:16.867            SendSensorTrippedEvents: wrong node ID: 18, 11 <0xb68f9b90>
05      05/14/08 0:01:16.867            SendSensorTrippedEvents: wrong node ID: 18, 12 <0xb68f9b90>
05      05/14/08 0:01:16.867            SendSensorTrippedEvents: wrong node ID: 18, 13 <0xb68f9b90>
05      05/14/08 0:01:16.867            SendSensorTrippedEvents: wrong node ID: 18, 14 <0xb68f9b90>
05      05/14/08 0:01:16.867            SendSensorTrippedEvents: wrong node ID: 18, 15 <0xb68f9b90>
05      05/14/08 0:01:16.867            SendSensorTrippedEvents: wrong node ID: 18, 16 <0xb68f9b90>
05      05/14/08 0:01:16.867            SendSensorTrippedEvents: wrong node ID: 18, 21 <0xb68f9b90>
05      05/14/08 0:01:16.867            SendSensorTrippedEvents: wrong node ID: 18, 1 <0xb68f9b90>

Two questions:
- is the config correct ?
- what does the wrong node ID message mean ?

thanks in advance...

54

Installation issues / Re: Z-WAVE: How to get Seluxit ViaSENS Homecontroller to work?

« on: May 13, 2008, 07:30:51 pm »

I did my production installation with a ZTH200 but aside from that, I have done some tests with the seluxit controller, a spare dimmer module and z-tool before I added it to LMCE, and I was able to use it as a primary controller with Z-Tool and the software from seluxit (http://www.seluxit.com/download/software/ - I used Alpha1). So a hardware controller may not be required after all.

55

Users / Re: Current State of VDR vs MythTV

« on: May 05, 2008, 09:06:26 am »

Darren,

according to this post from Michael: http://smart-home-blog.com/archives/1001 the VDR integration is not complete, e.g. you cannot use it independently on MD. For that reason I am going to switch back to Myth on my next install.

The answers to your questions should be "yes to all".

I stand to be corrected :-)
Sam

56

Users / Re: CM11a gives Exception on serial port

« on: April 15, 2008, 11:31:33 pm »

Thanks a lot NOS... I've re-installed with the trac ticket and was still getting the same problem... Checking the source I found that the serial port was not supposed to say "0" but a full string with the serial device. So it had to be wrong and guess what, the port was not set in the web admin any more :-)
No idea why it has been de-configured, but that's another story. Thanks !

57

Users / Re: CM11a gives Exception on serial port

« on: April 15, 2008, 09:22:03 pm »

Hi William,

thanks for your answer. For sure, I do search the forums. In this particular case, I have been following the issues with CM11a for about two years in pluto. And in particular the topic you mention.

The issue I am referring to is not the 0x05 checksum error, but a new problem I am reporting here happens with the latest sources, which - unless I am mistaken - contain the fix from jondecker76.

A search in the forums for "Exception occured" does not lead any result, and I have read all CM11a threads I could find. So I opened a new thread because it is a different issue. Sorry, professional bias ;-)
Maybe I am missing something ? Any suggestion is welcome.

thanks,
Sam

58

Users / Re: x10 CM11A support is now fixed!

« on: April 15, 2008, 04:12:49 pm »

Is anyone seeing this with the svn sources ?

Code: [Select]

Exception occured on CM11A's serial port: 0. Sleeping for 5.1 second.

It has worked for a while, not sure what changed...

59

Users / CM11a gives Exception on serial port

« on: April 14, 2008, 09:31:26 pm »

I've been using the new CM11a code from svn happily for a while, but now I am getting a lot of these error messages in the logs (and cannot control lights any more):

Code: [Select]

Exception occured on CM11A's serial port: 0. Sleeping for 5.1 second.

The CM11a is connected via a gc100, but if I stop the CM11a process and run heyu, I can control the CM11a which indicates that the gc100-serial-bridge is working fine.

Any idea ?

60

Feature requests & roadmap / Re: feature request-dreambox intergration

« on: April 13, 2008, 11:10:23 am »

There seems to be support for dreambox running the "neutrino" firmware (you can google for it), although I'm not sure how maintained it is, or if workable at all.

There are clones of dreamboxes, like the itgate, which can run some of the firmwares for the dreambox (like "enigma") but I don't think it supports the "neutrino" image