- This topic is empty.
July 14, 2013 at 8:26 pm #22532
I just tested both the OSPi Interval program and the Mobile WebApp with some strange station names. It seems Ray allows the use of both the
and the characters in the station names. Using either of these characters causes a bit of a problem in both your applications. It ranges from missing characters to names jumping from one station to the next.
The problem is that the mentioned characters are used as delimeters. My suggestion is to limit the use of these as they cause issues even in the native OS Web Interface.
IngoJuly 14, 2013 at 8:41 pm #24814
These characters work fine in the microcontroller-based OpenSprinkler. Just tested and it’s displayed correctly. I recall including code that converts special characters with their HTML code back and forth. For example, ‘space’ will be stored as ‘%20’ any so on. It’s possible that the OSPi’s interval program skipped this. I will do some testing later to check.July 14, 2013 at 8:47 pm #24815
Unfortunately not on my IE 10 or Chrome browsers. I tested both OS and OSPI. See below for OS results:July 14, 2013 at 9:45 pm #24817
(Uncaught syntax error…)
the abc,`def’ string has a apostrophe at the end itself, so that will cause ambiguity with the apostrophe used to define a string.
So yes, for now try to avoid using single quotation mark.July 14, 2013 at 9:54 pm #24818
By the way, if the station name is messed up and you need to reset the station name without resetting the controller, you can use direct HTTP command, for example:
will reset the first station name to abc.August 5, 2013 at 7:28 pm #24819
Just to comment on the current state of this issue.
Dan pushed an update to the interval program to support unicode characters, commas, etc. Afterwards, I pushed an update for my mobile app to handle all of the same issues. Therefore, this issue by and large should be solved.November 21, 2013 at 4:31 am #24820
The new interval program now supports more than 16 characters for station names. Any chance of removing the limitation in the mobile app or is that for backwards comparability?November 21, 2013 at 5:22 pm #24821
The problem lies in all the common firmwares (OS, OSPi interval program and OSBo interval program) not reporting which device/specific version they are. Therefore, I can’t tell between OS vs OSPi and I also can’t tell between OSPi old vs new (before and after large station name support).
I can extend support universally however that will cause problems for some people on the more restricted firmwares. Each time I try to identify between the two I fail especially because the OSPi program is constantly changing so it’s hard to find a unique difference that persists through versions.November 21, 2013 at 8:04 pm #24822
- You must be logged in to reply to this topic.