

Many of our standard grid sets include basic template grids for setting up Environmental Control to use with your TV, Hi-fi and other devices, and are usually set up with the appropriate GEWA command. The next step is for the GEWA unit to ‘learn’ the codes associated with various buttons on your remote controller.
Here is an example grid set up to include all functions for a TV, but you can build your own grids as well.
Enter editing mode by pressing F11, and choose a cell that you want to edit, such as the vol up cell. If there is not a GEWA press button command showing in the edit window, click on add a command and type GEWA into the search box. Select GEWA press button from the list, and click on OK.
Once you have the command shown above, click on Select Button. If this is the first time you have used the environment control, select COM Port and then Auto Detect to locate the GEWA Prog.
Choose a button (you have 256 at your disposal!), and rename it to something relevant, e.g “TV vol up”. Click on the Rename button to do this.
Ensure the button is highlighted, and select Learn from remote.
Locate the EC window on your device, it usually looks like a dark piece of plastic or glass, and point the remote control towards it. Click on the Start learning button, and follow the instructions listed. The first instruction is to hold down the button on the remote control. In this example, it will be the ‘Volume up’ button. Once there is a green tick in the first box, release the button and press it again quickly. You will now have 3 ticks displayed.
If you have problems with this, make sure the remote control is close to the EC window, and pointing directly at it. If you continue to have problems, click on Cancel and select Prog and Check alignment from the previous window to check you are holding the remote control in the correct place.
Once you have trained this button, you can test it works by clicking on Test button. When you are finished, press OK to return to the editing grid.
This process can now be repeated for all the other buttons on your remote control.
Previously we chose to add the GEWA press button command, but there are some other commands available for use with the GEWA unit, which are listed here:
This option is useful when wanting to avoid repeated pressing of one button. For example, if used with the volume button, the volume would increase until you selected the volume cell again. This is useful when using scanning, so that you don’t have to repeatedly navigate to the volume button when significantly varying the volume.
Some devices can be fussy about the amount of time a button needs to be held down for. For example, if you press the number one on your TV remote too long, it will take you to channel 11 rather than channel 1. This command can be used to minimize or maximize the time required to hold down the button.
Some EC devices, such as dedicated lights or curtain openers, may specify which GEWA codes need to be used. You can enter the code, rather than using the remote control to learn particular functions.
Join the Smartbox mailing list for regular updates and news.
You can change your mind at any time by clicking the unsubscribe link in the footer of any email you receive from us, or by contacting us at hello@thinksmartbox.com.
We use MailChimp as our marketing email platform. When you join, you acknowledge that the information you provide will be transferred to MailChimp for processing in accordance with their Privacy Policy and Terms.
Cookie | Duration | Description |
---|---|---|
AWSALBCORS | 7 days | This cookie is used for load balancing services provded by Amazon inorder to optimize the user experience. Amazon has updated the ALB and CLB so that customers can continue to use the CORS request with stickness. |
cookielawinfo-checkbox-advertisement | 1 year | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Advertisement". |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
PHPSESSID | session | This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__zlcmid | 1 year | This cookie is used by Zendesk live chat and is used to store the live chat ID. |
player | 1 year | This cookie is used by Vimeo. This cookie is used to save the user's preferences when playing embedded videos from Vimeo. |
Cookie | Duration | Description |
---|---|---|
_gat | 1 minute | This cookies is installed by Google Universal Analytics to throttle the request rate to limit the colllection of data on high traffic sites. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
_gat_UA-65566191-1 | 1 minute | This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites. |
_gid | 1 day | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form. |
_hjFirstSeen | 30 minutes | This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. |
vuid | 2 years | This domain of this cookie is owned by Vimeo. This cookie is used by vimeo to collect tracking information. It sets a unique ID to embed videos to the website. |
Cookie | Duration | Description |
---|---|---|
_hjAbsoluteSessionInProgress | 30 minutes | No description |
_hjid | 1 year | This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
_hjIncludedInPageviewSample | 2 minutes | No description |
_hjShownFeedbackMessage | 1 day | No description |