Thank you for sharing jsglazer.
also seeing this. the weird part is that it was working with fahrenheit for a long time, then ran out of battery. i think i had to futz with it a bit to get it back online after replacing the batteries, and since then it’s always been in celsius…
I never found a way to configure the sensor to report temperature in Fahrenheit. Since I’ve recently started delving into rules, I created a rule that converts Celsius to Fahrenheit. I created a dummy item (Sen02_TempA) to accept the converted value, but you may not need to.
Item:
Number Sen02_TempA "Shop TempA [%.1f °F]" <temperature>
rule:
// Celcius to Fahrenheit for Sen02_Temp => Sen02_TempA
rule "Sen02_Temp_C-F"
when
Item Sen02_Temp received update
then
val numTemp = Sen02_Temp.state as Number
numTemp = ((numTemp * 9/5) + 32)
Sen02_TempA.postUpdate(numTemp)
end
I long for a more elegant solution…but until then this works. Josh
The latest development binding, which should be merged to master in a few weeks, supports UoM for temperatures, so you can have whatever scale you like .
Any traction on this, I’m still seeing the values reporting in Celsius for my zse40?
Tried changing the setting from (C to F) in PaperUI and HABmin with no luck? I get an error 500 in PaperUI and HABmin shows no error but as soon as I go back and look at the variable its set back to Celsius?
Thanks
This is quite an old thread, and a lot has changed since the previous posts. I’m not sure if that’s what you mean by “traction”?
I was just wondering if there is a solution to the following.
Tried changing the setting from (C to F) in PaperUI and HABmin with no luck? I get an error 500 in PaperUI and HABmin shows no error but as soon as I go back and look at the variable its set back to Celsius?
I’m not sure what you are changing? If it is the internal configuration parameter, then this has been removed and will not work on 2.4 or above. Maybe you refer to something else?
I was just looking for some help, and I was trying to change the tempature reporting from Celsius to Fahrenheit?
With either HABmin or Paper UI ???
Thanks for any help.
In the new binding, this selection has been removed as the system now uses the UoM features to automatically convert data into the units your system requires. I guess you’re using an older version - it might be worth changing to the latest snapshot or milestone release?
If you use the latest version, then the system uses the configuration you make in the locale section of the configuration.
Thanks for the update, I will look for the latest snapshot and try that…
Chris
Thanks for the help that did work!
Chris
One other question, I do have two different ZSe40’s, one from (Vision Security and one from (zooz), I was trying to set up some rules over the weekend and I was not having much luck, I was wondering if you could confirm that my items file format looks right:
//node 4 is zooz and is the small one located in the Bedroom by (Vision Security)
Contact zwave_device_512_node4_sensor_binary “motion sensor node4 [MAP(zwave.map):%s]”
Contact zwave_device_512_node4_alarm_burglar
Number zwave_device_512_node4_sensor_luminance “motion sensor node 4 light level [%.1f]”
Number zwave_device_512_node4_sensor_relhumidity “motion sensor node 4 humidity [%.1f]”
Number zwave_device_512_node4_sensor_temperature “motion sensor node 4 temp [%.1f]”
Number zwave_device_512_node4_battery_level “motion sensor node 4 battery level [%.1f]”
//node 5 is zooz and has a bracket and is the one located in the Laundry room by (zooz)
Contact zwave_device_512_node5_alarm_motion “motion sensor node5 [MAP(zwave.map):%s]”
Contact zwave_device_512_node5_alarm_tamper
Number zwave_device_512_node5_sensor_relhumidity “motion sensor node 5 humidity [%.1f]”
Number zwave_device_512_node5_sensor_luminance “motion sensor node 5 light level [%.1f]”
Number zwave_device_512_node5_sensor_temperature “motion sensor node 5 temp [%.1f]”
Number zwave_device_512_node5_battery_level “motion sensor node 5 battery level [%.1f]”
Thanks again for any help…
If you link the items on the paperUI AND define the items in an *.items file, it won’t work. You need to do one or the other.
Remove the link in paperUI, delete the item zwave_device_512_node4_sensor_binary
in the paperUI
and then in the items file do:
Contact zwave_device_512_node4_sensor_binary “motion sensor node4 [MAP(zwave.map):%s]” { channel="xxxxxxxxxxx" }
Copy and paste the channel from the paperUI to replace the xxxxxxxxxx
Where do I find the channel info in PaperUI?
Here’s what I see under Properties?
Status: ONLINE
HIDE PROPERTIES
dbReference | 491 |
---|---|
defaultAssociations | 1 |
manufacturerId | 027A |
manufacturerRef | 2021:2101 |
modelId | ZSE40 |
vendor | Zooz |
zwave_beaming | true |
zwave_class_basic | BASIC_TYPE_ROUTING_SLAVE |
zwave_class_generic | GENERIC_TYPE_SENSOR_NOTIFICATION |
zwave_class_specific | SPECIFIC_TYPE_NOTIFICATION_SENSOR |
zwave_deviceid | 8449 |
zwave_devicetype | 8225 |
zwave_frequent | false |
zwave_lastheal | 2018-11-19T08:13:09Z |
zwave_lastwakeup | 2018-11-19T18:21:02Z |
zwave_listening | false |
zwave_manufacturer | 634 |
zwave_neighbours | 1 |
zwave_nodeid | 5 |
zwave_plus_devicetype | NODE_TYPE_ZWAVEPLUS_NODE |
zwave_plus_roletype | ROLE_TYPE_SLAVE_SLEEPING_REPORTING |
zwave_routing | true |
zwave_secure | false |
zwave_version | 17.9 |
Okay, is this the channel info needed?
{ channel=“zwave:device:512:node4:basic_sensor_binary” }
Yes
I hope this is appropriate to post here.
I’ve got a FGMS001 and a ZW100 reporting celsius. (16C should be 61F)
Actually, not always, I think the zw100 sends different reports for different reasons (periodic, and based on degrees changed), so, when I graph the history of the temperature bounces back and forth between 16 and 61.
I’m on 2.4.0.M7 Openhab and Zwave
my language is English and my locale is US
19:25:02.026 [INFO ] [e.core.internal.i18n.I18nProviderImpl] - Locale set to 'en_US'.
I see scale=0 in the log coming from zwave. I shouldn’t need to set scale, right?
Is there something in the zwave device configuration I need to set to F?
03-Dec-2018 20:04:20.153 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 37: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0
03-Dec-2018 20:04:20.153 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 37: SECURITY not supported
03-Dec-2018 20:04:20.153 [DEBUG] [e.internal.protocol.commandclass.ZWaveCommandClass] - NODE 37: Received COMMAND_CLASS_SENSOR_MULTILEVEL V5 SENSOR_MULTILEVEL_REPORT
03-Dec-2018 20:04:20.154 [DEBUG] [col.commandclass.ZWaveMultiLevelSensorCommandClass] - NODE 37: Sensor Type = Temperature(1), Scale = 0
03-Dec-2018 20:04:20.154 [DEBUG] [col.commandclass.ZWaveMultiLevelSensorCommandClass] - NODE 37: Sensor Value = 16.3
03-Dec-2018 20:04:20.154 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 37: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
03-Dec-2018 20:04:20.154 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 37: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_MULTILEVEL, value = 16.3
03-Dec-2018 20:04:20.155 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 37: Updating channel state zwave:device:controller:node37:sensor_temperature to 16.3 °C [QuantityType]
2018-12-03 20:04:20.157 [vent.ItemStateChangedEvent] - storageTempF changed from 16.4 to 16.3
Here’s the same node reporting as scale = 1. No system changes between the two. No reboots. nothing.
03-Dec-2018 21:10:49.563 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 37: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0
03-Dec-2018 21:10:49.563 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 37: SECURITY not supported
03-Dec-2018 21:10:49.563 [DEBUG] [e.internal.protocol.commandclass.ZWaveCommandClass] - NODE 37: Received COMMAND_CLASS_SENSOR_MULTILEVEL V5 SENSOR_MULTILEVEL_REPORT
03-Dec-2018 21:10:49.564 [DEBUG] [col.commandclass.ZWaveMultiLevelSensorCommandClass] - NODE 37: Sensor Type = Temperature(1), Scale = 1
03-Dec-2018 21:10:49.564 [DEBUG] [col.commandclass.ZWaveMultiLevelSensorCommandClass] - NODE 37: Sensor Value = 61
03-Dec-2018 21:10:49.564 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 37: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
03-Dec-2018 21:10:49.564 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 37: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_MULTILEVEL, value = 61
03-Dec-2018 21:10:49.564 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 37: Updating channel state zwave:device:controller:node37:sensor_temperature to 61 °F [QuantityType]
I think it’s the same, but here’s the FGMS001 log (but it’s always in C, not F)
03-Dec-2018 22:18:49.872 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 35: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0
03-Dec-2018 22:18:49.872 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 35: SECURITY NOT required on COMMAND_CLASS_SENSOR_MULTILEVEL
03-Dec-2018 22:18:49.872 [DEBUG] [e.internal.protocol.commandclass.ZWaveCommandClass] - NODE 35: Received COMMAND_CLASS_SENSOR_MULTILEVEL V8 SENSOR_MULTILEVEL_REPORT
03-Dec-2018 22:18:49.872 [DEBUG] [col.commandclass.ZWaveMultiLevelSensorCommandClass] - NODE 35: Sensor Type = Temperature(1), Scale = 0
03-Dec-2018 22:18:49.872 [DEBUG] [col.commandclass.ZWaveMultiLevelSensorCommandClass] - NODE 35: Sensor Value = 20.5
03-Dec-2018 22:18:49.872 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 35: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
03-Dec-2018 22:18:49.872 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 35: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_MULTILEVEL, value = 20.5
03-Dec-2018 22:18:49.872 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 35: Updating channel state zwave:device:controller:node35:sensor_temperature to 20.5 °C [QuantityType]
You should really open a new thread…
ok. I opened a new post and got the answer here: