Posted Wednesday at 07:29 PM3 days 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 Wednesday at 07:49 PM3 days by MMAltair added detail
Wednesday at 09:03 PM3 days Author 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.
Thursday at 03:18 AM3 days 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 Thursday at 03:35 AM3 days by Panda88
Thursday at 01:43 PM2 days Author 10 hours ago, Panda88 said: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.Thanks for the feedback. It does appear to be related to the console since I can select Fahrenheit in the drop down box but it doesn't get applied when the Action is applied. As I mentioned in my first post I have an Ambient Weather system and have the plugin for this system installed. When I create a program using this plugin it allows me to select Fahrenheit or Celsius and the correct selection gets applied when the Action is added to the Then or Else clause. I think this means that it is possible for this to work but perhaps it means, as you said, all of the temperature values would need to be duplicated in the node. It would take looking into the Ambient Weather plugin to see how it is done there.I'm surprised no one else has run into this?My next step is to try and implement the math to do the conversion in the program.Thanks again!
Thursday at 01:57 PM2 days Author 10 minutes ago, MMAltair said:Thanks for the feedback. It does appear to be related to the console since I can select Fahrenheit in the drop down box but it doesn't get applied when the Action is applied. As I mentioned in my first post I have an Ambient Weather system and have the plugin for this system installed. When I create a program using this plugin it allows me to select Fahrenheit or Celsius and the correct selection gets applied when the Action is added to the Then or Else clause. I think this means that it is possible for this to work but perhaps it means, as you said, all of the temperature values would need to be duplicated in the node. It would take looking into the Ambient Weather plugin to see how it is done there.I'm surprised no one else has run into this?My next step is to try and implement the math to do the conversion in the program.Thanks again!I went ahead and implemented the math to do the conversion in each of the programs that read Yolink temperature data and this worked just fine. Problem solved. Thanks again!
Thursday at 04:25 PM2 days I think the only way is to make two different node definitions - it may be possible, and I can take a quick look to replace one on the fly - if so it is an option - I will not start developing two sets of nodes for each device
Thursday at 04:52 PM2 days Author 2 hours ago, Ross said:Mine shows F in the program. But, I'm on 1.5.16.I was on 1.5.16 when I first tried this and then upgraded to 1.6.2 to see if it helped, no joy. The fact that it works for you is interesting. Which version of IoX are you running?
Thursday at 04:55 PM2 days I do not believe it works - it is internal to the console - it does not convert - only show the unit of the number provided My only solution would be to overwrite node definitions - not select between the units as I do now It has not been an issue for be as I work in C
Friday at 04:56 PM1 day I think I found a solution - I can create two nodes one for F and one for C and select them dynamicallyThe only issues is the water sensors that have the same issue but besides temperature they have water volume (4 units) so it creates 8 nodes I'll try to get it done in next release, but you will need to fix your code then
19 hours ago19 hr @MMAltair I get confused with all the versions of this and that in this universe, but I'm using an ISY and the version is 5.3.4. If that's not what you are looking for, please let me know how to find it. Thanks,Ross
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.