Jump to content

Device comm problem with BB mobile access to ISY-26


dpeterson4ca

Recommended Posts

Discovered a very strange behavior when accessing my ISY-26 (f-w 2.6.4) from my BB today (8230/TMobile-Edge).

 

Logged into the ISY-26 successfully, got the HTML screen and selected DEVICES. Got my device list and selected a controller. Controller came up and I set the device ON. Command sent and verified successfully. About 30s later, I sent the OFF command from the same screen and the response to the request "timed out" with "Command error occurred with the seclected Mobile Data service..." Tried again, same timeout error.

 

At this point, I selected DEVICES and the command successfully went thru and displayed my devices screen with updated status.

 

From here, I did the same thing again with another device (selected device, tried to turn on-then-off) and received the same timeout message after the first command was successfully executed. Doesn't matter if you send ON first or OFF then ON, same timeout issue on the 2nd send.

 

Going back to the DEVICES screen repeatedly allows you to select a device, send one command (at least ON or OFF), but then it will lock up to any further device commands before returning to the DEVICES screen.

 

This seems to be a bug... or my BB is behaving badly...

 

Dave

Link to comment

Hi Dave,

 

Would you be kind enough to try the same with a scene?

 

Thanks and with kind regards,

Michel

 

Discovered a very strange behavior when accessing my ISY-26 (f-w 2.6.4) from my BB today (8230/TMobile-Edge).

 

Logged into the ISY-26 successfully, got the HTML screen and selected DEVICES. Got my device list and selected a controller. Controller came up and I set the device ON. Command sent and verified successfully. About 30s later, I sent the OFF command from the same screen and the response to the request "timed out" with "Command error occurred with the seclected Mobile Data service..." Tried again, same timeout error.

 

At this point, I selected DEVICES and the command successfully went thru and displayed my devices screen with updated status.

 

From here, I did the same thing again with another device (selected device, tried to turn on-then-off) and received the same timeout message after the first command was successfully executed. Doesn't matter if you send ON first or OFF then ON, same timeout issue on the 2nd send.

 

Going back to the DEVICES screen repeatedly allows you to select a device, send one command (at least ON or OFF), but then it will lock up to any further device commands before returning to the DEVICES screen.

 

This seems to be a bug... or my BB is behaving badly...

 

Dave

Link to comment

Michel,

 

Tried sending some commands after selecting SCENES and every command I tried with several scenes failed with the "comm timeout". No scene command was successful. I verified the DEVICES has the same initial problem before I started during one session, then closed the browser, went directly to SCENES, tried sending commands again and saw same timeouts.

 

Did find an interesting result after playing around with the DEVICES issue mentioned above. If, after you have sent the 1st device command successfully, you select "Refresh" on that page, the 2nd command works! Turns out the command sequence on any device page "cmd-Refresh-cmd-Refresh-cmd-..." always works, but the 2nd command of 2 sent back-to-back never works.

 

BTW, this is the first time I've spent any significant time with the mobile access, as I initially had trouble getting my BB to work with my https site. It's working now and I'm seeing these issues.

 

 

Cheers!

 

Dave

Link to comment

Hi Dave,

 

Please note that ISY puts a one second delay between your request and when ISY actually refreshes your BB with the current status. So, if you keep trying on/off within a second, then you will make all the subsequent attempts timeout since ISY locks you out.

 

The second issue might be that possibly ISY is too sensitive for your BB gateway. As such, you can adjust the HTTPS timeout value by issuing CWT in the shell (telnet to your ISY, login, and then issue CWT). Please note that adjusting this to a very high value might have a negative impact since ISY will wait the "timeout" value to get all the information from your gateway (if it does not sense the end of transmission).

 

With kind regards,

Michel

 

 

Michel,

 

Tried sending some commands after selecting SCENES and every command I tried with several scenes failed with the "comm timeout". No scene command was successful. I verified the DEVICES has the same initial problem before I started during one session, then closed the browser, went directly to SCENES, tried sending commands again and saw same timeouts.

 

