Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jun 27 11:36
    calohmn milestoned #3319
  • Jun 27 11:36
    calohmn labeled #3319
  • Jun 27 11:36
    calohmn labeled #3319
  • Jun 27 11:36
    calohmn opened #3319
  • Jun 27 11:23
    calohmn assigned #3305
  • Jun 27 08:28
    sophokles73 commented #3317
  • Jun 27 08:11
    calohmn commented #3318
  • Jun 27 08:03

    sophokles73 on master

    Adapt to Hono 2.0.0 chart Sign… (compare)

  • Jun 27 07:59
    sophokles73 commented #3318
  • Jun 27 07:58
    sophokles73 labeled #3318
  • Jun 27 07:35
    calohmn labeled #3318
  • Jun 27 07:35
    calohmn opened #3318
  • Jun 27 07:35
    calohmn milestoned #3318
  • Jun 27 07:35
    calohmn labeled #3318
  • Jun 27 06:21
    calohmn commented #3301
  • Jun 27 06:12
    sophokles73 commented #3314
  • Jun 27 06:11
    sophokles73 milestoned #3317
  • Jun 27 06:11
    sophokles73 labeled #3317
  • Jun 27 06:11
    sophokles73 labeled #3317
  • Jun 27 06:11
    sophokles73 labeled #3317
