filehippo copypast

Insteon and nest.Insteon Raises the Curtain for the Next Act

By admin on July 12, 2021 0 Comments

 

Insteon and nest.Announcement

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Recommended Posts.Nest thermostat gets Insteon smart home integration – SlashGear

 

Feb 06,  · No, Nests are wifi and Insteon is not–even very different frequencies. Above cb suggestions are a good idea. If the Nests start working, turn one cb on at a time to help isolate the problem. I have one gen 3 Nest thermostat, four gen 2 Nest smoke detectors, and all Insteon . Mar 12,  · Smart home addicts relying on Nest for their HVAC can now hook the learning thermostat up to an Insteon automation system, integrating it with Estimated Reading Time: 1 min. Control Insteon Devices. With Google Assistant and an Insteon Hub (), control your lights with just your say “Hey Google, dim the bedroom lights”. If you are looking for more heat, just say “Hey Google, make it warmer” and the the Insteon Thermostat will raise the temperature.

 

Insteon and nest.Works with Nest — Insteon

Feb 06,  · No, Nests are wifi and Insteon is not–even very different frequencies. Above cb suggestions are a good idea. If the Nests start working, turn one cb on at a time to help isolate the problem. I have one gen 3 Nest thermostat, four gen 2 Nest smoke detectors, and all Insteon . Jan 05,  · Insteon is now an official Works with Nest product, and Nest customers can benefit from access to a simple and reliable connected home experience that can be powered by a Estimated Reading Time: 5 mins. Nov 08,  · The nest protect (the smoke/carbon alarm) is a really good product. Now that they’ve added the thermostat support, any news on adding the nest protect to the Insteon hub?
 
 
related:
Insteon home automation adds unofficial Nest support
Insteon works with Nest
Insteon home automation adds unofficial Nest support – CNET
Nest thermostat gets Insteon smart home integration
Join the conversation
Insteon Raises the Curtain for the Next Act | The Digital Media Zone

You can edit the text in this area, and change where the contact form on the right submits to, by entering edit mode using the modes on the bottom right. I did a bit of googling and came across Homebridge , an open source project to bridge existing hardware to HomeKit via an always-on computer somewhere in your home.

I was originally going to use my Magic Mirror’s Raspberry Pi, but after hitting a configuration issue I used my Mac mini server instead. Homebridge is implemented through node. On the Mac, this wasn’t overly complex, especially with their instructions. There also provide detailed installation instructions. The first step is to download and install Xcode from the Mac App Store so the you can set up everything else. Note that you have to launch Xcode once or enter the appropriate command line string and agree to the license before you can continue.

Next, download and install node. Once that’s set up, you can get Homebridge itself installed from the Terminal. I found that I needed the –unsafe-perm flag to get it to install properly this flag is mentioned in the HomeBridge readme. The OS X instructions also include information about how to update Homebridge and its plugins with npm. I found SmartThings support from the associated homebridge-smartthings project. Installing that package is also quite simple:.

You then have to configure the SmartThings SmartApp. This requires adding its Github repository to your SmartThings developer page, adding it and turning on OAuth.

Then in the smartphone app you open the SmartApp and check off all the devices you want. This snippet doesn’t contain any information about your SmartThing modules, so if you add new devices later you don’t have to do this again.

The code looks like this:. The Homebridge devs say not to use TextEdit, but of course I tried it anyway and had odd problems that were fixed only by retyping entire lines by hand.

Here’s a complete example config. I think I saved it to my desktop first, opened my user folder in Finder, created the. Then I just dragged config. With luck, you should see Homebridge initialize, load up all the SmartThings devices you flagged, and show you a code to enter into your HomeKit app. During setup t’s more useful to run Homebridge manually but once everything is compete you’ll probably want to have it launch automatically.

The Homebridge macOS installation docs this. It’s pretty easy: simply create an file named com. Once loaded, Homebridge will immediately begin running in the background. If the app crashes or is killed, it will automatically restart. If you’d on’t want it to restart, you have to unload it, which will immediately kill it.

While you’re doing setup you’ll likely wind up needing to stop and start the server and look up the output a lot, so you’ll want to just keep it unload it and manually launch it form the terminal with homebridge. The pin code in the config. You’ll need to enter that code into your app; theoretically, you can use your phone’s camera to read the number, but I couldn’t get a good image off my screen.

Once added, all of the devices you’ve flagged in the SmartApp should show up in your HomeKit app. You should now be able to turn devices on and off both from within the app as well as with Siri.

