Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Can be absolute, like 20, 18, etc., or relative, like +2, -2, etc. The temperature is always in degrees celsius, and the application is expected to convert to Fahrenheit if necesssary.
Sounds like a feature request.
Hi, sorry, but no there is no way to adjust how the thermostat communicates through zwave. If you have any additional questions please don't hesitate to contact us.
iptables -A BLOCKLIST -s 220.127.116.11 -j DROP
Perhaps my question wasn't very clear.
Your thermostat interprets commands sent over Zwave and modifies its settings (example heating termperature setpoint) accordingly. The means by which it interprets those zwave commands is what I am questioning, and is irrespective of the Zwave controller.
The zwave controller manufacturer will not be able to help me with this and will refer me back to you.
Please tell me if there is a way to change the behaviour of the CT100 so that it interprets temperature setpoint changes received via Zwave as degrees Celsius as opposed to degrees Fahrenheit (note that I'm not referring to the display units which is a different matter).
Did you check with the manufacturer?
There is nothing in the template that decides what unit the temperature is interpreted as. All my devices works as expected (I also use Celsius) and I don't recall having to do anything special. But I do think some devices has a configuration setting to toggle the unit it interprets values as - you should read the manual for your device.
See page 5
*Implements adding new orbiter from splash screen
*Implements switching between form factors. Ex: it is on the phone skin, but you want the tablet one.
-This is under the advanced menu on both Android Tablet and Phone UI
-Switched smokey skin to default for Android tablet.
*Added A-Z jumping functionality to Android tablet media grid.
*multiple other smaller fixes.
Anyone besides me tested these yet?
Please keep in mind that the z-wave implementation in Lmce 12.04 (based on open-zwave) is a lot different than the one in Lmce 10.04.
In comparison, the open-zwave based version has a lot more features and is very well maintained, but is also much pickier when it comes to its zwave-network setup.
Open-zwave needs a very good and stable z-wave network to work good, so if things worked in Lmce 10.04, that does not necessary mean they work as good in Lmce 12.04.