christianschmizz / iotsys

Automatically exported from code.google.com/p/iotsys

Hi there 👋

I am Christian Schmizz ℤ, guardian of innocent software-projects. My mission is to protect us, you and me from unfortunate code and short-sighted decisions (and their consequences).

• 🌱 Love helping people grow and succeed. It's always the people.
• 🧑‍🏫 Focussing on forward-thinking solutions by learning the lessons and letting them go.
• 🗿 Creating distributed systems by running SOLID software with the power of event sorcery.
• 🫥 I am a strong advocate of 🩳 "Less is more", 🧠 "Don't make me think" and 🧟 "Keep it simple, stupid".
• 🫙 I strictly believe that the best code, is code never written.
• ʕ◔ϖ◔ʔ Avid Gopher. 🐍 Avid Pythonista and 🦄 Djangonaut.
• Did PHP, Java ☕️ – a while ago
• JavaScript since the early days of jQuery, Backbone.js and Node.js

iotsys's Issues

oBIX object serialization based on EXI

Currently oBIX objects are serialized to XML and then to EXI and the same way 
around for deserialization. An oBIX encoder/decoder for EXI should be provided 
that allows to directly serialize oBIX objects to EXI.

Original issue reported on code.google.com by [email protected] on 7 Mar 2013 at 8:37

Update to latest CoAP implementation

Update the CoAP server part to the latest CoAP implementation. Currently the 
gateway is CoAP 08 compliant. Modifications (e.g. MultiInterfaceUDPLayer) need 
to kept.

Original issue reported on code.google.com by [email protected] on 31 Mar 2013 at 12:52

IoTSyS and big data

Reuse the oBIX server from the gateway and create a scalable oBIX server based 
on scalable distributed data stores in order to allow data analytics and 
trending on the oBIX data points and histories. 

The gateway should feed data to the centralized data store using the history 
append functionality.

Original issue reported on code.google.com by [email protected] on 7 Mar 2013 at 11:34

HTML5 Web interface

HTML5 control interface to interact with the oBIX objects and visualize oBIX 
histories.

Original issue reported on code.google.com by [email protected] on 7 Mar 2013 at 3:07

IoTSyS - startup errors

What steps will reproduce the problem?
Ans: I followed all the steps given in the gettingstarted guide. On running the 
last command "java -jar bin/felix.jar", I am getting certain errors which I've 
attached over here. The key errors seems to be:
5 Jun, 2013 1:55:20 PM 
at.ac.tuwien.auto.iotsys.gateway.connectors.bacnet.BACnetBundleActivator start
SEVERE: Could not find a running object broker to register devices!

2013-06-05 13:55:20 [at.ac.tuwien.auto.iotsys.gateway.Log] INFO - ==[ START-UP 
]========================================
================
2013-06-05 13:55:20 [at.ac.tuwien.auto.iotsys.gateway.IoTSySGateway] INFO - 
Server starting.
2013-06-05 13:55:21 [at.ac.tuwien.auto.iotsys.gateway.DeviceLoaderImpl] INFO - 
Found device loader: at.ac.tuwien.auto.io
tsys.gateway.connectors.knx.KNXDeviceLoaderImpl
2013-06-05 13:55:21 [at.ac.tuwien.auto.iotsys.gateway.DeviceLoaderImpl] SEVERE 
- Could not instantiate device loader at.
ac.tuwien.auto.iotsys.gateway.connectors.knx.KNXDeviceLoaderImpl - not found on 
classpath!



What is the expected output? What do you see instead?
When I try the command: http://localhost:8080/obix, I expected to see the 
HTTPInteraction page. Instead, I see the error in the cmd line:
g! 2013-06-05 13:57:44 [at.ac.tuwien.auto.iotsys.gateway.obix.server.NanoHTTPD] 
INFO - Serving: /obix for 0:0:0:0:0:0:0:
1
Exception in thread "Thread-5" java.lang.NoClassDefFoundError: 
at/ac/tuwien/auto/iotsys/xacml/pdp/PDPInterceptorSettings

        at at.ac.tuwien.auto.iotsys.gateway.obix.server.NanoHTTPD.serve(NanoHTTPD.java:179)
        at at.ac.tuwien.auto.iotsys.gateway.obix.server.NanoHTTPD$HTTPSession.run(NanoHTTPD.java:847)
        at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.ClassNotFoundException: 
at.ac.tuwien.auto.iotsys.xacml.pdp.PDPInterceptorSettings not found by at.a



What version of the product are you using? On what operating system?
I'm using the latest IoTSyS distribution cloned from the source tree on 05 June 
2013. 

Java = java version "1.6.0_25"
Java(TM) SE Runtime Environment (build 1.6.0_25-b06)

Windows 7 64-bit.

Original issue reported on code.google.com by RSutaria on 5 Jun 2013 at 8:30

