Messages

91

Users / Re: Advice On New Setup - Hardware/Networking

« on: January 09, 2011, 10:54:37 am »

Bear in mind some user pages are plagiarised though, hey Valent?

Jup, I tool your intro, maybe I should have asked for permission first? Sorry, but you just said exactly what I thing but don't have such english writing skille to write it on my own so I borrowed your intro. The rest is mine "original" work

92

Users / Re: *WARNING* IMPORTANT MESSAGE for all people using "free email" accounts.

« on: January 09, 2011, 10:52:08 am »

Some spam prevention modules have been installed. In theory they should make life hard for the spammers, but should be OK for real people. I never used these before, so I have no idea if they'll behave themselves. If they misbehave, please drop me a line.

Do you know which plugins exactly got installed? I have other forum that I co-admin so that I can take a look at them.

Thanks.

93

Users / Re: New power controller: Tellstick

« on: January 09, 2011, 12:11:04 am »

Whoow, cool. Tellstick could replace ZWave in some simpler installations.

Can you please share any links to web shops that sell european compatible (220V) equipment that works with tellstick.

Thank you very much once more for your contribution!

Cheers,
Valent.

94

Users / Re: Advice On New Setup - Hardware/Networking

« on: January 08, 2011, 11:57:29 pm »

First read wiki and look what other people are using:
http://wiki.linuxmce.org/index.php/Category:User_Setups

95

Users / Re: Chromoflex RGB LED controller supported in 0810

« on: January 08, 2011, 11:52:13 pm »

Got one Chromoflex II to play with and LED strip 2m long. Just playing with Chromoflex effects is nice but I would like now to connect it to lmce and see what can I do with it then.

How do I connect Chromoflex to Core? I see that Chromoflex has only two pins, one to receive data and ground pin. So I guess that I need to connect pin 3 (data send) on Core PC to RX pin on Chromoflex, right?

96

Users / Battery powered ZWave switch

« on: January 08, 2011, 10:01:10 pm »

Hi guys,
I bought Battery powered ZWave switch [1], and I must say that it looks just awesome! It is super thin, and when installed on the wall it wont be any thicker than regular wall switch (huge bonus!).

Just imagine that you finished renovating your flat or house and see that you need few more light switches. Instead of engineers coming back and punching new holes in your walls you just install new battery operated wireless zwave switches and you are done.

It seams that doing inclusion and association is a bit complicated on this device, even more that doing inclusion of security battery powered devices And german only manuals are not much help.

Anybody got this switch? How did you do inclusion and associataion?

Any help is apprecaited.

Cheers,
Valent.

[1] http://wiki.linuxmce.org/index.php/D%C3%BCwi_Popp_ZW_WS_05443

97

Users / Re: ACT Homepro ZTH200 remote

« on: January 06, 2011, 10:13:17 am »

Nice device but does not work as inclusion Controller in SIS mode.

Which remote do you suggest?

98

Users / Re: Newbie needing help with build

« on: January 06, 2011, 10:07:49 am »

@ghope5 and @Tinkerbot please also consider other newbies that come to this forum and when create wiki pages for any gear that you have tested with lmce so that we get better wiki pages with more hardware gear listed working ok and especially gear that has some quirks.

Cheers,
Valent.

99

Users / Re: Z-wave woes - Everspring door/window sensor not behaving

« on: January 06, 2011, 10:03:47 am »

you need to put the dongle's node id into the association group 1 of the everspring sensor.  From the manual:
"The Door/Window Detector supports one association group with five nodes. This has the effect that when the Detector trigger, all devices associated with Detector will be operated."

so please RTFM: http://wiki.linuxmce.org/index.php/Everspring_SP103#Association
then send a "Set Association" command to the ZWave device, with the following parameters:
#239 - the node ID of your everspring sensor (can be seen in the port/channel field)
#249 - group number, this is 1 for this device
#250 - the node id of your dongle, probably 1 when you are using the crap dongle with the inclusion button

Hari

I have done inclusion and association, but how to check and where that I did association correctly? Is there a way to list which device is associated with Aeon labs dongle?

#239 - channel for motion sensor is 7 and for door sensor 8
#249 - group is 1
#250 - aeon labs controller channel is 1

UPDATE: I got both SP103 (motion sensor) and SM103 (door sensor) to work and send trigger events!

