eclipse / org.eclipse.sensinact.gateway Goto Github PK

License: Eclipse Public License 2.0

HTML 0.04% Java 85.27% Shell 0.10% JavaScript 0.01% Gherkin 0.02% ANTLR 1.88% TypeScript 11.67% Vue 0.88% SCSS 0.13%

org.eclipse.sensinact.gateway's Introduction

Updating the sensiNact Device API - Prototype

This repository aims to prototype how devices connectors should integrate with sensiNact in a clean way, fitting with the EMF model of the device

Annotation

The annotation module contains the sources for annotations used to define the "code first" connectors

Models

The models module contains the EMF models and the code generated from them

Sensinact-API

The sensinact-api module contains the API for the sensinact core

Examples

The examples project contains examples demonstrating how to use the sensiNact API

org.eclipse.sensinact.gateway's People

Contributors

Stargazers

Watchers

Forkers

isabella232 tcalmant stbischof juergen-albert gg-dim timothyjward isalvadori maho7791 datainmotion vwfox

org.eclipse.sensinact.gateway's Issues

Revisit how we detect Resources on a service after EObject Push is done.

EmfGeojson Handling

integration of EMFGeoJson

#106

Support "hello" events for arriving providers

A "Hello" event indicates the arrival of a provider with a known model. It may include initial values for resources.

Resource values are lost when adding a new resource

When creating new resources calling ModelNexus.handleDataUpdate(), all the resources the service was already containing have their values removed (set to null).

I have added a test to show the error.

I suspect the issue comes from the attribute version check in SensinactCopier

Here is an example of error we currently get for a resource name containing a dot:

Illegal character 46 at index 52 of topic string: LIFECYCLE/XXXXXXXXXX-airquality-NNNNNNN/pollutant/PM2.5
        at org.apache.aries.typedevent.bus.impl.TypedEventBusImpl.checkTopicSyntax(TypedEventBusImpl.java:495)
        at org.apache.aries.typedevent.bus.impl.TypedEventBusImpl.deliver(TypedEventBusImpl.java:410)
        at org.eclipse.sensinact.prototype.notification.impl.NotificationAccumulatorImpl.lambda$doComplete$5(NotificationAccumulatorImpl.java:316)
        at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
        at java.base/java.util.AbstractList$RandomAccessSpliterator.forEachRemaining(AbstractList.java:720)
        at java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:762)
        at java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:276)
        at java.base/java.util.TreeMap$ValueSpliterator.forEachRemaining(TreeMap.java:3215)
        at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)
        at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
        at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
        at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
        at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
        at java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:596)
        at org.eclipse.sensinact.prototype.notification.impl.NotificationAccumulatorImpl.doComplete(NotificationAccumulatorImpl.java:316)
        at org.eclipse.sensinact.prototype.notification.impl.AbstractNotificationAccumulatorImpl.completeAndSend(AbstractNotificationAccumulatorImpl.java:98)

Support "goodbye" events for removing providers

Currently it is not possible to remove a provider from the digital twin. We need to be able to do this when providers are removed in the real world.