Attachments:

• iotsys-startup-errors.txt

IoTSyS gateway persistence

The gateway holds currently all data point values of the oBIX objects in 
memory. A lightweight persistence layer should be introduced so that the data 
point values and especially the histories "survive" a gateway restart.

Original issue reported on code.google.com by [email protected] on 7 Mar 2013 at 11:30

Completion of the reference implementation of oBIX 1.1 working draft

Currently the gateway partly implements the oBIX watch service, history 
service. 

The oBIX server reference implementation should be completed (Watches, History, 
Alarming)

Original issue reported on code.google.com by [email protected] on 7 Mar 2013 at 8:29

Errors when running using OSGi

What steps will reproduce the problem?

I cloned the latest version from google code and followed all steps from here: 
https://code.google.com/p/iotsys/wiki/gettingstarted
It compiles successfully, only with some "deprecated" warnings. When I try to 
run it using OSGi, this is the console output:


C:\iotsys\felix-framework-4.2.1>java -jar bin/felix.jar
VII 31, 2013 1:10:34 PM at.ac.tuwien.auto.iotsys.gateway.connectors.bacnet.BACne
tBundleActivator start
INFO: Starting BACnet connector
VII 31, 2013 1:10:34 PM at.ac.tuwien.auto.iotsys.gateway.connectors.bacnet.BACne
tBundleActivator start
SEVERE: Could not find a running object broker to register devices!
VII 31, 2013 1:10:34 PM at.ac.tuwien.auto.iotsys.control.TestClientActivator sta
rt
INFO: Starting Test Client.
VII 31, 2013 1:10:34 PM at.ac.tuwien.auto.iotsys.control.TestClientActivator sta
rt
SEVERE: Could not find a running object broker to register devices!
VII 31, 2013 1:10:34 PM at.ac.tuwien.auto.iotsys.demoapp.DemoAppActivator start
INFO: Starting demo app
VII 31, 2013 1:10:34 PM at.ac.tuwien.auto.iotsys.demoapp.DemoAppActivator start
SEVERE: Could not find a running object broker to register devices!
VII 31, 2013 1:10:34 PM at.ac.tuwien.auto.iotsys.gateway.connectors.enocean.Enoc
eanBundleActivator start
INFO: Starting Enocean connector
VII 31, 2013 1:10:34 PM at.ac.tuwien.auto.iotsys.gateway.connectors.enocean.Enoc
eanBundleActivator start
SEVERE: Could not find a running object broker to register devices!
VII 31, 2013 1:10:34 PM at.ac.tuwien.auto.iotsys.gateway.IoTSySGatewayActivator
start
INFO: Starting IoTSySGateway.
VII 31, 2013 1:10:34 PM at.ac.tuwien.auto.iotsys.gateway.IoTSySGatewayActivator
start
SEVERE: Could not find mDNS-SD Service!
2013-07-31 13:10:34 [at.ac.tuwien.auto.iotsys.gateway.Log] INFO - ==[ START-UP ]
========================================================
2013-07-31 13:10:34 [at.ac.tuwien.auto.iotsys.gateway.IoTSySGateway] INFO - Serv
er starting.
ERROR: Bundle at.ac.tuwien.auto.iotsys.gateway [9] Error starting file:/C:/iotsy
s/felix-framework-4.2.1/bundle/iotsys-gateway-0.1.jar (org.osgi.framework.Bundle
Exception: Activator start error in bundle at.ac.tuwien.auto.iotsys.gateway [9].
)
java.lang.NoClassDefFoundError: at/ac/tuwien/auto/iotsys/gateway/obix/objects/kn
x/datapoint/DataPoint
        at at.ac.tuwien.auto.iotsys.gateway.obix.objects.ContractInit.init(Contr
actInit.java:126)
        at at.ac.tuwien.auto.iotsys.gateway.IoTSySGateway.startGateway(IoTSySGat
eway.java:106)
        at at.ac.tuwien.auto.iotsys.gateway.IoTSySGateway.startGateway(IoTSySGat
eway.java:91)
        at at.ac.tuwien.auto.iotsys.gateway.IoTSySGatewayActivator.start(IoTSySG
atewayActivator.java:80)
        at org.apache.felix.framework.util.SecureAction.startActivator(SecureAct
ion.java:645)
        at org.apache.felix.framework.Felix.activateBundle(Felix.java:2146)
        at org.apache.felix.framework.Felix.startBundle(Felix.java:2064)
        at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1291)

        at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStart
LevelImpl.java:304)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassNotFoundException: at.ac.tuwien.auto.iotsys.gateway.ob
ix.objects.knx.datapoint.DataPoint not found by at.ac.tuwien.auto.iotsys.gateway
 [9]
        at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDele
gation(BundleWiringImpl.java:1532)
        at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringIm
