Tyler Electric Posted May 12, 2008 Posted May 12, 2008 i am trying to access via a blackberry pearl phone. I can access my isy 26, log in and see the devices. I can select a device and see it's current status however after selecting a device I can't control it. When i try turning the device off or on i get a message saying "A communication failure has occurred. The server may be busy, please try again later. If the problem persist contact your service provider." I thought this may have been because a timeout so i increased the timeout value via telnet to 20000ms but it did not help. Quote
Michel Kohanim Posted May 12, 2008 Posted May 12, 2008 Hello Tyler Electric, Please read this post: http://forum.universal-devices.com/viewtopic.php?t=1264 at the end of which there's a solution. With kind regards, Michel i am trying to access via a blackberry pearl phone. I can access my isy 26, log in and see the devices. I can select a device and see it's current status however after selecting a device I can't control it. When i try turning the device off or on i get a message saying "A communication failure has occurred. The server may be busy, please try again later. If the problem persist contact your service provider." I thought this may have been because a timeout so i increased the timeout value via telnet to 20000ms but it did not help. Quote
Tyler Electric Posted May 12, 2008 Author Posted May 12, 2008 Hi Michel, As usual, thanks for your quick response. I had already read that post and had made the changes suggested by Dave. It looks like changing the setting "support Javascript" option to disable is what made my phone display the behavior listed in my first post. This morning I set the option to support javascript back to enable and now can switch my devices off and on again. FYI, this is a blackberry pearl phone running on a verizon network. best, Ron Quote
dpeterson4ca Posted May 12, 2008 Posted May 12, 2008 Ron, Interesting result, just the opposite of what worked for me and my 8320/Curve (T-Mobile). I verified again this morning enabling "Support JavaScript" caused comm error problems. Maybe service provider dependent? what a pain... Cheers! Dave Quote
Tyler Electric Posted May 12, 2008 Author Posted May 12, 2008 I guess it has to either be model specific or service provider specific. It certainly makes troubleshooting a pain. Thanks for your input. Ron Quote
Michel Kohanim Posted May 13, 2008 Posted May 13, 2008 Hi Ron, This is quite interesting ... in both cases - and if we have the user agent correct - we do not add any JS in the resulting HTML. We search for RIM to make sure if the device is BB- it is possible that the user agent for David's and your BB does not include RIM. With kind regards, Michel I guess it has to either be model specific or service provider specific. It certainly makes troubleshooting a pain. Thanks for your input. Ron Quote
dpeterson4ca Posted May 13, 2008 Posted May 13, 2008 Michel, I'm not familiar with the term "user agent". Is this something you can provide more detail on? where can I find this value? Thanks, Dave Quote
Michel Kohanim Posted May 13, 2008 Posted May 13, 2008 Hi Dave, user agent is a field in HTTP requests which identifies the type of device making the request. We use this field to figure out if the requester is a mobile device. With kind regards, Michel Michel, I'm not familiar with the term "user agent". Is this something you can provide more detail on? where can I find this value? Thanks, Dave Quote
dpeterson4ca Posted May 13, 2008 Posted May 13, 2008 Michel, Ah, understand now. However, if the HTTP request did not indicate to your code you were talking to a mobile device, you would probably send not only the headers "DEVICES, SCENES, PROGRAMS" but probably "ADMINISTRATIVE CONSOLE", which I do not get. Does this sound right? I'm sure there's a root cause here somewhere. Thanks for the continuing thought cycles... Cheers! Dave Quote
Michel Kohanim Posted May 13, 2008 Posted May 13, 2008 Dave, Precisely: If we "know" it's a mobile device, then we do NOT send: 1. Admin Console 2. Javascript used to close the browser when you close the Admin Console So, if you do NOT see the Admin Console in either case then the problem is NOT the user-agent since ISY has correctly identified your device as BB. Do you get the Admin Console link in both cases? With kind regards, Michel Michel, Ah, understand now. However, if the HTTP request did not indicate to your code you were talking to a mobile device, you would probably send not only the headers "DEVICES, SCENES, PROGRAMS" but probably "ADMINISTRATIVE CONSOLE", which I do not get. Does this sound right? I'm sure there's a root cause here somewhere. Thanks for the continuing thought cycles... Cheers! Dave Quote
dpeterson4ca Posted May 13, 2008 Posted May 13, 2008 Michel, I do not get the Admin console header in either case, which seems to indicate my BB is recognized as a mobile device. Which leaves the bigger question of why enable/disable JavaScript has anything to do with the problem... hmmm... Dave Quote
Michel Kohanim Posted May 13, 2008 Posted May 13, 2008 Dave, It is indeed quite perplexing ... I suspect it has to do with the gateway expecting something from ISY and not receiving it. With kind regards, Michel Michel, I do not get the Admin console header in either case, which seems to indicate my BB is recognized as a mobile device. Which leaves the bigger question of why enable/disable JavaScript has anything to do with the problem... hmmm... Dave Quote
dpeterson4ca Posted May 13, 2008 Posted May 13, 2008 Michel, More experimenting with BB browser configuration changes and I found another combination that makes a difference. The browser configuration item "Content Mode" has 3 choices, HTML only, WML only, WML & HTML. With Content Mode set at HTML only, disabling JavaScript allowed my BB to successfully communicate with the ISY. Enabled JavaScript caused comm errors. With Content Mode set at WML & HTML, the state of JavaScript did not matter, the communications were SUCCESSFUL whether enabled or disabled. Do you use any WML in your scripts?... still confusing, but I feel I am getting somewhere. Cheers! Dave Quote
Michel Kohanim Posted May 14, 2008 Posted May 14, 2008 Hi Dave, Thanks again for the update ... we do NOT use WML at all. I think this is all pointing to the gateway between ISY and your BB. I am unsure as to what we can do next since our BB emulator works fine (probably since it does not go through a gateway). Do you have any suggestions? With kind regards, Michel Michel, More experimenting with BB browser configuration changes and I found another combination that makes a difference. The browser configuration item "Content Mode" has 3 choices, HTML only, WML only, WML & HTML. With Content Mode set at HTML only, disabling JavaScript allowed my BB to successfully communicate with the ISY. Enabled JavaScript caused comm errors. With Content Mode set at WML & HTML, the state of JavaScript did not matter, the communications were SUCCESSFUL whether enabled or disabled. Do you use any WML in your scripts?... still confusing, but I feel I am getting somewhere. Cheers! Dave Quote
dpeterson4ca Posted May 14, 2008 Posted May 14, 2008 Michel, Unfortunately, no further suggestions at this time, but I will continue to snoop around and post if I discover any more detail. Thanks so much for you support and keep up the great work! I'm just having a BLAST with my ISY. Cheers! Dave Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.