Fibaro Motion Sensor FGMS-001 Working !

[wolffromthenorth]

Hi everyone,

I tought to give you an update !

this is working !

i got values for temp, lux and battery !

still working for rules on the motion detection ( i see commands recieved under the contact from the item file )

further testing !

i'll post more when i know more

kind regards

item file

Contact Fibaro_Motion_1 "Fibaro_Motion_1" { zwave="4:1:command=basic" }
Group Motion_Sensors "Fibaro_Motion"
Number Fibaro_Motion_1_Temp "Bureau_temp [%.2f °C]" <temperature> (SensorTemperature)  { zwave="4:1:command=sensor_multilevel,sensor_type=1" }
Number Fibaro_Motion_1_Lux "bureau_lux [%.0f Lux]" <sun> (SensorLuminance)  { zwave="4:1:command=Sensor_multilevel,sensor_type=3" }
Number Fibaro_Motion_1_Bat "bureau_motion_bat [%s %%]" <energy> (Batterylevel_Sensors_Zwave)  { zwave="4:1:command=BATTERY" }

sitemap

sitemap jarvis label="Main Menu"
{
 Frame label="RGB"  {
  Group item=gRGBW  {
   Slider item=RGBWControllerAll switchSupport    
   Colorpicker item=RGBW    
  }  
 } 
 Frame label="Motion Sensors"  {
  Group item=Motion_Sensors  {
   Text item=Fibaro_Motion_1_Bat label="Bureau_temp [%.2f °C]"    
   Text item=Fibaro_Motion_1_Temp     
   Text item=Fibaro_Motion_1_Lux    
  }  
 } 
}

[Ivar V]

Hi 

Thank you!
Just got my FGMS-001 a few days ago.. your post helped me set it up easily :) 

I have one problem tho.. I'm trying to change Association Groups, but can't get it to work. 
I just stays yellow all the time, awaiting wakeup i guess?
I tried leaving it one day and even tried manual wakeup by pressing button 3 times. Still no update. 
It's the same with the other Configuration parameters. 

Did this work for you?

Cheers
Ivar

openhab 1.4.0 / zwave binding 1.5.0.20140510

[Chris Jackson]

>
> I have one problem tho.. I'm trying to change Association Groups, but can't get it to work.
> I just stays yellow all the time, awaiting wakeup i guess?
> I tried leaving it one day and even tried manual wakeup by pressing button 3 times. Still no update.
> It's the same with the other Configuration parameters.
>
> Did this work for you?

It works ok here for me. This probably indicates that the sensor is not communicating with the controller in it’s current position? If you wake it up (by pressing the button 3 times) and things don’t change then I would suspect its not able to communicate and might need to move closer to the controller. Alternatively, you might need to do a heal quite a few times over a longish period to make sure that the mesh routing has sorted itself out. I’ve seen this sometimes - you include the device next to the controller, then move it to where the controller can’t hear it, and it takes a while for the network to sort out the routes… Just a thought….

Chris

[Ivar V]

Hello Chris

One of them (bought 2) should be in direct contact with the controller.. the second one I think is via the mesh.
Same behavior on both.. At least I know it's not supposed to be that way, so I'll investigate some more. 

Btw.. do I need to add the main controller (Node1) to the sensors Association group, for it to report the values to Openhab correctly? 
How's that working exactly? 

Ivar

kl. 14:15:45 UTC+2 søndag 8. juni 2014 skrev Chris Jackson følgende:

>It works ok here for me. This probably indicates that the sensor is not communicating with the controller in it’s current position? If you wake it up (by pressing the button 3 times) and things don’t change then. I would suspect its not able to communicate and might need to move closer to the controller. Alternatively, you might need to do a heal quite a few times over a longish period to make sure that the mesh >routing has sorted itself out. I’ve seen this sometimes - you include the device next to the controller, then move it to where the controller can’t hear it, and it takes a while for the network to sort out the >routes… Just a thought…. 

>Chris

[Chris Jackson]

Hi Ivar,

One of them (bought 2) should be in direct contact with the controller.. the second one I think is via the mesh.
Same behavior on both.. At least I know it's not supposed to be that way, so I'll investigate some more. 

I would wake the unit up a couple of times and then have a look in the log to see if anything was received...

Btw.. do I need to add the main controller (Node1) to the sensors Association group, for it to report the values to Openhab correctly? 
How's that working exactly?

Yes- you need the association with node 1 in order for the sensor to report automatically. Associations are z-waves way of allowing you to say what nodes get to be told what’s happening. At some stage, I’d like to set this up automatically when a new device is found, but at the moment you need to do it manually.

Without an association, you would need to poll, which for a battery device doesn’t work well, and for a motion sensor, is not really appropriate :)

Cheers

Chris

[Ivar V]

Hello 

> I would wake the unit up a couple of times and then have a look in the log to see if anything was received...

Okay.. I restarted openhab and make sure all sensors was awake during the initialization. 
It seemed the Group Assignment did update, because I started receiving allot more sensor data now. 
It's still yellow in Habmin tho.. 

> Yes- you need the association with node 1 in order for the sensor to report automatically. Associations are z-waves way of allowing you to say what nodes get to be told what’s happening. At some stage,
>I’d like to set this up automatically when a new device is found, but at the moment you need to do it manually.

Thanks.. wasn't quite sure about that :)

Now I lost all the info on Node12. Guess that will fix itself over time?  

//Ivar

[Ivar V]

Finally got the parameter settings to stick!
Howto:
- Make sure to be in direct contact with the main controller.

I got a wide stretched house, so one of the FGMS sensors wasn't in direct contact.
It seems strange since the motion/alarm messages went through from the final position. 

