Notice: This forum has been recovered from an old backup, so some content, links, and dates may be outdated. The forum is currently read-only while we restore sign-in and registration functionality. Details
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
terRemote wrote:
When you say "home screen", do you mean the "lock screen" that appears when you reactivate your device? I'm not sure if using terRemote as home screen (i.e. as a launcher app) is realistic in the foreseeable future. The lock screen feature is.
I meant using it as a Home Screen Launcher App. So when you boot up your device it will load right into terRemote.
terRemote wrote:
The toggle/switch widget can be emulated by using the "Widget Data -> Set Design" action and then having two designs "switch on"/"switch off". Or you can use the "Widget Data -> Set Icon" action for showing the picture glowing or non-glowing led. I agree that a special widget would be easier.
Thanks for the work around. I'll try it out.
Also, I still wanted to know is it possible to have a "durable" option when setting up Macro Actions?
I don't think there will be a possibility soon to have terRemote as a desktop (=launcher) app. It would be no problem, though, to implement an event "device booted" and then have terRemote start itself on this event. This might give you the behavior that you wanted.
About the durable/enduring actions: it currently can't be done in terRemote because there is no "start/stop an event" action. I might be able to implement this but the Network Event Receiver in EG cancels all these events automatically when any other signal is received. You can not start an event, send another one-time event and then later cancel the first one.
A python script in EG might give the solution. I'll see if I can figure out something.
just wanted to say that in the last 30 mins I have installed EventGhost, terRemote and the tasker plugin; and sent an event from tasker to EventGhost to fire an action on my PC.
very impressive, could do with a little more documentation, but love it !
If you have a few minutes, could you send me an email with some of the points that you didn't find very intuitive/well documented for first time users?
Most of the feedback I get is from experienced users and I can never tell myself which parts of the app are difficult to understand at the first use.
I found the tutorial in terRemote very helpful, the problem I had was not being able to find anything on the Tasker plugin, and the settings in terRemote to talk to it. I pieced it together from various comments in this forum.
1 - what are the plugin settings that interface with terRemote
2 - how do you enable terRemote to receive and action the event
I am currently experimenting with terRemote Pro and have added one button that sends a 'test' Event without payload, which triggers the following Error command in Eventghost on the PC:
13:34:16 NetworkReceiver md5 error
Any idea what this means and what I should do to get the right Event?
Hopefully another easy one:
I am trying to send a number value of 45 as payload to Eventghost and have added a button in terRemote which sends a payload value of 45. I do not want to have an Event name, so I leave Event name blank.
However, it is received in Eventghost as follows: TCP.0 ['192.168.1.42', u'["{45}"]']
by using eg.event.payload [1] in Eventghost, I should get what I want, namely: ["{45}"]
I want to use this as a number, but I can't seem to make work with it in any way by using my standard (limited) repertoire of solutions, e.g. by eg.event.payload [1] or str(eg.event.payload [1]) or float(eg.event.payload [1]). I am already using a http event from an existing Eventghost webserver that results in HTTP. [u'45'] event in the Eventghost log, which I can then use in a calculation by applying float(eg.event.payload [1])
My question is: why does the payload number turn op in Eventghost in this format and what could I do to make a number value out of it?
sorry for not answering for so long. The issue you describe is indeed a bug. Although in my tests the value appeared as ["45"] without the braces. I will fix it as soon as possible in the next version.
Until then you can use eg.event.payload[1][2:-2] or eg.event.payload[1][3:-3] to slice away the extra characters.
I hope this helped. Sorry about the bug and the delay. But thanks for reporting it
I entered just the number 45 in the payload field. When I go into edit mode and check the action, the payload field now has a similar strange entry, but slightly different from the one that was received in EG as stated in previous post. This is the exact entry in the payload field in the Android device:
["[\"[\\\"[\\\\\\\"{45}\\\\\\\"]\\\"]\"]"]
If I escape from that without saving and issue the command, it results in EG in the PC in the following (different) result:
TCP.0 ['192.168.1.42', u'["[\\"[\\\\\\"[\\\\\\\\\\\\\\"{45}\\\\\\\\\\\\\\"]\\\\\\"]\\"]"]']
I then go into terRemote again and delete the extra stuff from the payload field so it just says 45 again and save. If I then enter the command again I get the correct event in EG:
TCP.0 ['192.168.1.42', u'45']
I just noticed that other commands have the same strange behaviour. The event I receive in EG when I issue from TerRemote the command to get Eventghost on my PC to switch off my radio:
TCP.goodbye ['192.168.1.42', u'["[\\"[\\\\\\"[\\\\\\\\\\\\\\"[\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"[\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"[\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"[\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"]\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"]\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"]\\\\\\\\\\\\\\"]\\\\\\"]\\"]"]']
It looks as though random amounts of backslashes are built up over time in the payload field.
I went into edit mode into the command and found the payload field (which I never intended to populate for this command) filled with the backslashes stuff. I deleted those and saved the action again, reissued the command and now got a clean event again:
TCP.goodbye ['192.168.1.42', u''].
It seems really weird. I will re-try at certain points in time to see what happens and let you know if the issue persists.
BTW, my android device is a galaxy tab P1000 running Android 2.2 Froyo (JPJM5).
1) Was putting together some new png icons for use with terRemote and just discovered that I can't add any new icons to the app. This has worked in the past but haven't tried to add any since Ver 1.31 Pro was released. Tried on both my phone and 3 separate tablets just to be sure I wasn't crazy.
I enter edit mode via menu and then edit a widget. I select "Icon" within the edit widget screen then select the icon picture in order to change the icon. When presented with the "Pick Icon" screen, I then select the "Add" button and am presented with a circular working icon like it's loading the file system, but never loads, after about 3 or 4 minutes I have to press the system back button to get back to the "Pick Icon" screen again. I can change the icon with the already loaded icons in the pick screen but can't load new icons from the file system.
I have experienced this on my
Samsung Captivate with Android Ver 2.3.5
Motorola Xoom with Android Ver 4.0.3
terRemote Ver 1.31 Pro
2) Was trying to test my eventghost action in eventghost using the test button, rather than viewing the
event preceded with "TCP" in EG, I receive the following event:
TCP.null ['192.167.4.098'], This happens everytime I try test with each of the handhelds above.
EDIT: I also cannot import layouts via options menu. it seems the android file system is not being accessed thru terRemote.
EDIT: Thanks for the quick update. Best App around!!!
Thanks in advance.
Steve
Last edited by steve@rpad on Tue Aug 06, 2013 7:36 pm, edited 1 time in total.