Same here started 2 days ago
Same here – noticed this last night.
I tried deleting the plugin, re-creating the device, and even changing my credentials and nothing helped. At first I was seeing “Invalid Token” in the logs, but after I deleted the device and changed my password they just say “HNYWL TCC ERROR: TCC authentication error”. Honewell app and website both work fine.
I am having the authorisation error from the plugin. Running Beta2. Honeywell’s iPhone App is working.
It looks like this is a pretty easy fix. The last firmware updates provide a new version of LuaSec, the library that underlies the HTTP/SSL module the plugin uses (this is an important and necessary update, as the LuaSec module has been way out of date for a long time and is missing ciphers that are well on the way to becoming mandatory). This later version of LuaSec requires that the “protocol” option be set in requests, which the plugin is not doing (and thus causing an error).
I’ve patched up the plugin, and the file is attached below. Someone else needs to test and confirm the fix–it’s working for me, but one data point is worth very little. The author of the plugin needs to integrate these fixes throughout the code as needed for the new LuaSec. I’m happy to confer as needed.
Download, unzip, and send the one file up to your Vera via Apps > Develop apps > Luup files.
THIS PATCH SHOULD ONLY BE APPLIED TO SYSTEMS RUNNING 7.31 AND UP
EDIT: Updated file to include prototypical fixes for all platforms (EMEA, etc.–I can only test legacy/US)
L_HoneywellLib_legacy.zip (24.0 KB)
hopefully 7.31 goes to production soon
When you refer to systems running 7.31 and up, what are you referring to? The plugin stopped working for me and I am on firmware 1.7.4452. I tried the new files you uploaded but they don’t seem to help.
Thanks for your work on this!
No, they wouldn’t. I can take a pass at a more comprehensive fix that might also work on older firmware, but as my earlier message says, the old version of LuaSec on firmware 7.29 and prior is in danger of not having ciphers/features that some sites are now requiring as they enhance security. Give me a bit to make a new pass at this for that older firmware, and we’ll see where we end up.
What platform are you using (TCC, Euro, mobile, EMEA, etc.)?
I use TCC, personally. If you can implement the fix for that, I would be much appreciative.
Is the 7.x series of firmware for a different set of devices? I’m on the Vera Edge myself.
7.x applies to all legacy Vera devices (but not Atom or PlugHub). Stay tuned… updates coming…
I am on 1.7.4453 on a Vera Plus and it stopped. If you can fix this @rigpapa, please add the updated Lua file floating around that I reposted in post 772. This fixed missing fan features.
Unfortunately, the original author and the 2nd author are both gone to my knowledge. I wish Ezlo would add native support for Honeywell thermostats like most competitors.
Edit: firmware is 7.0.29 to help clarify
OK. This ZIP file includes all API interfaces with adjustments for both LuaSec 0.5 (firmware 7.29 and below) and LuaSec > 0.5 (firmware 7.30 and .31 except Vera Edge). This also includes the fan-fixed version of the plugin implementation file referenced in the prior post by @Nameless, so this ZIP file contains a comprehensive update of everything (as far as I know) since the app store release.
L_HoneywellLib_rigpapa-2020-02-14.zip (24.4 KB)
If you all would test please and report back success or fail and your firmware version and hardware platform, that would help get the loop closed quickly.
Just tested this patch, works for me under 1.7.4832 (7.30)
Thank you very much!
Edit: oops, forgot to mention this is on a vera edge
Working for me on Vera Edge with 1.7.4452 firmware.
Thank you thank you thank you!
Working for me on VeraPlus firmware version 1.7.4453
I use: L_Honeywe llLib_rigpapa-2020-02-14.zip
platform EMEA in The Netherlands (Europe)
@rigpapa Thank you !!
My wife is happy now that the heating goes on automatically
I was too quick with the response. I get an error message after about 1 hour
Thanks for the fix, working now on Vera Plus 1.7.4453, in the US through updating the *_legacy.lua file. Thank you!
It looks like there has been some changes in the EMEA/EU api. Hass, for example, now has a completely separate component for Honeywell EU. The URLs in the current Vera plugin don’t appear to work at all. Unfortunately, I have no way to develop or test for that locally, so it’s a non-starter, I’m afraid, unless someone in the EU with Honeywell devices wants to make the effort.
I don’t know if I can help. Im in Europe but EMEA api as far as I know and if needed I can do some testing.
For the time being I’m not able to connect with your new files .
I’m on Vera Edge with 1.7.4832 (7.30) firmware
08 02/16/20 2:00:01.784 JobHandler_LuaUPnP::HandleActionRequest device: 50 service: urn:joeyd-com:serviceId:HoneywellTCC1 action: SetUsernamePassword <0x72ee3520>
08 02/16/20 2:00:01.784 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=50 <0x72ee3520>
08 02/16/20 2:00:01.785 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:joeyd-com:serviceId:HoneywellTCC1 <0x72ee3520>
08 02/16/20 2:00:01.785 JobHandler_LuaUPnP::HandleActionRequest argument action=SetUsernamePassword <0x72ee3520>
06 02/16/20 2:00:01.788 Device_Variable::m_szValue_set device: 50 service: urn:joeyd-com:serviceId:HoneywellTCC1 variable: credAuthorized was: now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x773d5000>
06 02/16/20 2:00:01.789 Device_Variable::m_szValue_set device: 50 service: urn:joeyd-com:serviceId:HoneywellTCC1 variable: cookieRefreshTime was: Sun, Feb 16, 01:59:42 AM now: Sun, Feb 16, 02:00:01 AM #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x773d5000>
01 02/16/20 2:00:02.027 LuaInterface::CallFunction_Job device 50 function SHoneywellTCC1_HoneywellTCC1_SetUsernamePassword_job failed [string “module(“L_HoneywellLib_emea”, package.seeal…”]:187: attempt to concatenate local ‘code’ (a nil value) <0x773d5000>
01 02/16/20 2:00:02.028 Lua_Job::Run job#72 : dev:50 (0x1a65118) P:50 S:0 Id: 72 failed <0x773d5000>
04 02/16/20 2:00:02.029 <0x773d5000>
02 02/16/20 2:00:02.030 JobHandler::PurgeCompletedJobs purge job#72 : dev:50 (0x1a65118) P:50 S:2 Id: 72 status 2 <0x773d5000>
06 02/16/20 2:00:02.844 Device_Variable::m_szValue_set device: 787 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: KWH was: 36.9370 now: 36.9370 #hooks: 0 upnp: 0 skip: 0 v:0xeb0c28/NONE duplicate:1 <0x76bba520>
This is strange, I’m on 1.7.4903 (7.31 on VeraPlus) I run TCC using EMEA and never noticed any issue on the login. Just checked while reading this thread and it was still running OK. I might be lucky but the change described on the EMEA/EU api should affect all users, isn’t it?
maybe I have to upgrade to 7.31 to solve this issue. i don’t have the knowledge to adjust the api. I don’t know if 7.31 is stable enough to work with without getting into other problems