What I was able to figure out when I first looked at this was
that Mr. Cool doesn't have an API.? However, what Jon's links in
his original email point to is the javascript driver by Nicholas
Robinson that communicates with a Cielo smart thermostat that is
compatible with a Mr. Cool system.? I couldn't even find a
published API for the Cielo smart thermostat so I'm not sure
whether Nicholas Robinson figured it all out by sniffing the
network or developed a relationship with Cielo and they provided
him with one.?
The reason I passed on this was simply because I wasn't going to
be effective at trying to reverse engineer something written in
javascrip, especially something that appeared, to me, to be fairly
complex.? Someone who is fluent in javascript might be able to
knock this out in no time.? I just know that isn't me.
Jay
On 2/21/2021 6:23 PM, Steve Kuehn
wrote:
toggle quoted message
Show quoted text
Troy,
I agree 100% with you -- it is best to keep it all confined in the
Crestron processor.? But I gathered from the original poster that
that for some reason, SIMPL# could not handle it.
But I think there is an even bigger? question here.? Does Mr Cool
have an open API?? From the blog post, it appears the Mr Cool has
a closed API.? If that is really case, do you want to spin your
wheels writing a program only to find it breaks if Mr Cool has a
firmware update or if someone replaces the controller board in Mr
Cool that has a different protocol or if there are several
different version of Mr. Cool.? I myself would never even consider
telling a client that I can integrate Mr. Cool into Crestron
because of that.
Now, if it was for my own system, I would have no issues
intermixing technologies to get the job done.
Steve