- It takes multiple retries where you need to wake up the sensor by triple clicking the B-button.
It might apply one change each wakeup. Just needed to repeat until all settings went through. 

Now.. just the lost info on Node12 to solve :) 

Cheers
Ivar

[christophe xxx]

Great you have thema working man.
They neef all their 3 groups tot report to the controller. Searched also for quite a bit to find out. YelloW is normal, it means its syncing. Try also to reload the habmin site while configuring Evert setting this helps. Also make dure you configurere the tamper setting, i had the issue here that without that in the item file it was not included in the network.

Kind regards

Op 9-jun.-2014 01:07 schreef "Ivar V" <ivar.v...@gmail.com>:

--
You received this message because you are subscribed to a topic in the Google Groups "openhab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab/8uMM-xT_WoE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
For more options, visit https://groups.google.com/d/optout.

[Chris Jackson]

It's still yellow in Habmin tho.. 

It's possible for the configuration to be updated, but this to still be yellow in HABmin. There are actually 2 things that need to happen - firstly, the binding sets the configuration/association, then it reads back the setting to be sure it was actually set. Both of these commands get queued at the same time, but with battery devices it can still take a couple of wakeups for them to both get through to the device.  The yellow background just means that the configuration is pending, or unconfirmed.

 

They neef all their 3 groups tot report to the controller. Searched also for quite a bit to find out.

This shouldn't be the case - you should just have to use group 3 which (from my understanding) is designed to be used with a controller. This is standard on all Fibaro devices and from my experience seems to be correct. I've not used the FGMS very much, so maybe this is different, but the manual seems to say the same thing as other units (3rd Association Group reports the device status and allows for assigning a single device only (the main controller by default - the device reports its status to the main controller).)

Maybe your experience shows this is incorrect, but did you try just setting group 3?

For example, with group 3 set, I definately get the tamper alarm which is otherwise assigned to group 2, so I believe that group 3 will get all alarms and is the one that should be set to the controller. Setting all 3 groups to the controller will likely reduce your battery life as I think it will be duplicating all messages.

 

YelloW is normal, it means its syncing. Try also to reload the habmin site while configuring Evert setting this helps

Reloading HABmin will not do anything to speed things up since all the 'real' work is done in the binding - HABmin just sends a single message to openHAB and after that everything is done there.

Cheers

Chris

[Sebastian Waitz]

Hey all,

I received my Fibaro motion sensor two days back and was able to get it activated (green) in Habmin. The motion sensor part of the device does work fine in Openhab already and I've written a small rule that turns on the lights on motion recognition.

But I cant get the Temp, lux & Battery to work. Here's my item config.

Contact Fibaro_Motion_1                "Bewegungsmelder [MAP(fibaro.map):%s]" {zwave="2:0:command=basic"}

Number Fibaro_Motion_1_Temp     "Temperatur [%.2f °C]"    <temperature>                   {zwave="2:1:command=sensor_multilevel,sensor_type=1"}

//Number Fibaro_Motion_1_Lux      "Lux [%.0f Lux]"    <sun>                                          {zwave="2:1:command=Sensor_multilevel,sensor_type=3"}

//Number Fibaro_Motion_1_Bat      "Bewegungsmelder Bat. [%s %%]"    <energy>         {zwave="2:0:command=battery"}

The error message I receive in regards to the Temperatur is the following:

2015-02-19 14:33:32.371 [DEBUG] [.o.b.z.i.c.ZWaveBasicConverter:75  ]- Generating poll message for BASIC for node 2 endpoint 0

2015-02-19 14:33:32.375 [DEBUG] [z.i.p.c.ZWaveBasicCommandClass:124 ]- Creating new message for application command BASIC_GET for node 2

2015-02-19 14:33:32.379 [DEBUG] [o.b.z.i.protocol.SerialMessage:109 ]- NODE 2: Creating empty message of class = SendData (0x13), type = Request (0x00)

2015-02-19 14:33:32.383 [DEBUG] [b.z.i.protocol.ZWaveController:956 ]- Callback ID = 179

2015-02-19 14:33:32.387 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:237 ]- NODE 2: Putting message SendData in wakeup queue.

2015-02-19 14:33:32.391 [WARN ] [.b.z.i.c.ZWaveConverterHandler:171 ]- No command class found for item = Fibaro_Motion_1_Temp, command class name = sensor_multilevel, ignoring execute refresh.

2015-02-19 14:33:32.395 [WARN ] [.b.z.i.c.ZWaveConverterHandler:243 ]- No command class found for item = Fibaro_Motion_1_Temp, command class name = sensor_multilevel, using 0 refresh interval.

2015-02-19 14:33:32.398 [WARN ] [.b.z.i.c.ZWaveConverterHandler:243 ]- No command class found for item = Fibaro_Motion_1_Temp, command class name = sensor_multilevel, using 0 refresh interval.

From hardware point if view I'm just running a Z-stick S2 connected to my rPi and the Fibaro sensor. I guess my config is not valid, since I'm quite new to the zwave topic. If anyone could point me into the right direction, that would be awsome!

Thanks much.

[Davor Fikais]

Hello!

I'm not 100% sure (pretty sure Chris would know if this is true), but as I can recall, I've read in some topic here that Fibaro doesn't use endpoint 0, so you should replace zwave=2:0:command=basic with zwave=2:command=basic. I have the same motion sensor, but I don't use basic for motion report. Here is my binding line for the motion sensor item:

7:command=sensor_binary

