I've only been using the virtual switches up until now. Now for my dumb question: how are the temperature devices meant to be used (as opposed to just a simple variable)? I'm asking about this because I thought that maybe defining a virtual temperature device could allow Alexa to see the device as a thermostat, or something that could report and say the value (temperature or otherwise). This is something that's missing with Alexa: a way to have her say a number from a variable. This could be a temperature, level, percentage, etc. I tried creating a virtual temperature device and then adding it in the portal, but the device types offered don't include temperature or thermostat. I have Venstar thermostats and they do appear as thermostats, so the Alexa device type exists. It would be a great if a virtual device type that Alexa sees as a thermostat could be defined.

Hi Guy,

Not a dumb question at all.

So the temp devices have a history before me but I did for a time make use of it ; I think some of the features are a bit depreciated.

As you can see there is conversion of F to C or other way and as its called raw. The temp conversion is not as useful as the ISY has that built in now. The raw is really a divide by 10 which can be handled by precision. This is one of the devices I would like to know if there are people using it ; and if its meeting there needs or could be enhanced. So far in my rework of the code I have kept it static, even though there could be improvements.

It can be useful if you want to move from or to variables, val or init, on a periodic basis and give a nice display of the temperature.

I have had issues with Alexa and device types, not with this but with contactors versus switches versus lights. Can be very frustrating.

I do know that if we want to change this I will need to reach out to the guys at UDI and ask how that is done. Not sure if the hints have something to do with this or its something they need to hardwire. I just checked the hints for the temperature devices & they were not set. I set it to a temperature device & pushed to the non-production Store the change, its V3.1.25 and has some other minor changes. You can try that out, I don't have high confidence but would be the easiest path.

Let me know.

edit: you can install the non-production on top of your production and all will be fine. Then go back later. Not all the plugins will do that pain free.

Edited 23 hours ago23 hr by sjenkins

I'll certainly 3.1.25 a try. I have a test controller that's perfect for this. It would be really great if we could have a virtual device that Alexa could pronounce the numerical value of.

I use the temperature node to track/display a high and low value.

@tazman,

Is the value a temperature or just a generic value?

If we wrote a device from scratch, what else would it do (nor not)?

ex. Would you have alarm limits? If it hit those limits would you have the node send a CMD?

Like DON at hight limit, DOF at low. This would mean it could be used in a program or a scene.

There are some interesting possibilities in this little platform.

Just tried 3.1.25. No luck. If you have a chance, do reach out to UDI and see if making it a thermostat device is possible. It certainly would be a useful addition. Thanks!

2 hours ago, sjenkins said:

@tazman,

Is the value a temperature or just a generic value?

If we wrote a device from scratch, what else would it do (nor not)?

ex. Would you have alarm limits? If it hit those limits would you have the node send a CMD?

Like DON at hight limit, DOF at low. This would mean it could be used in a program or a scene.

There are some interesting possibilities in this little platform.

The values are pulled from some YoLink sensors and WeatherFlow node server where I send 2 push notifications with values I like to see in the morning before I reset the values with a program.