scyto said:
Well, apologies for wasting everyone time. It seems the thermostat ONLY works reliably when it is connected to the TP-LINK wifi router included in the thermostat kit.
My mistake was connecting it to my Asus wifi router. I fucking hate carrier. So now the TP Link router is plugged into a spare port on my Asus router.
I don't see coil, airflow, outside or fan speed readings - i assume this is because i have a non communicating air conditioner unit?
Now i need to figure out how to use the non-resty API inteface in infinitude to hook to either Vera or ISY994i... will keep people updated if interested.
Also i noticed that '
System settings updated Thu 2015-06-18 at 9:40PM' doesn't report last contact time, this made me think it had stopped reporting, but i noticed currentactivity was updated almost instantly - could we have a heartbeat time somewhere?
Lastly it is raining outside, it is 68F outside, not sure why it shows freezing rain on the thermostat
@scyto ughhh. Sorry about the wifi router issue. I have no idea why that might be, but I'm glad you're at least seeing some progress. I actually installed OpenWRT on my TPLink router that they gave me. Would be pretty funny to install Infinitude on that, but the platform is a bit restrictive for perl libs etc.
I haven't written a completely RESTy interface to Infinitude just yet because of other priorities, but check out
https://github.com/nebulous/infinitude/issues/2 for info on how to run simpler GET/POSTs to Infinitude for access/control.
A heartbeat indication is a great idea. Adding to todo.txt... And yes, infinitude should respond much more quickly than carrier's apps do. Their default update rate is in minutes, but infinitude polls every 12 seconds which is as arbitrary as it sounds. Could be faster.
Now, for weather: It's entirely possible that I mixed up one of the icon types. You can hit
http://yourInfinitudeBox/weather/yourzipcode/forecast and send me the xml and I'll see if I can figure it out. Alternately you may set your wunderground id to an empty string and allow infinitude to pass the weather request on to carrier's servers. That, or look the other way until it updates again
It sounds like you're almost completely in business now though, which is cool! Keep letting me know what works and what doesn't and we'll get it all sorted.
Speaking of perl libs: sorry the dependencies are such a pain. Perl and I go way back, so I sometimes gloss over some of the finer points. @lleo, are you saying that the debian package was out of date, but Mojolicious installed from cpan worked out? If so, that's fairly typical since Debian tends to lag far behind. One thing I would suggest to any future travelers installing perl modules. Try the system supplied packages first of course, but if you would like to install from cpan, use the cpanminus tool. (
http://cpanmin.us/) It's fantastic. Much lighter than the default cpan tool, and has a flag to allow for all libs to be installed in the directory of your choice: which should eliminate the possibility of borking the whole install. Though it's highly reliable when installing libs to the system path as well.
lleo said:
@scyto - after I installed the right mojolicious from cpan, './infinitude test' and 'prove -v' ran without errors. I started infinitude in daemon mode on the default port 3000 and can access it on my network. I am not getting any data on the status page, however, there is data coming in on the serial page from my system.
At this point I will need more hand holding as not sure how to move past this point.
I am interested in just getting realtime usage data on my system. My system is a 2-zone variable speed NG furnace/airhandler with a greenspeed variable speed heatpump and an older non-networked thermostat/control in 1st zone and a Smart Sensor in the 2nd zone. I have however a SAM connected to my wired network. The serial port of the SAM is connected to my Elk M1 and I am able to do basic control/automation through that. The SAM also provides a web interface for directly altering the settings of the control.
@nebulous - should infinitude report system data with my arrangement?
I'm glad to see serial is working. As tuits permit I'm going to see if I can setup a "send debug info" button of some kind so we can easily snarf and compare serial data. Yours is of course especially interesting since the SAM is included
As for the dashboard, here's how it works:
The top row contains items sent over tcp from your touch thermostat to infinitude. This only works if your stat is configured (in proxy settings) to send its data to carrier by way of infinitude.
The bottom row shows data from the serial stream, but is still limited to registers and devices that I have on my system. It's entirely possible that your devices have different addresses and/or report temperature/fan speeds in different registers. So, infinitude should be able to report the data it sees, but we may need to update it with where to look. Fortunately the serial tab makes that easy(er) to determine. The top of the serial page shows frames scrolling by in realtime, and the bottom shows current overall state of the system that infinitude is aware of(presently that state is persisted only in your browser). When an item in a particular device changes, infinitude should create another row in the "state" table for it, and highlight the bytes which changed. Basically with a bit of detective work*, any data that comes from your wired devices and is displayed in some way on the thermostat should be available to infinitude and in that stream. Non-communicating devices of course will report no data.
*you can always force some variables to change to narrow it down. For instance, you could (after setting your zones to off so the AC doesn't go bananas) start running the serial monitor and then take a hairdryer to the smart sensor. The highlighted skyrocketing values are likely to be its temperature.