pl.java:75)
        at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadCla
ss(BundleWiringImpl.java:1955)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        ... 10 more
2013-07-31 13:10:34 [at.ac.tuwien.auto.iotsys.gateway.connectors.knx.KNXBundleAc
tivator] INFO - Starting KNX connector
2013-07-31 13:10:34 [at.ac.tuwien.auto.iotsys.gateway.connectors.knx.KNXBundleAc
tivator] SEVERE - Could not find a running object broker to register devices!
ERROR: Bundle at.ac.tuwien.auto.iotsys.mdnssd [11] Error starting file:/C:/iotsy
s/felix-framework-4.2.1/bundle/iotsys-mdnssd-0.1.jar (org.osgi.framework.BundleE
xception: Not found: at.ac.tuwien.auto.iotsys.mdnssd.MDnssdActivator)
java.lang.ClassNotFoundException: at.ac.tuwien.auto.iotsys.mdnssd.MDnssdActivato
r not found by at.ac.tuwien.auto.iotsys.mdnssd [11]
        at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDele
gation(BundleWiringImpl.java:1532)
        at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringIm
pl.java:75)
        at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadCla
ss(BundleWiringImpl.java:1955)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at org.apache.felix.framework.BundleWiringImpl.getClassByDelegation(Bund
leWiringImpl.java:1374)
        at org.apache.felix.framework.Felix.createBundleActivator(Felix.java:432
9)
        at org.apache.felix.framework.Felix.activateBundle(Felix.java:2141)
        at org.apache.felix.framework.Felix.startBundle(Felix.java:2064)
        at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1291)

        at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStart
LevelImpl.java:304)
        at java.lang.Thread.run(Unknown Source)
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.gateway.connectors.virtual.Virtual
BundleActivator] INFO - Starting Virtual connector
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.gateway.connectors.virtual.Virtual
BundleActivator] SEVERE - Could not find a running object broker to register dev
ices!
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.gateway.connector.wmbus.WMBusBundl
eActivator] INFO - Starting WMBUS connector
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.gateway.connector.wmbus.WMBusBundl
eActivator] SEVERE - Could not find a running object broker to register devices!

2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.xacml.PDPBundleActivator] INFO - X
ACML module enabled: false
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.gateway.connectors.xbee.XBeeBundle
Activator] INFO - Starting XBee connector
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.gateway.connectors.xbee.XBeeBundle
Activator] SEVERE - Could not find a running object broker to register devices!
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.control.TestClientActivator] INFO
- Service changed.
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.control.TestClientActivator] INFO
- Service changed.
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.control.TestClientActivator] INFO
- Service changed.
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.control.TestClientActivator] INFO
- Service changed.
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.control.TestClientActivator] INFO
- Service changed.
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.control.TestClientActivator] INFO
- Service changed.
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.control.TestClientActivator] INFO
- Service changed.
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.control.TestClientActivator] INFO
- Service changed.
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.control.TestClientActivator] INFO
- Service changed.
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.control.TestClientActivator] INFO
- Service changed.
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.control.TestClientActivator] INFO
- Service changed.
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.control.TestClientActivator] INFO
- Service changed.
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.control.TestClientActivator] INFO
- Service changed.
2013-07-31 13:10:35 [at.ac.tuwien.auto.iotsys.control.TestClientActivator] INFO
- Service changed.
____________________________
Welcome to Apache Felix Gogo

g!

Original issue reported on code.google.com by mishoboss on 31 Jul 2013 at 10:15

Mobiler user interface

Generic android user interface for the oBIX server exploiting the CoAP features 
and providing a generic interace for oBIX object interaction and illustration 
and filtering of oBIX histories.

Original issue reported on code.google.com by [email protected] on 7 Mar 2013 at 3:06

Security

The gateway needs to be enhanced with security features including mechanisms to 
authenticate clients, authorize access and encrypt communication.

For application layer security the oBIX SOAP interface can be security by 
applying WS-Security. For the RESTful interfaces at the application layer XML 
Signature and XML Encryption can be used.

For transport layer security TLS/SSL can be applied either for the TCP based 
interfaces or DLTS for the UDP based interface.

Original issue reported on code.google.com by [email protected] on 7 Mar 2013 at 8:25

oBIX server redesign

The oBIX server needs to be redesigned. Currently the design is fine for a 
rough prototype but the ojbect broker requires and the HTTP and CoAP server 
strongly need a redesign, since a lot of stuff is hardcoded. 

The identification of oBIX objects within the object broker needs to be made 
independent of the underlying protocol and it should be transparent if an 
object is addressed by the unique IPv6 address or the context path of the 
centralized IPv6 interface. This influences the encoding of the oBIX objects 
and has further side effects that need to be considered.

Original issue reported on code.google.com by [email protected] on 7 Mar 2013 at 8:35