Kai Hudalla
@sophokles73
Nice :-)
@/all I will start the 1.8.3 build now ...
Julian
@JulianFeinauer
I never used AMQP before so please excuse my noob questions : )
Kai Hudalla
@sophokles73
no sweat, it is not that popular anyway so you are part of the majority ;-)
Julian
@JulianFeinauer
But I think the documentation could be improved a bit then… from my understanding the address is a fixed AMQP attribute of a message, right?
Kai Hudalla
@sophokles73
fixed?
Julian
@JulianFeinauer
I got a bit confused since I passed the „to“ and „subject“ as Message Properties to QPid (as read from the Hono docs) but it seems that qpid at least likes to have the explicit attributes „address“ and „subject“ to work
So i thought it might be „special“ fixed properties but it seems thats just an issue of qpid and not of Hono
From my understanding, it should be a valid AMQP message if I pass a properties dict with keys to and subject but it seems that qpid wants it as separate properties address and subject directly (see here: https://qpid.apache.org/releases/qpid-proton-0.32.0/proton/python/docs/proton.html#proton.Message)
Julian
@JulianFeinauer
Another question regarding the command and control API from HONO. If the application wants to send a command to a device… it needs to implement a strategy to basically „retry“ it until it gets an answer accepted (and even if that, in case of one-way it needs to hope that it worked). Or is there anything more „intelligent“ that works with all adapters (in case of HTTP it could simply react to a message received event with a ttd set
Kai Hudalla
@sophokles73
The "ttd" mechanism works for all protocol adapters. See https://www.eclipse.org/hono/docs/1.8/concepts/device-notifications/ An application simply need to check the ttd application property in messages from devices in order to determine if the device can currently accept commands ...
Julian
@JulianFeinauer
okay.. so in most cases I would „piggybag“ my commands to send them after I received telemetry data
But I just discovered the command router API which should be some kind of generalization of this idea, right?
Kai Hudalla
@sophokles73
it depends. If a device maintains a permanent subscription for commands, e.g. using MQTT or AMQP 1.0, then your application can send commands at any time after it has received a notification containing a ttd value of -1 and before receiving a message with ttd = 0. For devices using stateless protocols like HTTP or CoAP, the application can send commands after it has received a message containing a ttd > 0 and before the ttd has been reached ...
Julian
@JulianFeinauer
I see
But generally speaking I should implement some kind of „mailbox“ mechanism in my app that „buffers“ the commands (if they are NOT ephemeral)
Kai Hudalla
@sophokles73
yes, Hono does not provide such an outbox for each device.
Julian
@JulianFeinauer
got it, thanks
Slowly I start to see how we would need to modify our application to get it working on HONO
Julian
@JulianFeinauer
And regarding the relation of Hono and EnMasse… in a scalable setup we would use an EnMasse „controlled“ infrastructure as Broker and Dispatcher and not the single containers provided with the Helm Chart?
Kai Hudalla
@sophokles73
That's the idea, yes. However, we are currently implementing support for using Apache Kafka as an alternative messaging infrastructure (i.e. replacing Dispatch Router and Artemis). This is already available in Hono 1.9 as a tech preview and I guess in the upcoming 1.10.0 version we will declare this fully supported ...
Julian
@JulianFeinauer
Ah, so all communication woudl then be done via Kafka Topics basically?
Kai Hudalla
@sophokles73
Julian
@JulianFeinauer
yes, I saw it in the docu but did not have a deeper look. What about the internal APIs? Would these still be AMQP?
Kai Hudalla
@sophokles73
If by "internal" you mean between protocol adapters and device registry, then the answer is yes. However, these components talk to each other directly, i.e. they do not need the Dispatch Router ...
9 replies
Kai Hudalla
@sophokles73
@/all I am now starting the 1.9.1 release build ...
Kai Hudalla
@sophokles73
@/all 1.8.3 and 1.9.1 have been released successfully ... The Hono helm chart has also already been updated accordingly
Anoop Kumar
@anoopk30
Hello, I want to know whether we can connect Eclipse Hono with Eclipse Kapua along with Eclipse Kura?
Bob Claerhout
@BobClaerhout
Hi all, I've question concerning the quarkus images. Some time ago I noticed the quarkus images didn't do what I expected. Yesterday I installed the latest hono version on our test cluster and the quarkus images were used automatically. However, it seems some configuration is not passed to the container. I can't seem to find where the configuration (in code) is coming from. I found QuarkusMqttProtocolAdapterProperties but couldn't find where this was populated. Do I have to provide the configuration in a different way for these quarkus containers?
17 replies
Julian
@JulianFeinauer
Short feedback after all my struggle with the initial setup and getting everything right in my tooling we finally start to use Hono and really like it. Very well done guys (special thanks to @sophokles73 for all the help). I try to prepare a little PR with some minor updates in the documentation (things that confused me) to help others to ease their „onboarding"
Kai Hudalla
@sophokles73
@JulianFeinauer thanks for the feedback :-) A PR would be more than welcome ... Would you also mind sharing some details about your use case/scenario where you are deploying Hono?
Julian
@JulianFeinauer
@sophokles73 Of course. We have a SaaS Offering for Machine Builders (not Factories) where we give them their own whitelabeled „Portal“ to communicate with their machines as well as their clients. So one part of the system is a little bit like the Azure IoTHUB / Boschs IoT Suite but more focused on Metadata and their relation with the Machine and so on. Another crucial part for us is the data history so we rely heavily on Apache IoTDB (there were / are also discussions in the #eclipse/ditto channel about some possibilities to integrate timeseries storage with Ditto in some way)
But simply put.. we have gateways that read data from machinery (a bit like Kura) and sends them via Messaging (currently MQTT only) to our backend where we then do several things with it
And we now decided to migrate to Hono for simple scaling reasons. Not about the infrastructure but the device management as our customer base (luckily) grows : )
Kai Hudalla
@sophokles73
Awesome. Thanks @JulianFeinauer :-)
Dejan Bosanac
@dejanb
@calohmn @sophokles73 Just got the confirmation that Quarkus 2.2.x is ready and productized and will be supported long term ... Next productized version will be 2.2.3
Kai Hudalla
@sophokles73
@dejanb thanks for checking, I am already in the process of updating my PR to use 2.2.2.Final instead of 2.0.3.Final ...
Dejan Bosanac
@dejanb
@sophokles73 sounds good
Kai Hudalla
@sophokles73
@/all I would like to do the 1.10.0 release this week. Anything else you need to go into it in addition to what we already have on the project board?
2 replies
samrose
@samrose
Is it feasible to use hono outside of kubernetes? It seems so, but I wondered what knowledgeable people here think
Abel Büchner-Mihaljević
@b-abel
@samrose It is possible. There used to be deployment scripts for Docker Swarm, but they were removed a long time ago. The deployment of the sandbox VM was still running on Docker Swarm until recently. That can still be found in the Git history for inspiration: https://github.com/eclipse/hono/tree/5505c3c6f6d4cb2ba70828188c9e38af2d02f1de/deploy/src/main/sandbox
samrose
@samrose
@b-abel I was considering running this with nomad, consul cluster
thank you!
Kai Hudalla
@sophokles73
@/all I will now start the 1.10.0 release build ...
Kai Hudalla
@sophokles73
@/all Our PGP key used for creating signatures of our release artifacts has expired. I have created an issue with Eclipse webmasters to extend the key's validity. Until then we cannot publish the artifacts to Maven Central ...
Kai Hudalla
@sophokles73
@/all The 1.10.0 release build has succeeded and I have pushed the container images to Docker Hub. However, the artifacts still cannot be published to Maven Central but that shouldn't be a big issue as most people install using the container images anyway ...
Bob Claerhout
@BobClaerhout
Hi, I was trying to run the quarkus images just now (version 1.10.0) and I stumbled upon a change in the lora adapter. In the spring lora adapter I'm not obliged to confugre following property: hono.lora.commandEnabledTenants. I was wondering why this is required in the quarkus version?
As you might imagin, I would not like to change my deploy because I'm adding a new tenant. Why can't the lora adpater look at the gateways with a commandEndpoint and add those dynamically to the used tenants?
Kai Hudalla
@sophokles73
This is probably a bug in the LoraProtocolAdapterOptions configuration class where the corresponding property is not optional. Anyway, it looks like LoraProtocolAdapterProperties.getCommandEnabledTenants() is never used anywhere in the Lora adapter so I guess we can simply remove the configuration property altogether.
Kai Hudalla
@sophokles73
@BobClaerhout can you create an issue and a corresponding PR?
Bob Claerhout
@BobClaerhout