LinuxMCE Forums
General => Users => Topic started by: mikeybs on September 12, 2014, 10:25:45 pm
-
I am playing around with a couple of these and I have gotten them working well as a motion sensor.
I have not been able to get the temperature, light-level, humidity sensors to provide any information.
From this post it seems that temperature and motion work, but not light level
http://forum.linuxmce.org/index.php?topic=11674.0
I placed the temperature sensor on my floor plan and I see the thermometer on my floor plan. I can select it and it displays the name "temperature sensor", but it does not show what the current temperature is.
If I open the climate section of the web admin, and open the advanced page of the temperature sensor, "state" and "status" are blank...
In the advanced zwave page the device usually appears as a yellow dot, status = "ok" , awake = "No"
-
Hi mikeybs,
Any progress with this?. I just installed one last night. And can see 4 sensors detected. Light sensor and temperature, the other two are detected as generic. did you manage to get at least one working?
Cheers,
T
-
Please contact sambuca on irc about the status of zwave items. He has been quite busy lately. :)
J.
-
Thanks Phenigma!!.... .. how do i do that (IRC)? :o ;D
-
Initially use the web client: https://webchat.freenode.net/
Join #linuxmce as the users channel, and type in sambuca'a nick name and a description of what you are trying to do. Stay connected to irc as users are all over the world and will respond when they are around.
J.
-
hi tompin2,
Are you using 1004 or 1204 ?
In 1204 the zwave has changed a lot so I would think the device mostly works out of the box.
br,
sambuca
-
I have one of them. As a battery powered device it is not very reliable. Try using USB-power cable. then it is much more responsive.
I'm using two Fibaro motion sensors. They work as expected (except tamper detection which is not used by LMCE atm). With the latest lmce-updates brightness level can be used in the state field. I'm testing this right now.
Getting them to work was a bit time consuming. I had to wake them up several times manually to let my Aeon stick get all the needed device info over the mesh network.
In my OZW setup I disabled polling completely. There were too many messages flying around and RTT were very high.
Using 10.04 and ZWave is not a good decision. 12.04 and Zwave is much better.
My hints:
- wake up device (3 button presses) 2-3 times
- be patient, battery powered devices are not so responsive
- check Advanced Zwave page, if device has been fully configured
- check Advanced Zwave page, if device has "values".
- check ZWave.log if the device reports values (especially brightness and temperature) to the correspondend LMCE-devices
- check node instances, e.g. temperature ist instance 1 ("12/1"), brightness is instance 2 "12/2", motion has no instance ("12").
-
I'd like to receive feedback as to how the brightness detection is working for others. It was created as part of a LinuxMCE installation on Cypress for one of our sponsors.
-
My observation of brightness detection with zwave sensor until now:
- brightness value is appearing correctly in web admin in "state" field -> so ok
- I created some events: if device's (brightness sensor) state field contains values lower than 150 (e.g.) AND motion is detected then turn on light
- basically light turns on, when movement is detected in the dark. But in more than 70% of all occurings light does not turn although movement is detected and it is dark.
ATM I try to find out, why it is not turning on. Unfortunately I did not have the time to look a little more into the logs to find out what is going on exactly.
-
hi tompin2,
Are you using 1004 or 1204 ?
In 1204 the zwave has changed a lot so I would think the device mostly works out of the box.
br,
sambuca
Hi Sambuca,
Im using 1204... so far it seems to be detected but I get no values, there must be something Im missing.
Follow log of main zwave controller (zstick), are here.
05 10/05/15 22:22:24.968 * Device id = 22, dt = 1813 (Generic Sensor), main label = Sensor, pk_parent = 182 <0xb6e23700>
05 10/05/15 22:22:24.968 -> Already mapped to device, PK_Device=206 <0xb6e23700>
05 10/05/15 22:22:24.968 * Device id = 22/1, dt = 1744 (Temperature Sensor), main label = Temperature, pk_parent = 181 <0xb6e23700>
05 10/05/15 22:22:24.968 * Device id = 22/2, dt = 1745 (Brightness Sensor), main label = Luminance, pk_parent = 181 <0xb6e23700>
05 10/05/15 22:22:24.968 * Device id = 22/3, dt = 1813 (Generic Sensor), main label = , pk_parent = 0 <0xb6e23700>
Values under advance zwave
Values
Index Label Value Units Genre PK_Device Polled
0 Sensor False user 206
0 Battery Level 100 % user 206
1 Minimum Wake-up Interval 0 Seconds system 206
2 Maximum Wake-up Interval 0 Seconds system 206
3 Default Wake-up Interval 0 Seconds system 206
4 Wake-up Interval Step 0 Seconds system 206
0 Wake-up Interval 0 Seconds system 206
0 Library Version Unknown system 206
1 Protocol Version Unknown system 206
2 Application Version Unknown system 206
1 Temperature 0.0 user 207
3 Luminance 0.0 user 208
5 Relative Humidity 0.0 user 209
Any hints?
-
Hello to all,
Ok I have finally reach to a better test. I deleted the sensor from using the remote. Reload the sensor again.
lmce detected:
Temperature as instance 1 (23/1)
Brightness (23/2)
and two generic sensor
Generic 23 (suppose is motion)
Generic 23/3 Could this be humidity?
I had to press the button at the sensor in order to make it alive, before that, it was posting no values.
So at the zwave advance, under values it started posting values as the picture attached.
This sensor has motion, temp, luminescence and humidity. Temp is totally off is there a way to calibrate or to shift values.
How can I let LMCE battery values?
Ill continue testing and keep all posted
T
-
I finally removed the Aeon device completely from my home.
My observations:
- temperate is measured in F not C
- temperature values are far away from "reality" (x/1)
- luminance level is ok (x/2)
- motion detection is ok (x)
- humidity values shown in log, but not in lmce (x/3)
- device fires brightness level changes (1 lux!) too frequently what leads to unresponsive mesh network
- in battery mode it is nearly unusable
- use of usb power makes it more responsive
-
Guys, what sensor is this exactly? Can you be more specific than 'multisensor'? :)
J.
-
Aeon Labs 4in1 Multisensor ( The old one!)
http://wiki.linuxmce.org/index.php/Aeon_Labs_Z-Wave_Multisensor
-
Thanks! :)
J.
-
I finally removed the Aeon device completely from my home.
My observations:
- temperate is measured in F not C
- temperature values are far away from "reality" (x/1)
- luminance level is ok (x/2)
- motion detection is ok (x)
- humidity values shown in log, but not in lmce (x/3)
- device fires brightness level changes (1 lux!) too frequently what leads to unresponsive mesh network
- in battery mode it is nearly unusable
- use of usb power makes it more responsive
Thanks for the feedback Rebelkiller!..., I guess thats a nice way to say ... don't waist your time!! hahahahaah.
Are you using a better zwave sensor with at least movement, temp and luminance? One you could recommend?
-
I'm using two Fibaro Multisensors FGMS with no problems. The only thing that does not work is tamper detection. But i do not need this. The Fibaros are much smaller and look nice.
Greets
Bernd
-
I have a HomeSeer HSM-100 that works well.
I also have a new Aeon Labs Gen5 MultiSensor 6 that I am unable to get motion detection events from, everything else appears to work, but I cannot send configuration values to it either for some reason. I have no idea why at this point.
J.
-
Thanks Phenigma and Rebelkiller,
Ill get a pair of Fibaro Multisensors FGMS which are easy to get via amazon and start doing test.
Since I had nothing to loose, I tried to update the firmware of one of the aeon sensors. It got killed!, it just blinks and that's it!.. So how to I remove it?. Manually remove, do I have to do anything else on the controller?. I kept the other sensor untouched as reference point and for torture purposes... There most be a way to make them speak to lmce!!!
Cheers,
T
-
Fibaros:
The Fibaros need 1-3 attempts ("wake-up") do be fully configured and recognizes by lmce. So be patient. ;)
Aeon:
You must exclude them from mesh network und do a (or two) router reload. Your Zwave-Stick still has all formerly included devices in its database und will try to bring them up. It will not be possibe to delete a device only by deleting the device in lmce. After next reboot you will get the device back (as new device with a new #id). so my solution:
- remove the working one by (first!) excluding it from mesh network and then remove the obsolete lmce devices in lmce-admin.
- dealing with the killed one you will have two options:
1. reset the whole mesh network by completely reset the controller und start adding all devices again. This will cost you hours, since you must reconfigure all of your scenarios, configuration entry and so on (depending on your config). OR
2. just disable the lmce-devices und ignore this dead device in the future. Then you should do a network heal afterwards just to give mesh network information alternative routes.
Greets
bernd
-
Hey everyone,
I've upgrade openzwave to 1.3.1224, this should end up hitting the repository very soon. A lot more configuration files are available for many, many devices. The new Aeon Labs Gen5 MultiSensor 6 works perfectly now.
When then upgrade comes through you can "rm /etc/openzwave/zwcfg*" and restart your ZWave device for any of your devices to be re-detected by openzwave with the new configuration files. You should not have to adjust anything in your ZWave network or your LMCE device tree.
Happy LMCEing!
J.