That’s a good idea. Here is the config of my zwave devices:
// Fibaro Multisensor (FIB_FGMS-001)
Number Movement "Movement: [%s]" <present> { zwave="4:0:command=sensor_binary" }
Number Alarm "Alarm: [%s]" <fire> { zwave="4:0:command=sensor_alarm" }
Number Lux "Lux: [%.2f Lux]" <sun> { zwave="4:0:command=sensor_multilevel,sensor_type=3" }
Number Bat "Battery: [%d %%]" <energy> { zwave="4:0:command=battery" }
Number Temp "Temperature: [%.1f °C]" <temperature> { zwave="4:0:command=sensor_multilevel,sensor_type=1" }
// Fibaro Wall Plug (FIB_FGWPF-101)
Switch Wall_Plug "Wall Plug" { zwave="3:command=switch_binary"}
Number Wall_Plug_Power "Wall Plug - current energy [%.1f W]" { zwave="3:command=sensor_multilevel"}
Number Wall_Plug_Energy "Wall Plug - total energy [%.2f KWh]" { zwave="3:command=meter" }
CT100 with refreshing setpoints (so manual changes are captured) items:
Number HVAC_HeatSetPoint "Heat Set [%.0f F]" <temperature> (gHVAC) {zwave="7:command=thermostat_setpoint,setpoint_type=1,setpoint_scale=1,refresh_interval=20" }
Number HVAC_CoolSetPoint "Cool Set [%.0f F]" <temperature> (gHVAC) {zwave="7:command=thermostat_setpoint,setpoint_type=2,setpoint_scale=1,refresh_interval=20" }
Number HVAC_Temperature "Temperature [%.1f F]" <temperature> (gHVAC) {zwave="7:1:command=sensor_multilevel,sensor_type=1,refresh_interval=60" }
Number HVAC_Humidity "Rel Humidity [%.1f %%]" <temperature> (gHVAC) {zwave="7:2:command=sensor_multilevel,sensor_type=5,refresh_interval=60" }
Number HVAC_Mode "Mode [MAP(thermostatMode.map):%d]" (gHVAC) {zwave="7:command=thermostat_mode" }
Number HVAC_Fan_Mode "Fan Mode [MAP(thermostatFanMode.map):%d]" (gHVAC) {zwave="7:command=thermostat_fan_mode" }
Number HVAC_Operating_State "Op State [MAP(thermostatOpState.map):%d]" (gHVAC) {zwave="7:command=thermostat_operating_state,refresh_interval=60" }
Number HVAC_Fan_State "Fan State [MAP(thermostatFanState.map):%d]" (gHVAC) {zwave="7:command=thermostat_fan_state,refresh_interval=60" }
Number HVAC_Battery "Battery State [%d %%]" (gHVAC) {zwave="7:command=BATTERY"}
Sitemap definitions (with coloring):
Frame label="Thermostat" {
Setpoint item=HVAC_HeatSetPoint minValue=45 maxValue=90 step=1 valuecolor=[>0="red"] labelcolor=[>0="red"]
Setpoint item=HVAC_CoolSetPoint minValue=60 maxValue=90 step=1 valuecolor=[>0="blue"] labelcolor=[>0="blue"]
Text item=HVAC_Temperature
Text item=HVAC_Humidity
Text item=HVAC_Mode valuecolor=[0="gray",1="red",2="blue",3="green"]
Text item=HVAC_Fan_Mode
Text item=HVAC_Operating_State valuecolor=[0="gray",1="red",2="blue"]
Text item=HVAC_Fan_State valuecolor=[0="gray",1="green",2="green"]
Text item=HVAC_Battery
}
Thanks alot for the example configs!
I’m also using the Aeotec Multisensor, but I can’t make it work. It seems to randomly send values.
Most often I get battery, temperature and motion but I have never seen any values of humidity and luminance.
Note that the multisensor does not send these values by default - you need to enable them in the configuration of the sensor (ie in HABmin). I think it’s normally parameters 100 to 103, but take a look at the manual - it should tell you there…
I have two of them working in my setup. Here is what I had to configure in Habmin. On Configurgation tab, Binding, z-wave binding, expand to your Aeon multisensor node, expand Configuration Parameters.
3: On Time: 30 (this is just personal preference of 30 second reports, I wanted to see how long the battery would last. so far have 58% left after about a month and a half.)
4: Motion Sensor: Enabled
5: Command to send when movement: Send binary report
101: Which reports to send automatically in timing to group 1: 225
102: group 2: 0
103: group 3: 0
111: Interval to send out reports to group 1: 240 (also personal preference for testing battery life)
112: Interval to send out reports to group 2: 720
113: Interval to send out reports to group 3: 720
Hope this helps get everything working. I found those parameters on someones guide when doing a google search
Jim,
That Aeotec Door/Window sensor you have configs for. I just got one and I have had nothing but problems trying to get it configured. I was wondering if you had any advice or things you had to do to get it working? I can’t seem to get it initialized correctly (it will never create my node.xml file), I was able to get the open/close working first but the battery and alarm never reported. I messed with the Habmin config and got the alarm and battery working but now the door open/close is broken and the magnet trigger just sends a battery report, lol. Now I’m wishing I had just left it alone so the door sensor still worked. Any help/suggestions would be great.
Well, I can tell you I have parameter 121 set to 256 and I am getting alerts back to the Z stick every time the door opens. Other than that, nothing I can see that is special. The battery life is still 100%. When first setting it up, I had to take a paperclip and push the little center button a few times. Never had to hold it in or anything. Now when I reset OpenHAB (running OH2 and Habmin2), and I want it to register things, I can just poke the button one time, and it creates the xml without issue. The only other thing to mention is it is part of a mesh and has at least 2 neighbors that have line power. It really has been a dependable device to date.
I had a hard time of setting up the Zwave.me Double paddle wall switch WCD1 (this also works with the newer model WCD2), so I would like to share the inputs I got from different forums:
Include the device (send additional NIF according to the manual if it does not show up right away)
Go to habmin and change the configuration parameters to:
11: Send scenes 12: Send scenes 13: Send scenes 14: Send scenes
Set all four Association Groups to a member for your controller (for example Group 1 … Node 1 … Member and so on)
Again, send some NIF to transfer the new values to the device
Start openhab in debug mode, push all buttons at least once and find out the scene numbers in openhab.log, you will need those for your items:
Number Temperature { zwave=“4:0:command=SENSOR_MULTILEVEL,sensor_type=1” }
Number Set_Temp { zwave=“4:command=THERMOSTAT_SETPOINT,setpoint_type=1,setpoint_scale=0” }
Number Mode {zwave=“4:0:command=THERMOSTAT_MODE” }
DateTime LastUpdated { zwave=“4:command=info,item=LAST_UPDATE”}
It would be great if this kind of information was available on the Wiki in as browsable/searchable way, e.g. structured by manufacturer (Fibaro, Vision, etc.) and model (e.g. FGK-101, FGMS-001, etc.)