FS-100 sensor displaying in Celsius, not Fahrenheit

[madcodger]

@Michel Kohanim

I have a Homeseer FS-100 Z-Wave Flex Sensor that is reporting temperatures in Celsius, not Fahrenheit. I have reported this to Homeseer, and they tell me that it's not their sensor, which reports only in Fahrenheit, they say, so it must be the controller. I can find no user-configurable parameters that would control this for the device, and no such parameters are noted in the device documentation. Another Z-Wave sensor in the system (a Homeseer LS-100) reports in Fahrenheit as expected, so I suspect the problem is in how the ISY reads this device's information.

So, UDI Support, if you see this, can you please look into this? While having some reporting is helpful, it would be better if it were in the expected Fahrenheit format. I have attempted to report this as a ticket on the UDI site, but it is currently just "spinning" when I do so, so I can't complete that (so you might want to look into that, as well).

Thank you.

 

[larryllix]

@madcodger You may want to include a UDI person in your post to attract their eye, using the "@" prefix. 

Do you need a conversion program workaround?

[madcodger]

Thanks, @larryllix.

D'oh! Well, yeah, the "@" would be a good idea, wouldn't it? I'm not much of a social media guy, so I often forget that it works on forums, as well. I copied Michel, as he's the only person with whom I have interacted with to any great degree. 

And yes, I would very much appreciate a conversion program, if you have one handy. Thanks in advance!

 

[larryllix]

23 minutes ago, madcodger said:

Thanks, @larryllix.

D'oh! Well, yeah, the "@" would be a good idea, wouldn't it? I'm not much of a social media guy, so I often forget that it works on forums, as well. I copied Michel, as he's the only person with whom I have interacted with to any great degree. 

And yes, I would very much appreciate a conversion program, if you have one handy. Thanks in advance!

 

Since I do not use F and work in C anyway I will have to create a program on the fly. Here goes.
 

Program 'Synchro FlexSensorTemp'   [enabled]

If
   Flex_Sensor Temperature < 999
Then
      $integerVariable = FlexSensor Temperature
      $integerVariable *= 1.8                                <---------set variable  precision at 1 or 2 digits of fraction
      $integerVariable += 32.0
      $sFlexSensorTemp = $integerVariable    <----------set variable precision at 1 or 2 digits of fraction
      $sFlexSensorTemp init $integerVariable  <---------if needed when just powering up It will be a stale value though
Else
    ----

Notes:
 - the usage of the final value state variable for calculations is discouraged, as it could trigger your downstream program(s) every time the value changes during intermediate calcs.
- the integer variable could also use a state variable, placed next to the state variable for easy finding later. I don't like to waste state variables in order to keep unused ISY engine triggering down. This may not be completely valid as I am only guessing how the ISY engine works.
- you will require v5 to save a sensor value into a variable and use decimal variables
- this program will be self running and can be placed in an obscure folder. I have one with a few dozen synchro programs. They just work and I don't need to see them.
- to use this resultant you would just use the $stateVariable instead of the FlexSensor Temperature like this
 

If
    $sFlexSensorTemp < 72.0
Then
    set heater On
Else
    wait 2 minutes
    set heater Off

 

When you get the sensor to report F instead of C, just destroy the synchro program and substitute the sensor for the variable in the usage program(s). Delete the variables.

[Michel Kohanim]

@madcodger,

Please make sure your ISY unit of measure is Imperial. If that does not work, please submit a ticket to support@universal-devices.com AND include the output of:

Right mouse click | Z-Wave | Show Information in Event Viewer | All

With kind regards,
Michel

[madcodger]

@larryllix Thanks again for your help and support. Sadly, I got pulled into a variety of last-minute things before we leave for a few weeks, and did not get a chance to try the program yet. But again, greatly appreciated and wil do so when back at this location.

@Michel Kohanim Thanks for your reply. The units (installed other Flex sensors as I was posting original note) all report in Celsius, and the ISY is now set to British Imperial (also tried on the US setting). My battery-operated temp sensors are reporting in Fahrenheit, so it’s something to do with how ISY is interpreting the data from these Flex sensors. Also, other units from the same shipment are reporting in Fahrenheit on a separate Homeseer installation in another building. Assuming I can follow through on your instructions remotely I’ll do so in next few days and send report in via support on UDI site. Tried to do that earlier but your support site was down at the time.

Not a huge issue as I can just use Celsius for now, but thanks for reply.

 

[Michel Kohanim]

@madcodger, 

Thank you. Very much looking forward to what you find. One more request, please upgrade to 5.0.16 before sending us the data.

With kind regards,
Michel

[bktong]

All, 

Was anything done on this thread/issue?  I recently also installed a HomeSeer FS-100 sensor and reports in Celsius instead Fahrenheit.  When I do a Query, it would display Fahrenheit until the next polling, then it's back to Celsius.  Thanks. 

Billy

[madcodger]

I'm the OP for this thread, and *think* I sent in a copy of my log a couple of months ago or more, but I can't tell you the exact date and time, so I won't swear to it. Please send one yourself as a support ticket (not here on the forum) just to be sure. I'll do the same. Anyway, UDI first thought it was the settings on my ISYs (it's not), then that it was the firmware for the device (I'm skeptical of it being a particular firmware version/release issue, but agree it has something to do with the device's reporting as no other types of temp sensors I own have this problem).

Homeseer, of course, blames UDI and says their device doesn't even report in Celsius. I've learned to be skeptical of such claims. Anyway, please become a fellow squeaky wheel as to date I've been the sole one, with no relief to date.

Anyway, the  bright sides to date are that 1) this is easily the most reliable temp and moisture sensor I own, when plugged into an AC power source and 2) my Canadian and European friends are impressed with my now-much-improved C to F/F to C mental calculation abilities. .

[bktong]

Here is a quick and short log on the sequence events.  When I query, the log shows in Fahrenheit and a minute later the system polls the device again and now it's in Celsius.  Is this what you are looking for (see attached)? 

UDReport.txt

[madcodger]

21 hours ago, bktong said:

Here is a quick and short log on the sequence events.  When I query, the log shows in Fahrenheit and a minute later the system polls the device again and now it's in Celsius.  Is this what you are looking for (see attached)? 

UDReport.txt 415 B · 2 downloads

They are looking for a log sent as a support ticket, in their website. This forum isn't really for UDI to provide support. They chime in at times, but they can't track things from here. So, suggest you send as attachment via a support ticket.