You can try to use your way of binding item to device (just remove endpoint 0 part), but in case it doesn't work, try it with sensor_binary, because in my case, it works that way.

Best regards,

Davor

[Sebastian Waitz]

Hey Davor,

thanks for your quick reply and optimization hint. The motion sensor is already working, but I've reviewed my config according to you hint. At the end, I came up with this config:

{zwave="2:command=sensor_binary,respond_to_basic=true"}

The main problem I have is to get the other items to work properly. Like Temp, Lux & Bat. They dont work at all and I only receive "uninitialized" as value in OH.

Thanks much.

2015-02-19 15:02 GMT+01:00 Davor Fikais <dav...@gmail.com>:

Hello!

I'm not 100% percent sure (pretty sure Chris would know if this is true), but as I can recall, I've read in some topic here that Fibaro doesn't use endpoint 0, so you should replace zwave=2:0:command=basic with zwave=2:command=basic. I have the same motion sensor, but I don't use basic for motion report. Here is my binding line for the motion sensor item:

7:command=sensor_binary

You can try to use your way of binding item to device (just remove endpoint 0 part), but in case it doesn't work, try it with sensor_binary, because in my case, it works that way.

Best regards,

Davor

On Thursday, February 19, 2015 at 2:37:15 PM UTC+1, Sebastian Waitz wrote:

--
You received this message because you are subscribed to a topic in the Google Groups "openhab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab/8uMM-xT_WoE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab/83a51481-8cb3-4b04-a8c1-8f5afd91a305%40googlegroups.com.

[Davor Fikais]

Hello Sebastian,

regarding other items, I think that motion sensor does not have endpoint 1 either. Here are my items definitions for other sensors (tamper alarm, battery, temperature and lux):

Tamper alarm: 

7:command=sensor_alarm

Battery:

7:command=battery

Temperature:

7:command=sensor_multilevel,sensor_type=1

Lux: 

7:command=sensor_multilevel,sensor_type=3

Hope this helps. 

Best regards,

Davor

[christophe xxx]

Idd should work mine are also set like this. Wake the unit up a few times by tripple clicking and also assing group 3 to controller

Kind regards

Op 19-feb.-2015 15:38 schreef "Davor Fikais" <dav...@gmail.com>:

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab/75c0516e-2c9e-424e-a3ab-eb7c33ec9b0b%40googlegroups.com.

[Sebastian Waitz]

Ok, I got some initial data from the Fibaro sensor in Openhab now. This was after forcing the device to wake-up (3times button press). I already assigned the 3rd group to the controller. But I also added the first two groups to the controller now.

But it seems that the values (Lux, Temp) never update itself. I've closed all blinds (the room is dark now) and the Lux value is still 144. The value stays for hours like this. Only when forcing a wake-up of the device, the values get updated.

I've tried setting the wake-up interval to 300 seconds (default was 7200 sec.), but this did not help. Any hint how I could make the "self update" to work would be appreciated.

Btw: is temp and lux, etc polled by the controller or pushed from the device during wake-up phase? Is there any other config setting I have to tweak?

Thanks much for you help.

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab/CAFyOZuiihN01m-G2GDX%3D4UpVcvZYjcv3dsvwKT%3D5oaSi7zrCcg%40mail.gmail.com.

[christophe xxx]

Habmin and configure there, read manual for all indtructions on the parameters

Op 20-feb.-2015 17:02 schreef "Sebastian Waitz" <sebasti...@gmx.de>:

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab/CAMu7JKuSbNNrBv0eOqVDjYsVxUKd-2U2v8zARpGk300zipnYfw%40mail.gmail.com.

[Chris Jackson]

Habmin and configure there, read manual for all indtructions on the parameters

Absolutely - if I remember correctly, there are 4 parameters that need to be set to get temperature and lux readings. These set when the messages will be sent depending on how much change there is. I think by default these values are not sent.

[Sebastian Waitz]

Hey all,

thanks for pointing me into the right direction. Indeed there were a few parameters to set. For others that might stumble upon this thread, the values are:

40: Illumination report threshold

42: Illumination report interval

60: temperature report threshold

62: interval of temperature measuring

64: temperature report interval

After setting those, OH constantly receives temp and lux values.

Thanks

[Martin Naughton]

Did anyone else notice that the Fibaro motion sensor never wakes up? I have to physically wake it up by pressing the button 3 times.

I did a test of deleting all node configuration in openhab and restarting the board.

Since the Fibaro motion sensor was already configured to report information to my controller before i restarted i started getting information like this after restart which is correct.
NODE 23: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 12.4

Only problem is I restarted 12 hours ago. I am getting sensor information from the motion sensor but in that 12 hours i did not get a WAKE_UP notification. WAKE_UP will send the node information to openhab so at the moment i am missing all node information. The WAKE_UP interval is defaulted to 7200 seconds which is 2 hours. I  did not change this.

Anyone else see this problem? I prefer to let the device sync up it self with out me clicking the button.

[Martin Naughton]

Here is some logs from when it started up. I just did a grep for "NODE 23". At the end you can see that it stops waiting.

2015-02-23 19:53:01.122 DEBUG o.o.b.z.i.p.i.ZWaveNodeSerializer[:129]- NODE 23: Serializing from file etc/zwave/node23.xml

2015-02-23 19:53:01.160 DEBUG o.o.b.z.i.p.i.ZWaveNodeSerializer[:132]- NODE 23: Error serializing from file: file does not exist.

2015-02-23 19:53:01.192 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:267]- NODE 23: Node advancer - EMPTYNODE: queue length(0), free to send(true)

2015-02-23 19:53:01.210 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:333]- NODE 23: Node advancer: loop - EMPTYNODE try 1: stageAdvanced(false)

2015-02-23 19:53:01.226 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:338]- NODE 23: Node advancer: Initialisation starting

2015-02-23 19:53:01.249 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:835]- NODE 23: Node advancer - advancing to PROTOINFO

2015-02-23 19:53:01.266 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:333]- NODE 23: Node advancer: loop - PROTOINFO try 0: stageAdvanced(true)

2015-02-23 19:53:01.285 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:347]- NODE 23: Node advancer: PROTOINFO - send IdentifyNode

2015-02-23 19:53:01.350 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:240]- NODE 23: Node advancer - queued packet. Queue length is 1

2015-02-23 19:53:20.217 DEBUG o.o.b.z.i.p.s.IdentifyNodeMessageClass[:52]- NODE 23: ProtocolInfo

2015-02-23 19:53:20.225 DEBUG o.o.b.z.i.p.s.IdentifyNodeMessageClass[:61]- NODE 23: Listening = false

2015-02-23 19:53:20.236 DEBUG o.o.b.z.i.p.s.IdentifyNodeMessageClass[:62]- NODE 23: Routing = true

2015-02-23 19:53:20.248 DEBUG o.o.b.z.i.p.s.IdentifyNodeMessageClass[:63]- NODE 23: Version = 4

2015-02-23 19:53:20.256 DEBUG o.o.b.z.i.p.s.IdentifyNodeMessageClass[:64]- NODE 23: FLIRS = false

2015-02-23 19:53:20.265 DEBUG o.o.b.z.i.p.s.IdentifyNodeMessageClass[:76]- NODE 23: Basic = Routing Slave

2015-02-23 19:53:20.276 DEBUG o.o.b.z.i.p.s.IdentifyNodeMessageClass[:83]- NODE 23: Generic = Binary Sensor

2015-02-23 19:53:20.288 DEBUG o.o.b.z.i.p.s.IdentifyNodeMessageClass[:90]- NODE 23: Specific = Routing Binary Sensor

2015-02-23 19:53:20.299 DEBUG o.o.b.z.i.p.c.ZWaveCommandClass[:220]- NODE 23: Creating new instance of command class NO_OPERATION

2015-02-23 19:53:20.318 DEBUG o.o.b.z.i.protocol.ZWaveNode[:497]- NODE 23: Adding command class NO_OPERATION to the list of supported command classes.

2015-02-23 19:53:20.329 DEBUG o.o.b.z.i.p.c.ZWaveCommandClass[:220]- NODE 23: Creating new instance of command class BASIC

2015-02-23 19:53:20.349 DEBUG o.o.b.z.i.protocol.ZWaveNode[:497]- NODE 23: Adding command class BASIC to the list of supported command classes.

2015-02-23 19:53:20.364 DEBUG o.o.b.z.i.p.c.ZWaveCommandClass[:220]- NODE 23: Creating new instance of command class SENSOR_BINARY

2015-02-23 19:53:20.396 DEBUG o.o.b.z.i.protocol.ZWaveNode[:497]- NODE 23: Adding command class SENSOR_BINARY to the list of supported command classes.

2015-02-23 19:53:20.708 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:980]- NODE 23: Node advancer - PROTOINFO: Transaction complete (IdentifyNode:Request) success(true)

2015-02-23 19:53:20.717 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:201]- NODE 23: Node advancer - checking initialisation queue. Queue size 1.

2015-02-23 19:53:20.725 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:207]- NODE 23: Node advancer - message removed from queue. Queue size 0.

2015-02-23 19:53:20.736 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:267]- NODE 23: Node advancer - PROTOINFO: queue length(0), free to send(true)

2015-02-23 19:53:20.745 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:333]- NODE 23: Node advancer: loop - PROTOINFO try 1: stageAdvanced(false)

2015-02-23 19:53:20.756 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:835]- NODE 23: Node advancer - advancing to NEIGHBORS

2015-02-23 19:53:20.765 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:333]- NODE 23: Node advancer: loop - NEIGHBORS try 0: stageAdvanced(true)

2015-02-23 19:53:20.778 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:357]- NODE 23: Node advancer: NEIGHBORS - send RoutingInfo

2015-02-23 19:53:20.788 DEBUG o.o.b.z.i.p.s.GetRoutingInfoMessageClass[:29]- NODE 23: Request routing info

2015-02-23 19:53:20.821 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:240]- NODE 23: Node advancer - queued packet. Queue length is 1

2015-02-23 19:53:31.194 DEBUG o.o.b.z.i.p.s.GetRoutingInfoMessageClass[:47]- NODE 23: Got NodeRoutingInfo request.

2015-02-23 19:53:31.198 DEBUG o.o.b.z.i.p.s.GetRoutingInfoMessageClass[:78]- NODE 23: Neighbor nodes: 1

2015-02-23 19:53:31.381 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:980]- NODE 23: Node advancer - NEIGHBORS: Transaction complete (GetRoutingInfo:Request) success(true)

2015-02-23 19:53:31.385 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:201]- NODE 23: Node advancer - checking initialisation queue. Queue size 1.

2015-02-23 19:53:31.391 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:207]- NODE 23: Node advancer - message removed from queue. Queue size 0.

2015-02-23 19:53:31.395 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:267]- NODE 23: Node advancer - NEIGHBORS: queue length(0), free to send(true)

2015-02-23 19:53:31.399 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:333]- NODE 23: Node advancer: loop - NEIGHBORS try 1: stageAdvanced(false)

2015-02-23 19:53:31.405 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:835]- NODE 23: Node advancer - advancing to FAILED_CHECK

