rccoleman

Fair enough on the first part. Regarding 2FA, once I added the code from the link I mentioned, it asked me for the authentication code the first time and hasn't since. I suppose that it now sees this rpi as "trusted", but it may time out at some point in the future. I reverted back to the original distance_home_delta calculation and it's now working fine. Rob

I thought that I'd be able to create an app-specific password for your script, but it's not accepting the one that I created. That's supposed to be the answer for third-party apps, and I'd expect it to work just fine. The more I look at this, I'm wondering if it's just a bug in the loop. I get this in the log: 2016-09-25 09:48:42,519 - rpi3 iPhoneLocation(v0.12)[11999]: WARNING - MAIN - Reading the iCloud iPhone location from API failed! Sleeping for 30 seconds. Traceback (most recent call last): File "./iphonelocation.py", line 586, in <module> distance_home_delta = distance_home - distance_home_previous TypeError: unsupported operand type(s) for -: 'float' and 'str' on this line: ### Determine the change in distance: distance_home_delta = distance_home - distance_home_previous I suspect that "distance_home" should be "distance_home_precision", and that's causing the loop to fail on subsequent executions, but changing that isn't enough. I suspect that the error message that I'm seeing is not really accurate. Edit: Got it working. I changed "distance_home" to "distance_home_precision", as described above, and also added "float(xxx)" around the expression on 578. Otherwise, it evaluates to a string and the delta calculation fails. I think the "float(xxx)" change is the only one that's really needed, but I also wanted to do the delta calculation with equivalent significant digits. Edit 2: See here for info on 2-factor authentication with pyicloud. I added the code and it seems to work, but for some reason it doesn't seem to matter. I can just leave this code out, ignore the 6-digit code that pops up on my Macs and it works fine. I can't seem to make app-specific passwords work for this, unfortunately. Rob

Hmm.. After updating to v0.12, the first iCloud request succeeds and any after that fail. I worry a bit that it's because of the two-factor authentication that I have turned on. When I first run the app, I get the normal "someone is trying to access your account - accept/deny" popup, I hit "accept", it gives me a six digit code to enter on the client, and I ignore it. The app continued to be able access my account forever yesterday, but now it's failing after the first query. Do you have two-factor authentication enabled?

Sounds good, Steven. Thanks! It's working well enough for me that I switched my triggers to it and deleted my Locative geofence.

I set this up today and it looks like it should work for me. I had to install some additional requirements (PyMySQL was one), but nothing too complicated. It was also my first attempt to use MySQL, so that may prove helpful in the future. One quick comment is that having the distance in whole miles is a bit coarse for me. I'm using v5.0.4 on my ISY, which allows you specify variable precision, and it would be great if I could get at least 1 decimal place. I'd like to be able to arm my alarm when I'm 0.5 or 0.25 miles away from my house, for instance. I quickly hacked that by changing exit_code, isy_status = isy_variable('set', 'state', device_conf['ISYDistanceVAR'], int(distance_home)) to exit_code, isy_status = isy_variable('set', 'state', device_conf['ISYDistanceVAR'], round(distance_home,2)) Now, to drive around a bit a try it out! Edit: It looks like there are few more things that need to change, but I think I got them all now. Back to testing! Rob

I'm excited about this! I've been trying to find a reliable geofence mechanism it's been harder than I expected. For some reason, IFTTT doesn't trigger for me most of the time unless I start the app (despite having "background app refresh" and location "always" allowed), so that's out. Locative works much better, but I still routinely get multiple triggers upon crossing the geofence (either all the same, or sometimes is oscillates). I'll give this a try and see if it works better for me. Rob

The ElkRP software is Windows only, but runs fine in Parallels, VMWare Fusion, and (I suspect) VirtualBox. After configuration, I rarely need to use it, though. I control my M1 through my phone (currently eKeypad) and ISY programs.

If you hit the circled "x" in your screenshot, it clears the notifications for that particular day. I like to use the notification center for notifications that I haven't read yet, so I regularly clear it out. That's curious, because the way I described it is exactly as it works on my phone. I just had an unread email in the notification center, I went to the iOS mail app and read it, and it was gone from the notification center when I reopened it. I honestly think the intention of the iOS notification center is to keep track of things that you haven't yet attended to.

He's saying that they disappear from the iOS notification page when you open the app, and he'd prefer that they stayed there. It doesn't bother me (I just open the app to see historical messages), but I also clean out the iOS notification page on a regular basis. Notifications usually disappear when you read them in the originating app (like email), so I think it's consistent behavior.

Oops, perhaps that's why I had it set up as an email instead of a network resource . It was a while back and I couldn't remember why I had to do it that way, only that it was the only easy way to do a arbitrary text substitution that I could find. Sorry for the misinformation.

