Skip to content
Permalink

Comparing changes

This is a direct comparison between two commits made in this repository or its related repositories. View the default comparison for this range or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: hivemq/hivemq-edge
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: c1678bbb03fa5b757d63787262e628c35b3b1768
Choose a base ref
..
head repository: hivemq/hivemq-edge
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 9ab720e25fa977c1bfc7bcf47ba9d75a26a838f1
Choose a head ref
Original file line number Diff line number Diff line change
@@ -12,7 +12,7 @@
},
"page": {
"title": "Data Hub on Edge",
"description": "The Data Hub on Edge provides mechanisms to define how MQTT data and MQTT client behavior are handled from the adaptors to the HiveMQ broker"
"description": "HiveMQ Data Hub on Edge provides mechanisms to define how the HiveMQ Edge MQTT broker handles MQTT data, MQTT client behavior, and data from the protocol adaptors."
},
"policy": {
"type_CREATE_POLICY": "No type",
42 changes: 21 additions & 21 deletions hivemq-edge/src/frontend/src/locales/en/translation.json
Original file line number Diff line number Diff line change
@@ -105,7 +105,7 @@
},
"welcome": {
"title": "Welcome to HiveMQ Edge",
"description": "Connect from and to any device and send streams of data to your enterprise.",
"description": "Connect to and from any device for seamless data streaming to your enterprise infrastructure.",
"onboarding": {
"title": "Get data flowing",
"errorLoading": "We cannot load the onboarding tasks. Please try again later.",
@@ -116,29 +116,29 @@
"label": "Read more"
},
"protocolAdapter": {
"title": "Use HiveMQ Edge modular Protocol adapters to connect to local and network based devices.",
"title": "Use modular HiveMQ Edge protocol adapters to connect to local devices that use different communication protocols.\n",
"label": "Use a Protocol Adapter"
}
},
"connectEnterprise": {
"header": "From HiveMQ Edge to the Enterprise",
"bridge": {
"title": "Connect your HiveMQ Edge MQTT Broker to your Enterprise using MQTT Bridge connections.",
"title": "Connect your HiveMQ Edge MQTT broker to your enterprise infrastructure with MQTT bridge connections.",
"label": "Use a Bridge"
}
},
"connectCloud": {
"header": "Connect To HiveMQ Cloud",
"section": {
"title": "You should connect your HiveMQ Edge deployment with a HiveMQ Cloud MQTT Broker, which will be the source of truth for your business data",
"title": "Create a single source of truth for all your enterprise-wide data by seamlessly connecting your HiveMQ Edge deployment to a HiveMQ Cloud MQTT broker.",
"label": "Connect To HiveMQ Cloud"
}
}
}
},
"bridge": {
"title": "MQTT bridges",
"description": "An MQTT bridge lets you connect two MQTT brokers together. They are generally used for sharing messages between systems.",
"description": "MQTT bridges let you connect multiple MQTT brokers to enable seamless data sharing between different networks or systems.",
"list": "List of bridges",
"action": {
"add": "Add bridge connection",
@@ -395,7 +395,7 @@
},
"protocolAdapter": {
"title": "Protocol Adapters",
"description": "Protocol adapters provide the ability to connect your HiveMQ Edge installation to local and remote devices. Once a connection has been established, you can consolidate data from this connection into your HiveMQ MQTT Broker.",
"description": "Protocol adapters allow you to connect your HiveMQ Edge installation to local and remote devices that use communication protocols other than MQTT. Once a connection is established, you can seamlessly consolidate all device data into your HiveMQ Edge MQTT broker.",
"list": "List of protocol adapters",
"action": {
"goCatalog": "Add a new adapter",
@@ -661,25 +661,25 @@
},
"unifiedNamespace": {
"title": "Unified Namespace Prefix",
"description": "Set your unified namespace architecture.",
"description": "Setting up a Unified Namespace (UNS) for MQTT data helps you create a centralized, standardized framework for organizing and accessing data across your entire organization.",
"standard": "ISA-95",
"action": {
"define": "Modify the UNS Prefix"
"define": "Configure Unified Namespace"
},
"error": {
"loading": "We cannot load your namespace for the time being. Please try again later"
},
"container": {
"prefix": {
"title": "My namespace prefix"
"title": "Your namespace prefix"
},
"info": {
"title": "ISA-95 Unified Namespace",
"descriptions": [
"A Unified Namespace is a middleware solution that allows you to collect data from various industrial systems, add context to it, and transform it into a format that other systems can understand.",
"ISA 95 provides a convenient way of structuring data sources in relation to their position within a manufacturing enterprise, hierarchically. "
"A Unified Namespace is a centralized framework that allows you to integrate and harmonize data from diverse industrial systems to achieve seamless real-time data exchange and interoperability.",
"ISA-95 is an international standard that defines a structured way to exchange data within a manufacturing enterprise."
],
"link": "Go to hivemq website to know more"
"link": "Learn more about UNS and smart manufacturing on the HiveMQ website"
},
"recommend": {
"title": "Recommended format",
@@ -691,34 +691,34 @@
},
"enabled": {
"label": "Enable Unified Namespace",
"helper": "When enabled, unified namespace will provide tokens that can be used in topics to apply UNS convention to your data."
"helper": "When enabled, the Unified Namespace tokens can be used in topics to apply the UNS convention to your data."
},
"enterprise": {
"label": "Enterprise",
"helper": "An enterprise is a collection of sites and areas and represents the top level of a role based equipment hierarchy."
"helper": "An enterprise is a top-level hierarchical structure that provides a consolidated view and context for all underlying systems, sites, and processes of an organization."
},
"site": {
"label": "Site",
"helper": "A site is a physical, geographical, or logical grouping determined by the enterprise."
"helper": "Sites are physical, geographical, or logical groups within an enterprise."
},
"area": {
"label": "Area",
"helper": "An area is a physical, geographical, or logical grouping determined by the site."
"helper": "Areas are physical, geographical, or logical groups within a site"
},
"productionLine": {
"label": "Production Line",
"helper": "Production lines are low levels of equipment scheduled for discrete manufacturing processes."
"helper": "Production lines group related work cells and operations into a single logical unit within the manufacturing or operational process."
},
"workCell": {
"label": "Work Cell",
"helper": "Work Cell are low levels of equipment scheduled for discrete manufacturing processes."
"helper": "Work cells are low-level functional units within a manufacturing or operational process that perform a designated task or series of tasks."
},
"options": {
"legend": "Options"
},
"prefixAllTopics": {
"label": "Add prefix to all topics",
"helper": "MQTT topics will use the namespace defined"
"label": "Add UNS prefix to all MQTT topics",
"helper": "MQTT topics will use the defined namespace"
},
"submit": {
"label": "Submit"
@@ -991,7 +991,7 @@
},
"eventLog": {
"title": "Event Log",
"description": "System components generate events in the system which can help in the diagnosis of issues or general system monitoring. The Event Log allows you to interact with the events and explore the system",
"description": "HiveMQ Edge components generate many events that are useful for system diagnosis and monitoring. The Event Log allows you to interact with events and gain system insights.",
"table": {
"header": {
"id": "Details",
Original file line number Diff line number Diff line change
@@ -18,7 +18,7 @@ describe('ProtocolAdapterPage', () => {
.find('h1 + p')
.should(
'contain.text',
'Protocol adapters provide the ability to connect your HiveMQ Edge installation to local and remote devices'
'Protocol adapters allow you to connect your HiveMQ Edge installation to local and remote devices that use communication protocols other than MQTT. Once a connection is established, you can seamlessly consolidate all device data into your HiveMQ Edge MQTT broker.'
)

cy.getByTestId('test-pathname').should('have.text', '/protocol-adapters')
Original file line number Diff line number Diff line change
@@ -27,10 +27,10 @@ const InfoPanel: FC = () => {
as={RouterLink}
to={config.documentation.namespace}
target="hivemq:docs"
aria-label={t('unifiedNamespace.container.info.link')}
leftIcon={<GoLinkExternal />}
data-testid="namespace-info-documentation"
size="lg"
whiteSpace="normal"
>
{t('unifiedNamespace.container.info.link')}
</Button>
Original file line number Diff line number Diff line change
@@ -62,7 +62,7 @@ private SimulationProtocolAdapterInformation() {

@Override
public @NotNull String getDescription() {
return "Without needing to configure real devices, simulate traffic from an edge device into HiveMQ Edge.";
return "Simulates device message traffic to enable observation of adapter behavior without the need to configure actual devices.";
}

@Override
Original file line number Diff line number Diff line change
@@ -78,7 +78,7 @@
"id" : "http",
"version" : "2024.9",
"name" : "HTTP(s) to MQTT Protocol Adapter",
"description" : "Connects HiveMQ Edge to arbitrary web endpoint URLs via HTTP(s), consuming structured JSON or plain data.",
"description" : "Polls data from one or more web endpoint URLs and converts the consumed structured HTTP bodies (XML, JSON, text, CSV) into an MQTT message.",
"author" : "HiveMQ",
"documentationLink" : {
"url" : "https://docs.hivemq.com/hivemq-edge/protocol-adapters.html#http-adapter",