Sarah, can we please have an update on the status of codes for the Logitech Harmony PS3 Adapter?
A couple of weeks ago you asked whether people were having problems with the navigation commands (which I am) and I'd like to know whether you've published an updated codeset to resolve this.
Also, the existing codeset 1403 is missing the most critical function - power off. This requires macro consisting of a long press of the PS (playstation) button and then a couple more presses. I understand this is included in the Harmony remotes (though I don't own one myself). Can this be added somehow? I can't see how this can be added to Activity Shutdown (because of the long press).
Sorry about that. The codes we added in our database are specific to the Logitech PS3 adapter, so I'm not sure why this is happening. You could try adding a new device with the manufacturer Sony and device type Video Game Console and save code set 4153 (these are also for the Playstation). Please let me know if those solve the problem, or if you experience the same issue.
Just wanted to let you know that Craig is working on re-learning these commands from his old Harmony so we can get a new code set up for you to test out. Additionally, I actually have another question. I have a customer with a PS3 who's having trouble turning the device off. He's using the Harmony adapter. It seems you need to press and hold the PS button, then hit enter twice, correct? I've had him set the PS button to repeating to allow the press and hold functionality but he's unable to power it off. Any tips for me?
To clarify, I know you were having trouble with this in a shutdown action, but I was wondering if you were able to use it in an activity layout that had the PS button and the Enter button. Sorry if I wasn't clear enough!
I have also been having problems with my Harmony PS3 adaptor but have
come up with a couple of work arounds by capturing some new control
signals from my old harmony remote and writing a basic script for the
PS3 off functionality.
I first tried using the 4153 codes but had no luck with these, i then
used 1403 codes and majority of the functions worked except for the PS
button (needed for turning the PS3 on and off) as well as the up, down,
left, right buttons that were essentially performing double clicks on
the PS3. To fix this I used my old harmony to capture new control
signals for the above commands.
To get the PS3 off working I had to create a script in my shutdown
action that replicates the functionality of the Harmony which is to hold
the PS button for 3 secs, press down, press up, press x, press x.
The code for the script is:
for count = 1, 20 do Scripting.SendCommand(517--[[Device: PS3]], 485--[[Command: PS]]) end
Understood, thanks! I was under the impression you had to press and hold the PS button and then hit enter twice, but either way if it works with scripting this is a great suggestion for a customer currently having trouble.
Thanks, Simon. I'm working on creating the codeset today now that my Harmony adapter has arrived. Actually doing the same thing you did with one of my Harmony remotes. I'll test the script out as well.
Just finishing-up the new codeset here, and i had a comment for you if you don't mind. Looking at your script, I notice that your pattern is PS hold, down, up, cross, cross. The Harmony PS Off macro seems to send PS hold, down, down, down, up, cross, cross. I believe it does this because whether you are in the PS menu, watching a movie, or playing a game, the menu that comes up after holding PS is different. The key, though, is that the option to turn the system off is always the second from the bottom. So, the Harmony sends enough downs that it is at the bottom (cannot go through the bottom back to the top) then goes up one. At this point, it assumes that the system off option is highlighted and sends cross to shutdown followed by cross to confirm.
I guess what I'm looking for is confirmation that you believe my assertion to be correct if you have the time to check it out.
Sorry to all interested parties for the delay on this. I've finished programming a RedEye to work properly with the PS3. Sarah is going to make the codeset available soon and let us know the number and how to download it in this thread as soon as it's ready. In the meantime, here are some details.
- Started with codeset 1404.
- Replaced the up, down, left, and right command IR codes to avoid the "double-clicking" issue.
- Added a new command, PS Hold, that is just the PS button being held down for 2 seconds.
- If you want to include the PS3 in an activity, you need the following launch and shutdown actions...
Launch - Send the PS command one time to turn the PS3 on.
Shutdown - Include your own variation of the following script to shut the PS3 off. I say your own variation because the IDs in your setup will be different. You can use the browser app to edit the script for a shutdown action, paste in the following code, and then use the Commands drop-down boxes to insert the proper IDs for your PS3 device and commands into the Scripting.SendCommand function calls. The script is mildly complex, but I've included lots of comments to explain what's happening and why each thing is required.
-- Start by sending the PS command to tell the PS3 that the RedEye is the -- current controller for the system. This is required if you've been -- using, say, one of the PS3 controllers to play a game. Scripting.SendCommand(57--[[Device: PS3]], 24--[[Command: PS]])
-- Wait a moment. Scripting.Wait(1000)
-- Send the PS Hold command. Scripting.SendCommand(57--[[Device: PS3]], 64--[[Command: PS Hold]])
-- Wait for a second to make sure the list of options is presented. Scripting.Wait(1000)
-- The list of options should now be on screen. -- The position of the "Turn Off the System" option will be different -- depending upon the status of the PS3. It may be the first option of 2 or -- the third option of 4. The key is that it's always the second-to-last -- option.
-- Send enough down commands to ensure that the last option is selected. Scripting.SendCommand(57--[[Device: PS3]], 39--[[Command: Down]]) Scripting.Wait(500) Scripting.SendCommand(57--[[Device: PS3]], 39--[[Command: Down]]) Scripting.Wait(500) Scripting.SendCommand(57--[[Device: PS3]], 39--[[Command: Down]]) Scripting.Wait(500)
-- Send one up command to get to the second-to-last option. Scripting.SendCommand(57--[[Device: PS3]], 49--[[Command: Up]]) Scripting.Wait(500)
-- Select the "Turn Off the System" option. Scripting.SendCommand(57--[[Device: PS3]], 30--[[Command: Cross]]) Scripting.Wait(500)
-- Confirm that you want to turn off the system. Scripting.SendCommand(57--[[Device: PS3]], 30--[[Command: Cross]])
So, first thanks to Craig for doing this. I thought we'd be able to upload the captured files to our database, but it seems we won't be able to do this because of other complications this would cause.
The good news is that our developers are currently working on some command repetition changes that should fix the problems with Up/Down/Left/Right. The bad news is that we won't be able to add in a "long press" version of that PS button.
I sincerely apologize for getting everyone's hopes up about the new code set. I can continue searching for a different code set online but we haven't found anything different thus far.
It's not too cumbersome for us to add in some different commands to that code set, so I'll grab a few more hex commands online for u/d/l/r at least and get those into the database for you all to try in the mean time. Thank you again for your patience.
Just a note that most of what I posted is still valid. I was unable to get the PS hold to work by using the regular PS command in a loop. Thus, the reason why I added the PS hold command. So, if you're replacing a Harmony (or another IR remote that can control the PS3) or can borrow one from a friend, then you can do exactly what I did. We'll try to get a PS Hold type command in our database as well if possible.
For now... For those willing to start over with their configuration, you can actually use the attached backup file and the web app to load your RedEye with a working PS3 device and basic activity. It contains the stuff I mentioned above. Then, you can add all the rest of your devices, activities, etc. on top of it. Sorry there's no way to merge my configuration with your configuration.
PLEASE NOTE THAT THIS BACKUP FILE IS FOR WI-FI and WI-FI 2 UNITS. IT SHOULD NOT BE USED ON A PRO.
Sometimes it takes a little while for the backup to fully load. Try deleting your application and re-installing to make sure that cached data is not the issue. Then you should have only one device, the PS3. Let us know if you have any more trouble.
Ive used the ps3 codeset backup to start over my configuration, and it worked just fine. After restoring the backup you'll have only one device and no activities. I've upgraded to 2.7.0 after the restore, though.
Oh, awesome. I already replied about this in an older thread (sorry about that), but I wanted to say I just applied this and it appears to completely fix the U/D/L/R issue. I can also confirm that the PS hold function works as expected. Only issue I've found is that the "R1" and "PS" functions seem to be swapped (PS doesn't do anything that I can see, and R1 behaves as a "short PS" command). Your shutdown script does appear to work quite well.
I'm continuing to test as much as I can; sony doesn't really seem to provide a decent test function for their controllers anywhere. Maybe I'll fire up a game that uses everything and see if it works as expected. Unfortunately, I can't really test beyond what the sixaxis does other than, "yep, it did a thing," as I don't have access to a "real" sony PS3 remote.
Hey, my Redeye odyssey continues - so apparently you had the issues with the Logitech adapter figured out *a year ago* but still haven't updated the code database? So in order to add my PS3 to my setup I have to blow away my entire carefully created config and start over from Craig's backup file, or I have to laboriously reproduce the steps he posted above. Which at least I can do as I have a real Harmony; people who don't apparently get one option.
Man, everywhere I turn with this device, it seems like you're needlessly making my life harder. Why couldn't you get the fixed codes into your database at _any time in the last year_?
We cannot upload the learned command for PS Hold because its format in our database would not be compatible with the RedEye mini. Trust me, if we could simply fix that issue, we would love to. It is just not an option. I added codes from every source I could find for months and they all had the same problem.
Thank you for the offer. The problem is that the learned command will crash the App for anyone using a RedEye mini, and the only option for them will be to re-install the App, which erases all of their configuration. That's the reason we haven't added it (and can't). We have a copy of the learned command, but it will cripple the configuration of any mini customer who downloads the code set. We have 1 product database, accessible by all RedEye devices in the product line (RedEye, RedEye Pro, and RedEye mini).
Leave a comment on mpg732's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic