I've been suffering with the same problem ever since the new firmware release. I reported it on a separate thread. But I do have a very interesting result. If I leave my pronto TSU9600 in the docking cradle I get absolutely no command failed messages. I've even cleared the diagnostic log of all the 450/405 messages and then used it for 24 hours - nothing new in the logs whatsoever. Up to now in trying to resolve the problem I've tried loads of things. Changing wireless security between none (just MAC security), WEP128, WPA; changing wireless channels (I already run the pronto on a standalone LAN connected to only the RFX9400 and a second ethernet port on my NAS for squeezeserver access); and I even tried rolling back the firmware on my devices (the main achievement being that I managed to brick my RFX9400 and had to replace it). None of these things have had any impact on the command failed messages. I haven't been able to run a DHCP server on my standalone pronto LAN, so I haven't been able to confirm/deny that that resolves the problem; but leaving the panel in the docking cradle seems to completely resolve things. I'm therefore left wondering whether this is actually a power management issue in the new wireless stack that came with the latest firmware update?

Can anyone else having the same problem try leaving their panel in the dock?

The pronto does not log off the wifi when in the dock (depending on what you set in the timeout settings in PEP). Undocked, it will log off when the display dims. Thats the big difference.

I leave my 9800s in the docking stations virtually all the time and I have experienced the "command failed" and "extender not found" issue. Maybe less so than others seem to be reporting. I have fixed ips for both TSU and RFXs. I also have specified channels at high and low end of 2.4 GHz range. I think that things got better when I specified channels but I've been away for a few days and haven't had a chance to use the TSUs too much so I am not sure how much it has helped.

I've been off using wifi some some years, but thought I'd give it a go since moving to a new house...

Terrible results. Tried all the suggestions in this thread (fixed ip/dhcp), wpa, but getting the same problem as others...

Really unusable if you ask me, which is a shame, because I purchased prontosqueeze and haven't been able to use it for years (along with any other ifi module - weather etc).

Any progress, or is this the wrong thread?

As far as I can tell there has been no progress. I keep checking the pronto.philips.com website and there has been no update I can find there. I have tried twice emailing support via the pronto website and they have yet to answer me. I have tried pretty much everything in this thread - including running both RFX9400 and TSU9600 on DHCP. There is no other traffic on this segment of the LAN. I only have 4 devices running on a standalone wireless network. The wireless access point. A NAS with squeezeserver running (the NAS has 2 NICs so I have one port dedicated to the TSU9600). The TSU9600 and the RFX9400. The RFX9400 is wired and the TSU is the only thing that talks wireless on this segment. No-one else in the vicinity is using this wireless channel, and it is the best wireless channel for minimal interference (plus I have tried other channels).

If I leave the TSU9600 in the cradle I get a lot less errors (which is how I use it now). I have tried rolling back the firmware (I only get the errors since the new firmware last December) unfortunately, all that did was brick my RFX9400 and forced me to replace it.

I'm get desperate - I'm on the verge of throwing out the whole Pronto setup and getting the Harmony remotes instead. At least they work, even if they don't have the wireless to allow me to use the SqueezeServer properly. I could basically use a Harmony remote and one of Logitech's custom wifi remotes for the SqueezeServer.

If anyone has any further ideas, or any idea when Philips are actually going to pull their finger and and fix this problem which has made thousands of dollars worth of equipment worthless because of a bad update, please let me know. It is getting rather depressing.

daveand send me a PM ..

From what i understand WEP will always be a faster authentication protocol than WPA and better suited to the likes of the current Pronto Range.

The packets of data transmitted over WEP contain a constant Initialization Vector that never changes. I.E when the panel wakes up it carrys on transmitting data in the same way it was before it went to sleep.

WPA on the other hand has a varied Initialization Vector that changes as it transmits data, so the Pronto goes to sleep and when it wakes up it has to scan through the last data it was sending and work out what the next vector is before it can start sending commands

this Vector is also what enables your devices to still operate with hidden ssids its kind of like two pairs of flash lights talking in morse code, only one of the pairs decided it would be fun if they used the enigma code first. :-)

dont know if thats of any use to anyone?

I also get the "command failed" sometimes. Nothing that I can duplicate. It just seems to happen now and again... SJ

Guys, I have several TSU9600 units in the field, most using RFX9400 without many/any issues related to communication.

I have however started playing with RS232 and as such, had to get the RFX9600.

Two questions (I'll post second one separately);
As inefficient as it may sound, can I have my TSU9600 communicate to RFX9400 which would then forward the request to RFX9600?

My thinking is that if I don't have issues with the Pronto Channel communications, but do have issues with WIFI like so many others reported, why not use the rock solid RFX9400 link and be done with that.

For the lucky ones that don't have issues with WIFI communications:

For a simple single TSU9600 & RFX9600 setup, with really minimal ProntoScript in the mix (HAI module only)...

What router/AP do you use and what settings do you utilize?



I'm getting tired of "Command Failed" issues.
My clients are getting tired. Few of them that didn't even want to discuss $300+ AP solutions, are now asking me to put something, anything, that in a word, just works.

This shouldn't be that difficult.
I'm in a rural area and so are some of my clients that are having connection issues, with no other WiFi signals in range.

I, like others have made sure that my controller/extender/router/AP were all up to date. I played with WEP, WAP, no-security, different timeouts, etc. I haven't tried with unit in the base, cause it's a wireless remote that won't be used from the base.

I can stand 5 or 50 feet away from my AP unit and get the same results. 50-80% of the time all works well. It's the other % that is my issue, and what my clients remember.

I'm at a client's house right now, and I was just issuing a simple 4 step macro: TV On (IR), DirecTV On (WiFi), Matrix source select (WiFi).
It all worked well 4 times, for me.
Turned the components off; called a client to show how it works.
Client stood in the same spot (8-10' from D-Link DIR-625 router) and that %$#^&!% thing did work (command failed, and extender didn't receive the signal). Yes the TV turned on (IR).

I know the Pronto dropped WiFi when the screen went dark. But my client doesn't care. They want a working system and they deserve it.

I called Pronto tech support, they were no help, I mean none at all.
Guy started talking about lighting conditions and version of my PEP. Nothing that had any relevance to the issue at hand. He's suppose to email his eng dept., we'll see if I ever hear from them.


Please help me! Tell me what to get and what to set it to, and I will!
If it takes a $600+ Rokus unit, than so be it.

Mario

No, such behavior is not supported.

You did not mention what firmware you are running. Have you contacted belgium (see ProntoTeam user account here for email address) and requested the 'beta' firmware to see if it might help solve your problem? Last I heard, the beta version was 7.2.23 for the remote. Not sure if there's a beta version for RFX9600.

I asked for the beta over 2 months ago.  I explained to them that I have 2 TSU9600's & 2 RFX9600's w/ multiple brands of access points and would be happy to do testing. 

After two weeks, I finally received this response:
Thank you for contacting the Prontoteam.
We would like to apologize for the inconvenience and we can assure you that these issues are currently looked into with a high priority.
Chances are likely that we will release a new firmware addressing these issues shortly.

What's their definition of shortly?  They need to pick up the pace and do something about this problem.  It's more than just a couple of people that are having this issue. 

Lyndel, how are you buddy?
You're right. While I stated that all devices were up to date, I should have listed the actual firmware. I'm not on that site right now, but will give the firmwares of my house's setup when I get back.
I did not know there was a beta firmware.
I did contact stateside tech support and they were worthless.
I was not offered a beta to see if it would address my issue.

Mario

Mario,

You need to email Belgium directly.