2015-02-23 19:53:31.409 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:333]- NODE 23: Node advancer: loop - FAILED_CHECK try 0: stageAdvanced(true)

2015-02-23 19:53:31.412 DEBUG o.o.b.z.i.p.s.IsFailedNodeMessageClass[:31]- NODE 23: Requesting IsFailedNode status from controller.

2015-02-23 19:53:31.425 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:240]- NODE 23: Node advancer - queued packet. Queue length is 1

2015-02-23 19:53:36.958 DEBUG o.o.b.z.i.p.s.IsFailedNodeMessageClass[:54]- NODE 23: Is currently marked as healthy by the controller

2015-02-23 19:53:37.041 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:980]- NODE 23: Node advancer - FAILED_CHECK: Transaction complete (IsFailedNodeID:Request) success(true)

2015-02-23 19:53:37.045 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:201]- NODE 23: Node advancer - checking initialisation queue. Queue size 1.

2015-02-23 19:53:37.050 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:207]- NODE 23: Node advancer - message removed from queue. Queue size 0.

2015-02-23 19:53:37.054 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:267]- NODE 23: Node advancer - FAILED_CHECK: queue length(0), free to send(true)

2015-02-23 19:53:37.058 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:333]- NODE 23: Node advancer: loop - FAILED_CHECK try 1: stageAdvanced(false)

2015-02-23 19:53:37.064 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:835]- NODE 23: Node advancer - advancing to WAIT

2015-02-23 19:53:37.068 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:333]- NODE 23: Node advancer: loop - WAIT try 0: stageAdvanced(true)

2015-02-23 19:53:37.072 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:380]- NODE 23: Node advancer: WAIT - Listening=false, FrequentlyListening=false

2015-02-23 19:53:37.077 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:398]- NODE 23: Node advancer: WAIT - Still waiting!

2015-02-23 19:53:39.123 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:966]- NODE 23: Node advancer - WAIT: The WAIT is over!

2015-02-23 19:53:39.127 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:201]- NODE 23: Node advancer - checking initialisation queue. Queue size 0.

[Chris Jackson]

Mine wakes up fine. Is the wakeup class configured correctly? If you use the 'masterController' option set to true (or actually, if it's not set to false) then the binding ought to automatically configure this anyway.

[Chris Jackson]

The log looks fine thus far - the initialisation of the sensor hasn't started yet, but this is all ok to me...

Chris

[Klaus Hildner]

Hi all,

thanks for sharing this. -- I use OpenHAB 1.6.x, Z-Wave binding, ozwcpPi, and I have a ZME_UZB1 stick, a Düwi switchable 230 VAC plug a(show in ozwcpPi as node 2) nd a Fibaro motion sensor FGMS-001-EN-A-V1.01 (shown as node 3).

ozwcpPi reports the node Id 2 LBR of basic type "routing slave", generic type "Binary Power Switch", product "Popp/ Duwi ZW ZS 3500 Plugin Switch",

node Id 3 BR as basic type "routing slave", generic type "Routing binary Sensor", product "FIBARO System Unknown: type=0800, id=1001".

The Düwi works fine: I can switch it on and off from OpenHAB:

items:

Switch Fibaro_Switch_1 { zwave="2:command=SWITCH_BINARY" }

sitemap:

Switch item=Fibaro_Switch_1 label="Fibaro Switch 1"

in ozwcpPi, the motion sensor shows up as node 3, and I see logs messages coming in from the Z-Wave bundle.

But all of these 9desperate) item / sitemap definitions did not show any value fed back from the sensor:

Contact Fibaro_Motion_1_Tamper "Fibaro Tamper [%s]" { zwave="3:command=SENSOR_ALARM" }

String Fibaro_Motion_1_Basic "Fibaro Tamper [%s]" { zwave="3:0:command=BASIC" }

Number Fibaro_Motion_1_1_Temperature "Fibaro 1 Temp [%.2f °C]" <temperature> (SensorTemperature)  { zwave="3:0:command=SENSOR_MULTILEVEL,sensor_type=1,refresh_interval=15" }

Number Fibaro_Motion_1_2_General "Unknown 2 [%.2f °C]" <temperature> (SensorTemperature)  { zwave="3:0:command=SENSOR_MULTILEVEL,sensor_type=2,refresh_interval=15" }

Number Fibaro_Motion_1_3_Luminance "Fibaro 1 Lux [%.0f Lux]" <sun> (SensorLuminance)  { zwave="3:0:command=SENSOR_BINARY,sensor_type=3,refresh_interval=15" }

Number Fibaro_Motion_1_4_Power "Unknown 4 [%.2f °C]" <temperature> (SensorTemperature)  { zwave="3:0:command=SENSOR_BINARY,sensor_type=4,refresh_interval=15" }

Number Fibaro_Motion_1_5_RelativeHumidity "Unknown 5 [%.2f °C]" <temperature> (SensorTemperature)  { zwave="3:0:command=SENSOR_MULTILEVEL,sensor_type=5,refresh_interval=15" }

Number Fibaro_Motion_1_6_Velocity "Unknown 6 [%.2f °C]" <temperature> (SensorTemperature)  { zwave="3:command=SENSOR_MULTILEVEL,sensor_type=6,refresh_interval=15" }

Number Fibaro_Motion_1_7_Direction "Unknown 7 [%s]" <temperature> (SensorTemperature)  { zwave="3:command=SENSOR_MULTILEVEL,sensor_type=7,refresh_interval=15" }

Number Fibaro_Motion_1_Battery "Fibaro 1 Batterie [%s %%]" <energy> (Batterylevel_Sensors_Zwave)  { zwave="3:command=BATTERY" }

