There’s no indoor humidity. I assumed all thermostats would have a humidity reading (obviously wrong). It is easy enough for me to make it optional, but I’d like to think about how to make the humidity channel disappear when indoor humidity is not available. At the same time I’d like to bring the current release up to my version. I’ll set it up tomorrow and update the thread. Thanks.
This thermostat at least can’t control the humidity so I guess there’s no reason for it to have a sensor for it.
I don’t think any of them can (at least might can’t). Well, with openHAB integration it does now, because I use it to turn on bathroom fans and dehumidifiers.
Breaking down the problems on your first go with the binding.
I think I have resolved that issue and a new version has been released.
I’m not sure what went wrong. I think you were right the missing UI log level setting was due to the binding being broken. The UI log level is available on mine. Please verify that it is available when the thermostat is working properly.
I’ve added code to restart the API and do an initial load of thermostats and sensors after the authorization through the connect Honeywell servlet. This should make the initial setup a little more seamless.
Let me know how the new version works. Thanks.
First I just removed the add-on through the Add-on store and reinstalled it from there without removing the old Things. When the add-on became reinstalled the Thermostat Thing went back to configuration pending and then to a new error:
Thermostat data received from Honeywell not understood: Schedule data update is not a valid item: Cannot invoke "com.google.gson.JsonElement.getAsString()" because the return value of "com.google.gson.JsonObject.get(String)" is null
To be thorough I removed the Thermostat Thing and rediscovered it through the Inbox, which worked as expected this time. Same error.
Logs for all of the above are below. Too big for the forum so uploading a file again.
openhab.log (192.3 KB)
I missed a priority type field that my thermostat has that yours does not. I think that is the last one, but I thought that before and I was wrong . I made the priority type optional and checked the other “schedule” type fields that are imported on the data feed.
https://github.com/protectivedad/openhab-addons/releases/download/beta-v1.6a/org.openhab.binding.honeywell-4.2.3-SNAPSHOT.jar
I’ll wait to release until it is running properly.
Hi, I have the same thermostat as Rich Koshak. Obviously, I have exactly the same issue.
Did you manage to get it working with T6 finally? I can beta test any build if you want.
Thanks.
I was waiting on the one I linked being tested. Have you used the one in the post above? I haven’t had any feedback on that one yet. Let me know, it should have fixed the last problem. If there is a new issue post the logs. I was waiting on finally getting the T5/T6 working before releasing a new beta. Plus I need to update it to 4.3 now that it is out.
Hi, Yes I did install the latest 4.2.3 Snapshot provided and I still have the issue. I’d set the log to trace so if you need it, I’ll provided it.
Honywell_binding_trace.json (19.9 KB)
Here’s the log taken a few minutes ago
Also, I’m still on 4.2 if you want to fix the issue before updating it to 4.3. In both case,I should be able to test it.
Can you get me the md5 of the jar you are using? Based on the log you sent me the update I posted here:
Should work. Plus copy the error in the thing for me.
EDIT:
I think it is a different error. Post the thing error message for me please. If you are using the one I posted I think it got a little farther. It then got stuck on your thermostat data not having any room informatiion. My binding populates the OpenHAB location with the room name from the thermostat feed. Which yours does not have. Once I confirm I’ll send an update.
Yeah, that is a different error. Here is a test build that will get past the latest error. Unfortunately, Honeywell doesn’t have a testing API, and I don’t know how to take your file and feed it into my program except through the real API. But cross fingers this will get the Thermostat thing working for the T5-T6.
https://github.com/protectivedad/openhab-addons/releases/download/beta-v1.6b/org.openhab.binding.honeywell-4.2.3-SNAPSHOT.jar
I apologize for missing the post. I was waiting for a version to test and missed that you already posted it.
I can confirm the latest jar file you just posted at least gets the thermostat Thing to become ONLINE. On to test the Channels.
Thanks for the work on this and again, sorry I missed the previous post with the new version.
Question: Way back when I was messing with this API there was a way to independently control the fan. Is that end point still there and can it be exposed as a Channel?
All channels appear to be reporting.
No problem. I appreciate your testing it. The fan information and controls are in the API, but I’ll need to do a bit of work to get them “out” where you can use them. I’ll put it on a TODO for after I’ve gotten this sorted and published. Continue testing it and let me know if there are any other issues. After a week or two of it working I will look at the fan control if that is important to people.
If you haven’t already, replace the link in the OP with the latest working jar file so those who stumble across this through the marketplace get the working version.
It works for me. the sensor thing isn’t but I won’t use it anyways. If it is supposed to works with T5/T6 and you want me to test it, let me know. I’ll do the tests for you.
The sensors are only on the T9/T10 thermostats. That was the reason I had to make so many changes for the T5/T6 they don’t have any of the sensor information.
Dominique_Gagnon:
Your thermostat information has an “EmergencyHeat” mode. It will show up as an option in the mode settings but because I didn’t account for it setting that mode from OpenHAB will fail. The other modes you should be able to set. I will resolve the issue in a future update. Let me know what happens when you try and set it and if you need the feature right away.
rlkoshak:
Same for your thermostat information, only it is a “Auto” mode.
All seems well here for the day it’s been running. I’ve not tried to exercise it much yet by changing anything but so far the sensors are reporting correctly.
More to follow if something crops up but if you don’t hear from me it’s working and meeting my needs.
Thanks!