jasont

Just wanted to add that I got my Elk via @Scottmichealj and it was a great experience all around!

Have you seen the project that integrates BI with DeepStack AI (which you host/manage yourself)? Haven't tried it yet but it's high on my list of things to try. https://ipcamtalk.com/threads/tool-tutorial-free-ai-person-detection-for-blue-iris.37330/

FWIW, there is a separate, optional cloud version of Polyglot @Blackbird, there are a good number of folks using the cloud version to integrate with their Ecobee. There’s a separate thread for that

I wanted to thank you for your advice. Putting my roommate’s lights/heating pads behind FilterLincs totally fixed the problem... haven’t seen an X10 command show up in the ISY log since then. Thanks again!

I was looking for advice on if this is something I should just let ride, or something I should look to take action on: I have no X10 devices in my house, but starting about a month ago, my ISY is showing X10 events in the logs. I originally thought this might be a side effect of a failing PLM. About two/three weeks after the X10 events started appearing in the logs, some of my ISY programs were randomly failing to turn on/off SwitchLincs. My PLM was 2.5 years old, so I figured it was dying and ordered a new one. Installed the new PLM last night. Restore Modem had a problem with one of my SwitchLincs, and the little dialog box looked like it said X10 something or another when it was trying to write to it. I ended up having to restore that device. It's been working great since then. After the PLM replacement, I'm still seeing X10 commands show up in the logs, some with commands like "All Units Off" and "All Lights On". I don't know if/how the ISY reacts to these commands, if they may interfere when the ISY talking to my Insteon devices (because when they happen, there seem to be a lot of X10 commands back-to-back), etc. Thinking about anything that may have changed electrically around the house, ... my roommate is working on growing some flowers (truly just flowers) from seeds for the first time, so he has recently added three LED grow lamps (on from 8AM-midnight) and a heating pad thingy (on 24 hours) that goes under some of the plants. I've heard that grow lamps can cause "interference", but I thought it was RF and not electrical. The X10 events happen randomly, even when the lamps are turned off, so I'm wondering if the heating pad thingy he has may be introducing noise on the wires that the ISY thinks may be X10... Should I be worried about the phantom X10 commands they ISY is seeing if none of my programs look for them? Is it worth trying to filter out? Thanks for any advice! .

I wish there was a Zwave sensor rated for outdoor use that was as highly recommended.

For me, it'd fit in as the most universal bridge I could own for bringing Insteon and z-wave products that aren't each natively HomeKit compatible into the HomeKit world...

In the process of troubleshooting an Insteon Motion Detector whose Dusk.Dawn started acting wonky (after a battery change), I started fiddling around with its Darkness Sensitivity. For comparison, I'd like to know what the initial Darkness Sensitivity setting was, but I forgot to jot it down. What's the best way to pull that info from a previous backup? I tried unzipping a backup and looking through the files, but they appeared to be binary, and I don't know how to pull data from those. This was my next plan: 1. Backup ISY 2. Restore ISY from an older backup 3. Look for setting 4. Restore ISY from backup taken in Step 1 Is there any other way for me to see the setting other than this method? Anything warnings or gotchas from doing this? Thanks!

