[HELP] iBeacon/Eddystone Scanner plugins & supported hardware #5245

alexcorvis84 · 2024-05-23T09:38:10Z

alexcorvis84
May 23, 2024

Hi,

I'm thinking to use the iBeacon/Eddystone plugins with a sensor that seems to use that protocols.

My doubts are:

Does these plugins only works with the default Bluetooth adapter from a RaspberryPi (hci0) or I could use an external USB Bluetooth BLE adapter in the RaspberryPi or in a generic X86_64 device?
What are the main difference between advertiser and scanner packages? I guess the scanner 'listen' for iBeacon/Eddystone frames and the advertiser 'broadcast' iBeacon/Eddystone frames ¿isn't it?

Many thanks in advance.

pierantoniomerlino · 2024-06-10T13:22:32Z

pierantoniomerlino
Jun 10, 2024
Collaborator

Hi @alexcorvis84, I apologize for the late reply...

Does these plugins only works with the default Bluetooth adapter from a RaspberryPi (hci0) or I could use an external USB Bluetooth BLE adapter in the RaspberryPi or in a generic X86_64 device?

Yes, you can select with Bluetooth adapter to use. In the RPI the default one is hci0 but when you plug a USB-BT adapter, a new one is created. Use hciconfig to check the available adapters.

What are the main difference between advertiser and scanner packages? I guess the scanner 'listen' for iBeacon/Eddystone frames and the advertiser 'broadcast' iBeacon/Eddystone frames ¿isn't it?

Yes, the difference is the one you've reported.

4 replies

alexcorvis84 Jun 10, 2024
Author

No worries! I'm still waiting to receive the sensor...so I'll try the Driver as soon as I`ll get on my hands. Glad to know that I can use a USB-BT adapter. Thanks for your feedback!

alexcorvis84 Jun 19, 2024
Author

Hi @pierantoniomerlino,recei

I received the sensor and I was trying to follow the docs to read the data from sensor.

As decribed in the docs, I need the Wires Script Filter for Kura 4/5, but the issue is that after achieve installation, it seems it can not be activated.

I'm receiving the following error in kura logs when trying to install:

2024-06-19T18:35:01,843 [qtp27900535-3018] INFO  o.e.k.w.s.GwtDeviceServiceImpl - Starting bundle with ID: 214
2024-06-19T18:35:01,849 [qtp27900535-3018] ERROR o.e.k.w.s.GwtDeviceServiceImpl - Failed to start bundle 214
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.kura.wire.script.filter.provider [214]
  Unresolved requirement: Require-Capability: osgi.ee; filter:="(& (&(osgi.ee=JavaSE)(version=1.8)) (!(&(osgi.ee=JavaSE)(version>=15))) )"

	at org.eclipse.osgi.container.Module.start(Module.java:463)
	at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:439)
	at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:458)
	at org.eclipse.kura.web.server.GwtDeviceServiceImpl.startBundle(GwtDeviceServiceImpl.java:394)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
	at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:587)
	at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:333)
	at org.eclipse.kura.web.server.OsgiRemoteServiceServlet.processCall(OsgiRemoteServiceServlet.java:208)
	at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:303)
	at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:373)
	at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
	at org.eclipse.kura.web.server.OsgiRemoteServiceServlet.service(OsgiRemoteServiceServlet.java:95)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
	at org.eclipse.equinox.http.servlet.internal.HttpServiceRuntimeImpl$LegacyServlet.service(HttpServiceRuntimeImpl.java:1459)
	at org.eclipse.equinox.http.servlet.internal.registration.EndpointRegistration.service(EndpointRegistration.java:159)
	at org.eclipse.equinox.http.servlet.internal.servlet.ResponseStateHandler.processRequest(ResponseStateHandler.java:67)
	at org.eclipse.equinox.http.servlet.internal.context.DispatchTargets.doDispatch(DispatchTargets.java:117)
	at org.eclipse.equinox.http.servlet.internal.servlet.ProxyServlet.dispatch(ProxyServlet.java:147)
	at org.eclipse.equinox.http.servlet.internal.servlet.ProxyServlet.preprocess(ProxyServlet.java:115)
	at org.eclipse.equinox.http.servlet.internal.servlet.ProxyServlet.service(ProxyServlet.java:104)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
	at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:305)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:799)
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:554)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
	at org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:722)
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
	at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235)
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1624)
	at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1440)
	at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:505)
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1594)
	at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1355)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
	at org.eclipse.jetty.server.Server.handle(Server.java:516)
	at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:487)
	at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:732)
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:479)
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277)
	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
	at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:555)
	at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:410)
	at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:164)
	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
	at org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104)
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338)
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315)
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173)
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131)
	at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:409)
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883)
	at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034)
	at java.base/java.lang.Thread.run(Thread.java:840)

I'm running Kura 5.4.2 in a Raspberry Pi 4 with JAVA 17. It seems that plugin is only compatible with JAVA 8??

Are you planning to release a compatible version of it (or the different plugins available in Eclipse Marketplace) compatible with Java 17? As I guess I'll face the same issue with other plugins that are based in Java 8... 😕

As far as I know your plans are to use Java 17 as default framework in the next Kura releases (starting from 5.5?) isn't it?

I look forward to hearing any feedback. Many thanks in advance.

pierantoniomerlino Jun 20, 2024
Collaborator

Indeed the Wire Script Filter is not compatible with Java17. We replaced it with the new Wire Script Tools. Here are a comprensive documentation.

alexcorvis84 Jun 21, 2024
Author

Thank you so much @pierantoniomerlino . I've been able to install the Wire Script Tools plugin in Kura 5.4.2 running on Java17.

mattdibi · 2024-07-19T06:22:20Z

mattdibi
Jul 19, 2024
Collaborator

Closing this. Feel free to reopen if needed.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[HELP] iBeacon/Eddystone Scanner plugins & supported hardware #5245

{{title}}

Replies: 2 comments 4 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

[HELP] iBeacon/Eddystone Scanner plugins & supported hardware #5245

alexcorvis84 May 23, 2024

Replies: 2 comments · 4 replies

pierantoniomerlino Jun 10, 2024 Collaborator

alexcorvis84 Jun 10, 2024 Author

alexcorvis84 Jun 19, 2024 Author

pierantoniomerlino Jun 20, 2024 Collaborator

alexcorvis84 Jun 21, 2024 Author

mattdibi Jul 19, 2024 Collaborator

alexcorvis84
May 23, 2024

Replies: 2 comments 4 replies

pierantoniomerlino
Jun 10, 2024
Collaborator

alexcorvis84 Jun 10, 2024
Author

alexcorvis84 Jun 19, 2024
Author

pierantoniomerlino Jun 20, 2024
Collaborator

alexcorvis84 Jun 21, 2024
Author

mattdibi
Jul 19, 2024
Collaborator