Frequently Asked Questions
CTbee is one of the element composing our commercial offer of shared parking technology.
It is a piece of HW derived from Gollum, but with specific features dedicated to gate/garage door openers (dedicated API, Backend support, specific ciphering/deciphering features, etc…)
Gollum is the foundation for our CTbee commercial product.
Gollum includes a HW module (the dongle) + a FW stack + a SW library (Android/iOS/C).
While CTbee is dedicated to our shared parking operation, Gollum can be used for anything a developer can think of.
You can link with Gollum using an Android/iOS smartphone with Bluetooth Smart feature.
In some cases, you will need a higher throughput than what BLE can offer, so you will have to use Gollum using its USB port.
You can connect Gollum to an Android Smartphone with USB Host mode (USB host mode is supported in Android 3.1 and higher) using a USB micro Male/Male cable.
You can also connect Gollum to a computer (Linux) and use #rfcat Python scripts or our native C stack to send/receive data.
If you are interrested in shared parking, get a CTbee.
If you want to develop & learn in other areas, get a Gollum.
Well, part of.
Some pieces are definitely open source (eg. the #rfcat fork we have made), others will also be open-source as there are important for developers to use Gollum.
Others pieces are custom parts of our CTbee product, and cannot be disclosed without altering our relationship with existing CTbee customers.
But we will release everything needed for developers to use Gollum.
A CTbee dongle and a Smartphone. That’s all.
Simply plug your CTbee dongle into your Smartphone, put the ComThings app in clone mode, and activate (press) the remote control. That’s all. ComThings captures the radio transmission and programs your CTbee dongle accordingly. Unplug your CTbee dongle and use it as you would use the original remote control.
No problem. CTbee dongle can replace the remote control for almost all the gate openers on the market. Just connect your CTbee dongle, launch the app and select your gate opener from the list. Then follow the instruction on your smartphone.
In CTbee V1, there was 2 USB port: 1 micro male & 1 micro female.
To program CTbee V1 dongle before usage, it needed to be plugged into your Smartphone USB port. This is why there was a micro-B USB male connector.
The micro-B USB female connector was for easily recharging the builtin battery & powering the phone at the same time.
CTbee V2 and your smartphone still exchange data using the USB protocol.
We also have kept a micro-B USB female connector for easily recharging the builtin battery.
The same applies for Gollum V1/V2.
Gollum can be paired with a Smartphone & used immediatly after unboxing.
Yes, we distribute SDKs and web APIs to our partners for easy integration to their application.
There are various modes of sharing. You can send the code by email or use ComThings web platform to create a new user.
Our SDK also include APIs for code sharing.
We are currently supporting almost 70% of the gate or garage door openers on the market. The list will be published soon in the support section.
ComThings servers are located around the world, distributed and synchronized to ensure that there is no single point of failure.
Your personal data is yours. But you can share your gate opener radio access code with your family, friends, or third-parties if you want to. No obligation.
Yes, but only if you want to. You can choose to use CTbee in local mode only. In this case, ComThings will not store anything on servers. But if you choose to save your configuration on our servers, you can always adjust your settings later.
ComThings has servers with databases of all “languages” (aka radio protocols) spoken by almost all the gate openers on the market. When your ComThings dongle scans for a new gate opener, it works in partnership with the Cloud to establish the radio communication.
ComThings Servers supports HTTPS for secure communication with app.
No. In operation mode, a CTbee cannot be copied as it only acts as a transmitter. It receives orders from the Smartphone app and does what the app asks.
Link between the app and the CTbee module is encrypted.
Absolutely not! Unless you send them, nobody can use your radio access codes. One can only program a CTbee Dongle with the radio codes he/she has authorization for.
To lose a CTbee dongle is the same as to lose an original remote control. There is nothing we can do about it. But if you declare the loss on our web portal, we will revoke your CTbee dongle validity and make it impossible to reprogram.
Yes. CTbee has builtin support of Firmware Over the Air. It will check for new firmware availability and update when needed. As data is stored in your cloud account, you will not lose any of your data.
Your Smartphone needs to have support of Bluetooth Low Energy (BT4.0). This depends on the Smartphone Manufacturer.
You can google it or check your device here.
CTbee dongle is available in small quantities for testing, integration & evaluation. Check the Product Launch Timeline to know more.
There are various schemes available depending on your level of integration. Please contact us to know more.
Gollum will be available 1st half of 2016 for pre-orders, but only a limited quantity will be produced (100-200 units).
Register on our website to be notified when pre-orders start.
Nothing. There is no installation needed. CTbee can work almost out-of-the-box.
All you have to do is:
This was a tricky question. There is no commercial app, only libraries and SDKs to integrate to your application.
Currently, Android and iOS are supported.
Nothing…because we have no commercial app.
The CTbee module is provided with Android and iOS SDKs, web APIs and sample apps.
All you have to do is to integrate CTbee libraries with your existing app.
The price of the CTbee HW module, which is the only thing you need to start opening your gates, is currently not frozen, but will be very low.