[quote=“manish500, post:80, topic:170555”]I am very new to all this. Just ordered vera lite. I would like to pick up the 3M-50 at home depot.
Can I use this thermostat with vera lite
If yes, what else (interface) do I need to make this work with vera. Is it just a software type plug in that I download, or do I need a physical device?
Once you get your Vera Lite installed and updated to the latest firmware, you’ll just need to install the thermostat plug-in to have it work with the 3M-50. It takes just a couple of clicks. Full instructions for installation and setup of the plug-in can be found here:
Anyone using the SQ Remote HD app? This plugin works perfectly using Automator.app but when I use SQ Remote, the Fan control (Auto and On) does not seem to have any effect. Temperature control works correctly. Any known workarounds?
I used to be able to see and control the thermostat thru iVera on my iphone but now the thermostat is gone (from iVera only), it still works fine on UI5 webportal . Any ideas?
Is it not working at all? (i.e. if your fan is not currently running, and you set the fan to “On” mode, does the fan start?)
There is a bug in the current version that the On/Auto status takes a while to update in the UI, even though the thermostat itself is correctly set to the right mode.
The fix will be in the next release, which should be out in a day or two.
Thanks for the reply Hugh. I don’t think your problem lies in your excellent plugin, but I thought there might be a workaround.
Right, if my fan is either set to On or Auto, and I select the other, using SQ Remote HD, the mode on the app changes, but the mode never changes either directly on the thermostat nor looking at your plugin on UI5. However, this behavior only happens using SQ Remote HD. Changing the mode using UI5 or Automator.app, it functions correctly.
I am thinking at one time, I had the same problem. I contacted iVera and was told that the thermostat had to be associated with a room. As soon as I added the thermostat to a room in the user interface, the thermostat then showed up on my iPhone.
Sorry for the very late reply… I missed your question in the forums. (I need to figure out how to get an automatic notification of any new 3M-50 topics).
Anyway, your issue is very likely due to the device “compatibility” changes that were made in Version 2.0+ of the plug-in. To make a long story short, in order for your thermostat to show up in iVera, you’ll need to go into the Vera UI advanced settings tab for your 3M-50 thermostat, change the value of the “CreateGenericDevice” field from “0” to “1”, and click “Save”.
Yes, Still the same problem, iVera shows the thermostat but cant control it
[quote=“hugheaves, post:91, topic:170555”][quote=“mmaslank, post:90, topic:170555”]@ Hugh
…Update…iVera will show the thermostat now but wont be able to control it :([/quote]
mmaslank,
Sorry for the delayed reply, it’s been a very busy few weeks and I haven’t had chance to check the message boards.
Are you still having this issue? If so, let me know and we can try and figure out what the issue is.
Yes, Still the same problem, iVera shows the thermostat but cant control it[/quote]
Ok, i don’t have an iOS device, but let’s see if we can figure out what’s going on.
First, a couple of sanity checks:
In the Vera UI, on the advanced tab for the 3M-50 thermostat device, what do you have for the values of “PluginVersion”, and “FirmwareVersion”?
Can you control the 3M-50 in the Vera UI using the “generic thermostat device” that was created when you turned on “CreateGenericDevice”? (i.e. the one that doesn’t have the 3M-50 icon).
Let me know, and we’ll continue troubleshooting from there.
Huge thanks to Hugh for the wonderful plugin. I’ve got a question on the RemoteTempDevice. I have my 3M50 working properly with RemoteTempDevice=11 in order to use a sensor (device#11) placed in a room upstairs as the point to control in the tstat. The main display on the tstat shows the remote temp value. Even the radiothermostat.com web interface shows the remote temp as the current temperature. This part works great.
But I wonder if I can still read the actual temperature at the location of the tstat? It looks like the CurrentTemperature of the tstat is replaced by the value of the remote sensor. I tried polling TemperatureSensor1 of the tstat and no difference. I tried putting the tstat device# in the PMATempDevice and no dice (shows the remote sensor temp).
Second question, I’d like to switch the tstat between using the actual temp during the day vs. the remote temp at night. I can write a luup code to read/write the RemoteTempDevice variable and put it in a scene or virtual switch to achieve that. My question is when I change the variable, what do I put in the code to ‘Save’ it? Like when we the web UI we always click ‘Save’ whenever we change a value to reboot the luup. Again thanks.
Remember there are different URN’s for cool setpoint and heat setpoint. In my case I use the 3M-50 with Fahrenheit. I haven’t played around with Celsius.
And by the way, I’m not sure you have to click “Save” for your temperature setting to take effect. The 3M-50 has kind of a wimpy processor, and the radiothermostat.com documentation suggests you shouldn’t make requests more often than every 15 seconds. If you watch the debug logs, Hugh’s code will try several times over the course of a few minutes to try and set the temperature setpoint. With a little patience, you’ll note your changes will eventually take effect–usually fairly rapidly.
As far as luup code goes, the SetCurrentSetpoint action is all you need to do. There is no step to “Save” it. Hope that helps!
[quote=“SM2k, post:95, topic:170555”]nanotube: I only have a useful response to the second half of your question. I suspect you’re looking for code like:
Remember there are different URN’s for cool setpoint and heat setpoint. In my case I use the 3M-50 with Fahrenheit. I haven’t played around with Celsius.[/quote]
Thanks. Silly me forgot I could check Hugh’s source codes. So I did some digging. To answer my own questions, I found that
Once RemoteTempDevice is used, it’s impossible to find out the thermostat temperature. Turns out this function uses the RTCOA API /tstat/remote_temp, which when set, causes the any queries to the tstat to return the remoteTemp value (tested using /tstat/temp API). So it’s a problem with the 3M50’s API, not Vera’s fault. I just hope someone finds a better API or a hidden API in RTCOA’s collection that returns the actual device temperature.
I know user/consumer is advised to use call_action instead of variable_set but the actions you mentioned are for the legacy/generic uPnP tstats. After reading through Hugh’s codes I couldn’t find an action name to set the variable “RemoteTempDevice”. Still this gave me some ideas though. I am going to create two scenes using variable_set and give it a try later.
The code I posted was lifted from my own luup, so I know that method works. your mileage may vary. Setting the variable might work as well. Never tried it that way.
[quote=“nanotube, post:97, topic:170555”][quote=“SM2k, post:95, topic:170555”]nanotube: I only have a useful response to the second half of your question. I suspect you’re looking for code like:
Remember there are different URN’s for cool setpoint and heat setpoint. In my case I use the 3M-50 with Fahrenheit. I haven’t played around with Celsius.[/quote]
Thanks. Silly me forgot I could check Hugh’s source codes. So I did some digging. To answer my own questions, I found that
Once RemoteTempDevice is used, it’s impossible to find out the thermostat temperature. Turns out this function uses the RTCOA API /tstat/remote_temp, which when set, causes the any queries to the tstat to return the remoteTemp value (tested using /tstat/temp API). So it’s a problem with the 3M50’s API, not Vera’s fault. I just hope someone finds a better API or a hidden API in RTCOA’s collection that returns the actual device temperature.
I know user/consumer is advised to use call_action instead of variable_set but the actions you mentioned are for the legacy/generic uPnP tstats. After reading through Hugh’s codes I couldn’t find an action name to set the variable “RemoteTempDevice”. Still this gave me some ideas though. I am going to create two scenes using variable_set and give it a try later.[/quote]
@nanotube, glad you were able to figure most of this out. Yes, there is no API to set RemoteTempDevice as you discovered, but setting the variable should work. (I say should because I’ve not actually tested changing the remote temp device “on the fly”).
Also, you’ll need to set RemoteTempSet to “0” otherwise the thermostat plugin will keep trying to send the last received temperature from the temperature device to the thermostat.
Let me know if you run into any problems getting this to work, and I’ll see what I can do.
I know this plug-in was originally designed for the 3M-50 Thermostat with USNAP wifi module. Will this plug-in work with different thermostats that also use the same USNAP module?
I am interested in the Lockstate Connect branded LS-90i thermostat. It looks to be the same as the Radio Thermostat branded CT80 so I am guessing they are the same unit.
Is there a good chance this unit will work with this plug-in?