Text item=Fibaro_Motion_1_Tamper label="Tamper [%s]"

Text item=Fibaro_Motion_1_Basic label="Basic [%s]"

Text item=Fibaro_Motion_1_1_Temperature label="Temperature [%.2f °C]"

Text item=Fibaro_Motion_1_2_General label="General [%s]" 

Text item=Fibaro_Motion_1_3_Luminance label="Luminance [%s]" 

Text item=Fibaro_Motion_1_4_Power label="Power [%.2f °C]"

Text item=Fibaro_Motion_1_5_Relative_Humidity label="Relative Humidity [%s]" 

Text item=Fibaro_Motion_1_6_Velocity label="Velocity [%s]" 

Text item=Fibaro_Motion_1_7_Direction label="Direction [%s]" 

I see log output like: "Got a value event from Z-Wave network for nodeId = 3, endpoint = 0, command class = BASIC, value = 0",

and "No converter found for item = Fibaro_Motion_1_Basic, node = 3 endpoint 0, ignoring event"

What data type to use?

Do I address the sensor properly? (assuming node:endpoint:... is good)

Without going into HABmin and assigning scenes, is there an easy way of initializing the sensor to get it going?

best regards

Klaus

[Chris Jackson]

String Fibaro_Motion_1_Basic "Fibaro Tamper [%s]" { zwave="3:0:command=BASIC" }

Firstly, you are defining the endpoints incorrectly - endpoint 0 is not valid within the item definition and it should be removed.

I see log output like: "Got a value event from Z-Wave network for nodeId = 3, endpoint = 0, command class = BASIC, value = 0",

and "No converter found for item = Fibaro_Motion_1_Basic, node = 3 endpoint 0, ignoring event”

I think the main problem might be that the device is sending the basic command class and your item definition is a string, which I think it’s allowed. Try changing it to a switch or number

Chris

[Christophe Van Vossel]

Chris is correct.
If needed search the forum for correct item defs. If you like we can also post them.

Kind regards

Op 1-jul.-2015 20:19 schreef "Chris Jackson" <ch...@cd-jackson.com>:

--

You received this message because you are subscribed to a topic in the Google Groups "openhab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab/8uMM-xT_WoE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab/F75BAA30-8F92-4BA0-A26B-BAD1C0ECD046%40cd-jackson.com.

[Klaus Hildner]

Thanks so far!

I now have this items file (still guessing):

Contact Fibaro_Motion_1 "Fibaro_Motion_1" { zwave="4:1:command=basic" }

Group Motion_Sensors "Fibaro_Motion"

Number Fibaro_Motion_1_Tamper "Fibaro Tamper [%s]" { zwave="3:command=SENSOR_ALARM" }

Switch Fibaro_Motion_1_Basic "Fibaro Tamper [%s]" { zwave="3:command=BASIC" }

Number Fibaro_Motion_1_1_Temperature "Fibaro 1 Temp [%.2f °C]" <temperature> (SensorTemperature)  { zwave="3:command=SENSOR_MULTILEVEL,sensor_type=1,refresh_interval=15" }

Number Fibaro_Motion_1_2_General "Unknown 2 [%.2f °C]" <temperature> (SensorTemperature)  { zwave="3:command=SENSOR_MULTILEVEL,sensor_type=2,refresh_interval=15" }

Number Fibaro_Motion_1_3_Luminance "Fibaro 1 Lux [%.0f Lux]" <sun> (SensorLuminance)  { zwave="3:command=SENSOR_MULTILEVEL,sensor_type=3,refresh_interval=15" }

Number Fibaro_Motion_1_4_Power "Unknown 4 [%.2f °C]" <temperature> (SensorTemperature)  { zwave="3:command=SENSOR_MULTILEVEL,sensor_type=4,refresh_interval=15" }

Number Fibaro_Motion_1_5_RelativeHumidity "Unknown 5 [%.2f °C]" <temperature> (SensorTemperature)  { zwave="3:command=SENSOR_MULTILEVEL,sensor_type=5,refresh_interval=15" }

Number Fibaro_Motion_1_6_Velocity "Unknown 6 [%.2f °C]" <temperature> (SensorTemperature)  { zwave="3:command=SENSOR_MULTILEVEL,sensor_type=6,refresh_interval=15" }

Number Fibaro_Motion_1_7_Direction "Unknown 7 [%s]" <temperature> (SensorTemperature)  { zwave="3:command=SENSOR_MULTILEVEL,sensor_type=7,refresh_interval=15" }

Number Fibaro_Motion_1_Battery "Fibaro 1 Batterie [%s %%]" <energy> (Batterylevel_Sensors_Zwave)  { zwave="3:command=BATTERY" }

Switch Fibaro_Switch_1 { zwave="2:command=SWITCH_BINARY" }

String ZwaveNode02HomeID "Home ID [%s]" (gZwaveNode02) {zwave="2:homeid"}

String ZwaveNode02NetworkID "Network ID [%s]" (gZwaveNode02) {zwave="2:nodeid"}

String ZwaveNode02LastUpdated "Last Updated [%s]" (gZwaveNode02) {zwave="2:lastupdate"}

String ZwaveNode02Listening "Listening [%s]" (gZwaveNode02) {zwave="2:listening"}

String ZwaveNode02Routing "Routing [%s]" (gZwaveNode02) {zwave="2:routing"}

String ZwaveNode02Version "Version [%s]" (gZwaveNode02) {zwave="2:version"}

String ZwaveNode03HomeID "Home ID [%s]" (gZwaveNode03) {zwave="3:homeid"}

