Thanks, I guess it could be? I do have the Remote, Extender ect... All fixed IP's.

I checked and all WIFI around me is secure as well, should not be able to connect.

The foreign WIFI's may be secure, but that does not always prohibit a 'dead connection'. I haven't tried this with a pronto, but I have seen many an occassion where a WIFI equipped laptop shows a wireless connection to a somewhat protected AP but can't do anything. Basically it is letting you in but most probably is refusing to assign an IP address based on router security or potentially there are MAC or Network filters setup to stop it going any further.

Also have you checked your router/AP to see if it is blocking any ports on the internal or local network?

The other thing I can think of is if your SSID is hidden or if you have a duplicate SSID from another AP in range of the Pronto. A Hidden SSID on some routers can make the pronto go bucky. Rough translation it's got no idea where to go!

I think the one thing being missed which has gotten us off track a bit is this statement I made earlier

" The remote connected and showed full bars, no error codes or command fails. All seemed good. After the third time of picking up the remote to Fast Forward the show I was watching it connected and had 1 bar of signal. The commands still worked fine.
I then picked it up 3 more times each time it connected with only 1 bar, yet I didn't have any problems. I then ran the power off macro, worked flawless."

To get full bars back I had to cycle power to the remote.

The Remote is still connecting to my wireless network and still working but only shows 1 bar until I reboot it. Indicating it might be connecting to the AP. I almost have it ruled out, based on the signal is real weak down there, I can't see how or why it would reconnect to that AP over the Router which is much closer giving a real strong signal to that room. I plan on disconnecting the AP and seeing if it still happens or not. I will update soon.

Thanks for you input. Still much appreciated

One thing I have done for years is to make sure that all APs and the router are on the same channel. I work a lot in 10k to 15k plus square foot homes, and have always used this approach.

There are a lot of people that say that the APs and router should all be on different channels, as running them on the same channel causes interference between the broadcasts.

To me, it seems that clients (laptops, other WiFi devices) that have WiFi roaming capability transition more smoothly on same-channel configurations.

Power output and QOS settings are also important. Ideally, I have learned that all settings should basically be "cloned" between devices. I have never had an issue with Pronto when configuring systems like this.

Thanks for the advice. I will try this for sure.

Update: After a couple of weeks of tests, trial and error, talking with the guys at Phillips Pronto, they took my remote in and replaced the board. They felt the wifi chip was acting up. I should have it back this Friday.
HOPE!@! that fixes the issue.

Just wanted to Update. I got the board in the remote replaced, I do feel the remote connects much better now. This issue did not go away with just that.
I kept trying things and found the problem. In my POWER ON macro one of the commands is to Power On (RS232 command) a Yamaha RX-V3800 Receiver. I decided to remove this command. The macro worked, then connected an IR cable from the Serial Extender to a direct IR input port on the receiver. I added in the IR Power command and have used the remote for a couple of weeks. The macro
works perfect every time. I have no idea why the RS232 command was causing the issue and forcing a reconnect for the remote but it seems it was the fault. I have no problems controlling the Receiver with RS232, only during the Power On
macro.

Anyway all is working.

Thanks