I’ve removed all the files, cleaned up the system and started from scratch. I wanted to wait for an hour or so - keeping a close watch on the system. So far everything looks stable. Not sure why this all happened but then again this is Vera - so who knows. Right now I’m not running any logs/traces. The System monitor shows things are all calm, no restarts since 11:55 and my resources look good.
Mem Available 98216 kilo bytes
CPU Load (1 minute)0.36
CPU Load (5 minute)0.3
CPU Load (15 minute)0.26
Last CMH RebootLast Vera Restart 09:00:23 Wed 23 Dec 2015
Last Luup Restart 11:55:26 Wed 23 Dec 2015
Before I lose an opportunity to say so (I’m leaving the office and heading out of town), EVERYONE please have a safe/enjoyable holiday. Mikee, I can’t thank you enough for all your hard work, patience - everything. Again, Happy Holidays to everyone and your families…
The UI display definition is a bit limited here as the items that display on the dash tile are shared with the items that display on the first control panel. The size of the display area is different so you can be more verbose in the control panel than you can in the dash tile. The ‘Refreshed’ and ‘Status’ labels are shared as are the time and the status. The labels ‘Last’ and ‘Refresh’ as well as the date are not shared and only displayed on the control panel so you get ‘Last Refreshed’ and ‘Refresh Status’ on the panel along with the date and time. The alignment is done by offsets. I think that the fonts that are used are not fixed size so the date will vary in width sometimes giving the appearance of a missing space. There has to be a better way to do this and I’ll see if I can find one. Unfortunately I don’t see a way to display things on the tile and not in the control panel so it is not as easy as specifying one set of items for the tile and one for the panel…
Having said all this, I think we can fit the fill date/time in the tile and use the same format on both. We’ll see …
Thanks for the log. It looks like the right thing happened here, the auth failure triggered a re-authenticate and things picked up again. I am not happy with the overall retry behavior of the plugin so I’ll be reworking that but in this case it worked properly.
I need to be able to log into an account with thermostats to develop this. I believe I have the APIs but I don’t have access to test it. If you are willing to set up an account PM me.
Update on where the plugin is currently. It has been pretty well rewritten. I split the Vera front end stuff from the honeywell back end stuff so I could have multiple backends. I currently have 4, the original TCC APIs, the mobile APIs, the Lyric APIs and the European APIs. They all seem to be operating on the same set of data (except lyric) but do so with different APIs, sigh.
I created an account in europe and moved one of my thermos over so I could test the interface. Seems to work. I have lingerba’s Lyric running as well as my original TCC thermo. Kinda amusing, I am controlling my mudroom from the UK.
All backends can operate in one vera but you need to have an instance of the plugin for each API (each API can have up to 8 thermos in multiple locations). I am running 3 instances now, Lyric, Legacy and Euro.
Anyway, the cost of all this is a more complex plugin and a few new files. There are currently 6 lua files:
L_HoneywellTCC.lua - the front end
L_HoneywellTCC_const.lua - common constants
L_HoneywellLib_legacy.lua - the existing backend API
L_HoneywellLib_mobile.lua - the Mobile V2 XMl based API
L_HoneywellLib_lyric.lua - the Lyric API
L_HoneywellLib_webapi.lua - the European API
There is a new icon for Lyric as well and right now it need to be manually installed. I am not sure how to package all this without publishing it as an app.
This is awesome news and great progress. Thank you so much for all of the work! I think it may be worth publishing a separate app for Lyric is Honeywell does intend for it to be a completely separate platform form TCC. They will be developing additional devices beyond the thermostat on that platform as well so it might be good to just have the Lyric be separate from the beginning. (note - this is easy for me to say since I am not doing the work, if this creates more work for you, then it may not be worth it).
Anyway, do you have any files you can share for testing?
[quote=“lingerba, post:429, topic:185402”]So far everything still seems to be working from the Honeywell perspective.
Is there any chance any of the updated files last night could have some how affected my ping sensors? They are no longer working…?? I am trying to figure out if that is somehow related to the stuff we were doing last night.[/quote]
I know this is a really weird issue, but I was having issues with the ping sensor ever since installing some of these “beta” lua files over the last couple of weeks. The ping sensor(s) would work fine for about a day and then they would completely stop responding. If I would restart my vera (or restart luup) they would work fine again. I installed system monitor and I didn’t see anything out of the ordinary. I uninstalled and reinstalled the ping app and still had the same issue. Two days ago I uninstalled the Honeywell app and since then I have not had any issue with the ping sensors. I am going to reinstall the Honeywell app today (hopefully the newest/updated version that mikee has been working on) and see how that goes.
Here is the latest plugin. You need to install all files as they have all changed. The two icons go in
/www/cmh/skins/default/img/devices/device_states. I think you will be fine without them, the lyric dashboard icon will just not switch to the lyric. The others all use the same icon as I haven’t found anything suitable yet.
To install:
Upload all S_, I_, D_ and L_ files with the restart checkbox selected. You can skip the icons unless you are really bored.
Wait for the restart to complete
If you did not delete your existing TCC device you will be connecting as usual and if you don’t need any additional interfaces you can skip the remaining steps. If you are starting from scratch or if you want to add a Lyric follow the next steps.
Create a new device, enter D_HoneywellTCC1.xml in the Upnp Device Filename, I_HoneywellTCC1.xml in the Upnp Implementation Filename and a name in the Description input box.
If you are going to connect to multiple backends then repeat with a different name in the Description box for each instance you need (this is not typical but if you have Lyric and Wifi thermostats you will need to do this).
Reboot the vera. I am not sure if a Luup restart would suffice but just to be safe reboot.
When it comes back go to the new devices, select the Setup page (used to be TCC Setup) and select the interface type and your login credentials. You will see 4 buttons under the login input boxes marked “TCC”, “Euro”, “Mobile” and “Lyric”. For US based installations you can use “TCC”, “Mobile” or “Lyric”. For European installations you can use “Euro” and maybe “Lyric”, I don’t know about that one.
1 - I installed the lua files you posted and they work fine on my Veralite with UI7. I will let you know how it goes over the next couple of days.
2 - I do not know where or how to access the “/www/cmh/skins/default/img/devices/device_states” directory that you posted.
3 - I think the attached file would be a better icon to use for Lyric.
Nice, I updated the icon. Looks good. Thanks! Oh, if you have logging enabled still you might try turning it off to see if it is interfering with your ping sensors. I am not sure what the mechanism is but it seems clear the new plugin is doing something disruptive.
[quote=“mikee, post:457, topic:185402”]Argh, I don’t have access to UI5 machines. Can you grab a log (or scan it to see if a require file is missing or something) ?