“The best part of Console 2.0 is Flows. Its visual representation among devices, integrations, and functions makes life easier when handling multiple assets.”
Sateesh, Community Member
You can read more about Flows in the Helium Docs here.
The second major new feature to Console 2.0 is the XOR filter, designed specifically to improve performance for Console. As the Helium Network grows and usage increases, the XOR filter allows the Console back-end, Router, to only process known traffic. This will significantly improve performance by allowing Router to avoid spending resources on unfamiliar packets.
Important: The first time a device joins the Network, its keys need to be added to the blockchain and the updated block propagated to the miners (Hotspots).
This initial join process could take up to 20 mins depending on:
- When this transaction (batched with others) gets added to the Helium blockchain
- The overall performance of the blockchain
While Flows and the XOR filter represent major beneficial changes to Console, non-node areas will remain largely the same and will remain familiar to existing Console users. This includes Data Credits, Organizations, and the Users sections.
Additionally, the custom and pre-built Integrations from Console will remain unchanged and available for use. You can read more about the available Integrations and how to use them here.
Sign up for and start using Console 2.0 today here.
You can find more information about Console 2.0 in the Heliums Docs here.
What has changed in Console 2.0 and what will remain the same?
The biggest changes to Console 2.0 are the additions of Flows and the XOR filter (see above).
The interface and workflows for Data Credits, Users, and Organizations have remained largely unchanged.
What do I need to do during the Console 2.0 release?
There’s no action required. Your devices and configurations will be preserved and you won’t need to take any action. In addition, your Data Credit balance will remain unchanged.
Why did you make these changes for Console 2.0?
Based on learnings from your feedback, the team wanted to deliver a much more streamlined and intuitive experience to accomplish core user goals including adding devices, defining Functions, and setting up Integrations to transfer data to endpoints.
Do Labels still exist? Do I still need Labels? What capabilities do Labels have?
Yes, Labels still exist to organize and manage devices. Users can choose to apply a single Label or multiple Labels to as many devices as needed. For example, a Label can be used to identify a sensor type (i.e., a temperature sensor), or to find the location of that sensor. Anytime Labels are updated, the changes flow to all devices with those Labels.
What happens to the functionality that used to be tied to Labels (ADR, CF List, Notifications, packet purchase)?
This functionality still exists. ADR and CF List can be directly applied to a device or group of devices. With notification and packet purchase users can define these features with general settings and apply to devices or groups of devices in the Flows workspace. For more help check Console docs here.
What will happen to my devices and settings when Console 2.0 is migrated to the production server?
Nothing. Your devices and configurations will be preserved, and you won’t need to take any action.
What will happen to my Data Credit balance when Console 2.0 is migrated to the production server?
Your Data Credit balance will remain unchanged. The migration will have no impact on Data Credit balances.