Forum Replies Created
-
Posts
-
@salbahra wrote:
@donc wrote:
BTW, I occassionally reach the TP Link instead of OS when invoking OS. Is this normal? Or do I have something set up incorrectly?
I wouldn’t say that is normal however if they are sharing the same IP (if it is routing instead of switching) and you have port 80 forwarded I suppose it is possible there is a conflict between the port forward and the HTTP server on the device.
Maybe I should ask to clarify. Are you saying when you open the browser to http://192.168.2.120 sometimes you see a TP link configuration page? And other times you see the web interface?
Yes, I do occassionally see a TP link configuration page.
@salbahra wrote:
@donc wrote:
I’m somewhat reluctant to install Chrome or Firefox as this computer is part of my business network, and our IT person prefers we all stick with the same browser as it’s easier for him to maintain and troubleshoot problems.
I just fixed this for IE9. Please try now.
You might have to refresh a few times to update the cache.
This was related to IE9 specifically. I have code in place for ajax transport methods but somehow jQuery didn’t detect it resulting in an error, “No Transport” from jQuery. Should be fixed now.
Had to close then reopen IE9 plus delete browsing history to get it to work, but it DID WORK! 😀 Thank you!
BTW, I occassionally reach the TP Link instead of OS when invoking OS. Is this normal? Or do I have something set up incorrectly?
@ray wrote:
@donc, my suggestion is to try a different browser (Chrome or Firefox would be my recommendation). At least this will help us find out if it’s a browser related issue. I can’t test IE9 right now because my XP says it can’t upgrade to IE9 and my Win8 says it can’t downgrade to IE9…
Thanks all.
I’m somewhat reluctant to install Chrome or Firefox as this computer is part of my business network, and our IT person prefers we all stick with the same browser as it’s easier for him to maintain and troubleshoot problems. I’ll contact him and discuss installing Chrome.
BTW, take a look at the update to my previous post regarding being able to communicate with OS via my home automation system. Considering that, It seems to me that it’s probably an issue related to IE9.
@ray wrote:
@donc: can you try the following:
http://your_device_ip/su
and put in the default password opendoor, then click on submit. Does it report ‘script url saved’, or does it throw out an Unauthorized error? If it reports url saved, that means the password is accepted and it’s likely a UI or browser related issue; if you see ‘Unauthorized’, that probably means the EEPROM reset was not successful, please redo the EEPROM reset (make sure you wait until the ‘RESETTING EEPROM’ message on the LCD is done).I did the following:
1. Reset EEPROM.
2. Changed IP to 192.168.2.120 vi B3 “Set Options”
3. Opened new browser page (IE9)
4. Set URL to 192.168.2.120/su
5. Browser returned with “Rayshobby.net” page asking for password
6. Entered “opendoor” password; browser returned dialog “Script url saved”
7. Clicked on OK button; browser page changed to “new” login/password page
8. Entered “opendoor” password; yielded “INVALID PASSWORD”Note: Sometimes after step 4 the browser page is the page that says password incorrect and goes on to ask about caps locked, etc. This is the same page that would sometimes show up in the old UI when changing from one mode to another or going to or returning from Options page. This was inconsistent on the old UI — didn’t always happen, but after a page refresh all would start working again.
UPDATE: My Home Automation System (Mi Casa Verde Vera3) is able to successfully communicate with OS using opendoor pw. I can change pw in Vera to a bogus pw and it doesn’t work. Change it back and it does work. Does this point to a browser/UI problem?
@salbahra wrote:
@donc wrote:
Sorry, no luck. Tried resetting EEPROM via B3 options and using “opendoor” as PW. No success. Any ideas?
Okay I think I know part of the problem. Let me take a look at this tonight (flying back home soon) and I will get back to you with a possible solution to this.
I understand how inconvenient this can be and appreciate your patience as we try to resolve this.
Thanks Salbahra.
@salbahra wrote:
Sorry to hear about the problem your having.
When you upgrade your firmware, the settings are cleared and the password defaults back to opendoor. The ignore password field is also reset back to default (unchecked).
This is likely your problem.
Sorry, no luck. Tried resetting EEPROM via B3 options and using “opendoor” as PW. No success. Any ideas?
Overall setup: TP Link Wireless set to Client Mode, static IP. I get to the password screen but no password I have EVER used works, nor does “opendoor.”
