terRemote - Android remote app for EventGhost

[terRemote]

In this case, the value you are looking for is the first entry of the payload (index 0). When Macros react to events, they automatically provide the payload and other things as variables. In your case, the variable is ${payload.0}. It will have the value 34 (or whatever you send). Just setting the "to" field to "${payload.0}" should do the trick.

Tip for debugging: When you click on any action in the log, you see all the variables that were available when the action was performed. You have to activate the debug mode for this to work (also in the log)

Best
Chris

[mpg732]

When I set it to ${payload.o} the slider does update to the variable, but with one problem. My slider range is 0 to 34. When I send the variable of 10 or above, terRemote only reads the first digit. so if I send 22 the slider goes to position 2. So looking in the log, it looks like when I send a double digit number it sends it as two different variables. So this script, eg.plugins.NetworkSender.plugin.Send("Set.Volume", "19") sends the number 1 and the number 9 separate variables. Any though on how to send is as one variable and not as 2 variables.
Thanks again,
Mike

[terRemote]

Probably because the send function needs an array as the second argument. Try

Code: Select all

eg.plugins.NetworkSender.plugin.Send("Set.Volume", ["19"])

[r0lZ]

I have had a similar error when I was trying to understand the examples from the help of the app. They contain several errors, fixed in the same examples on the web site. IMO, they should be fixed in the app too, as studying the exampled given with the package is the first thing a new user does, and he may switch to another app if the example do not work out of the box.

BTW, I've just noticed the update on the Play Store. I haven't tried it yet, but thanks anyway!

[mpg732]

OK, got it all working, so thanks for the help. But I did finding an issue with sliders after this last update. If you have a slider set to vertical, every time you adjust the slider it reverts back to vertical.

Thanks
Mike

[terRemote]

@mpg732
I'll fixe the slider issue in the next update. I want to include the (preliminary version of the) http action and I think I'll have some time tonight.

@r0lZ
You're of course right in what you say. The first-time user experience is something where I mostly rely on user feedback. So thanks for pointing out that issue

[terRemote]

Alright, the update is out. It should fix the slider issue. Also, there are two new ways of sending multiline text, including base64 functions. The documentation will be updated tomorrow but it's pretty self-explanatory, I guess.

The XBMC "Get Data" action left the beta status, you can now get the data of the currently playing audio track or video file. There are more things to come, of course. ^^

[r0lZ]

Also, there are two new ways of sending multiline text, including base64 functions.

Thanks for that!

[CypherMK]

Hi. First off all, a big thank you for this app!

I use this app in combination with tasker and eventghost to automatically turn on my receiver when I start my squeezecommander app. I use the free app.


I have only 1 small issue. When the app gets updated by the play store, it won't work with tasker anymore until I start the app manually. Then everything is fine. Known issue or a limitation of this app or limitation of Google update process?

Thx

[terRemote]

Hi,

the issue itself is new to me though it might have a known cause. By "won't work with tasker", do you mean sending tasker data or receiving from the terRemote Tasker plugin? From the use you describe, it seems like the second one is more plausible. Did the terRemote notification about the background service appear after the update? Maybe you deactivated it, anyway, but my guess is that the service is not restarted after the update. It usually starts on the device's startup or when the app is started manually so the explanation would fit. I'll see what I can do

Chris

[mpg732]

The update from last night did not fix the slider. Its was really late and didn't have time to play around with it. The problem with it is different from before, and like I said it was really late and I was half asleep and when it didn't work I just put it back to Horizontal. LOL I will try more tonight and let you know what I found.

PS.

Thanks for the quick patch.

Mike

[CypherMK]

Hi,

the issue itself is new to me though it might have a known cause. By "won't work with tasker", do you mean sending tasker data or receiving from the terRemote Tasker plugin? From the use you describe, it seems like the second one is more plausible. Did the terRemote notification about the background service appear after the update? Maybe you deactivated it, anyway, but my guess is that the service is not restarted after the update. It usually starts on the device's startup or when the app is started manually so the explanation would fit. I'll see what I can do

Chris

'but my guess is that the service is not restarted after the update'

That's also what I think. Because it works after a manual restart. Thanks for trying to 'fix' this!

[mpg732]

If you have sliders set to horizontal, and try to preposition it by dragging it around the screen, it reverts back to a vertical slider. then one you leave edit mode it goes back to being a horizontal slider. So this makes it hard to set the slider were you want it.

Mike

[terRemote]

Thanks for the description. Easy to reproduce. Will be fixed with the next update.

[r0lZ]

I've updated the remote with the current version of the Play Store, and it seems that the calls to Tasker are broken again. At least, the layout I did with the beta you gave me, that use Tasker to send the HTTP requests do not work any more.

Also, I have tried to use the new HTTS option to adapt my layout to the new version and get rid of Tasker. I can send the HTTP requests, and obviously my Lacie device receives them, but they do not work as expected. Now, each time I send a single request, the Lacie acts as if I had sent 2 or 3 of them. For example, sending the "down" request has the same effect as pressing down 2 or 3 times on the physical Lacie remote. I wonder why. (I have not that problem with Tasker.)

BTW, currently, I have just tried with some simple buttons, and I have hardcoded the IP of the Lacie in the HTTP address of the action of all buttons. But since the IP can change, it should be defined in a global variable, and the variable should be used in the actions of the buttons, so that you have just to edit one value when the IP changes. But I haven't found how to define a global variable, and how to use it in the actions. Is it possible? Can you explain how?