The system is trying to match picks to actual events in bookmakers based on the team names provided by the tipster and the team names used by the book.
Often, a tipster will use a different team name than the one used by the book, for example a pick could be submitted on "ROMA - NAPOLI", while the bookmaker has "AS ROMA - NAPOLI".
The event matching algorithm is using a custom database of team name variations and mappings, it knows, for example, that "AS ROMA" = "ROMA'.
However, there is a possibility that an event cannot be mapped to the corresponding bookmaker event in cases such as a typo mistake or using an ambiguous or non-standard team name, or if the database mapping is missing from our side. In these cases, the order's status will be set to "EVENT NOT FOUND".
Although the mapping database contains 1000's of team name variations for almost all sports and leagues, it is possible that there could be missing mappings especially for lower leagues. In this case, please report the missing mapping so that it can be included in the database.
If you cannot login to your gmail account, you may have to enable access at https://www.google.com/settings/security/lesssecureapps. Even if you enable the previous setting, your connection to gmail will still be encrypted, provided that you connect to port 993 of imap.gmail.com.
Also, if you are trying to connect from a new IP, such as a VPS/VPC, you may need to login manually to gmail through a browser and complete any verification that google might require.
Check also your emails for a message from google, where they may say that they have blocked access from the new IP, until you confirm that you are the owner of the account and you are indeed the one using the new IP.
The placer is controlled directly by the main application and launched/exited as needed. The placer's executable is the file "betplacer.exe" which is located in the application's main folder.
The most common reasons for the placer remaining offline are:
The scraper is controlled directly by the main application and launched/exited as needed. The placer's executable is the file "betscraper.jar" which is located in the application's main folder.
The scraper requires the java runtime environment to be installed on your PC. You can install java by running the included file jxpinstall.exe or you can download from www.java.com
You will need to change your Windows settings so that the decimal symbol is represented with the character "." and the digit grouping symbol with the character ",".
These settings can be changed in Control Panel -> Clock, Language, and Region --> Change date, time, or number formats --> Additional Settings
Smartbet.io's VPCs are carefully configured to offer optimal performance and reliability for most types of use. However, you may notice a delay or lag in your connection with the VPC, which becomes particularly noticeable when large portions of the VPC's screen change rapidly, like when scrolling up or down in web pages, watching a video, switching between browser tabs, etc.
This lag is in fact caused by the speed of your own connection to the VPC. In order to insulate VPCs from their physical network interface and make them appear like regular home PCs when using a virtual or physical connection, we use a custom remote desktop protocol for connecting to a VPC which is very bandwidth-intensive. This means that when you are RDPing to your VPC you are effectively connecting to a middle server that fetches the VPC's screen and transmits it back to you, rather than using the VPC's network interface. This has the added benefit of being able to stay connected to your VPC even when the VPC's network connection is down or when the VPC is rebooting. It does however require a very fast connection on the receiver's end.
Fortunately, there is a solution to that: You will need to get a cheap 5-10 EUR/month conventional windows VPS (virtual private server) from a provider such as contabo.com or webtropia.com, or any other VPS provider. This VPS will have a very fast network connection and will be suitable for accessing your smartbet.io VPC with no delay or lag. Then, instead of connecting directly from your home PC to your smartbet.io VPC, you would instead connect with the standard remote desktop protocol (fast) to your VPS and from there you would connect with our custom remote desktop protocol (slow) to your smartbet.io VPC. Effectively, you are mitigating the issues that are caused by the increased bandwidth requirement of our custom remote desktop protocol by using the VPS's fast connection instead of your own slow home network connection.