String ZwaveNode03NetworkID "Network ID [%s]" (gZwaveNode03) {zwave="3:nodeid"}

String ZwaveNode03LastUpdated "Last Updated [%s]" (gZwaveNode03) {zwave="3:lastupdate"}

String ZwaveNode03Listening "Listening [%s]" (gZwaveNode03) {zwave="3:listening"}

String ZwaveNode03Routing "Routing [%s]" (gZwaveNode03) {zwave="3:routing"}

String ZwaveNode03Version "Version [%s]" (gZwaveNode03) {zwave="3:version"}

This is my experimental sitemap snippet:

   Group item=Motion_Sensors  {

  Text item=Fibaro_Motion_1_Tamper label="Tamper [%f]"

  Switch item=Fibaro_Motion_1_Basic label="Basic [%s]"

  Text item=Fibaro_Motion_1_1_Temperature label="Temperature [%.2f °C]"

  Text item=Fibaro_Motion_1_2_General label="General [%f]" 

  Text item=Fibaro_Motion_1_3_Luminance label="Luminance [%f]" 

  Text item=Fibaro_Motion_1_4_Power label="Power [%.2f °C]"

  Text item=Fibaro_Motion_1_5_Relative_Humidity label="Relative Humidity [%f]" 

  Text item=Fibaro_Motion_1_6_Velocity label="Velocity [%f]" 

  Text item=Fibaro_Motion_1_7_Direction label="Direction [%f]" 

  Text item=ZwaveNode02LastUpdated label="ZwaveNode02LastUpdated [%s]"

  Text item=ZwaveNode02Listening label="ZwaveNode02Listening [%s]"

  Text item=ZwaveNode02Routing label="ZwaveNode02Routing [%s]"

  Text item=ZwaveNode02Version label="ZwaveNode02Version [%s]"

  Text item=ZwaveNode03LastUpdated label="ZwaveNode03LastUpdated [%s]"

  Text item=ZwaveNode03Listening label="ZwaveNode03Listening [%s]"

  Text item=ZwaveNode03Routing label="ZwaveNode03Routing [%s]"

  Text item=ZwaveNode03Version label="ZwaveNode03Version [%s]"

  }

  Switch item=Fibaro_Switch_1 label="Fibaro Switch 1"

  } 

Logs now read:

2015-07-02 14:41:32.596 [DEBUG] [ZWaveMultiLevelSensorConverter:68  ]- Generating poll message for SENSOR_MULTILEVEL for node 3 endpoint 0

2015-07-02 14:41:32.598 [DEBUG] [veMultiLevelSensorCommandClass:220 ]- NODE 3: Creating new message for application command SENSOR_MULTI_LEVEL_GET

2015-07-02 14:41:32.601 [DEBUG] [o.b.z.i.protocol.SerialMessage:108 ]- NODE 3: Creating empty message of class = SendData (0x13), type = Request (0x00)

2015-07-02 14:41:32.603 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:243 ]- NODE 3: Message already on the wake-up queue. Removing original.

2015-07-02 14:41:32.604 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:247 ]- NODE 3: Putting message in wakeup queue.

2015-07-02 14:41:32.607 [DEBUG] [ZWaveMultiLevelSensorConverter:68  ]- Generating poll message for SENSOR_MULTILEVEL for node 3 endpoint 0

2015-07-02 14:41:32.609 [DEBUG] [veMultiLevelSensorCommandClass:220 ]- NODE 3: Creating new message for application command SENSOR_MULTI_LEVEL_GET

2015-07-02 14:41:32.611 [DEBUG] [o.b.z.i.protocol.SerialMessage:108 ]- NODE 3: Creating empty message of class = SendData (0x13), type = Request (0x00)

2015-07-02 14:41:32.613 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:243 ]- NODE 3: Message already on the wake-up queue. Removing original.

2015-07-02 14:41:32.615 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:247 ]- NODE 3: Putting message in wakeup queue.

2015-07-02 14:41:32.617 [DEBUG] [ZWaveMultiLevelSensorConverter:68  ]- Generating poll message for SENSOR_MULTILEVEL for node 3 endpoint 0

2015-07-02 14:41:32.619 [DEBUG] [veMultiLevelSensorCommandClass:220 ]- NODE 3: Creating new message for application command SENSOR_MULTI_LEVEL_GET

2015-07-02 14:41:32.621 [DEBUG] [o.b.z.i.protocol.SerialMessage:108 ]- NODE 3: Creating empty message of class = SendData (0x13), type = Request (0x00)

2015-07-02 14:41:32.624 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:243 ]- NODE 3: Message already on the wake-up queue. Removing original.

2015-07-02 14:41:32.625 [DEBUG] [.i.p.c.ZWaveWakeUpCommandClass:247 ]- NODE 3: Putting message in wakeup queue.

Fibaro_Motion_1_Basic goes from OFF to ON in the GUI when a motion is detected, and it jumps back after about 30 sec. -- First success! :-)

But the other values do not yet show up in the GUI. The timestamps in the logs suggest periodic polling (15 sec as specified).

Any hint what the "Putting message in wakeup queue." could mean?

Then I found this: https://groups.google.com/forum/#!msg/openhab/PGbU-6nl2I0/2X2G82Q7S6sJ

And looked up this:

pi@haus /opt/openhab-1.6.2-runtime/etc/zwave $ cat node3.xml

