Can I use Nexus Keycode and Nexus Channel with the PAYG software platform of my choice?
Yes, any PAYG platform (including your own solution) can integrate with Nexus. The three largest PAYG platforms are already Nexus-ready, including of course Angaza. We are happy to provide advice on platform integration, and you can even manage Nexus-enabled devices with your own solution.
How are individual Nexus devices deployed?
In order to sell a PAYG device, distributors need important operational information like device-specific identities from manufacturers. The Nexus API provides a central platform to manage this type of data. When manufacturers create units, the device-specific information is stored on the Nexus API servers. PAYG platforms can use the API to generate Nexus Keycodes for their devices, or export the identity and cryptographic data in order to generate those keycodes outside of the API. As a result, manufacturers can create true single-SKU devices and ship them to any distributor without regard to the PAYG platform the distributor is using.
Who controls keycode generation via Nexus Keycode?
Because Nexus is open-source and integrated with a number of PAYG software platforms, you get to choose how you want to manage keycode generation and device state updates. You may utilize the managed Nexus API to control keycodes and generate them via our servers. You may also use a compatible PAYG software platform, in which case the keycodes will be generated on the servers of the software provider of your choice. Of course, since the code is open source, you can also manage the devices independently and generate keycodes using an independent service.
Can I use Nexus Keycode for offline devices?
Yes, Nexus devices do not require a digital connection. In order to keep track of keycodes for offline use, we recommend a mobile application like the Angaza Activator that is designed for a large network of agents with intermittent connectivity.
Can I use other keycode protocols with Nexus Channel?
No, currently Nexus Channel only supports Nexus Keycode. In the future, it can support other communication protocols including Nexus GSM.
What information can Nexus Channel transmit between devices?
Nexus Channel supports much more than keycode sharing and device state management, and we invite you to explore the possibilities. For example, devices powered by a central solar home system (SHS) battery could exchange data about energy priority, allowing the SHS to make intelligent decisions about which appliances to power or not when energy is low. As another example, low-cost accessory devices could collect telemetry data and send it to cloud platforms via a GSM-enabled controller device.
Device manufacturers can use existing resource models or introduce new ones customized to their specific use case. You are free to develop independent proprietary resource models, or contribute to the publicly available set of models for wider adoption and interoperability.