I think there is possibly a bug in selecting the Fahrenheit temperature reading for a Yolink temperature sensor in a program. I'm working on displaying various Yolink temperature sensors in UD mobile. I have a program that reads a temperature sensor and assigns the temperature to a variable. When I check the variable it always shows the Celsius temperature regardless of selecting Fahrenheit or Celsius in the drop down box.

When I check the node in PG3 it shows the correct temperature in Fahrenheit.

I also have an Ambient Weather station and if I select Fahrenheit for it's temperature sensor I gets the correct number.

In the PG3 Yolink configuration I have TEMP_UNIT set to F Is this correct? How does this interact with the Program dropdown selection of Fahrenheit vs Celsius?

Edited 8 hours ago8 hr by MMAltair
added detail

Update -

After investigating some more I'm even more confused. When I look at the Yolink temperature sensor node in the administrative console it shows the correct value in Fahrenheit, which is what is selected in the Yolink plugin in PG3.

What I have noticed is that when I select Fahrenheit in the Program settings dialog box it does not reflect this setting when added to the Then clause in the program. Ex -

The Yolink Node is at version 1.6.2 and is installed in slot 9 in PG3. I have noticed recently that when I synchronize UD Mobile with EISY it is complaining about a Status Name being missing for Node server 9. I'm not sure what this is about.

I agree it is confusing - I actually think it is a bug in the console -

I use a special method to specify temperature - I specify an option for F and an option for C (and an option for unknown as text)- otherwise I would need to generate 2 versions of any node that has different unit support (and code for each of them)

The unit defaults to C (as this is what YoLink uses as default) and is changed (forced) to F whenever data is accessed - Console knows both exists and I believe in this case believe it selects the default - It may be there is something I can do to fix this (besides having one C variable and one F variable in the node), but I do not know how to.

Edited 49 minutes ago49 min by Panda88