<node>

  <deviceClass>

    <basicDeviceClass>ROUTING_SLAVE</basicDeviceClass>

    <genericDeviceClass>BINARY_SENSOR</genericDeviceClass>

    <specificDeviceClass>ROUTING_SENSOR_BINARY</specificDeviceClass>

  </deviceClass>

  <homeId>-861435197</homeId>

  <nodeId>3</nodeId>

  <version>4</version>

  <manufacturer>0x10f</manufacturer>

  <deviceId>0x1001</deviceId>

  <deviceType>0x800</deviceType>

  <listening>false</listening>

  <frequentlyListening>false</frequentlyListening>

  <routing>true</routing>

  <supportedCommandClasses>

    <entry>

      <commandClass>VERSION</commandClass>

      <versionCommandClass>

        <version>1</version>

        <instances>0</instances>

        <libraryType>LIB_UNKNOWN</libraryType>

      </versionCommandClass>

    </entry>

    <entry>

      <commandClass>WAKE_UP</commandClass>

      <WakeUpCommandClass>

        <version>1</version>

        <instances>0</instances>

        <targetNodeId>1</targetNodeId>

        <interval>7200</interval>

        <minInterval>0</minInterval>

        <maxInterval>0</maxInterval>

        <defaultInterval>0</defaultInterval>

        <intervalStep>0</intervalStep>

      </WakeUpCommandClass>

    </entry>

    <entry>

      <commandClass>ASSOCIATION</commandClass>

      <associationCommandClass>

        <version>1</version>

        <instances>0</instances>

        <configAssociations/>

        <maxGroups>0</maxGroups>

      </associationCommandClass>

    </entry>

    <entry>

      <commandClass>MANUFACTURER_SPECIFIC</commandClass>

      <manufacturerSpecificCommandClass>

        <version>1</version>

        <instances>0</instances>

      </manufacturerSpecificCommandClass>

    </entry>

    <entry>

      <commandClass>CONFIGURATION</commandClass>

      <configurationCommandClass>

        <version>1</version>

        <instances>0</instances>

        <configParameters/>

      </configurationCommandClass>

    </entry>

    <entry>

      <commandClass>SENSOR_MULTILEVEL</commandClass>

      <multiLevelSensorCommandClass>

        <version>5</version>

        <instances>0</instances>

        <sensors>

          <sensorType>LUMINANCE</sensorType>

          <sensorType>TEMPERATURE</sensorType>

        </sensors>

      </multiLevelSensorCommandClass>

    </entry>

    <entry>

      <commandClass>MULTI_CMD</commandClass>

      <multiCommandCommandClass>

        <version>1</version>

        <instances>0</instances>

      </multiCommandCommandClass>

    </entry>

    <entry>

      <commandClass>SENSOR_BINARY</commandClass>

      <binarySensorCommandClass>

        <version>1</version>

        <instances>0</instances>

      </binarySensorCommandClass>

    </entry>

    <entry>

      <commandClass>NO_OPERATION</commandClass>

      <noOperationCommandClass>

        <version>1</version>

        <instances>0</instances>

      </noOperationCommandClass>

    </entry>

    <entry>

      <commandClass>SENSOR_ALARM</commandClass>

      <alarmSensorCommandClass>

        <version>1</version>

        <instances>0</instances>

        <alarms>

          <alarmType>GENERAL</alarmType>

        </alarms>

      </alarmSensorCommandClass>

    </entry>

    <entry>

      <commandClass>BASIC</commandClass>

      <basicCommandClass>

        <version>1</version>

        <instances>0</instances>

      </basicCommandClass>

    </entry>

    <entry>

      <commandClass>BATTERY</commandClass>

      <batteryCommandClass>

        <version>1</version>

        <instances>0</instances>

        <batteryLevel>88</batteryLevel>

      </batteryCommandClass>

    </entry>

  </supportedCommandClasses>

  <nodeNeighbors/>

  <lastSent>2015-07-02 08:32:20.585 UTC</lastSent>

  <lastReceived>2015-07-02 10:32:47.15 UTC</lastReceived>

pi@haus /opt/openhab-1.6.2-runtime/etc/zwave $

Looks like I have drained the battery to 88 percent.

Could it be that I need to explicitly switch the luminance and temperature sensors on? (guessing: instances 0)

best regards

Klaus

[Christophe Van Vossel]

I will post my item file tonight so ypu can see how it works. Battery devices operate differently. For values to be read directly tripple click the button a few times and modify the dzvice optionq of reporting. The initiam values are very slow in reporting to sustain battery life

Op 2-jul.-2015 15:19 schreef "Klaus Hildner" <hil...@gmail.com>:

--

You received this message because you are subscribed to a topic in the Google Groups "openhab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab/8uMM-xT_WoE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab/5c64bb31-4080-4b9d-ac12-dcf6558b8c31%40googlegroups.com.

[Klaus Hildner]

How are these parameters set?

In .items, I tried:

String Fibaro_Init { zwave="2:command=basic,24=3" }

Along those lines, I have trouble understanding https://github.com/openhab/openhab/wiki/Z-Wave-Binding, chapter "Item Configuration", as well as the command class BASIC for set and get. An example would be good.

Does this sort of "startup configuration" really belong into .items, and what is the syntax for these (assumedly) key/value pairs?

Thanks!

[Chris Jackson]

How are these parameters set?

In .items, I tried:

String Fibaro_Init { zwave="2:command=basic,24=3” }

They are not set in the items file - you need to use HABmin…

https://github.com/cdjackson/HABmin/wiki/Z-Wave-Configuration

Does this sort of "startup configuration" really belong into .items, and what is the syntax for these (assumedly) key/value pairs?

No - this is device configuration, and it relates to the devices, not the items. That’s why you need to use something like HABmin to configure the devices.