Did find an interesting result after playing around with the DEVICES issue mentioned above. If, after you have sent the 1st device command successfully, you select "Refresh" on that page, the 2nd command works! Turns out the command sequence on any device page "cmd-Refresh-cmd-Refresh-cmd-..." always works, but the 2nd command of 2 sent back-to-back never works.

 

BTW, this is the first time I've spent any significant time with the mobile access, as I initially had trouble getting my BB to work with my https site. It's working now and I'm seeing these issues.

 

 

Cheers!

 

Dave

Link to comment

Michel,

 

I'm not quite sure I understand your response, but let me clarify my observations/actions and follow-up with a question.

 

Time between sending commands is well over 30s. Fact is the BB browser process to send the command and receive a response ("requesting-loading" cycle) takes 7-15s typically (this is EDGE not 3G).

 

Now with that being said, could this timing be what you are referencing to as the "HTTPS" timeout? if the BB takes a long time to send a command...

 

Finally, the complete inop of the Scene commands has me troubled. Not sure why there would be a difference between Device commands and Scene commands from the HTML interface... I could actually deal with the "cmd-refresh-cmd" cycle, but I really would like the Scene commands to work.

 

Appreciate any additional insight you can offer here. Thanks!

 

Dave

Link to comment

Dave,

 

This is indeed quite strange. Please do be kind enough to increase your HTTPS timeout in the shell (CWT) 50% and let me know the outcome.

 

Thanks and with kind regards,

Michel

 

 

Michel,

 

I'm not quite sure I understand your response, but let me clarify my observations/actions and follow-up with a question.

 

Time between sending commands is well over 30s. Fact is the BB browser process to send the command and receive a response ("requesting-loading" cycle) takes 7-15s typically (this is EDGE not 3G).

 

Now with that being said, could this timing be what you are referencing to as the "HTTPS" timeout? if the BB takes a long time to send a command...

 

Finally, the complete inop of the Scene commands has me troubled. Not sure why there would be a difference between Device commands and Scene commands from the HTML interface... I could actually deal with the "cmd-refresh-cmd" cycle, but I really would like the Scene commands to work.

 

Appreciate any additional insight you can offer here. Thanks!

 

Dave

Link to comment

Michel,

 

2x the CWT timeout (20Kms HTTPS/2Kms HTTP) and the results are exactly the same. Interesting the BB browser error message does not take 20s to appear, it happens in 5-7s. Maybe the key is in the error text itself:

 

"A communication failure occurred with the selected Mobile Data Service. The server may be busy, please try again later. If the problem persists, contact your administrator. (OK)"

 

This actually may not be a timeout message, but certainly a comm error. Retries of the command are consistently unsuccessful. The result however is very consistent when going through these steps and only happens when tyring to execute a command.

 

Patterns: DEVICES>Controller>1st cmd>2nd cmd [fail]; SCENES>Scene>cmd [fail].

 

I have not seen this error with any other non-command selection. PROGRAMS seems to work fine. Are there any other BB users who have seen these issues?

 

Dave

Link to comment

Dave,

 

Thanks so very much for the update. This is indeed very strange. I would really like to know if anyone else is experiencing these issues with BB.

 

With kind regards,

Michel

 

Michel,

 

2x the CWT timeout (20Kms HTTPS/2Kms HTTP) and the results are exactly the same. Interesting the BB browser error message does not take 20s to appear, it happens in 5-7s. Maybe the key is in the error text itself:

 

"A communication failure occurred with the selected Mobile Data Service. The server may be busy, please try again later. If the problem persists, contact your administrator. (OK)"

 

This actually may not be a timeout message, but certainly a comm error. Retries of the command are consistently unsuccessful. The result however is very consistent when going through these steps and only happens when tyring to execute a command.

 

Patterns: DEVICES>Controller>1st cmd>2nd cmd [fail]; SCENES>Scene>cmd [fail].

 

I have not seen this error with any other non-command selection. PROGRAMS seems to work fine. Are there any other BB users who have seen these issues?

 

Dave

Link to comment

Michel,

 

Thanks for your attention to these issues... I'll keep plugging away to see if I can find a configuration change or workaround which may improve my results.

 

Meanwhile maybe a BB user will come forward with another view...

 

Cheers!

 

