Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[hono-dev] client registration error in Hono lwm2m adapter

Hi hon dev,
I knew add_lwm2m  breanch  is outdated and not priority. But this is the only place I can refer for my lwm2m. 
I registered leshan client using “endpoint”: mydevice, “identity”: mypskid, “key” : aabbccdd1) 
When I observe client, I receive  "Warn message endpoint mydevice cannot be resolved to Hono ID, has device been registered with Hono?”. Please advice.

The following is my registration is hono.
1) Check registration in hono

HTTP/1.1 200 OK content-type: application/json; charset=utf-8 content-length: 64 {"device-id":"mydevice","data":{"ep":"mydevice","enabled":true}}

2) Retrieve credentials
HTTP/1.1 200 OK
content-type: application/json; charset=utf-8
content-length: 329


When I observe sensor values, giving me the follow error 

11:47:38.826 [main] INFO  o.e.h.adapter.lwm2m.LeshanDemoServer - using LwM2mModelProvider: org.eclipse.leshan.server.model.StandardModelProvider
11:47:39.004 [main] INFO  o.e.h.c.ConnectionFactoryImpl - connecting to AMQP 1.0 container [amqp://]
11:47:39.269 [main] INFO  o.e.h.adapter.lwm2m.LeshanDemoServer - using SecurityStore:
11:47:39.282 [main] INFO  o.e.h.adapter.lwm2m.LeshanDemoServer - using ServerKeyProvider: org.eclipse.hono.adapter.lwm2m.StaticEccServerKeyProvider
11:47:39.309 [main] INFO  o.e.h.adapter.lwm2m.LeshanDemoServer - using CaliforniumRegistrationStore: org.eclipse.leshan.server.californium.impl.InMemoryRegistrationStore
11:47:39.340 [main] DEBUG org.eclipse.hono.client.HonoClient - already trying to connect to Hono server ...
11:47:39.341 [main] DEBUG org.eclipse.hono.client.HonoClient - already trying to connect to Hono server ...
11:47:39.379 [main] INFO - Loading standard properties from file
11:47:39.464 [main] DEBUG o.e.h.adapter.lwm2m.LeshanDemoServer - adding observation listener: org.eclipse.hono.adapter.lwm2m.observation.TelemetryForwarder@7b4a0aef
11:47:39.465 [main] INFO  o.e.californium.core.CoapServer - Starting server
11:47:39.465 [main] INFO - Starting endpoint at /
11:47:39.472 [main] INFO - Starting endpoint at /
11:47:39.476 [main] INFO  o.e.c.scandium.DTLSConnector - DTLS connector listening on [] with MTU [1,280] using (inbound) datagram buffer size [16,474 bytes]
11:47:39.476 [main] INFO  o.e.l.s.c.impl.LeshanServer - LWM2M server started at coap://, coaps://
11:47:39.583 [main] INFO  org.eclipse.jetty.util.log - Logging initialized @3260ms
11:47:39.653 [main] INFO  o.s.b.c.e.j.JettyEmbeddedServletContainerFactory - Server initialized with port: 8090
11:47:39.654 [main] INFO  o.e.h.adapter.lwm2m.LeshanDemoServer - set root context resource base
11:47:39.677 [main] INFO  org.eclipse.jetty.server.Server - jetty-9.3.11.v20160721
11:47:39.747 [main] INFO  o.e.j.w.StandardDescriptorProcessor - NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet
11:47:39.761 [main] INFO  o.e.j.server.handler.ContextHandler - Started o.e.j.w.WebAppContext@58af5076{/,file:///Volumes/Data/Project/hono/hono-add_lwm2m/adapters/lwm2m/target/classes/webapp/,AVAILABLE}
11:47:39.761 [main] INFO  org.eclipse.jetty.server.Server - Started @3439ms
11:47:40.053 [main] INFO  o.s.j.e.a.AnnotationMBeanExporter - Registering beans for JMX exposure on startup
11:47:40.069 [main] INFO  o.e.jetty.server.AbstractConnector - Started ServerConnector@49e6c755{HTTP/1.1,[http/1.1]}{}
11:47:40.070 [main] INFO  o.s.b.c.e.j.JettyEmbeddedServletContainer - Jetty started on port(s) 8090 (http/1.1)
11:47:40.074 [main] INFO  o.e.hono.adapter.lwm2m.Application - Started Application in 3.157 seconds (JVM running for 3.751)
11:47:53.095 [CoapServer#4] INFO  o.e.h.a.l.o.TelemetryForwarder - New observation for resource [client: mydevice, path: /3303/0/5700] has been established
11:47:54.997 [CoapServer#2] WARN  o.e.h.a.l.o.TelemetryForwarder - endpoint mydevice cannot be resolved to Hono ID, has device been registered with Hono?

Back to the top