If you add new SmartThings devices or flag new devices in the SmartApp, you’ll need to restart the Homebridge server, either by ctrl-c in the terminal, or ill pgrep homebridge if you have it running through launchd , or by unloading it and loading it again with launchctl. Nest support through Homebridge is also available. Installing the plug-in is easy, but you have to jump through a number of hoops to get it set up.

Installing is just another call to npm. You then have to update your config. This takes some back and forth; after setting up the Nest developer account, you have to put some data in your config. I’m not going to try to cover the steps here just go to the Nest Homebridge page and follow the steps. The only thing I had to do differently was change the name of my “Product ID” on the Nest site to be unique, but everything else went smoothly.

Once that’s all set up and you’ve relaunched Homebridge, you should just be able to open your favorite HomeKit app and see your newly-added Nest devices. For reason I don’t really understand, there isn’t a Homebridge package for Insteon. After a bit of hunting, I found someone who had created their own based the Homebridge legacy plug-ins. So the first step is to install those:.

Next I added Insteon. This path requires admin rights, so expect to enter your password. I didn’t need any of the other platforms in that folder, so I created a subdir called Disabled and moved them all into there. After that, you need to add each of your Insteon devices, one at a time, to the accessories part of your config.

Here’s a simple example:. You’ll need to create an accessory block for each of the the devices you want to add. You’ll probably wind up running this through jsonlint to find all the extra or missing commas and quotes before you get it right. Now you should be able to restart the Homebridge, open your HomeKit app, and turn on and off your Insteon devices.

However, the above Insteon home bridge solution doesn’t handle them. The problem lies in the fact that FanLinc is really two devices in one, each addressed through different group codes, and Insteon. After failing to find anything about how to set the group over the HTTP-based protocol used by the hub, I resorted to setting up a packet sniffer to monitor traffic from my iPhone. This article in particular was invaluable in getting that working. You can use WireShark or just the command line tcpdump ; I used both as I learned how to find the information I needed.

The URL used to provide a group code is much longer than the one used for the lights, and not publicly documented unless you buy an SDK from Insteon.

Luckily, a resilient developer has figured out much of the protocol on his own , including how to compute the checksum required for I2CS devices like FanLinc. The checksum only includes the command and data bytes, note the device ID bytes, so I was able to just add the four cases directly to Insteon. After integrating the extended codes, turning the fan on and off the worked flawlessly.

Controlling the speed was another story. Dragging the “brightness” slider in Eve the fan shows up as a “dimmable light” actually changed the light brightness, not the fan speed. After screwing around with this for a couple of hours I finally realized that it has to do with how fast you send the commands for the fan.

Quickly sending a series of fan commands causes the light to change instead. To work around this, I have Insteon. This works great, and now I can control fan speed with HomeKit. The only problem now was that Siri doesn’t seem to have fan speed commands. Siri just said it couldn’t find the device, but it had no problem turning it on and off. To work around this problem, I added “onValue” and “offValue” entries to the config.

This let me create multiple instances of the fans, each with different on speeds. But this was really not how things should work. I did some more investigation and found that there is fan speed support, and that I just needed to add the “rotation speed” characteristic to the device, handling it specially form the light brightness.

Both the original and my modified Insteon. Since the main goal here is to control devices through Siri, I consider that acceptable for the time being. This should probably some homebridge-insteaon node. This is not the prettiest code; I’m more of a C programmer than a Javascript programmer, but it gets the job done. Now you just need to add your devices to your config.

For example, this adds a single FanLinc device as two separate accessories, one as “lightBulb” for the light, and one as “fanlinc” for the fan.

You will see two separate devices in your HomeKit app, and you can control the light and fan separately by using their individual names. For most devices, this is a value between 0 and For FanLinc devices, it’s one of “low”, “medium” or “med”, “high”, or “off”. There might be other commands that work as well. That’s it. It works well for me, and while I can’t guarantee it’ll work for anyone else, I don’t see why it wouldn’t.

Joe’s Projects. Info Email. Blog Projects Repairs and Maintenance Blog. Various electronics, programming, welding, mods and other non-automotive projects. Installing Homebridge Homebridge is implemented through node. Xcode The first step is to download and install Xcode from the Mac App Store so the you can set up everything else. Now Homebridge is installed, but it doesn’t do a whole lot yet. SmartThings and Homebridge I found SmartThings support from the associated homebridge-smartthings project.

Detailed steps for all of this information is described on the homebridge-smartthings page. Launching Homebridge Now you can manually launch Homebridge and try it out.

To stop Homebridge, just hit ctrl-c in the terminal window.

Comments are closed.