Record the myServer 6 IP address and ensure the SmartRemote template is installed. Then continue below to setup the SmartRemote on the myServer 6 network:
0:19: You will see the Allonis Logo, followed by an "explosion" clip.
0:15: You will see a "circle". The software image is expanding the SmartRemote's memory at this point.
0:31: Once booted you will be at the Android Desktop.
00:45: Wait and the SmartRemote app will launch. You will see the SmartRemote.apk launching.
00:50: Once finished loading:
In a few seconds, you will see your available Wifi Access Points that are within RF range.
3. Select the appropriate access point.
Only connect the SmartRemote to the one Wifi Access Point that connects to myServer. If you add a second wifi network, then the device might get on the wrong network and you'll wonder why the SmartRemote isn't able to control anything. Of course, you might use the SmartRemote in two facilities, each having it's own Wifi network. That's fine to configure both as the assumption is the SmartRemote won't see both of those networks at the same time and connect to the wrong one.
4. You can type that access point's password. You can click Show password to be sure you are selecting the correct letters / numbers from the tiny onscreen keyboard.
5. Once the password is entered, scroll down a bit and click on Advanced Options.
6. Recommended is to deselect DHCP and select Static addressing. This will allow the SmartRemote to connect to the network fast.
7. Type your correct IP address for the device. Ensure the IP address is not already in use, and if you set Static, then ensure the IP address is not in the DHCP range for the Router. You can click on the webpage to temporarily remove the on screen keyboard that may be covering the field you need to click on or see.
8. Type your Gateway IP address. Typically this is your Router's IP address on the LAN. (not WAN).
Type your Network Prefix Length. Most networks use "24". Android has a little bug entering information in these fields...make sure it doesn't add it's own digits to yours you type. Delete them if they appear.
9. Type your DNS server 1 and 2 addresses. This can be provided by your Internet service provider. You can also use the default Google's DNS servers which are: 220.127.116.11 and 18.104.22.168
7:10: Once all of your info is entered, click the Connect button. You should see that you are connected to the Internet.
Your SmartRemote should soon be on the network!
11. You can click the Back hard button to get back to the SmartRemote.apk
8:56: 12. Click Exit to close and then relaunch the SmartRemote app from the Desktop smartremote app logo.
9:17: If you are online, you should see the screen to enter your network information for myServer.
To Manually configure:
1. Type on the myServer IP Address box. The on screen keyboard will appear. Type myServer 6's IP address.
2. Next, click on the Project Name box. "smartremote" is the correct default folder name (the folder on myServer's webserver) (type with no quotes).
3. Click on the Clientname field. You can name your remote what you want. For our purposes, we will call it "SmartRemote8". Don' put spaces in the name. Keep the name simple as it will be used in lots of macros and variables.
4. Click the Save button. If you have a second myServer to configure, click on the Server #2 tab and enter that information. Click Save.
The Default Connection is the server that will be used on startup. You can also deselect but then you will need to choose which Server to connect to with each app startup.
The SmartRemote.apk (the "app") will launch, check that it's on Wifi, connect to myServer 6, and load the user interface smartremote template home page that you defined. If you don't see a webpage loaded, check your network settings, myServer connection settings and that you have a web project same name as the SmartRemote's connection settings are configured for.
Typically, once the webpage is loaded, you would click on the top of the webpage, select a user, then select which room you are in to control the devices in that room. The "activate-room.study" macro will be fired if you chose the Study room. This macro defines which device icons appear on the webpage and that webpage defines the function of the hard buttons (that you can edit in myDesigner).
Tidbit: If you are testing the smartremote webpage on a browser NOT on the SmartRemote, you can go HOME by clicking the F5 button.
Note that a LONG press on the side power button will reboot the OS of the SmartRemote. The Back and the Home button can be used to navigate the AndroidOS. No other buttons are enabled unless the smartremote.apk is running and a smartremote webpage is displayed on the screen.
Note that any new webpage will take much longer to load. On the second load, the graphics will already be saved in the SmartRemote cache to load quickly. If you shutdown the smartremote.apk and restart it, then the long load time will start again until all pages are loaded once.
From a PC browser, go to myServer 6's Dashboard. Click on Management / Drivers / AndroidTV's configure button.
Click the Discover button. Soon, the powered on and networked SmartRemote will be added automatically. You should see it's power state in the Power Testing area. Here you can update the SmartRemote.apk if updates are available. The apk updates are distributed in myServer 6 updates.
You can also test launching the smartremote.apk and shutting it down from within myServer's Driver dashboard.
The reset of the configuration is done in myServer 6's templates and macros, automation rules, etc.
System design consideration: Infrared
One of the reasons for creating a new hardware build version of SmartRemote was to add an Infrared emitter in the nose of the remote. The previous version did not have this because we believe the better strategy is to use a IR "IP2IR" hub anywhere on the network where you have IR devices. ie: a distributed IR network. But then we got thinking, for simpler "one room" systems, it would be a little more cost effective just to do the standard "point and shoot" remote control use.
If the SmartRemote loads to the Android Desktop, wait until the smartremote.apk auto launches. Sometimes this can take a few seconds.
Once it loads, if there is no Auto Launch settings configured, you should see the settings tab.
If the project launches "to a white page", then that's likely because you don't have your myServer IP and the smartremote folder properly configured. You can wipe all of these settings by clearing data/ cache in the smartremote.apk in the Android Desktop's Apps page.
You might not be able to reach the AndroidOS desktop to clean data. If this is the case, myServer Pi needs to have ADB access. This can be done within myServer's AndroidTV app (add the SmartRemote IP to the list of Android devices - which adds ADB connection to it). You can also from a terminal session, type: "adb connect 192.168.1.48:55055" (use your IP address). Then, in Chrome (on the myServer controller), go to "chrome://inspect" You should see the SmartRemote listed in the list of ADB connected devices. Click "inspect" link in the SmartRemote's Remote Target section.
Go to the Apps tab and click the Application Tab.
You can adjust the myServer IP address and the project name (the myServer smartremote folder) as well as change the SmartRemote's computer name.
SmartRemotes that are "off" in AndroidTVDriver will not show in Screencast view in Inspect. Turn it ON and it displays. So, the remote might be asleep.
You can set a clientname / folder / myServer address in a client device (like SmartRemote) by running a command like:
ClientCmd|SetLaunchProperties|<project name>~<server ip>~<clientname>
When that macro is run, myServer reconfigures the client to connect to a different myServer instance - like when moving your SmartRemote from House to RV networks!
Your "smartremote" web folder:
You can create a "wwwroot/backups" directory and put your old (but maybe customized?) folder in there, and rename the latest smartremote-sample to smartremote