Pete Zaparti
Members-
Posts
21 -
Joined
-
Last visited
-
Days Won
2
Everything posted by Pete Zaparti
-
Seems like after, that’s why the last action in a macro can’t have delay. Know what might be a neat feature: if you could assign a power on delay to any device, and that would automatically add that delay to any macro that includes powering on that device. For my setup, it would save me from having to manually add the delay to a bunch of different macros.
-
If I put a delay on an action, does that delay happen before or after the action?
-
The GUI reacted very predictably IMO. The colored outlines on each button reflect the actions I copy-pasted in the JSON, and the popup from clicking each button includes all of those actions, and they can be reordered or trashed, just as if I had added them in the UI. Pretty straightforward. ----------- Anyway, I'm liking the results! All of my configurations are now a combination of 2 buttons, the activity and then a number. (the numbers here reflect the order of inputs on my receiver remote) Play retro games - A2 Play Nintendo - A3 Play Playstation - A4 Watch Apple TV - A5 ...a few more Watch TV Tuner - B+RECORD (numbers are needed for this activity) Play PC - C1 (my PC has to be plugged directly into my TV for a few nitpicky reasons) Each of those macros sets the appropriate inputs for the TV and the receiver, but first includes POWER ON, which basically do nothing if the devices are already on, and I changed the power button to only POWER OFF devices, no matter what state things are in. A little weird? Maybe, but I'm liking it. To help remember that list ^ I'll print it for the coffee table or maybe even tape a list to the back of the remote.
-
Update: In the meantime, I was able to get what I'm trying to do by just editing the JSON. It's nice that the configs are JSON btw! Makes it easy to parse what's happening under the hood.
-
Thanks Jason. Btw, this is my first time coming back after using the Skip 1s for a few years to try out a new config, and I just wanted to say thanks for all your hard work. You were helpful last time I posted here, and now you're being helpful again. Much appreciated!
-
Any reason that device's action can only be assigned to 3 buttons? I'll explain what I'm trying to do. I want Activity A to be "my receiver as a hub". My receiver has a lot of devices plugged into it, so for Activity A I want the TV to use HDMI 2, and my number pad chooses the inputs on the receiver. For each number, I want to have 2 actions: TV - Input HDMI 2 Receiver - Input # (where # is the number pressed) The problem is that the TV's Input HDMI 1 can only be assigned to 3 buttons. After that, I can't drag it to any more numbers. Why do I want it to work this way? Because there are other activities where my TV is not on HDMI 2, like when I'm using the TV tuner to watch things over the air, or when I use HDMI 1 for my PC. So no matter what inputs are currently set to, I want to hit A and then a number and have the TV set to HDMI 1 and the Receiver to that input number. I'm trying to use the macro actions to minimize the buttons I have to press to switch all these inputs. If someone has a better approach that they've configured their Skip 1s for, I'm all ears.
-
Remote goes dead for a few seconds intermittently
Pete Zaparti replied to Pete Zaparti's topic in Skip 1s
Jason could you actually point me towards where in the forums I can stay up to date on the latest on firmware/software? If there's somewhere I can follow that, I'd love to stay informed. EDIT: Oh nice, I updated the app and I see the it now alerts you when there are available firmware updates. That's great. -
Remote goes dead for a few seconds intermittently
Pete Zaparti replied to Pete Zaparti's topic in Skip 1s
For the record ^ that person is complaining about the lack of communication on not receiving their product, weirdly choosing this thread as the place to do it. Apologies for missing the existing thread on the remote going dead, but glad it's fixed. -
Remote goes dead for a few seconds intermittently
Pete Zaparti replied to Pete Zaparti's topic in Skip 1s
Thanks Nathan. Appreciate the update and the hard work. Looking forward to Jason’s PHD thesis. -
Remote goes dead for a few seconds intermittently
Pete Zaparti replied to Pete Zaparti's topic in Skip 1s
Has this been addressed? Or is there a ticket I can watch to know when it is? It’s getting frustrating to have the remote just go dead for 10s randomly. -
Device searching broken in latest build?
Pete Zaparti replied to Pete Zaparti's topic in Beta Feedback
Thanks Nathan, and sorry for missing the beta forum. I'll use that in the future for subjects like this. -
I had my Skip App set for nightly builds, and in the build a night or two ago I could no longer search for devices. I was trying to add an Apple TV. It looked like the interface for device searching had been updated, but when I typed in Apple, nothing would show up. I switched back to 0.9.66 and it was fixed. Could be a known issue, or a hiccup with whatever API or data source you're using, but just thought I'd mention it.
-
For the record, with my latest changes I experience the same as splice.
-
I did, yeah. I have 3 activities, and each one involves the TV and receiver. By default, the power button for each device is "Power toggle", but I'm concerned the devices can become out of sync, like if one of them goes to sleep. Don't want to get in a state of toggling them to have one be on and the other off. So then I tried putting each device's "Power on" button in the Power on action, and likewise for off. But like I said, these actions don't do anything. Could be my device mappings? I have an LG C1 tv and I picked the first LG TV button set. /shrug
-
I second LouP's responses. Having just come from a Sofabaton X1, I can say the Skip1s is the much better experience. If there's any lag, I can't perceive it. It seems to be as reactive as using a device's standard remote. Holding vol up/down also appears to work naturally. That was actually one of my big problems with the X1, I just could never get holding volume to work the way I wanted.
-
Thanks Jason. At the time that I posted this, I upgraded to the latest firmware, 4.12.10 I think, and it started working again. Since then I've had this new issue I opened up, but we can mark this one solved. I upgraded to 4.12.11, and will keep that other thread posted.
-
I have this issue with my remote where every so often it just stops responding, for about 3-5 seconds. Every button I hit does nothing. Then suddenly it comes back and works again. It tends to happen a couple times over the course of a movie. I attached my config. My firmware is version 4.12.10-0-ga6a774d. I'll check if there's a newer version available. Has anyone else experienced this? Family Room.skip
-
I'd love an explanation of how Power on and Power off are supposed to work. I set them up the way I would think they would work: I have power on power on my TV and receiver, but it does nothing.
-
My remote was kind of working at first, but I was having the issue where it would always switch to activity A. I installed 4.12.8, and now the problem I'm having is that beyond the first button press, the remote just does nothing. No reaction from any button press. I just installed 4.12.10 to see if anything is fixed, but beyond that how can I help debug this?
-
Hi! Just getting started with my remote. I set up activity A to be for streaming on a Roku, and B as watching TV. The issue I'm noticing is that if I select B to watch TV, let the remote sit for a few minutes, when I pick it back up it's no longer controlling the TV and the activity A light goes on when I hit a button. So it seems like the activity is automatically switching to A. It happens repeatedly. I can't actually get the remote to stay on B. Has anyone else experienced this? EDIT: Shoot, looks like it's already covered in this thread. Apologies for missing that. Feel free to delete this one.
-
^ This post is filled with great feedback. I'm sure Flirc is tracking feedback from all kinds of sources as people get their products, but just suggesting you take note of what's mentioned here.