apostolakisl

Google voice allows email to text, but it is slightly tricky to set it up, but once set up it works perfectly every time. You need to enable google voice to send a copy of all your texts to your email. First thing is to receive a text from the phone number you want to send texts to. This could be you sending a text to yourself. Then copy the from address in that email copy of the text and put that as the to address in ISY. That address defines for google voice where to send it, both the phone number and the text thread. Of note, the email account that ISY sends emails must be the same one you have google voice copy texts to. It follows this format <yourphonenumber>.<thetophonenumber>.<stringofnumber/lettersthatidentifythethread>@txt.voice.google.com I sent myself a text to get the thread going so the two phone numbers in my case are the same. I set this up this many many years ago and the thread still keeps going. If you want to send the text to someone else, you would need them to send you a text or reply to a text from you to get that email address format I showed above..

Yes, IF the variable is a "state" variable. Integer variables are not triggers. Integer variable are used to affect the true/false status of a program when something else triggers it. No, if it is a state variable, it only triggers on a change of the value. Again, it is integer, it never triggers. Yes, when it changes at all it will be a trigger, if it is a state variable. It is the change of the variable that is the trigger. For example, If $s.test is 1 Then do something Else do something else In this case, if $s.test is currently 2 and it changes to 3, the program will trigger and go false. In the case it is 1 and some other programs sets it to 1 (so it doesn't change) nothing will happen. If it starts as 2 and changes to 1, it will trigger and run true. Status in an if clause triggers the clause on any change in status. For example, if status is 25% will trigger on any change in the status of the switch. Say it was off and it turned on, that would trigger the program to run false. Status responds to any change in the switch no matter how it happened. It could be responding to a scene command, responding to a program, or responding to local control. Control in an if clause ONLY triggers on that exact thing happening on that device. For example, control switched on, means someone clicked the on button on a switch. Nothing else done to the switch triggers the program. Turning on because it responded to a scene or program does not trigger the program.

I agree. The java admin console has all kinds of bugs in it that cause it to lock-up, have hidden windows, and generally just stop working when you leave it open. But never have I seen it do bad things to eisy/polisy/isy. In the very very old days of windows, ctrl-alt-delete /end program was just a thing you had to do for lots of stuff. But for the last 15 years or so, only with java.

Control statement important considerations 1) Only an action originating at that device is a trigger. Typically that means you physically acted on the switch. However, things likes motion sensors would also trigger a control statement if it picked up motion because that device is the origin, it isn't responding to another device. 2) The status of a device is not relevant to a control statement of a program. (though you can still have separate status lines in the same program, see point 5) 3) Use "is" logic to trigger true, use "is not" to trigger false and you can have both in the same program. For example: if device a is control switched on and device a is not control switched off. In this case, the program runs true when you click the on paddle, and runs false if you click the off paddle. What it does is make the program mirror an action at the switch. 4) A control statement using "is" logic will only ever be true if it is the trigger of the program. So if you mix status items into a program with control, then that program will never be true when triggered by the status line. Using "is not" logic is the same but opposite. Also along these lines, you would never have two "control is" statements in the same program if you ever wanted it to run true because you can never have two devices simultaneously hit the program at once. No matter how hard you try to hit two light switch on paddles at the same time, one will always come before the other. 5) You can combine status and control for certain logic. For example: If device a status if off and device a is control switched off, then . . . . In that case, if the light is off already, and you push the off paddle the program runs true. In my home I use this as a night light feature where I can get up in the middle of the night, hit the off paddle and the program turns the light on to 10% instead of the usual on level.

OK, I just tapped favorites, didn't hold it. I think that does it. Thx.

I tried again. Rebooted the phone and it is reverted to home page again. I tried deleting the icon (it was in quick launch bar), going back to original icon in my full list of apps, press/hold/add to home screen. That put it in the regular home screen. I pressed and held and hit favorites. Now it opened to favorites. I dragged that into quick launch bar. Still opens to favorites. Rebooted phone and it reverted to opening to home page. I tried then only having it on the home screen, not quick launch bar, still reboots revert it to opening in home screen. Not sure what else to try.

This seems to be only a sort-of fix. I rebooted my phone and it reverted back to opening on the home page.

Thanks. Not sure how you figured that out but good job.

My Android skips from lock edits to favorites span. I don't have the launch preference. Is it somewhere else in Android? EDIT: Don't know if this matters, but I have two ISY's on my UD mobile acct. Doesn't matter which I look under, it is the same, it skips that field.

That is a good idea too. I was just trying to teach someone how to use UD mobile and it is just way too much for a user only person to look at. A version that only opens to favorites and requires an admin password to edit the favorites.

I would like to make a suggestion that there is an option to set UD mobile to, by default, open to the favorites screen instead of the home screen. 99% of the time, I just have to click "favorites" after opening, and I'm guessing that is the same for a lot of others.

Yes, that is correct. The java console is still plagued with quirks and is supposedly soon to be replaced by a fully functional browser interface.

You need two programs, the first program contains all the if conditions. Then clause does a run then on second program and disables itself. If clause on second program is blank. Then clause contains your actions and concludes by re-enablung the first program.

From this screen. I have the edit enabled, I change the name (just deleted the AHU3 part). I hit "save" in the upper right corner that shows up after I start editing, it does the little swirly thing for a couple seconds and takes me back to the previous page. But nothing changed. Same name (which is apparently too long and it is cutting off the word "lobby"). And if I hit device dashboard again, it returns me to the page shown above with the name still un-edited. This ISY is running 6.0.4

Right after I upgraded, I went out of town. There was a big wind storm and it blew over an outdoor potted plant that had led lights in it controlled by a lamplinc. The wire to the lights tore and it was making the lamplinc sense go bananas. 6.0.5 could not function with that going on. Via VPN, Michel downgraded me to 6.0.4 which got ISY to run, but the java programs page wouldn't open. The programs were all working, you just couldn't get to them in java. But you could in UD mobile. Michel said there was a program set to run at start that was in a loop doing this. I was skeptical, because I have had all those programs for years without issue. Anyway, I shut down all the run at startup programs from ud mobile, but the programs page was still blank (no panes or grids or anything, just a blue screen). I tried upgrading to 6.0.5 again and now all is fine. I re-activated all the run at startup programs and all is still fine. My theory is that the downgrade wasn't complete and there were some mis-matched files preventing the java programs page to load. The main thing here, as I see it, is that 6.0.5 crashes if an Insteon device is misbehaving whereas previous versions could deal with it.