Messages

both are irrelevant afaict. This is a new *ZWave* device. It must be known to our ZWave stack, as LinuxMCE already knows about motion detectors. If I were in your shoes, I would create an issue on git.linuxmce.org make a note of all the information you have, and assign it to sambuca.

Hi Posde, I have created the issue (mistakenly I created a project  ), but now that finally understanding a little bit better the git interface, i´m unable to assign it to sambuca, I guess ill assign it to me for now.
Regards,
T

For signing into git, send a message to polly with your desired username and email address.

Thanks for the info, Ill work on that an keep all posted.

Cheers,
T

Ok, i got the motion sensor of my HSM100 sensor working.
This is what i had to do:

First i deleted the Motion Detector #54 DT, that i added, from the tree.
Then i did a reload and added the Motion Detector #54 DT again.
After this, i did another reload, this one is not mentioned in the wiki, but as far as i can tell at the moment, this is the one thats important, because as far as i know, when doing a reload, all DT's and child DT's get properly read again.
After this i did a sudo killall ZWave to restart the ZWave device.
Then i opened the Advanced ZWave page in webadmin, looked up the device and opened its Associations tab.
I had to set a association from the group motion to the controller node 1, this was not done automatically.
This is necessary, because only when set, the controller gets motion events.

Did another reload and a bit of rule #1 and voila, everything in working order.
Hope this helps you too,

br,
Raymond

EDIT: i updated the wiki with the above info.

Thanks Raymond,  I would like to help to make this devices PNP so it is more easy for non guru as me to get more out of LMCE for less effort.  In the mean time I might give it a try 

both are irrelevant afaict. This is a new *ZWave* device. It must be known to our ZWave stack, as LinuxMCE already knows about motion detectors. If I were in your shoes, I would create an issue on git.linuxmce.org make a note of all the information you have, and assign it to sambuca.

Thanks Posde!  How can I sign in to the git site, is it the same as this forum?  I may have to create more issues to more unknown Zwave devices like the KWIKSET lock, already got one, first alert smoke carbon monoxide alarm and a zwave sounder WA105BDZ.

Can you please provide update on your experience. I am planning to go for z-wave stick gen5 route and probably add some dimmer switches and more.

I am also on 14.04 install.

Thanks.

Hi Theteju,
No much luck so far due to I cant find detail documentation on the ZWN-BPC.  I would like to know which "# number" does what so I can make a new device.

If you go the 14.04 and zstick Gen5 you will be ok.
I have up and running.
4 leviton vrcs2-mrz , Many dimmers and single switches, 1 3way configuration etc, etc. 
Total of 25 zway switches.

If any one have a hint on how to make a new device.. Im all ears.

T

Dear All,

Im trying to get this zwave motion sensor to work but no luck so far.  I am able to add it to the network without any issues.
It gets detected as a generic sensor.  First try was to delete it and use the same port detected and add it again as Device Template #54, following this  procedure http://wiki.linuxmce.org/index.php/Express_Controls_EZmotion_%28HSM_100%29, still I believe the template might now be correct.

Here Is what I have:
LMCE 1404
zstick gen5

What is on advance zwave:
Unknown: id=011a

Unknown: type=0601, id=0901

I will continue searching on data online to see if I'm able to get it to work and continue posting as I Go.
Ill probably start adding more post for more test that are on the queue, the will be the same subject form but different device.  Next coming up is (WA105DBZ Z-wave sounder, KWIKSET z-wave lock)

Cheers,
T

Hi to all,

Here is some feedback.  Im running 1404 since a couple of days now and qt5 on a Samsung s6 is working ok.  Just a couple of buttons that dont do what they are supposed to.
Listed right below:

Power: it only have: Power off display, Power off MD, Reboot Core, Reboot MD.  There is no POWER ON.  POWER OFF DISPLAY works, POWER OFF MD doesn't.  I did not tested the other two!  It could have cause caos in the family

VIDEO: It does not have the ALL button, so if you dont have properly setup your DB, it will be impossible to find your files, but right I get nothing.  None of the movies are showing, not even the public.  If I start the movie on the MD orbiter, then I can control it on the QT5 orbiter on the phone without problems.

