mikkee, thanks for your work on this version of the plugin. I had contact with JoeyD in the early days of his plugin version. However his version was working in the US only.
I just installed version 2.3 in combination with an European Evohome with 7 rooms. The plugin seems te work fine (in EMEA mode), but I’m only able to set Heatpoints for a temporary 4 hours. When I try to change the Setpoint Behaviour setting in the main device to Permanent. I get an ERROR: No Implementation.
Is there a way to make the setpoints permanent or to set a timeframe for a temporary setpoint?
I have just published version 2.4 to correct the service name issue that was causing the “No Implementation” error. Let me know if you can now set permanent setpoints.
From what I understood honeywell is moving away from the alarmnet.com servers. I changed the url to use tccna.honeywell.com (but it looks like Euro still uses the old URL). You are getting alerts directly from honeywell by subscribing on their web ui ? Same for the alert about turning the heat on and off ? Let me know how to set this up and I’ll try to reproduce it.
@Mikee - Sorry, I forgot that I actually did make some code changes in my ping/motion activation code and how it turns on/off the thermostats. I removed the new changes and turned on email notification when Vera submits a change to the thermostats. Hopefully it will help me diagnose if it was my code changes or something in the app. It’ll probably take a few days for me to get enough cycles to test, but I’ll post back regardless. I’m also in the US, so I would be on the tccna.honeywell.com URL.
Thanks for your work on this app, it’s much appreciated.
@Mikee - Sorry, It was an issue with my code which caused a change event anytime motion was sensed, which caused a lot of rapid changes. I modified the code and haven’t had any errors since.
Hello, I have the European version of the honeywell round connected and installed the plugin, I can connect with the termostat and able to change the set points through the vera UI, but I’m not able to use luup to cancel the set point
I’ve used the code metioned in post 2
Quote
local lul_arguments = {}
lul_arguments[“ThermostatID”] = 123456
luup.call_action(“urn:joeyd-com:serviceId:HoneywellTCC1”,“CancelSetpointHold”,lul_arguments,10)
Unquote
I think the problem is related to the ID number which is in following format 1234567:1234567. No sure how I need to enter the ID, tried already several ways but none of them are working. Thanks for your help
Try sending the ID as a string exactly as it appears in the status page, i.e. “12345:12345”. Some of the backends require both the thermo id and the location id. This is the loc:thermo format.
Go to the advanced tab of the thermo you want to control. Find ‘altid’. It should be near the top of the list. It will have a format of TCC_xxxxx. Cut the xxxxx and put it in quotes as your lul_arguments[“ThermostatID”]=“xxxxx” value. You should have two numbers separated by ‘:’ in your quotes. If you have done this I will need to go back and do some more testing.
Just installed the plugin for the first time. It is looking very promising, great work.
Unlike @awenger I do have problems setting permanent setpoints. (I’m in Europe?)
When changing setpoints it only does so for exactly 2 hours.
I do not really understand your question about the permanent setpoint setting.
I have the temperatures programmed in the thermostat itself but I like to override these settings using the plugin.
I would like to program a scene where the temperature is set to a certain value for let say 4 hours.
But whatever I do, the set-point does change but always for exactly 2 hours.
On the Control panel of the TCC device (not the thermostat) you will find a setting for Setpoint Behaviour. The choices are temporary or permanent. Make sure this is set to permanent. You can then set your temp and it will stay until you set it again. There is currently no support for setting it for a period of time (other than to use schedules).
[quote=“MarcusB, post:655, topic:185402”]Hey Mikee,
I just wanted to say thanks. I installed the plug in and it works perfectly.
Great work :)[/quote]
I’ve got an update and a question
A few weeks ago Honeywell put out an update for the iPhone app with some comments about being required for new regions. I’m in Australia and some trial and error has shown me that I need to choose EMEA. Since the app update, it still all works perfectly but I get a message bar at the top of vera saying
-HNYWL TCC: : Honeywell TCC Authorization passed, but no devices were found.
My device still works and of course shows up in the list of devices.
Also, when I try to use advanced options in a scene, I’m asked for a thermostat ID. I’ve tried all sorts of numbers I can think of but nothing seems to work. Can anyone tell me what to enter in that field? I’ve tried the device ID, the thermostat ID as per the Honeywell site and any other option I can think of. I think when I create the entry it defaults to i4 but that doesn’t work either. I’d really like to be able to create a scene to cancel the current set point but that seems to be stopping me.
I have a version of this thermostat that is not wifi compatible, and therefore am unable to utilize the Honeywell TCC system. I would like to create luup code that will place the thermostat on permanent hold and change the set temp when I put the system in vacation mode. Will the code that you have created work without going through the TCC system?