I recently installed an ELK system (thanks Scottmichaelj!), which replaced the Raspberry Pi/AMP+ solution that I've been using. I only have one in-wall speaker, so I disconnected the Pi/AMP+ and have the ELK connected. This way I get all ELK announcements/prompts/etc directly. In terms of crispness, the ELK lady sounds like she's chewing on cotton balls when she speaks (compared to the WAV files I've been using on the Pi/AMP+). I've tried both the ELK-73 Echo and ELK-SP12F Flush Mount speakers, and there wasn't any real difference in quality. Been considering adding the ELK components that let you use your own WAV files, but seems kind of spendy for what you get. Oh well. lol

That's my plan. My mailbox is "just" metal (no brick) and about 60ft from the smart closet in my house where I want to put the Tag Manager. Sensors have 700ft line-of-sight range, so I guess the mailbox can block 90% of the signal and it'd still work? We'll see. Plenty of uses elsewhere if this doesn't work out.

Wonder how the big the difference in "operating environments" will play for these new ones mounted outside during the winter (in areas where the temp drops below the specs). Older one: Indoor / Outdoor, 0 to 120°F. Newer one: Indoor / Outdoor, 32 to 104º F

Looks like the API supports Playlists. Maybe use Kodi directly to create a Playlist for each genre, and then create a ISY NR for each Playlist?

Santa was a day late, so my Sunday project got bumped to after work last night. Got everything setup and working! This is the flow of my sounds so far: Wired doors sensor > Raspberry Pi + PiFace Digital 2 > ISY > Raspberry Pi + AMP+ > ELK SP12-F flush-mount speaker Out of 30+ door tests last night, only one time did the sound take longer than one second to play. It was after a period of no activity, and it took 2-3 seconds to play. I haven't been able to recreate that delay, but I'll keep my ears open. Using the guide on post #14, the only difference I found was that some menus were slightly different on the latest OpenELEC that I downloaded. System>Settings>Web Server>Allow remote control>On System>Settings>Music>Playback>turn off Play next song were both System>Settings>Services>Web Server>Allow remote control>On System>Settings>Services>Music>Playback>turn off Play next song on mine. Manually testing the JSON requests from a web browser, one very rookie mistake I made was typing in http://ipAddress/ and then pasting one of the JSON examples from post #14. This resulted in a request that started with http://ipAddress//jsronrpc?... The extra / in front of the JSON request caused it to bomb out with a file not found, which made me focus on the end of the request where I had the filename specified. derp derp Thanatar, thanks for sharing this awesome solution for playing sounds!!! And thanks to so many others for the great ideas on how sounds can be used!

I feel like an 8-year-old on Christmas Eve as I wait for USPS to deliver my Pi and HiFiBerry AMP+ today...

Sold here, too! And it (along with everything else I needed) was Amazon Prime, so I'll be geeking out Sunday when it arrives. I wish If found this thread a month ago, it'd save me the hassle of having to return an Aeotec ZW056 doorbell that I'm pretty sure I'm getting as a gift for Christmas. lol

Same here. I like how MyQ natively handles remotely closing the garage, although the audible warning is a little loud -- the dogs pull their tails between their legs every time it starts beeping. I used Homebridge to integrate it with HomeKit, so all I have to do to control it is lift my wrist and speak to my watch to open/close it, or query its status. I can also walk across my house and press a button.

So if you could adhere one of those to the inside of the trash can lid, I'm assuming it'd "report" when the lid gets opened. Do you know how quickly they report movement? I'd love to use one on the inside of my mailbox door, but it's an all metal mailbox. If they take a second or two before they transmit movement, the mailbox door would hopefully be open. Hoping if you can sense one 1.5 miles away within a car, maybe I could sense one 50 feet away in a metal mailbox?

I was in a similar situation when I first got my ISY, which was right before leaving a week-long trip. Ended up running up to Home Depot and getting a $40 Belkin WeMo (outlet) switch as a quick fix, with the intent of finding a better solution when I got back. It's been 8 months and between the ISY not needing remote reboots frequently, and the WeMo having worked great the few times I've needed it, I'm inclined to let it stay.

I think my confusion was thinking that cyberk was having problems getting his eKeypad app working via the ISY Portal, but I see from another thread that's not the case. Sounds like he's asking for the ISY Portal to also act as a portal directly to the Elk, so other software that connects directly to the Elk can tunnel in from the outside. Sorry about that.

I'm kind of confused. If the ISY Portal is in use, then nothing (neither the ISY or ELK) need to be open to the web? It sounds like you can take the special ISY Portal URL and put it in any app that connects to the ISY (like eKeypad). When you use that app, it's going to to connect to the ISY Portal, which then shoots it over to the tunnel to the ISY, when then can manage the Elk. If that's correct, then no port forwarding needs to happen. The ISY Portal and the ISY take care of that for you. Nothing's open to the web. The only vulnerability I can see is that if the ISY in the house uses regular HTTP to connect to the Elk in the house, then someone in your house could capture packets on your internal network and snag the login credentials. But if you've got someone unknown that can access the network inside of your house, there are probably bigger issues that can be addressed first. The fact that the Elk has https turned off doesn't make it open to the web. Going to your router and port forwarding the port that the Elk uses to the Elk is what would make it open to the web (regardless of if it uses http or https).

danbutter, thanks for this thread. I had the same issue (although with an Insteon motion sensor) and trying to fix it, I came up with basically the two programs you did in post #3. Great minds and all that. Thanks to everyone for the help. I think I understand the THEN and WAIT better now.