EyezOn Forum

I am trying to decide what thermostat to purchase. Previously I was thinking of getting a Wi-Fi enabled thermostat but that was before I purchased a 3DS and found out about the EMS100 support.

The problem is that the EMS100 is hard to find, a little pricey based on Ebay history, and I need two. I would go with an EMS300 which is easier to fine (although still pricey), but it apparently does not work as well with the 3DS as the EMS100.

The main feature that I want is the ability to control the Thermostat via my Android phone. I would also like the ability to adjust the schedule from my computer - which the Wi-Fi T-stat that I am looking at provides (Filtrete 3M-50).

On the other hand, if I go with the Filtrete I will lose the occupancy features of the EMS100.

One additional note is that the Filtrete apparently has an open API, so I was wondering how hard it would be to write an app that would cycle the AC on when the alarm is disarmed and vice-versa?

Or even better, maybe Eyez-On could add support for this T-stat. It is sold at Home Depot for around $100 and Amazon sells it for between $99 and $125.

Thanks for reading, any response/opinion is appreciated.

Interesting that you should mention this - I've published an android app in google market for the 2DS, and since I've also got a CT-30 myself (same as the 3M-50) I've published an app to manage it as well, and one for editing the t-stat schedule since it's so frustrating on the panel itself.

The apps are intended to be used on an android tablet or phone that's used as a console within your local network, since in both cases (here and CT-30/3M-50) there are cloud apps for remote access (though in both cases I do support SSH port forwarding for remote access).

I'm working on monitor apps that will provide secure, direct remote access, text message or email alerts, etc for both devices. These apps will need to run on a dedicated tablet/phone within your network and be permanently connected to the devices. You're quite right, it would be easy to use intents to trigger one from the other such as turning the AC/Heat on or off based on arming status (though I'd be tempted to adjust the temperature targets instead), cool idea, I'll add this to my feature list.

Mike

Awesome!

I think I tried your Android app and I liked it a lot.

I ended up uninstalling it though because for some reason it seemed to constantly log in and out of the 2DS which wasn't a huge deal except that I had notifications turned on for that so I was getting a lot of texts. My main problem was that it kept turning off the door chime feature of my alarm (DSC 1832) and I have small children at home so I could not risk having that turn off by accident. Let me know if you have seen that before and if there is a fix for that.

I will be more than happy to help test anything that you need. I am a Sys Admin and may be able to help you with other stuff as well, just let me know if you need anything. I am not strong at writing code, although I've done some scripting to automate tasks.

I have not opened the 3M-50 yet, but now that I hear that what I mentioned is possible I think I'll go ahead and install it.

I hope that Eyez-On will consider supporting a Wi-Fi thermostat like this, although I think they are more likely to support an X-10 style device since they are more DSC panel focused. From my research so far I think the 3M-50 provides a lot of functionality at a good price-point sorta like the 2DS. The only down-side I see is that you cannot control it with an Escort module.

Looks interesting. We'll take a closer look at it.

ralarm99 wrote: I think I tried your Android app and I liked it a lot.

I ended up uninstalling it though because for some reason it seemed to constantly log in and out of the 2DS which wasn't a huge deal except that I had notifications turned on for that so I was getting a lot of texts. My main problem was that it kept turning off the door chime feature of my alarm (DSC 1832) and I have small children at home so I could not risk having that turn off by accident. Let me know if you have seen that before and if there is a fix for that.

Right, each time you fire up the app it connects to the 2DS card, and it (the 2ds via the eyezon service) notifies you that there's been a TPI login. Unfortunately I'm not able to prevent that. However, my server version will be (or should be) always connected, so in this case the Eyezon message is quite helpful when something happens to the connection between the app and the 2DS.

I haven't seen anything that would cause the chime status to be removed (though the recent version did enable the chime button). I'll see if I can recreate it, thanks for letting me know.

Mike

<edited to clarify>