The tactic that I used for notifying me of specific alarm zone violations was to have a separate program for each with a useful name and then to use ${sys.program.#.name} in the subject and content. That gives me a separate text notification for each zone without the need for a bunch of network resources. I note that {sys.program.#.name} isn't listed at that link, and I'm actually using it in an email to Pushover, but it seems like it would work in a network resource, too. Rob

I think I had the programs set up to ensure that both relays weren't powered at the same time (luckily, they were both off when the Zwave relay first receives power), but the startup load of the fan exceeded the capacity of the relays. In the end, I like my whole house fan too much to put it at risk for an infrequent speed change.

I spent some time trying to get a Z-Wave dual relay to work in conjunction with my Insteon On/Off switch, but the relays were only rated to 10 amps and it had a bad effect on fan startup. You also have to ensure that both loads aren't powered at the same time, so you'd want to use a set of programs to change each relay and check the state. I just gave up on it and went back to manual speed switch. If you find a solution, I'd love to hear it. I don't often need to change the speed remotely, but the physical switch just makes my fan feel...incomplete

That bar comes and goes for me. Michel remoted into my system and observed the behavior, but there hasn't been much traction on getting it fixed. See if it comes back after you quit and restart the admin console a few times. My thread on this issue is here: http://forum.universal-devices.com/topic/18209-elk-bar-at-the-top-of-the-admin-console-sometimes-missing/?view=getnewpost

That would be useful. You can go back into the history to listen to what it heard for each instance when it responded, but not if it didn't. The available recordings haven't given me much insight when it doesn't do what I want - they sound perfectly understandable to me.

Thanks, I'll experiment with that. Maybe it won't look as goofy with black paper.

I've seen the same thing with just a Samsung TV using the built in speakers and my new Echo Dot. Even raising my voice and lowering the TV volume wasn't enough - I had to walk right up to the Dot and speak directly at it. Without the TV on, the Dot works fine from across the room. My Dot is next to a window, so I'm not excited about yelling at it and having my neighbors wonder what the heck I'm doing. That TV does seem to have an outsized influence on my Dot. I also have an Echo in the same room with a Denon surround sound system and its able to pick out my commands much better with the TV on. I've also had it spring to life when it heard something Alexa-like on the TV You may be onto something about there being background noise that I can't hear, but messes up the Echo/Dot's recognition.

My thinking was to put them all in a folder where I can enable or disable all of them using a variable, rather than enabling and disabling each one. Do you see anything wrong with that approach?

I really like the idea of a program triggering on activity and forcing an update - that's really clever! At least with my motion sensors, the worst case is that I'll have to walk around my house and let all of the sensors see me. Do you find it to be reliable? The motion sensors don't go to sleep before the ISY can write its updates? To be honest, I hadn't figured out why "write device updates" was a useful action in a program until you mentioned it. For now, I put all of the programs in a folder gated by a variable. I was hoping that simply turning off automatic updates would allow the current update to finish (fail) and not kick off another update, but this morning my ISY soldiered on and tried to update all nine motion sensors and remotes one after the other. Unless you have only one or two devices, it seems like that's rarely the behavior that you'd want. Rob

In an attempt to address some strange behavior that I've been seeing, I've swapped out my PLM and restored devices several times. Every time, I end up with many battery-operated devices that need updates, and the ISY starts a long and seemingly uninterruptible process of trying to communicate with each and every battery-operated device in my house, timing out and failing every time. I have a 994i Pro, so if I think ahead and turn off updates of battery-operated devices, I can prevent this long and fruitless process, but if it gets started, it basically ties up my ISY for a long, long time and accomplishes nothing. Worse yet, if I have to reboot the ISY for some reason (like installing a node), the default behavior is to turn automatic updates back on and it quickly kicks off this long process again. I'll get around to updating the battery-operated devices at some point, but it's a pain to hit them all and I'd prefer to do it at my own pace. I have a few questions - Is there a way to make the setting for automatic writes, for both wired and battery-operated devices, sticky across a reboot? Sometimes I'd really prefer to be in control of what the ISY does with my devices, and the power-on default is to automatically update everything. Is it possible to interrupt the automatic process once it's started? I've found that I can sometimes reboot the ISY and quickly log into the admin console and turn off updates, but it's a race that I sometimes lose, and it seems awfully brute force. Clicking the "turn off battery-operated updates" button when it's already in progress doesn't seem to help. Is it possible to force a node back to "up-to-date" and avoid the need to write any pending updates? I had some mismatched records in my wired devices that I fixed by doing a File | Restore Devices, but it also queued all of my battery devices for updates. I had just finished manually updating my battery devices (climbing up on ladders, etc.) and I know that they're all up-to-date, so I'd love to just say "that's already up-to-date". I was trying to avoid the long process of individually checking and restoring each of my 42 wired devices, but now I get to walk around the house again and "update" each battery device. Ugh. Rob

I'm not. I'm using port 2101 without SSL. My understanding is that using the secure port would prevent any communication with the M1XEP, but a) programs involving Elk components work fine and sometimes the bar shows up and sometimes it doesn't (as you saw when you remoted in). Rob

Michel, do you expect to look into this for 5.0? The Elk bar is still often missing as of 5.0.4. Rob

I'm trying to do something that feels simple to me, but I just can't figure it out. I basically want a Mobilinc (iOS) dashboard button that both shows the current alarm status (armed/disarmed) *and* lets me toggle the status by tapping it. Essentially what the giant red/green button does in the Mobilinc Elk plug-in, but on the dashboard. Simple requirements - * The dashboard button should always show the current alarm status (armed/disarmed), regardless of how it got that way (keypad, ISY admin console, program, etc). * Tapping the dashboard button should toggle the alarm state: If it's armed, disarm it. If it's disarmed, arm it in Away mode. I can write programs to do either one of these things, but not both together on the same button. I've tried all sorts of combinations of integer and state variables, disabled programs, and any other clever tricks that I can think of and I just can't make it work without unintended side effects. Is there an easy way to do this that I'm just not seeing? Edit: my apologies for putting this in the wrong area - I was looking for similar topics and ended up in the wrong one. Perhaps a mod can move it to "questions and answers". Thanks, Rob

Heh, that was on purpose. For whatever reason, I turn them north-south on single boxes and east-west on bigger ones. Feel free to disagree, but at least it's not random

Here's mine: Pretty easy to do, and easy to change out if you want to rename them. Rob