larryllix

Read this thread from the beginning but.... The Hue bulbs need a hub as a bridge between Etherenet and whatever the Hue protocol is. The ISY can use the Network resource module to access the Hub/Bridge. Start building resources to send URL codes out. See the previous post two back for sample screen shots. IIRC Polyglot has Hue support built into it for the RPi.

Very easily done. Create a program say "IamHome" and disable it so that no triggers in the ISY If section can trigger it. In the Then section that Alexa will cal on default to with the spoken "On", use a program line to call program (If) IamHome.2 In another proram "IamHome.2" disable it also, so no ISY triggers can trigger it. Set a condition time frame in the If section for your time frame you want bracketted. In the Then section turn on all the devices you want during that time frame. In the Else section turn on all the devices you want outside of the time frame. Go to ISY.io.com and enable voice control of the first program "IamHome" You will have to say "Alexa. Turn on I am home"

Examine ISY logs and compare with your SMS/email notification times. I have seen texts come in hours later and emails come the next day, in some cases. If texts take more than an hour or so they are sometimes dumped and never delivered.

I had some trouble also. IIRC mine showed I was linked to a registered account but it was linked to the wrong email account. Details are fuzzy at this point, but I installed the opposite end's email address....ie. ISY instead of Amazon or vice versa.

I has seemed to get slower as I use it...not sure, but right now I would say variable response times. I vocally use almost all ISY programs, no scenes, and a few single lights/devices. I'll keep an eye on it for speed and see if I notice a pattern. The not understand and then did it anyway happenned twice, IIRC.

Not enough plosive sounds? I had a few instances where Alexa reports she doesn't understand but still turns on/off the lights. I have only used "turn on" and turn off" so far. They seem to work about 99% of the time.

What would the vapour barrier be doing there? In colder climates, we use vapour barrier to keep the interior moisture out of the insulation so it can't freeze, and nullify the insulation properties, conducting heat out. Injected solid foam insulation doesn't require a vapour barrier to protect it from condensation. An outer membrane just under brick or siding to allow the moisture out of the insulation and framing but not allow water into the framing.

The Mycroft project should attract a few with it's stated "open source" claim. time will only tell how this pans out and "open source" is NOT just another trade mark. These companies go into these projects gung-ho and usually come out with their tails between their legs, as the task can be much bigger than they bargained for, and the job (competitive products) doesn't stand still. Many find by the time they get out a competitive product, it is now obsolete technology in the market. Very nice to see some competition for Echo. The intercom betweeen units is a nice feature.

Although Xathros has a black belt in ISY logic, I like to add an all-else-fails timer to that logic. Pendants Override If Control 'Kitchen / Kitchen Pendants' is switched On And Control 'Kitchen / Kitchen Pendants' is not switched Off Then Disable Program 'Pendants Timer' Wait 4 hours Run Program (else) Pendants Override Else Enable Program 'Pendants Timer'

My Tekmar stats have a programmable time out delay but default to two hours if a tap on the temperature up or down is done. My old HoneyWell non-WiFi stats did the same thing with a two hour default, non settable. I only use two setpoints per day on cooling so that would all day and not wanted to wait for the next setpoint. My $29 unit in my shop building waits until the next scheduled time point to fall out of temporary hold.

Sounds like the MS only has a BattLow On signal and not and Off being a one sided signal only. Also ISY has compensated by resetting ISY's status to Off by query.

Factory reset those things several times and then operate them from the link buttons a few times before hanging them back on the wall. I have always had problems with the MSes. I have 10 units. I have come to not trust the MS battery low signals or the flashing LED while seeing motion. I have one with a four month old battery, that has been flashing for two months of it, and yet never reported a low battery. Most of them don't seem to ever report it. I keep a list of every MS low battery signal reported in and a few have been flashing for the last two months but never reported in. This sometimes just goes away for another six month period and then resumes, also. I am just waiting until they stop working now. The battery clips won't stand much more of that nonsense. I keep my eye out for AC adapters and white 2.1mm x 5.1mm plug extension cords for a decent price. Only short ones seems to be out there for under the MS price.

A question please?Does this stat have a feature whereby you can click the current setpoint up/down a few increments and it does a temporary hold at that temperature and then returns the regularly scheduled program in 2 hours or some settable time? This is without disabling the schedule mode or multiple taps and/or menu shopping.

