Everything posted by Goose66
-
Airthings API
All this technology built into these things and no Wi-Fi? $229 for the sensor and you have to pay another $80 for a hub to connect it to the Internet and use it outside of the Bluetooth range of your phone? If I had a tiny house over a fracking site, maybe, but I wouldn't buy this for my home on the engineering principles alone!
-
Vista 20p forgot zone numbers after flooding
The are in the Installation and Programming Manual available online.
-
Vista 20p forgot zone numbers after flooding
Never done it on a Vista. I factory reset my DSC PowerSeries 1832 with 16 zones, 5 smokes, 3 heats, and 4 keypads and reprogrammed it from the worksheets in an evening. The worksheets were key!
-
Vista 20p forgot zone numbers after flooding
I really don't know much about tuxedo touch keypad. I imagine the 4-wire bus for the connection of keypads to Honeywell/Ademco systems is pretty universal, and is the same four wires as needed for keypad connections to other systems (GEM, Elk, DSC, etc.). As long as the keypad says it supports the panel then it speaks the right language. The main point I wanted to make was try factory reset before abandoning your current Vista board.
-
Vista 20p forgot zone numbers after flooding
It is possible that the panel may still be functional (i.e. capable of working) but that water damage caused problems with the memory/configuration. Before abandoning the panel altogether, I would try factory resetting and reprogramming the panel. You should be able to do this if you know the installer code. The installer code may stay the same after the reset, or may go back to factory default installer code. If the panel turns out to be bad, I would favor a different system over the Honeywell if interfacing with the ISY is desired. The EnvisaLink interface to the DSC Powerseries is far more functional than the EnvisaLink interface to the Honeywell Vista. Of course, then you are replacing keypads too, which makes it more expensive. You could also look at going to something completely different with built in Ethernet connectivity and home automation integration, like Elk M1 or Ring w/ Retrofit kit.
-
Future in Insteon
Ok, now we've really gone off the rails...
-
Future in Insteon
This forum may be one of the largest grouping of Insteon users there is (or I am delusional). Perhaps we should sign a petition or demand for a local TCP/IP-based API for a PLM or Insteon Hub to be added to the mix. I would develop and implement it if they would give me the Hub source code. Or better yet, put Node Server API support right in the thing!
-
Future in Insteon
But, again in the context of "full automation being the goal," manufacturers have done little to help by keeping their systems closed. The promise was the "Internet of Things" - everything online and talking to each other. The reality is that most manufacturers don't want anything to talk their things but their own things. Whether it is inability to provide interfaces or unwillingness to lose potential revenue streams, this tendency of manufacturers to lockdown their devices and ecosystems has been a thorn in the side of true home automation enthusiasts for decades.
-
Future in Insteon
And with full automation being the goal of some over the last 25+ years or so, there's been nothing but disappointment coming from manufacturers. In my first house in 1995 I had X10 switches and modules w/ a PC controller that output a GUI interface to my projection TV and a IBM voice processing card allowing for voice control. I ran VBscripts with time and event processing that allowed some real "automation" of the house. The problem then, of course, was that while I could control what X10 allowed, I couldn't really integrate it with a lot of other things in my house. Fast forward 25 years to today and all the new great technology has brought us...
-
Future in Insteon
What I would REALLY like to see (assuming, of course, the demise of the ISY/Insteon "partnership") is a local API for the Insteon hub - ideally two-way, realtime, and REST/UDP-based. That way, the hub would contain all the vagueries of PLM communications and device-specific data interfaces. A nodeserver could be developed to allow the ISY to continue to support Insteon and the Hub/app could be used for Insteon configuration (and, potentially for non core-ISY folks, local and remote control, Alexa/GH support, etc.) That way, when new Insteon devices were made available, support for them would be immediate - no need for Insteon to communicate details to third-parties (which they are evidently very bad at) or waiting for new ISY firmware for support of the new devices. Seems to make perfect sense to me for a hardware manufacturer to want this too, but based on what most of them end up doing, I obviously don't get it!
- Future in Insteon
-
Future in Insteon
If there was going to be a new PLM, wouldn't @Teken have posted something by now?
-
Future in Insteon
Has this thread devolved into a lottery pool? I'm in. ?
-
Future in Insteon
You're going on my "I told you so" list! ? In the interest of full disclosure, I am 100% Insteon here (meaning no Zwave or other lighting/switches/modules). $3500+ worth, I would imagine.
-
Future in Insteon
If you think the idea of hardware manufacturer closing their system in favor of pushing adoption of their own ecosystem is "outrageous," then you haven't been paying attention to the home automation industry for very long. It happens all the time. Is it likely to happen with Insteon? Don't know. But it's far from an outrageous possibility. You and I may wish they would "stay in their lane," but manufacturers rarely do when there are monthly subscription fees for cloud services to be had.
-
Future in Insteon
Let's hope that relaunch doesn't mean hub only (no PLM) and access limited to app.
-
Future in Insteon
They use to do many (like 10+) press releases a year since their inception in 2005. But after just a couple in 2017 and 2018, they've been silent. I don't think they've been at CES since January of 2018, either.
-
Future in Insteon
But we are talking years of quiet at this point. I sent an email to Insteon support a week ago and received and answer from Smarthome support within 24 hours claiming they are still around but blaming the shortages on COVID-based supply chain problems and "overwhelming Q4 demand." ? I wonder when the patents are up - maybe we will see an explosion of cheap and compatible products like we did with X10.
-
Led strip lights
Choosing the right controller for a strip light is based on the type of LED chip. Look for the chip type on the packaging, e.g. SMD2835, SMD3528, SMD5050, etc.
-
Keen Vents Nodeserver Creation- Anyone interested?
The KeenHome is considerably more expensive than Flair vents and works with my ecobee thermostat(s). I am not sure I can justify the additional expense of the KeenHome just to write a nodeserver.
-
Keen Vents Nodeserver Creation- Anyone interested?
I was going to say why would anyone want their ISY to know that a "Fancy turtleneck with deer on it" went on sale for $469.50. ? Actually, I've been wanting zone my three bedroom upstairs with the attic furnace because my son's room closest to the furnace runs a good 8 to 10 degrees warmer to my daughters room down the hall and over the garage. I was thinking I needed a whole new plenum and duct work, but smartvents could be a good way to go.
-
Alexa Constantly asking "Did you mean...?"
So you specify one or more "spokens" to each ISY device when adding them to the Echo integration (the first one defaults to the device name, I believe). When you perform a device discovery in the Alexa app or through the Echo, it queries the integration for the names of devices and an address. Each "spoken" is added as a device and resolves to the same address of the ISY device. If Alexa is giving you a "did you mean error," it most likely is confused by the name of the device with some other device (ISY or otherwise). Could be a TV from Roku skill, a thermostat, a Wemo outlet, etc. I explain this only to say the problem is more likely with Alexa and all of the devices discovered by Alexa in your setup then with the ISY or the ISY's Echo integration.
-
Alexa Constantly asking "Did you mean...?"
Is "heater room" a device name you have defined in the Echo integration, and is it appropriately unique?
-
Smarthome killed the Leak Sensor!
I think the arguments of legal liability for Smarthome show a lack of knowledge of consumer products law. More likely that they engineered the product to act appropriately to its task, in there opinion. Why not always default to user configurable?!?
-
Apparently I can't ditch the i/o lincs after all due to Liftmaster massive security flaw that would leave me unable to remotely control my door!!!
Standalone MyQ with the gateway device connected to the LAN by ethernet and corresponding MyQ-ready keypads that control older (purple button) LiftMaster openers. I also note that, despite the failure of the first commands to doors 1 and 2 through the API, the status reported through the API remained correct. So you could have a control mechanism that closed the doors, and then a few minutes later, if the status was still open, closed them again. But you would want some independent way to verify the door state IMO, like alarm system sensors (very common these days). I also also note that I don't count on my automation for security in this instance. I am old school - I don't move the car towards the driveway without visually confirming the door is coming down. Taught my kids the same thing. I mention this only to say that I haven't done a thorough investigation of the fail-secure nature of the MyQ system.