OverloadUT

Hi everyone, I am doing some development work to add heartbeat support to Home Assistant when it talks to an ISY994. I would really appreciate it if some people with Motion Sensors, Hidden Door Sensors, and Smoke Bridges could let me know what nodes appear in the ISY for these devices, and MOST IMPORTANTLY, what the subnode ID is for each of them. The subnode ID is the last number that appears for the device: What I'm mainly wondering here is if the Heartbeat node is always subnode 4, AND if there are any other things that can end up occupying subnode 4. I only have door sensors and leak sensors, and the behavior is consistent among them. I want to ensure these other devices will work with the code I am writing before I add them to Home Assistant. Thanks!

Yeah, I've seen that occupancy sensing solution, but unfortunately the limitation of it only working if the user unlocks his phone upon coming home is not acceptable to me. I'm actually in the process of writing my own geofencing app for iOS to ping a custom API that will solve this problem. As for bluetooth: While at home, I don't need any of our phones to pair to a second device, so I would be okay with that limitation. I do carry my phone around though, so sensing the vibration wouldn't work. Plus I'd like to use the data that a bluetooth device should be able to get, such as who is calling, and eventually work that in to my home theater system (to display who is calling in XBMC for example). What's killing me is that I swear I read about some router-sized device with wifi and bluetooth (might have been an actual router, might have not been) that people were buying on eBay and whatnot for Home Automation because it was an excellent way to get a cheap computer with bluetooth capability. But I have no idea what it was!

Here's an idea I hope you guys can help me figure out how to implement. I want my ISY to be aware of when I have incoming calls to my cell phone. I'd like to do this without Jailbreaking (otherwise I would use Notify Pro so that I can have it work for my housemates' unjailbroken phones. I figure the way to do this would be to have some sort of device that has bluetooth capability centrally located in the house (might need more than one if the range is too great), that can do something (like make a REST call to the ISY) when it detects an incoming call. However, I have no idea what kind of device I should be looking for, or if this is even possible at all! I have a vague memory of some sort of re-purposed router that the HA community was all about, due to it having Bluetooth and its ability to be rooted to run linux. Has anyone done this, or have any ideas on how to do it? As a bonus, this would also work for occupancy sensing!

I am curious what people's solutions are for getting audio feedback throughout their houses. I'm not looking for high quality per-room speaker systems for playing music, but a minimalist way to get audio in each room for doing simple things like playing audio files, text-to-speech, or beeps and boops in reaction to ISY events. For example, I'd like a nice chime to play (or maybe a "good night" voice) when a user double taps the off switch by my stairs, to indicate that the bed time program has activated. I figured with the abundance of ultra-lightweight computers like Raspberry Pi, and things like Ubi on the horizon, people must have come up with solutions that revolve around these devices rather than expensive distributed audio systems!

It would have been better to say not a "general purpose computer"...but it's still essentially like a highly-specialized embedded device. The "extraordinary silly" part was when you blasted the developers with exaggerated statements about jaws hitting floors, and statements like "It has been literally 15 years since I have had to worry about 8.3 filenames, and I could not believe that the ISY-994 is actually beholden to this!" I also still don't understand why you can't just rename all your files to match 8.3 scheme... I apologize. It was 1:30 in the morning after a terrible day at work and so I definitely came across a lot more angry than I meant to. I even changed the title of the thread this morning to be less incredulous. I never expected the ISY to have a full apache web server or anything, but it having a web server was one of the selling points for me, so it was that frustration mixed with the above that caused my anger. The issue with renaming the files is having to adjust the source code for bootstrap so that it knows about all of the shortened filenames. It's certainly not insurmountable, but it'll be annoying each time I want to update bootstrap. Realistically though, I'll probably never need to update bootstrap as once I build this it'll probably last for a very long time.

Thanks for the info Michel Kohanim; I figured it might be something like that. It's disappointing, but I'll figure out another way. Everyone else - I am perfectly capable of setting up a web server, but you guys are forgetting the entire point of needing to run it on the ISY itself: Same Origin Policy. I can't have javascript access the REST interface on the ISY unless that javascript is loading from the same domain. The objective was to have an extremely lightweight Bootstrap+jQuery webpage for turning on and off the lights. I suppose I could set up a simple REST mirroring interface on the separate web server. I'll have to look up what the best practices for accomplishing this are, as I'm not sure what is the most proper way to go. Also, calling the ISY not a "computer" is an extraordinarily silly assertion but let's not dwell on that!

This is a fantastic idea that I am going to steal to do the exact same thing with my Chevy car!

I've been working on making a little lightweight web interface for quick control of lights in my house to replace the atrocious one served up by the ISY. When I got to the step where I needed to test the AJAX calls to the REST API, I had to put my files on the ISY itself to play nicely with the Same Origin Policy. When I did, my jaw hit the floor when I got the error saying that most of my files couldn't be uploaded because they don't observe the 8.3 filename restriction. It has been literally 15 years since I have had to worry about 8.3 filenames, and I could not believe that the ISY-994 is actually beholden to this! What exactly is the webserver intended to be used for with this sort of restriction? You can't even load jquery! Is there any workaround to this or way to change the filesystem in the ISY?