Pre-release of Fibaro Motion Sensor

smart · March 23, 2015, 3:30am

Unfortunately you will have to go with the custom version as of now as that official device type template “code” is not available in the IDE as far as I know.

travisr100 · March 23, 2015, 5:31pm

I did a little digging and found that the office device type template code is available. I pulled up the parameters section and have gone through it to make sure I understand everything. In the version posted here it has…

[1], parameterNumber: 12, size: 1).format()  // only send basic "ON" command - not "OFF"

But in the release version they are setting parameter 12 to 0. Don’t know enough about all this to know what the difference is. I also noted the code here…

// There is a bug that does not look at the tile name. If you use 'active/inactive', it will step on
        // the motion sensor. Delete this tile below and uncomment the tile below this one. LOOK 4 'STBUG' to
        // see where else you need to update when bug is fixed.
               
        standardTile("acceleration", "device.acceleration") {
			state("vibration", label:'vibration', icon:"st.motion.acceleration.active", backgroundColor:"#53a7c0")
			state("still", label:'still', icon:"st.motion.acceleration.inactive", backgroundColor:"#ffffff")
		}
        
        /*
        standardTile("acceleration", "device.acceleration") {
			state("active", label:'vibration', icon:"st.motion.acceleration.active", backgroundColor:"#53a7c0")
			state("inactive", label:'still', icon:"st.motion.acceleration.inactive", backgroundColor:"#ffffff")
		}
        */

But in the release…

standardTile(“acceleration”, “device.acceleration”) {
state(“active”, label:‘vibration’, icon:“st.motion.acceleration.active”, backgroundColor:“#53a7c0”)
state(“inactive”, label:‘still’, icon:“st.motion.acceleration.inactive”, backgroundColor:“#ffffff”)
}

I guess they fixed whatever bug this was?

garyd9 · March 23, 2015, 7:55pm

The difference is, from a purely ST point of view, none whatsoever.

That parameter would only be used when the motion sensor is used with z-wave association. If associated with a light switch, for example, the motion sensor with param 12 set to 1 would turn ON a switch when motion is detected, but not turn it off.

The default (p12 == 0) would have the motion sensor turning ON the switch when motion was sensed, and turning OFF the switch when the motion was no longer sensed.

It’s possible. I haven’t seen anything announcing it being fixed, but that doesn’t mean much. Can someone from ST comment? @Jim?

travisr100 · March 23, 2015, 8:11pm

While I’ve read through all the code and understand the parameters I’m confused on how to actually update the device with these parameters that I’ve set in the code. I’ve currently got a Fibaro set up using the official device type. How do I actually update it? I read through the understanding lux thread but that wasn’t much help.

brianlees · March 23, 2015, 11:36pm

@travisr100 - you can’t update parameters with the official device type…yet. The way to update it now requires a bit of “hacking” - you use the pre-release device type in this thread and tweak the parameters near the bottom. There are instructions here. As far as I know, this device is one of the first ones out there with so many different parameters that can be modified. This has not been a common trait, so ST is not exactly ready for it yet.

I do know that @wackware is working on a way to update the parameters using the official device type - he also wrote the pre-release device type code that ST used for the official code. But, I also know he is a busy man and I’m quite sure there are plenty of things already in his queue. Nevertheless, it will come at some point. So, you can either use the pre-release device type or wait a little while for the “official” way to update them.

travisr100 · March 23, 2015, 11:52pm

I already created a device type with the code from here and set the parameters I want. You say instructions are here but I’ve not been able to find them. I’ve seen people mention bits and pieces of how to do it in another thread. I just need to know where to go from where I’m at now.

I currently have the device set up with the official device type.
I created the custom device type from the code here.
I updated the parameters in that code with what I want.

I’m stumped on what to do from this point.

brianlees · March 23, 2015, 11:59pm

@smart - Ron, would you be so kind as to point @travisr100 to the instructions for updating the parameters? You seem to find them faster than I do!

smart · March 24, 2015, 12:06am

First thing tmrw morning. Heating guys are here now fixing heating zone and feeder valves. Will post the instructions again…

travisr100 · March 24, 2015, 1:31am

Much appreciated. Thank you.

brianlees · March 24, 2015, 2:31am

And it’ll be cold again…ugh…

garyd9 · March 24, 2015, 2:35am

Ron, you have my most sincere condolences. Friday night, the ignitor in my system cracked (which renders the forced air gas furnace useless.) I wasn’t able to get the replaced until this morning (Monday morning.) It was a cold weekend.

(Thankfully, I have a gas fireplace in my family room, so we all (wife + 2 kids) “camped out” there Friday, Saturday, and Sunday night.)

Good luck
Gary

smart · March 24, 2015, 2:50pm

Re-posting the steps for @travisr100

(Thanks to @wackware @Mike_Maxwell and others for their help…)

In the IDE, open the fibaro motion that you created in “my device types”.
Scroll to resetParams2StDefaults() method.
Change the parameter of your choice (highly recommended to see the oem document so as not to brick it),
http://www.vesternet.com/us/downloads/dl/file/id/390/z_wave_fibaro_motion_sensor_us_manual.pdf
Save your changes. There’s no need to re-publish as you can’t activate the function resetParams2StDefaults from the device tile.
Click the set location button, click the device drop down, then select your actual Fibaro from the list (it should be one of the first in the list), then install.
Now you should see some additional buttons(don’t play clicky clack with it as yet).
Now wake up the fibaro, and click the resetParams2StDefaults thats under the custom commands section on the right side of the IDE.
(Click the b button inside the sensor quickly thrice, the diode should be solid blue then.)
At this point click on the resetParams2StDefaults button. The log should day something like setting resetting params, wait for some more messages to come thru as motion, lux etc…
(the solid blue diode will fade out at some point…). Wait for some time.
Click uninstall when done.

/**

Sets all of available Fibaro parameters back to the device defaults except for what

SmartThings needs to support the stock functionality as released. This will be

called from the “Fibaro Tweaker” or user’s app.

THIS IS AN ADVANCED OPERATION. USE AT YOUR OWN RISK! READ OEM DOCUMENTATION!

@param none

@return none
*/
def resetParams2StDefaults() {
log.debug “Resetting Sensor Parameters to SmartThings Compatible Defaults”
def cmds =

cmds << zwave.configurationV1.configurationSet(configurationValue: [8], parameterNumber: 1, size: 1).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [15], parameterNumber: 2, size: 1).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [1], parameterNumber: 3, size: 1).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [2], parameterNumber: 4, size: 1).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [0,30], parameterNumber: 6, size: 2).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [0], parameterNumber: 8, size: 1).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [0,200], parameterNumber: 9, size: 2).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [0], parameterNumber: 12, size: 1).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [0], parameterNumber: 16, size: 1).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [15], parameterNumber: 20, size: 1).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [0,30], parameterNumber: 22, size: 2).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [4], parameterNumber: 24, size: 1).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [0], parameterNumber: 26, size: 1).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [0,0], parameterNumber: 40, size: 2).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [2,88], parameterNumber: 42, size: 2).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [5], parameterNumber: 60, size: 1).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [3,132], parameterNumber: 62, size: 2).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [0,0], parameterNumber: 64, size: 2).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [0,0], parameterNumber: 66, size: 2).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [10], parameterNumber: 80, size: 1).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [50], parameterNumber: 81, size: 1).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [0,100], parameterNumber: 82, size: 2).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [3,232], parameterNumber: 83, size: 2).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [18], parameterNumber: 86, size: 1).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [28], parameterNumber: 87, size: 1).format()
cmds << zwave.configurationV1.configurationSet(configurationValue: [1], parameterNumber: 89, size: 1).format()