Dave

Link to comment

Dave,

 

My pleasure! Support for mobile devices is our top most priority.

 

With kind regards,

Michel

 

Michel,

 

Thanks for your attention to these issues... I'll keep plugging away to see if I can find a configuration change or workaround which may improve my results.

 

Meanwhile maybe a BB user will come forward with another view...

 

Cheers!

 

Dave

Link to comment

This is weird, as I am getting the same message today, but with a BB on ATT.

 

"A communication failure occurred with the selected Mobile Data Service. The server may be busy, please try again later. If the problem persists, contact your administrator.

 

Michael

Link to comment

Hi Michael,

 

Do get this consistently and in the same manner as Dave is experiencing?

 

With kind regards,

Michel

 

This is weird, as I am getting the same message today, but with a BB on ATT.

 

"A communication failure occurred with the selected Mobile Data Service. The server may be busy, please try again later. If the problem persists, contact your administrator.

 

Michael

Link to comment

Yes, it was working fine on Tuesday, then Wednesday I started getting the same error message, got in once, got a time out message, and then back to the other messages.

 

The only thing that changed from Tuesday to Wednesday is the firmware update to v4.21.79 on the blackberry.

 

I checked and I can get into the ISY from a ATT tilt, so it is something with the BB.

 

Dave did you change anything on your blackberry on Wednesday?

 

Michael

Link to comment

Michael, to answer your question, no I did not change anything on my BB. However, Wednesday was the first time I used the BB with my ISY-26. I had weeks of problems trying to get HTTPS to work, but finally got those issues resolved.

 

Dave

Link to comment

Michael,

 

It would be helpful to know exactly when you are seeing these errors occur. For example, is it after you access the HTTPS://ISY, select DEVICES/SCENES/PROGRAMS, send your username/password, select a controller/scene, send a command, send another command immediately after the 1st... I have only seen the comm error at very specific steps in this process (as mentioned above). I am curious whether you are seeing them at the exact same time or are your errors happening at different points.

 

Thanks,

 

Dave

Link to comment

Good news!

 

After some experimention I have discovered a BB Browser Configuration setting which eliminates the "comm errors" I experienced above and now all mobile commands and HTML functions execute successfully between my 8320 and ISY-26.

 

Changing the BB Browser configuration of "Support JavaScript" to DISABLE (not checked) allows all actions to work. Enabling and disabling this configuration verified this result. (...don't ask why, I don't have a clue...)

 

Can't imagine this is unique to me and hope this can help out other BB users.

 

Cheers! I'm a happy man today as I am finally "mobile"...

 

Dave

Link to comment

Michael,

 

Here is my BB browser config:

 

Browser Configuration

 

Browser: BlackBerry Browser

Support JavaScript DISABLED

Prompt to enable JavaScript ENABLED

Support HTML Tables ENABLED

Use Foreground and Background Colors ENABLED

Use Background Images ENABLED

Support Embedded Media ENABLED

Support Style Sheets ENABLED

Style Sheets Media Type: Screen

Show images: On WML & HTML pages

Emulation mode: Microsoft IE

Content mode: HTML only

Start page: Bookmarks Page

Home page address: http://mobile.blackberry.com

 

General Properties

 

Default Browser: BlackBerry Browser

Enable JavScript Location support ENABLED

Prompt before:

Closing browser on escape DISABLED

Closing modified pages ENABLED

Running WML scripts DISABLED

 

Hope this helps.

 

Dave

Link to comment

Dave,

 

Thanks so very much for sharing. I really do appreciate it.

 

With kind regards,

Michel

 

Good news!

 

After some experimention I have discovered a BB Browser Configuration setting which eliminates the "comm errors" I experienced above and now all mobile commands and HTML functions execute successfully between my 8320 and ISY-26.

 

Changing the BB Browser configuration of "Support JavaScript" to DISABLE (not checked) allows all actions to work. Enabling and disabling this configuration verified this result. (...don't ask why, I don't have a clue...)

 

Can't imagine this is unique to me and hope this can help out other BB users.

 

Cheers! I'm a happy man today as I am finally "mobile"...

 

Dave

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...