LoRa adapter: Create only one gateway device command consumer per application instance
See original GitHub issueApply some minor Command & Control improvements:
A command subscription for a gateway device only needs to be done once for the whole LoRa adapter application - currently the corresponding LoraProtocolAdapter#commandSubscriptions
map is kept per LoraProtocolAdapter
verticle instance.
Along with that, the closing of command consumers in the handleTenantTimeout
method (introduced in #2720) should then effectively only be done once per gateway device (not for up to as many times as the number of verticles as it is now).
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Contribute to eclipse-hono/hono · GitHub
LoRa adapter : Create only one gateway device command consumer per application instance enhancement good first issue Issues that do not require much...
Read more >LoRa Basics | DEVELOPER PORTAL
When the RXParamSetupReq MAC command is received, the end device must validate whether the new frequency and data rate are allowed by its...
Read more >What is new & noteworthy in Hono? - Eclipse
The HTTP protocol adapter now allows authenticated gateway devices to omit the tenant ID from the URI of requests used to upload telemetry,...
Read more >LG01N/OLG01N LoRa Gateway User Manual - Dragino
Firmware Version: lgw--build-v5.4.1607519907-20201209-2120 ... 1.5 Applications . ... Example 1: Manually send / receive LoRa packets .
Read more >HTTP adapter - Bosch IoT Device Management
The HTTP adapter supports publishing of telemetry data by means of request with method POST for devices and PUT for gateways using QoS...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I would like to work on this issue.
yes, fixed via #3421.