HomeGenie Forum
General Category => Troubleshooting and Support => Topic started by: bradvoy on June 21, 2015, 05:57:27 AM
-
I have 2 Radio Thermostat CT101 Z-Wave thermostats. I used to be able to control these via HomeGenie, but I'm no longer able to. I think the problem may have started at the time I switched the thermostats from heat mode to cooling mode, but I'm not sure. Maybe it was at the time of a HomeGenie update.
HomeGenie is able to poll the thermostats and display the current temperature. But it does not display the correct mode and setpoints for the thermostats. And if I try to change the setpoints via the thermostat widget, no error messages are displayed but the thermostat settings don't change.
I don't have a good understanding of how to go about investigating a problem like this with HomeGenie. Are there logs I should be looking at? Or other ways to troubleshoot this?
-
I don't have zwave or smart thermostat yet but thought I might offer some advice...
Go into config, maintenance, user interface and make sure event history is enabled. Then in the upper right of HG web page is a blue, circle, click it. Now you will have a log of messages, at the bottom you can filter them. Once on this screen change a setting on the thermostat that you know works and you should see a message for it. Then try filtering it based on the thermostat source id, or some unique domain text. Once you are confident that is working, then start changing various settings and thermostat and look for expected data here.
Post some of your results here and hopefully a zwave expert can help.
-
Thanks Kevin. I had not understood how to use the Event History.
After enabling the Event History, when I try to change the thermostat setting I see the following event:
2:40:54.559 PM Thermostat.SetPoint.Cooling 78 11 HomeAutomation.ZWave
That all looks correct to me. 11 is the Z-wave node number for the thermostat and 78 is the Fahrenheit temperature I selected.
-
What thermostat program are you using. I skimmed through the Weather Environment- Basic Thermostat code and I didn't notice logic to do cooling, only heating.
Is there another thermostat program people are using?
-
That's a good question Kevin. I think I'm using the homegenie/generic/thermostat widget. There must be some way to verify that, but I can't see it in the interface. Can anyone give me a pointer on that?
Also, I notice that there is another widget called DaniMail/generic/thermostats. Does that one work with Z-Wave thermostats? Can anyone comment on whether that one might work better for my situation?
-
Can you post a screenshot of the widget? There may be some text on it which gives a clue. There could possibly be multiple programs (code) using the same thermostat widget. When you add widgets they are usually grouped in a way to show which program created them. But once it has been added, not sure if we can tell.
-
Hello,
The widget homegenie/generic/thermostat widget is used by the default Thermostat module and the program Basic Thermostat.
The Basic Thermostat i's used only in Heating state. And yes it will work with ZWave sensor.
There is a difference between Sensor and Thermostat.
- Sensor give only the temperature, and in that case Basic Thermostat can control a relay (ZWave or other).
- Thermostat is able to control its own relay. The program as to set the temperature value on it. In that case it is the default Thermostat Widget by internal ZWave program of HG that send the risen tempertaure to the module. That's work if the module is automatically recognise by HG.
For know you have to check the technical specs of the equipement.
Cheers
Dani
-
I've attached a couple of screen shots of the thermostat widget I'm using. I think it's the homegenie/generic/thermostat widget.
-
Have you get tat technical sheet ?
https://radiothermostat.desk.com/customer/portal/kb_article_attachments/20336/original.pdf?1379455676
It speaks that in you want to control the temperature remotely you need a complementary modole called USNAP ZWave module. Do you have it ? I understand if not, you can send only BASIC_COMMAND_CLASS with value 0 or 1 in simple mode (PG 7), and then you have only access to Enargy saving Mode and Comfort Mode.
-
Dani, thank you for attempting to help me diagnose this problem. I appreciate your time and attention.
The USNAP Zwave module you linked to is for older versions of the Radio Thermostat thermostats (CT30, CT50, CT80). My CT101 thermostats have the equivalent of this module already built in.
I am able to change the Fan Mode (On, Auto) and change Operating Mode (Off, Cool, Heat) with HomeGenie. And HomeGenie is correctly displaying the current temperature from my thermostats. The only part that is not working is that I can't change the heating or cooling setpoints from HomeGenie. This used to work with an older version of HomeGenie. I'm not sure exactly when it stopped working, but I think it was with some update that came out between March and June of this year.
-
I am in version r493 and that works correctly as you can see in the log trace and my thermostat works, only it has the mode Auto. It's a Qubino factory.
I think the best way is to save your configuration and make a clean instal.
Cheers
Dani
-
I tried doing a clean install of HomeGenie, but unfortunately that didn't make any difference. My log trace looks similar to the one Dani posted. It doesn't show any errors, but the setpoints don't get changed on the thermostats. I'm wondering if it could possibly be a unit conversion problem. The widgets are displaying the current temperature and the setpoints in Fahrenheit (which is what I want). But could there be a problem where the widgets are sending new setpoint values to the thermostat in Fahrenheit and the thermostat is expecting Celsius?
-
In the screnshot of trace which value is sent ? Celsuis or Farenheit ?
-
The trace shows Fahrenheit values being sent.
-
And your equipment wants receive which value ? If celsuis I can guide you for modify the widget file
-
My thermostats use Fahrenheit on their front panels. But I don't know if they are expecting Celsius or Fahrenheit in ZWave commands.
I found the following entry in the HomeGenie log:
"2015-06-28T21:13:05.3783250-06:00 HomeAutomation.ZWave 10 ZWave Node Sensor.Temperature 25.0"
I believe that indicates that the thermostat reports the current temperature in Celsius. So maybe it's expecting to receive setpoints in Celsius also.
The log also contains many instances of the following errors. I don't know if these are related to this problem or something different:
"2015-06-28T20:46:56.0302830-06:00 HomeAutomation.HomeGenie.Automation 92 Automation Program Program.Notification {""Title"":""Z-Wave Thermostat Poll"""
"2015-06-28T20:46:56.0392470-06:00 HomeGenie.System Console StdOut/StdErr redirect Console.Output ZWave Interface Exception: Object reference not set to an instance of an object"
at ZWaveLib.CommandClasses.SensorMultilevel.Get (ZWaveLib.ZWaveNode node) [0x00000] in <filename unknown>:0
at MIG.Interfaces.HomeAutomation.ZWave.InterfaceControl (MIG.MIGInterfaceCommand request) [0x00000] in <filename unknown>:0
And I also see the following error in the log from the times when I attempted to change the setpoint via the HomeGenie interface:
"2015-06-28T20:47:52.3859400-06:00 MIG.Gateways.WebServiceGateway 192.168.1.127 api/HomeAutomation.ZWave/10/Thermostat.SetPointSet/Cooling/79/1435546075629 HTTP GET"
"2015-06-28T20:47:52.3876650-06:00 HomeGenie.System Console StdOut/StdErr redirect Console.Output SPO < 01 0C 00 13 0A 05 43 01 02 01 4F 05 06 E2"
"2015-06-28T20:47:53.5920800-06:00 HomeGenie.System Console StdOut/StdErr redirect Console.Output SPI > 01 05 00 13 06 00 EF"
"2015-06-28T20:47:53.5922440-06:00 HomeGenie.System Console StdOut/StdErr redirect Console.Output SPO < 06"
Hopefully some of that information is helpful. Thanks again for the time you've spent on this.
-
Here is one more bit of information. I see entries like this in the HomeGenie Event Monitor:
1:18:56.845 PM Sensor.Temperature 78.008 11 HomeAutomation.ZWave
So this is showing Fahrenheit temperatures. I don't know how to reconcile that with the HomeGenie log entries that show Celsius values for these Sensor.Temperature readings.
-
1 - I saw that the SetPoint is sent to ZWave Node 11.
2 - And the Sensor.Temperature is received from Node 10.
Is it normal way ? That is the same equipment ? Normally Theremostat Node make the 2 functions.
And yes I don't undertand the ZWave Polling thermostat Node. If you invalidate that function do you continue to receive the temperature ?
-
I have 2 thermostats, one upstairs and one on the main floor. One is ZWave node 11 and the other is ZWave node 10. In the examples I posted earlier I happened to mix messages from both. I actually see similar messages from both of them, and they both have the problem where they don't respond to setpoint changes.
I'll disable the ZWave polling program and see if HomeGenie continues to get the temperature from the thermostats.
-
I confirmed that if I disable the ZWave polling program then my thermostats no longer display the current temperature.
-
Dani, did the information in my previous 2 posts answer your questions? Is there any other information I can gather to help troubleshoot this problem?
Thanks,
Brad
-
The error StdErr you get is when the port (USB ZWave key) is not connect.
If you get many time that error, that means that USB is disconnected, or perhaps if you use Raspberry, the main supply is not strong enough. If it's 1 Amp it is not suffisant prbably. Try a main supply of 1.2 ou 2 Amps will be a good test.
Sure if ZWave controller is deisconnected many time, you get an erratic result. You must never get that error of StdErr on ZWave controller.
-
I'm pretty sure there is no problem with my USB ZWave key. It's working very reliably with my ZWave lights. And it works fine with my thermostats when I want to change modes and when it's reading the current temperature. It's only when I try to change the thermostat setpoints that I have trouble. I'm not running it on a Raspberry Pi; it's on a desktop computer running Ubuntu.
I'm no longer seeing the first error that was in my earlier post (ZWave Interface Exception: Object reference not set to an instance of an object). That was apparently a one-time problem.
The log still shows many instances of this sequence of error messages:
2015-07-07T15:15:30.2768520-06:00 HomeGenie.System Console StdOut/StdErr redirect Console.Output SPO < 01 09 00 13 07 02 20 02 05 59 9E
2015-07-07T15:15:30.2912630-06:00 HomeGenie.System Console StdOut/StdErr redirect Console.Output SPI > 06
2015-07-07T15:15:30.2914010-06:00 HomeGenie.System Console StdOut/StdErr redirect Console.Output SPO < 06
2015-07-07T15:15:30.4916400-06:00 HomeGenie.System Console StdOut/StdErr redirect Console.Output SPI > 01 04 01 13 01 E8
2015-07-07T15:15:30.5418130-06:00 HomeGenie.System Console StdOut/StdErr redirect Console.Output SPI > 01 05 00 13 59 00 B0
2015-07-07T15:15:30.5419200-06:00 HomeGenie.System Console StdOut/StdErr redirect Console.Output SPO < 06
2015-07-07T15:15:30.5919820-06:00 HomeGenie.System Console StdOut/StdErr redirect Console.Output SPI > 01 09 00 04 00 07 03 20 03 00 D5
2015-07-07T15:15:30.5921070-06:00 HomeGenie.System Console StdOut/StdErr redirect Console.Output SPO < 06
Before I thought these were associated with the ZWave setpoint commands. But I see now that they're not. I don't know what's causing them or what they mean, but they happen repeatedly even when I'm not doing anything with the thermostat.