check all the items on here first [Link: remotecentral.com]

I have been waiting on this firmware release since they ruined the pronto with the last firmware release. Unfortunately, things got worse instead of better. Ever since Philips have added WPA support the whole thing has been a crock. The "experts" on this forum keep asking for the same information about wireless access point versions and firmware versions, but the simple fact is that Philips have wrecked the Pronto, and in the process have lost a loyal customer in me. I'm very frustrated with them. I have one last roll of the dice which is to try the open source firmware for the WAP54G. If that doesn't fix it, My TSU9600 and RFX9400 are going in the bin. I'll be replacing them with a Harmony remote and a Squeezebox remote. I'm just thoroughly fed up that my Pronto that had worked perfectly for a year and a half, stopped working when the firmware last December was released and hasn't worked since.

It is absolutely clear that Philips really don't care about customers, otherwise they would take this problem seriously.

Incidentally, at the moment I'm running a totally insecure wireless network, and I still get a stack of problems. I have all my other wireless devices on another wireless access point (on a different channel). The channel that has least interference (confirmed with a scanner) is reserved for the Pronto and NO other traffic runs over that access point (or ethernet segment for that matter) and still, well in excess of 50% of transmissions are lost between the TSU9600 and RFX9400. I have absolutely no problems with the stack of devices that are on the other wireless segment. That includes a squeezebox radio (perfectly happy streaming MP3s), 4 squeezebox remotes, a couple of laptops and a wireless printer. There is no problem with wireless reception in my apartment, it is just the complete crock TSU9600/RFX9400 that can't communicate across an empty channel and an empty ethernet segment.

Philips YOU SUCK.

If anyone else is thinking of getting a Philips Pronto and is reading this thread. Take my advice - spend your money somewhere else. Philips Pronto were once the best programmable remote on the market, they are now useless. Spend your money on something that works.

Signed,

A highly frustrated, ex Philips Customer, and ex Philips Installer.

Sorry you feel like this , but looking through the thread , you still have not given all the information yet, why not start your own thread , and try to resolve the problem , or go to your distributor to see if they can help?

I've given all my details in private threads to other people on the forum, I also gave all my details on a different thread on this forum - I came onto this particular thread just because my problems seem to be the same as other peoples, and I wanted to consolidate. Basically I have a fully patched TSU9600 and RFX9400 (latest firmware on both - which SUCKS). I have a latest firmware WAP54G. The only active devices on the network are the TSU9600, RFX9400, a Netgear ReadyNAS running Squeezebox, the WAP54G and a Linksys switch. The WAP54G is running on a channel with no interference. I was running encryption, but I'm not running any encryption (or even MAC filtering) at the moment. There is no Internet connection or anything else on this ethernet segment. Everything is wired except for the TSU9600. I've tried running everything with static IP, I've switched the TSU9600 and RFX9400 to DHCP (served by the NAS). All IP addresses are without conflict.

Let me be absolutely clear, I know how to configure networks - I've been doing it professionally since the mid 90s. I know how to program as well - that is my main profession. This problem is NOT going to get solved by someone looking at my configuration and telling me something is incorrectly configured - I've checked everything so many times, and tried so many different configurations. This problem will ONLY get solved by Philips releasing a bug free firmware for these devices.

I've been watching this thread with interest since it started. I had my own thread reporting these problems, but it didn't seem to gain traction. It is clear with this thread though that loads of other people have the same problem. All the "experts" on the forum blame the wireless configuration, or wireless encryption, or something similar. But the fact remains that this many people wouldn't report a problem unless a problem was there. The common denominator between everyone's experience on this thread is that they have upgraded to the latest (2) firmwares. Philips still SUCK, and for me, having used Prontos of various sorts since 2001 I am now at the end of my tether. This is very expensive hardware, and it just doesn't work any more. I want to make one more thing clear, the only thing I think would fix these problems is rolling back to an earlier firmware, but my one attempt at doing this ended up bricking an RFX9400 which I then had to replace. These firmwares are super flaky, and the firmware upload system is super flaky. I do wish Philips would take these problems seriously, but I haven't even received replies to emails I've sent to them.

I've had a similar experience with various wireless routers and access points. The Pronto does seem very WAP sensitive!? I'm now only using LevelOne and/or Pakedge and always set to 'b/g' only.

I've also upgraded and downgraded the firmware on various TSU's without a problem, so I think may have just been unlucky..

Interesting. With the new firmware I don't get any wifi problems, wether i configure it as static or DHCP.

Maybe the gear people that still have problems can be correlated in some ways. Let's say like same wifi IC manufacturer etc. Can any of you that have such problems do some tests with a network analysis tool (like wireshark), and actually see there the communication breaks? Would be helpful.

I have the PadOne working here now and almost everything is fine. I'm just getting this "Command Failed" error with the STOP button of the player. Any other command is working just fine, except for the STOP.

FYI, the "Command Failed" error here is with regard to RF extenders and not PadOne. You may want to use your PadOne thread already opened or start a new thread.

I don't have any ideas as to why you are getting Command Failed on a Stop. Maybe LowPro or others who use PadOne might be able to provide some insight.

Thank you, Lyndel.

I'll take your advice and make a new thread.

So, finally, I'm on day 3 of a stable configuration. In desperation I changed the firmware of my wireless access point to one of the alternatives - specifically DD-WRT. So the problem looks like a conflict between the firmware of the Pronto and the firmware of the WAP54G. The problems all started when I installed the Dec 09 firmware on the Pronto which was the firmware that started supporting WPA, so it wouldn't surprise me if the incompatibility came in with that change.

Since flashing the access point to DD-WRT I've had no command failed errors - in fact last night I updated the wireless network to start using WPA encryption again without any problems.

It is supremely annoying that a device as expensive as this should only be compatible with certain wireless access points, and it should probably be noted that the WAP54G isn't one of them.

Thanks to everyone who helped out.

I am also having the command failure error's, been for a while now. I have tried static, DHCP, yada yada. I have to use wireless and not stand alone as I connect my TSU 9600 to HomeSeer. The extender I have is the RFX9400.

I noticed that you upgraded your router to DD-WRT, well that is what I am using and I am curious as to what version and what your wireless settings are. I have to use WEP to connect to some of my older equip btw.

Thanks,

Matt

I'm using the newest compatible release of DD-WRT with my WAP54G. With my WAP54G it is a micro build 11296M. I've actually found with further testing that the TSU9600/RFX9400 setup is very picky about what wireless access point it uses. For example, I've had much better stability with an older linksys router (running DDWRT) than I have with the WAP54G. Basically the wireless stack on the philips devices is dreadful and just plainly doesn't work with a bunch of devices. If the protocol that the TSU9600 uses to talk to the RFX9400 was more forgiving, they could get away with it, unfortunately, it isn't, so one error and the whole lot stops working with the command failed errors that we see. My recommendation is probably to get a new wireless access point, but get one that the professional installers on these forums recommend.

I finally set mine on fixed G and set the RFX9400 to DHCP and it seems to have settled down. I get the error some times when I pick it for the first time that day, but otherwise it seems much more stable now.

What a croc that one has to be DHCP. So counter intuitive. I have been running both static for years....Go figure.

Just curious.

What was the fixed IP address of the RFX9400 and was this address in the DHCP range of the router? Is there a chance you were having an IP address conflict with another device on the network?

I don't have all the settings to hand but I've used the WAP54G for a couple of years, sometimes on WPA, and it's been flawless. I'm not with it now so can't check the software build.
Strange that you should see something so different.