Any ideas?

T

It looks like your serial ports are not translating properly to actual /dev/tty devices all the time.  This looks to me like the device is dropping off the usb bus.  Sometimes the translate gets a result and other times not.  The only reason that would happen is if the device is not present anymore.  You might turn on LV_STATUS and LV_DEBUG loglevels and tail the HAL log to see if the device is disconnecting.

J.

Hi Phenigma,
I got tired of trying to find where the issue was and  migrated to 14.04, and all problems gone!. Furthermore, I replaced the z-stick s2 with a gen5 and Incredible positive results!.  Fast response zwave network, very stable so far with 19 devices.  Im not even running the stick on a dedicated usb powered switch!! No retries nor failed packages on any of the devices.  I hope this helps others.

I added Manually the zstick for testing, this is the error I get

Code Select Expand

== FRESH START ==
1 02/09/16 20:05:16 /usr/pluto/bin/Spawn_Device.sh 267 (spawning-device) device: 267 ip: localhost cmd_line: ZWave
0 02/09/16 20:05:16 267 (spawning-device) Entering 267
========== NEW LOG SECTION ==========
1 02/09/16 20:05:16 267 (spawning-device) Starting... 1
1 02/09/16 20:05:16 267 (spawning-device) Found /usr/pluto/bin/ZWave
05 02/09/16 20:05:16.758 Connection for client socket reported NEED RELOAD IP=::ffff:127.0.0.1, device 267 last error 2 <0xb6e83700>
05 02/09/16 20:05:16.758 The router must be reloaded before this device is fully functional <0xb6e83700>
05 02/09/16 20:05:16.759 void ClientSocket::Disconnect() on this socket: 0x946a610 (m_Socket: 5) <0xb6e83700>
05 02/09/16 20:05:16.811 Connection for client socket reported NEED RELOAD IP=::ffff:127.0.0.1, device 267 last error 2 <0xb6e83700>
2016-02-09 20:05:16.858 Info, Reading /etc/openzwave/options.xml for Options
2016-02-09 20:05:16.858 Info, Reading /etc/openzwave/options.xml for Options
05 02/09/16 20:06:55.412 Got a reload command from 0  <0xb5affb40>
05 02/09/16 20:06:55.664 void ClientSocket::Disconnect() on this socket: 0x946af18 (m_Socket: 6) <0xb6e83700>
05 02/09/16 20:06:55.665 Socket::ReceiveData 0x946a378 failed, bytes left -1 start: 10000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 4 Event Dev #267 <0xb6e83700>
05 02/09/16 20:06:55.665 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Event Dev #267 <0xb6e83700>
01 02/09/16 20:06:55.665 Lost connection device: 267 <0xb6e83700>
05 02/09/16 20:06:55.665 Handshake failed. Retrying in 5 seconds <0xb6e83700>
05 02/09/16 20:07:01.672 Connect() failed, Error Code 111 (Connection refused)) <0xb6e83700>
05 02/09/16 20:07:04.735 Creating child 268 <0xb6e83700>
05 02/09/16 20:07:04.735 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb6e83700>
05 02/09/16 20:07:04.735 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb6e83700>
05 02/09/16 20:07:04.735 Creating child 269 <0xb6e83700>
05 02/09/16 20:07:04.735 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb6e83700>
05 02/09/16 20:07:04.735 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb6e83700>
01 02/09/16 20:07:04.790 TranslateSerialUSB pci0000:00/0000:00:1a.0+1.6.2 result /dev/ttyUSB0 <0xb6e83700>
05 02/09/16 20:13:09.968 Got a reload command from 0  <0xb46ffb40>
== ATTEMPT FRESH START ==
1 02/09/16 20:41:31 /usr/pluto/bin/Spawn_Device.sh 267 (spawning-device) 2017 Dev: 267; Already Running list: 15,33,
== FRESH START ==
1 02/09/16 20:41:31 /usr/pluto/bin/Spawn_Device.sh 267 (spawning-device) device: 267 ip: localhost cmd_line: ZWave
0 02/09/16 20:41:31 267 (spawning-device) Entering 267
========== NEW LOG SECTION ==========
1 02/09/16 20:41:31 267 (spawning-device) Starting... 1
1 02/09/16 20:41:31 267 (spawning-device) Found /usr/pluto/bin/ZWave
05 02/09/16 20:41:31.558 Creating child 268 <0xb6e9c700>
05 02/09/16 20:41:31.559 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb6e9c700>
05 02/09/16 20:41:31.559 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb6e9c700>
05 02/09/16 20:41:31.559 Creating child 269 <0xb6e9c700>
05 02/09/16 20:41:31.559 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb6e9c700>
05 02/09/16 20:41:31.559 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb6e9c700>
01 02/09/16 20:41:31.619 TranslateSerialUSB pci0000:00/0000:00:1a.0+1.6.2 result  <0xb6e9c700>
2016-02-09 20:41:31.620 Info, Reading /etc/openzwave/options.xml for Options
2016-02-09 20:41:31.620 Info, Reading /etc/openzwave/options.xml for Options
05 02/09/16 21:07:11.236 Got a reload command from 0  <0xb5affb40>
05 02/09/16 21:07:11.488 void ClientSocket::Disconnect() on this socket: 0x9699ef8 (m_Socket: 6) <0xb6e9c700>
05 02/09/16 21:07:11.489 Socket::ReceiveData 0x969f2c0 failed, bytes left 0 start: 30000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 4 Event Dev #267 <0xb6e9c700>
05 02/09/16 21:07:11.489 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Event Dev #267 <0xb6e9c700>
01 02/09/16 21:07:11.489 Lost connection device: 267 <0xb6e9c700>
05 02/09/16 21:07:11.489 Handshake failed. Retrying in 5 seconds <0xb6e9c700>
05 02/09/16 21:07:17.495 Connect() failed, Error Code 111 (Connection refused)) <0xb6e9c700>
05 02/09/16 21:07:18.496 Connect() failed, Error Code 111 (Connection refused)) <0xb6e9c700>
05 02/09/16 21:07:21.560 Creating child 268 <0xb6e9c700>
05 02/09/16 21:07:21.560 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb6e9c700>
05 02/09/16 21:07:21.560 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb6e9c700>
05 02/09/16 21:07:21.560 Creating child 269 <0xb6e9c700>
05 02/09/16 21:07:21.560 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb6e9c700>
05 02/09/16 21:07:21.560 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb6e9c700>
01 02/09/16 21:07:21.613 TranslateSerialUSB pci0000:00/0000:00:1a.0+1.6.2 result  <0xb6e9c700>