Caveat #1: Motion sensor and led light
When I first turned on SP103 motion sensor whenever it's motion sensor was tripped red led light turned on, so it was an really easy to understand visual cue that device was working. After including motion sensor to my LinuxMCE via Aeon labs ZWave stick there was no led flashing when motion sensors was being tripped so I thought that motion sensor wasn't working and wasn't sending any alarm info to lmce, but it was. I just didn't know where to look and how to check if it was working ok or not. Now I know that all I need to do is look in webadmin Security > Status
After I done inclusion and association motion sensor showed tripping (motion detected) in webadmin Security > Status page.

Caveat #2: Door sensor needs convincing
Even after I got motion sensor to work my other sensor (door sensor SM103) didn't report any activity in Security > Status page. I tried triggering tamper switch, openning and closing doors, leaving door open, etc... but no activity showed in lmce webadmin page
Only after I deleted device from lmce, excluded it from my zwave network and repeated inclusion and association process I got it to work! First difference I saw was that now door sensor isn't using channel 8 anymore but that it is now on channel 10. And now everything works. When I open the door lmce gets signal immediately that door sensor is tripped.

I'm really, really happy that I got these sensors to work and now I can finally go do some more exciting stuff with programming lmce and making my flat smarter.

100

Users / Re: Z-wave woes - Everspring door/window sensor not behaving

« on: January 04, 2011, 08:54:07 pm »

Ok, deleted rogue device, removed and plugged aeon labs stick back in and now I got generic device back:
http://dl.dropbox.com/u/184632/generic_01.png
http://dl.dropbox.com/u/184632/generic_02.png

This looks ok, right?

101

Developers / Re: Preliminary 10.04

« on: January 04, 2011, 08:35:35 pm »

it is not the runlevel.  There is a couple of variables that when anded together will cause a true and reboot.  The problem is when the preferred driver is compared to the installed driver in a function in nvidia-install.sh they don't match as they should once the preferred driver installs.  I know this is the case since I changed a variable value in the function and stopped it from rebooting.  I got AVWizard and setup wizard to run and then the orbiter finally came up running.

So a change has to be made in how the name of the preferred driver is returned so that a match is eventually gotten.  I can see the result in the nvidia-install.log file.

Which variable you changed? I would like to continue testing 10.04 so please share info on how to stop rebooting it.

Thanks.

102

Users / Re: Z-wave woes - Everspring door/window sensor not behaving

« on: January 04, 2011, 08:31:30 pm »

I'm going to buy Seluxit ZWave controller but until it gets here all I have to work with is Aeon labs ZWave usb controller.

I associated SP103 and SM103 security sensors with Aeon labs stick and after plugging it back in into Core they got recognized and I edited descriptions via webadmin UI.

Even if I choose in which room each device is in next time I plugged in Aeon Labs wizard popped up and said that both security devices are not assigned to any room so I choose rooms again via video wizard.

http://wiki.linuxmce.org/index.php/Everspring_SM103:
http://dl.dropbox.com/u/184632/door_01.png
http://dl.dropbox.com/u/184632/door_02.png

http://wiki.linuxmce.org/index.php/Everspring_SP103:
http://dl.dropbox.com/u/184632/motion_01.png
http://dl.dropbox.com/u/184632/motion_02.png

After editing "PK_FloorplanObjectType" and adding "door" as object type sensor moved outside zwave device tree

What is going on? What should I do? Delete all devices and start over? Report bugs? Any other suggestions?

Cheers,
Valent.

103

Installation issues / Re: Home Remote HRDS1 Door Sensor not able to complete setup

« on: January 04, 2011, 07:10:49 pm »

ignore the wizard (until somebody feels like fixing it), use it as generic sensor (created automatically), assign it to a room and add a "door" icon from the webadmin..

br Hari

Assigning rooms is easy but I just don't see any option for adding door icon from webadmin, can you please help.

Cheers,
Valent.

104

Users / Re: ACT Homepro ZTH200 remote

« on: January 04, 2011, 05:55:56 pm »

Hopefully now others who have this device can fill in LinuxMCE relevant data and take out other info that is not relevant to LinuxMCE.

105

Users / Re: LinuxMCE 8.10 --> 9.04 upgrade fail

« on: January 04, 2011, 05:54:31 pm »

I know that upgrading to new version has a lot of issues but I had to try for myself and see how much stuff would break while doing distr-upgrade.

I needed to do a clean reinstall so I figured to try and see what happens during dist-upgrade. Now I know that everything breaks.