FAQs

How Do I Purchase Your Drivers?

All purchase are initiated via the bLicense driver and completed via PayPal. Please review bLicense documentation for more details.

How Do I Register with BNet Solutions?

There is no “Dealer Registration” or account creation requirements – I don’t want your usernames or passwords anymore than you want to create and track another set of credentials. All BNet Solutions drivers are available for anyone to download.

Do You Offer “Showroom” Licenses?

Yes, however as stated in the Terms and Conditions, the intention of this type of license is to further the product awareness of BNet Solutions offerings and is therefor restricted to environments where potential customers have access to view and interact with the product.

Is There A “Dealer” Price?

While we do offer discounts for bulk purchases and “Showroom” licenses, the driver cost is the same for everybody.

How Do I Transfer A License After An Upgrade?

After decommissioning the old Controller and installing the drivers on the new Controller, email me your transfer request, including the MACs, at blucas@bnet4solutions.com.

I Lost My License Key. Now What?

Using the bLicense driver, you can retrieve all license keys associated with your Controller’s MAC address. Simply run the “Get Purchased License Keys” Action and bLicense will retrieve, display and activate the appropriate installed drivers.

What Is the Driver Admin Server?

BNet Solutions drivers’ have a built-in webserver that looks and behaves like the Properties, Actions and Lua Output tabs for the driver in Composer. Some drivers have settings that an end-user may want to modify often – for example, bDexcom has properties that configure the low and high blood sugar alarms. By using the driver’s Admin Server, a homeowner can make frequent changes to the properties without involving the installer.

How Do I Access the Admin Server?

A driver’s Admin Server port is configurable in the driver’s properties. The following describes the default configuration.

Using a web browser, navigate to http://controller_ip:port where:

“controller_ip” is the IP Address of your Control4 Director (EA5, EA3, EA1, etc). For example 192.168.1.100

“port” follows the pattern: “4” (for Control4) + “Product ID” (two digits, starting at 01) + “Driver Instance” (two digits, starting at 00). For example, bLicense is Product ID “08” and there is usually only one instance, so the bLicense Admin Server would, by default, listen on port 40800.

Given the above controller IP, the bLicense Admin Server can be accessed at http://192.168.1.100:40800

Below is a list of all BNet Solutions Admin Server default ports:

  • bNexia: 40100
  • bTstat: 40200
  • bTimer: 40300
  • bEgaugeMonitor: 40400
  • bNightScount: 40500
  • bRoomba: 40600
  • bDexcom: 40700
  • bLicense: 40800
  • bTank: 40900
  • bMyQ: 41000
  • bReboot: 41100
  • bRename: 41300

Each additional instance of a driver will increment the port number. For example there are often multiple bTstat instances, so the first instance will use port 40200, the second 40201 and so on.

This is a little awkward because each Admin Server needs to listen for an incoming connection on its own port and Product IDs are internal but you have to have some way to reliably “find” the Admin Server for a driver.

What Is The Admin Server Token?

The Admin Server is protected by a challenge page that requires a token to continue. By default, the token is “Product Name” + “Admin”. For example, the bLicense Admin Server’s default token is “bLicenseAdmin” (case-sensitive). Once authenticated, the token is stored in a cookie (technically hashed, then stored) so you won’t need to log in every time. The token is configurable via the driver’s property page.

I Don’t Trust My User/Homeowner Using The Admin Server

The Admin Server is enabled by default but can be disabled entirely via the driver’s property page.