Not on purpose for the colour. My T7900 takes custom pictures in full colour but I find it annoying. Stats should disparear into the woodwork and not have a nuclear glow in the room. I have coloured lights for that. It would be hard to even figure out what the photograph is anyway with all the huge numbers and modes on the screen. Just makes a visual jumble of confusion.

That one seems to be very common in positive comments. With Zwave you eliminate all the components you can between ISY and the stat. That would be my pick and may be my next pick but without Zwave, maybe. Honeywell made good stats years back with the needed features.

Heard back is good!

It seems you can have Insteon/ISY simplicity with a very basic thermostat or you can go fancy with a stat and get control via NodeLink and a RPi. I do not support ZWave but I suspect they have some fancier models with better features. This is all dependant and what you want it for. The ecobee3 is the one I was considering to replace my Venstar T7900 but I don't wnt to make another $350 mistake out 6 devices and the real features you wil discover they have or do not have are never listed anyweher I have found. You may not even know what you want until about 6 months of usage and a few different seasons. My needs are very complex with my HVAC system. Some have been made possible by use of ISY programming but that is dependent on about 6 different devices functioning to be even possible. ISY, Router, WiFi, Rpi, WiFi, switches. Other stats will add the cloud to that mix.

Posts #57, 59, & 64 I use 2441ZTHs directly to ISY, for minor functions. I use Venstar T7900 for my A/C and some heating via NodeLink/Rpi to ISY I use various TekMar stats for main hydronic heating but they do not communicate without an additional $1000.00 bridge gadget. I use CAO Tags for probes, experiemntations and probes. I use a WC8 Webcontrol board with 1-wire sensors for outside and out building temps and wind speed REST interfaced into ISY. Wind speed is used to compensate chills in the winter by adjusting temps up half a degree C.

It is designed to piggyback off the 2441TH but ISY can control and recieve their signals directly.Having no hard contact o/p they are really only probe sensors for control elsewhere. I use one 2441ZTH units for humidity control in my cold cellar (ISY logic), and one for freeze alert/backup heater in my utility room (ISY logic). The OnOffLinc also acts as an Insteon repeater being at the corner of the L in my home and also acts as a powerline signal injector into one Inverter created phase/leg.

Which thermostat and how does ISY control it?

I only have the 2441ZTH, wireless. Answer: It does none of the above mentioned features.

Do any of these stats have things like: - Warm/cold weather shut down? - Dual schedules for heating and cooling - Temperature control based on external sensors, especially ANDing or ORing with inside sensor - Intelligent predictive setback compensation - most offer Intelligent setback recovery - better than 1 degree F resolution or sttability? I have a Venstar T7900 right now but it is very amateurish and seems to be created by a programmer, not an HVAC person. @Stu: Can you voice that stat from heat to Cooling and vice versa?

It is usually frowned upon, here, when you attack the 1 year old toddler from next door, with your GDO while attempting to crawl under to get that ball. That is the usual argument from the legal crowd on auto garage door closers.as per post #4. Unfortunately the links are all about selling contracts and the attempt to sell them through fear mongering but the risk does exist. I don't have my contacts connected to my GDO but only because of the ISY All On problem and laziness to connect. OTOH: I don't have the need for this HA or remote control due to my schedule and friendly neighbours I could call. I would have to worry more about racoons getting into my garbage than human intruders. I built this house without a security system.

Here is my date extraction tool Note: calculations are done in Integer variables and then copied to State variables to avoid multiple triggers. ---------------------------------- Set MM.DD - [iD 00B8][Parent 0006] If . . Time is 12:00:01AM . Or Time is 3:00:01AM . Or Time is 6:00:01AM Then . $sISY.DayOfWeek Init To [Current Day of Week] . $sISY.DayOfWeek = [Current Day of Week] . $sISY.DayOfMonth Init To [Current Day of Month] . $sISY.DayOfMonth = [Current Day of Month] . $ISY_Date.scratchpad = [Current Day of Month] . $ISY_Date.scratchpad /= 100 . $ISY_Date.scratchpad += [Current Month (Jan=1, Feb=2, etc.)] . $sISY.MM.DD Init To $ISY_Date.scratchpad . $sISY.MM.DD = $ISY_Date.scratchpad Else . - No Actions - (To add one, press 'Action') ------------------------------------------------

The first VenStat Log.newFile is the name of the ISY program that creates and writes the headers of the columns in the database file. The variable is created by myself using a separate program to extract the date. This requires V5 to get the date from ISY. You could just use any filename to start out. Mine switches files every first of the month. The "$s" indicates it is a state variable and I use it all through my system. See Next post