delayBetween(cmds, 500)

}

smart · March 24, 2015, 2:53pm

Oops…Sorry to hear that! Mine is eventually fixed as of now. Second zone valve and the feed/pressure reducer valve changed. First zone valve was changed just a few days back. I wish this winter (sorry spring) could go away soon.

Ron · March 24, 2015, 6:01pm

@travisr100 I modifed the fibaro Motion sensor to add preferences to turn on/off the LED’s.
You could look at my code and do the same type of thing for whatever parameter you want to adjust. If you have trouble let me know what parameter you want to change and I would be willing to try to modify my code to add the parameter to the preferences.

github.com

gouldner/ST-Projects/blob/master/SmartThings/src/FibaroMotion/Device/FibaroMotion.groovy

/**
 *  Device Type Definition File
 *
 *  Device Type:		RRG Enhanced - Fibaro Motion Sensor
 *  File Name:			fibarMotion.groovy
 *	Initial Release:	2014-12-10
 *	Author:				Todd Wackford
 *  Modified by:        Ronald Gouldner
 *  Email:				todd@wackford.net
 *
 *  Copyright 2014 SmartThings
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.

This file has been truncated. show original

You can see in my code that I added two preferences for option 80 and 89 which controls the LED for motion and tamper.

When you change these settings you need to triple click on the B button and when the LED displays blue click on “Configure” to send the new settings.

Of course @smart technique also works if you always want the same settings then you can just hard code the default configuration.

travisr100 · March 24, 2015, 11:35pm

Ron S, thanks! That was the missing link. I got it updated with my new parameters and I’m now getting temp reports every 15 minutes! Finally I can buy some more of these knowing that they’ll work for me. I’d never used the simulator before so wasn’t sure how it worked.

smart · March 24, 2015, 11:45pm

You will be fine, buddy! We all learn from each other here! Good luck, man!

eibyer · March 27, 2015, 5:42pm

I’ve read up to post 150 and I can’t contain my excitement so I will just ask now. I’m planning on installing this outside under an eave to detect motion at the car port. I think from scanning the last few posts, the LED can be turned off? I’m also in AZ so outside temps can be extreme. Anyone in AZ using this for outside use? There’s a possibility I can install the sensor behind a glass window if it’s possible to turn off the LED.

JDRoberts · March 27, 2015, 9:04pm

The Fibaro is a PIR (infrared) sensor. They cannot detect motion on the other side of glass.

V

patrickd · March 28, 2015, 1:25am

Ron, I get this message: “java.lang.RuntimeException: Metadata Error: input() can only be invoked inside a section definition @ line 38”

smart · March 28, 2015, 1:28am

What are you trying to do, buddy? More details!

Pre-release of Fibaro Motion Sensor

Customers

Developers

Download the SmartThings App