What is this connection refused?

Regards,

TP

PnpQueue::Process_Detect_Stage_Confirm_Possible_DT queue 7850 already unknown <0x8b9adb40>

^^ This line here indicates that the device is found in the Unknown Devices table.  Which means it has been told to Not be used and don't ever ask me again.  Hence why it is not adding the device.  Find the device in the webadmin -> advanced -> unknown devices list and remove it.  It should add itself the next time it is detected.

J.

Hi Phenigma,

Im Having more or less the same issue but in my case there is nothing under unknown devices.  How the issue was caused.  I wanted to do a fresh start of the zwave config, because I messed up one of my motion sensors and I was unable to remove it.  I used webadmin and removed zwave device, pull the stick out, reset the stick and the minimote and plug the zstick back again but it does not get detected by PNP.  Linux is detecting it and setting as ttyusb0

157645.840518] usb 1-1.6.2: cp210x converter now attached to ttyUSB0

But nothing happens later, there is no pnpqueue on the log registered neither. 
Any hints?

TP

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

Good to have you back.. no need for apologies.. I wish we could do more than complain  !!. Feedback is given with the best interest .. im sure must of us have plenty things to do in the outside world.   thanks for all your effort. Keep up posted on what else we can do to make your life more difficult ahhahahahahha!...

Cheers,
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

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?

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

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?