This document provides instructions for developing a first application using FI-WARE by connecting sensors to the FI-WARE IoT backend. It discusses connecting a basic Z-Wave sensor pack to the backend using FIGWAY software on a Raspberry Pi. The steps include including sensors in a Z-Wave network, editing registration and observation scripts to specify sensor IDs and callback URLs, registering sensors using fizway_register, and running fizway to interconnect sensors to the backend. Configuration files and ports for different sensor types like switches are also outlined. The goal is to enable sharing sensor data in FI-WARE's IoT Challenge HUB spreadsheet by connecting low-cost hardware to FI-WARE open APIs.
The document discusses Orion Context Broker, which is a context management enabler in FI-WARE. It intermediates between context producers and consumers. Orion stores context information using the NGSI information model, which represents context data as entities with attributes. Orion provides a RESTful NGSI API to allow updating, querying and subscribing to context changes. The document provides an overview of how Orion works and its role in FI-WARE applications.
FIWARE: Managing Context Information at large scale
This presentation describes how context management is implemented in FIWARE platform, base don Orion Context Broker GEri. Both basic usage of Context Broker and advanced topics are included.
This document provides an overview of Generic Enablers in the FIWARE platform. It describes Generic Enablers as reusable building blocks that provide common functions across multiple use cases and sectors. The Generic Enablers are divided into 7 technical chapters, including data/context management, interfaces to network and devices, security, and applications/services. Specific Enablers are also described as components that offer domain-specific functions for areas like manufacturing, media, healthcare, energy, and agrifood.
1) The document discusses Orion Context Broker, which is a component of the FI-WARE platform that intermediates between context producers and consumers to manage context data or context information.
2) Context information always relates to "entities" and has a name, type, and value. Orion Context Broker uses the NGSI information model and stores context information along with metadata in a database.
3) Orion Context Broker provides REST APIs for context availability management and context management to update, query, and subscribe to context information from distributed context sources.
FIWARE aims to transform the future internet by providing open-source generic enablers (GEs) through APIs that can be combined to build applications. These GEs include functions for context data management, big data analysis, device connectivity, and more. FIWARE also offers resources like the FIWARE Lab test environment and FIWARE Academy training to help developers build innovative applications that integrate diverse data and devices. The goal is for FIWARE to become the standard platform for the internet of things and smart cities.
This document provides instructions for 8 exercises involving deploying and using an IoT Agent to connect IoT devices to the FIWARE Context Broker. The exercises cover tasks like deploying an IoT Agent, provisioning devices, registering devices using the LWM2M protocol, retrieving and updating sensor data, detecting new data providers, customizing attribute mappings, and provisioning device groups. Contact information is provided for getting help with the exercises.
FIWARE NGSI: Managing Context Information at Large Scale
FIWARE NGSI: Managing Context Information at Large Scale, by Fermín Galán.
Orion Context Broker developing team. 1st FIWARE Summit, Málaga, Dec. 13-15, 2016.
This document discusses connecting IoT devices and systems to the FIWARE Lab ecosystem. It provides an overview of the FIWARE IoT proposal and community. It then describes the most common scenarios for connecting IoT providers and consumers to the FIWARE Context Broker using the IDAS/SBC Ultralight 2.0 protocol. Step-by-step instructions are provided for registering models and devices and sending measurements and commands. Additional options for connecting IoT systems like MQTT and LWM2M are also mentioned.
The Synchronization GE provides a generic scene data model and real-time two-way synchronization mechanism for multi-user web applications. It uses an entity-component-attribute structure to represent synchronized data and WebSockets to transmit updates between clients and servers. Developers can leverage the GE's synchronization capabilities to add real-time collaboration features to their applications without building these components from scratch.
The document discusses connecting IoT devices to the FIWARE IoT platform. It provides steps to connect a device using the UltraLight 2.0 protocol:
1. Specify connection details for the IoT Agent (IDAS) like IP, ports and API key.
2. Create a device model or use an existing one for the sensor type.
3. Register the device by creating an asset using the REST API and specifying the model.
4. Send observations from the device to IDAS using the UL 2.0 API, including the asset ID and API key.
5. Read the measurements from the Context Broker using NGSI queries to the asset entity.
This document provides instructions for developing a first application using the FI-WARE platform. It discusses the FI-WARE architecture, including key components like the context broker and Wirecloud. It then describes how to create widgets using Wirecloud, connecting them to context broker and other FI-WARE services. The document also explains how to include IoT devices in a Z-Wave network and register them with the FI-WARE IoT backend.
Nuxeo allows leveraging the OpenSocial standard within its platform. OpenSocial is a common standard used in enterprises that allows for easy development through HTTP, XML, JavaScript and RESTful APIs. Nuxeo includes both a full GWT container and a lightweight JavaScript container for simple gadget integration. It supports OAuth authentication and uses the OpenSocial standard, allowing gadgets from other containers like iGoogle to be used. Nuxeo also provides an automation JavaScript library and templates to simplify building gadgets that interface with the Nuxeo platform.
WebNet Conference 2012 - Designing complex applications using html5 and knock...
This document provides an overview of designing complex applications using HTML5 and KnockoutJS. It discusses HTML5 and why it is useful, introduces JavaScript and frameworks like KnockoutJS and SammyJS that help manage complexity. It also summarizes several JavaScript libraries and patterns including the module pattern, revealing module pattern, and MV* patterns. Specific libraries and frameworks discussed include RequireJS, AmplifyJS, UnderscoreJS, and LINQ.js. The document concludes with a brief mention of server-side tools like ScriptSharp.
Spark IT 2011 - Simplified Web Development using Java Server Faces 2.0
The document outlines new features in Java Server Faces (JSF) 2.0 including Facelets, composite components, integrated Ajax support, partial state saving, view parameters, system events, and resources. It provides examples of how these features can be used and notes they were inspired by other frameworks. The development and release of any features described remains at the sole discretion of Oracle.
[Srijan Wednesday Webinars] Ruling Drupal 8 with #d8rules
Speaker: Josef Dabernig a.k.a Dasjo
This webinar takes a look at how to automate some powerful backend capabilities for your Drupal site, using the Drupal 8 Rules. Take a look at how D8 Rules can change the way we build sites. Also, learn how you can contribute to getting Rules closer to a stable release.
Jetpack, with new features in 2021 GDG Georgetown IO Extended
Jetpack released new features in 2021 including:
- Compose integrations with libraries like Hilt, Paging, and Navigation.
- Improvements to CameraX, Room, DataStore, Navigation, and other libraries.
- New libraries like AppSearch, Macrobenchmark, and Google Shortcuts.
- Support for additional form factors with updates to libraries like Window and Wear.
- Many libraries reached stable versions or added new capabilities in alpha/beta stages.
Building the an End-to-End ASP.NET MVC 4, Entity Framework, HTML5, jQuery app...
This is a talk I gave at the spring 2013 AngleBrackets/DevIntersection conference in Las Vegas.
HTML5 is all the rage these days but where do you look to find robust examples of using it along with jQuery, client-side templates, Ajax calls, data access technologies, and more? In this session, Dan Wahlin will walk through an application that demonstrates how key HTML5 technologies can be integrated and used to present data to users in different ways. Topics covered include exposing data to the client using RESTful services created using the new ASP.NET Web API, using Handlebars templates to render data, JavaScript techniques for structuring code, the role of HTML5 semantic tags, as well as how technologies such as the canvas, SVG, and video can be used. If you want to learn server-side as well as client-side techniques and strategies then this session is for you.
TechDays 2013 Jari Kallonen: What's New WebForms 4.5
This document summarizes new features in ASP.NET WebForms 4.5, including strongly typed data controls, model binding, unobtrusive validation, HTML5 support, and asynchronous programming support. It provides code examples of using data binding, model binding with value providers, validation with data annotations and validation controls, and asynchronous code with the async and await keywords. The document demonstrates these new ASP.NET features.
Building Modern Apps using Android Architecture Components
Android architecture components are part of Android Jetpack. They are a collection of libraries that help you design robust, testable, and maintainable apps. In this talk, We will cover LiveData, ViewModel, Room and lifecycle components. We will go through practical code example to understand modern android app architecture especially MVVM architecture.
Build powerfull and smart web applications with Symfony2
Symfony2 first stable release is scheduled for the first week of March 2011. During this session, we will have a look at the new framework architecture and most of its powerfull features.
We will show you how Symfony2 implements the MVC pattern and an HTTP request is processed and converted as a response for the end user. Of course, we will talk about the configuration principles and how it's easy to configure Symfony2 project parts like the routing system or the data model. We will also focus on other major components of the framework like the Doctrine2 integration, forms, security (authentication and authorizations) or HTTP cache management.
This document summarizes Joone Hur's presentation on web standards support in WebKit. It discusses several new and emerging web APIs including custom protocol and content handlers, AddSearchProvider, Navigation Timing, device APIs for battery status, contacts, and media capture. It also covers the Unified Storage Quota API, Shadow DOM API, and notes that WebCL and WebKit2 have been added to Samsung and Nokia browsers.
This presentation was given at DevFest Twin Cities in 2013, and introduces droidQuery - the Android port of jQuery, that allows UI manipulation and traversal of the Android layout, asynchronous REST client calls, event handling, animations, and much more.
The Best Way to Become an Android Developer Expert with Android Jetpack
This document discusses how to become an expert Android developer using Android Jetpack. It recommends using Android Jetpack, which is a collection of components and libraries that make it easier to build Android apps. It describes some key components of Jetpack like architecture components like ViewModel and LiveData for lifecycle-aware data management. It also discusses other topics like navigation, testing, and architecture patterns that are important for Android development. The document encourages learning through online courses and emphasizes the importance of continuous learning and skills development for IT careers and the digital industry.
Sling is a RESTful web framework for building applications on top of Apache Jackrabbit. It allows resources like content, configurations, code, and binaries to be accessed over REST URLs. Sling maps URLs to resources rather than commands, supports various scripting languages as servlets, and has a modular OSGi-based architecture powered by Apache Felix. Examples shown include building a blog and coffee ordering application on Sling to demonstrate how it supports RESTful content creation and management.
This document discusses building mobile applications using PhoneGap, jQuery, and Dreamweaver. It provides an overview of different mobile application types including mobile HTML, web apps, hybrid apps, and native apps. It then demonstrates how to create hybrid mobile apps with PhoneGap and jQuery Mobile, including accessing device APIs, building user interfaces with jQuery Mobile, and creating customizable PhoneGap plugins.
This document discusses building mobile applications using PhoneGap, jQuery, and Dreamweaver. It provides an overview of different mobile application types including mobile HTML, web apps, hybrid apps, and native apps. It then demonstrates how to create hybrid mobile apps with PhoneGap and jQuery Mobile, including accessing device APIs, building user interfaces with jQuery Mobile, and creating lists and charts with JavaScript plugins. It also covers how to package and deploy the app to different platforms using PhoneGap.
Dojo is a JavaScript framework that helps build dynamic web applications. It provides tools and techniques to handle data, user interfaces, internationalization, and accessibility. Dojo includes data stores to retrieve and manage data, widgets to display data, and templating to generate interface code on the client-side. It also offers utilities to optimize application loading, such as file merging and minification.
The document discusses enhancing the OpenStack Horizon dashboard user interface with AngularJS. It provides an overview of OpenStack and Horizon architectures, and then describes how to add a new panel to Horizon using AngularJS. Key aspects covered include creating RESTful APIs, controllers, views, and templates to integrate new dynamic and client-side functionality within the existing Horizon framework. The approach allows cleaner separation of client and server code for improved user experience, testing, and development velocity.
The document introduces the Orion Context Broker, which is a component of the FIWARE platform for managing context information at large scale. It discusses how the Context Broker allows applications to gather and manage context data through its NGSI API. It provides examples of using the Context Broker to create entities and attributes, retrieve and update context data, subscribe to notifications, and perform batch operations.
The document provides an introduction to context management and the Orion Context Broker. It discusses:
- Implementing smart applications requires gathering and managing context information about entities and their attributes.
- The Orion Context Broker implements the NGSI API for managing context information and allows applications to create, retrieve, update, and delete entity attributes through RESTful operations.
- Context information can come from different sources like sensor networks, systems, and users, and the context broker acts as a common hub to integrate this information.
The document provides an introduction to context management and the Orion Context Broker. It discusses:
- Implementing smart applications requires gathering and managing context information about entities and their attributes.
- The Orion Context Broker implements the NGSI API for managing context information and allows applications to create, retrieve, update, and delete entity attributes through RESTful operations.
- Context information can come from different sources like sensor networks, systems, and users, and the context broker acts as a common hub to integrate this information.
The document introduces the Orion Context Broker, which is a component of the FIWARE platform for managing context information at large scale. It discusses how the Context Broker allows applications to gather and manage context data through its NGSI API. It provides examples of basic operations like creating and updating entities and attributes as well as more advanced operations like subscriptions and batch operations. The document recommends using Docker to easily install and run the Orion Context Broker for experimenting with its features and capabilities.
The document provides an introduction to context management and the Orion Context Broker. It discusses how context information from various sources can be gathered and managed to enable smart applications. The Orion Context Broker implements the NGSI API to allow easy management of context information through standard RESTful operations. Examples are given of creating, updating, and querying entity attributes to demonstrate basic usage.
Orion Context Broker NGSI-v2 Overview for Developers That Already Know NGSI-v...
NGSIv2 is a simplified and enhanced version of NGSIv1 that follows RESTful principles. Key improvements in NGSIv2 include simplified URLs and payloads, support for native JSON data types, improved filtering capabilities, geolocation support, datetime attributes, transient entities, and improved subscriptions and registrations. NGSIv2 provides a more developer-friendly API for managing context data compared to the legacy NGSIv1 version.
The document introduces the Orion Context Broker, which is a component of FIWARE that provides an API for managing context information. It describes how the Context Broker can be used to store and retrieve sensor data and other context data from various sources. It provides examples of creating entities and attributes, updating and querying data, and setting up subscriptions to receive notifications when data changes. The document recommends using Docker to easily install and run the Orion Context Broker for experimenting with its features and API.
Orion Context Broker NGSI-v2 Overview for Developers That Already Know NGSI-v...
- NGSIv2 is a revamped, simplified version of NGSIv1 that is designed to be more RESTful and developer-friendly.
- It supports native JSON data types for attributes, simplifies URLs and payloads, and improves capabilities for geolocation, datetime handling, and more.
- Some key enhancements in NGSIv2 include support for additional geoshapes beyond points, full datetime handling, and text-based operations for attribute values.
This document provides an introduction to FIWARE IoT. It discusses FIWARE IoT consumers and providers. For consumers, FIWARE provides a single point of access for IoT, open data, and other data through its context broker API and protocol. It supports querying and subscribing to entity and attribute changes. Typical IoT scenarios involve using the context broker to access observations and send commands. The document outlines two typical scenarios - a simple tested scenario and a more advanced native NGSI scenario still under testing. It also discusses FIWARE community events like hackathons that have helped develop IoT applications and engage developers.
The document discusses the Context Broker component in FIWARE. It describes how the Context Broker can manage context information at large scale, enabling applications to query and subscribe to context changes. It provides examples of using the Context Broker to create entities and attributes, update context data, query context information, and subscribe to context notifications. The Context Broker allows flexible context management through NGSI operations and convenience APIs.
The document summarizes FIWARE's IoT platform and the IDAS (IoT Device Management) component. It describes:
1) The typical IoT scenario supported by IDAS, which has been extensively tested and provides developers with measurements from simple sensors.
2) The modular architecture of the new IDAS 4.0, which uses separate IoT agents for different protocols like UL2.0, MQTT, LWM2M etc. This makes installation and extensions easier.
3) The available IoT agents for UL2.0, MQTT, LWM2M, SigFox and how to register devices and send measurements using the UL2.0 agent.
Orion Context Broker webminar 2014-04-01Fermin Galan
The document discusses Orion Context Broker, which is a context management enabler in FI-WARE. It intermediates between context producers and consumers. Orion stores context information using the NGSI information model, which represents context data as entities with attributes. Orion provides a RESTful NGSI API to allow updating, querying and subscribing to context changes. The document provides an overview of how Orion works and its role in FI-WARE applications.
FIWARE: Managing Context Information at large scaleFermin Galan
This presentation describes how context management is implemented in FIWARE platform, base don Orion Context Broker GEri. Both basic usage of Context Broker and advanced topics are included.
This document provides an overview of Generic Enablers in the FIWARE platform. It describes Generic Enablers as reusable building blocks that provide common functions across multiple use cases and sectors. The Generic Enablers are divided into 7 technical chapters, including data/context management, interfaces to network and devices, security, and applications/services. Specific Enablers are also described as components that offer domain-specific functions for areas like manufacturing, media, healthcare, energy, and agrifood.
1) The document discusses Orion Context Broker, which is a component of the FI-WARE platform that intermediates between context producers and consumers to manage context data or context information.
2) Context information always relates to "entities" and has a name, type, and value. Orion Context Broker uses the NGSI information model and stores context information along with metadata in a database.
3) Orion Context Broker provides REST APIs for context availability management and context management to update, query, and subscribe to context information from distributed context sources.
FIWARE aims to transform the future internet by providing open-source generic enablers (GEs) through APIs that can be combined to build applications. These GEs include functions for context data management, big data analysis, device connectivity, and more. FIWARE also offers resources like the FIWARE Lab test environment and FIWARE Academy training to help developers build innovative applications that integrate diverse data and devices. The goal is for FIWARE to become the standard platform for the internet of things and smart cities.
This document provides instructions for 8 exercises involving deploying and using an IoT Agent to connect IoT devices to the FIWARE Context Broker. The exercises cover tasks like deploying an IoT Agent, provisioning devices, registering devices using the LWM2M protocol, retrieving and updating sensor data, detecting new data providers, customizing attribute mappings, and provisioning device groups. Contact information is provided for getting help with the exercises.
FIWARE NGSI: Managing Context Information at Large ScaleFIWARE
FIWARE NGSI: Managing Context Information at Large Scale, by Fermín Galán.
Orion Context Broker developing team. 1st FIWARE Summit, Málaga, Dec. 13-15, 2016.
This document discusses connecting IoT devices and systems to the FIWARE Lab ecosystem. It provides an overview of the FIWARE IoT proposal and community. It then describes the most common scenarios for connecting IoT providers and consumers to the FIWARE Context Broker using the IDAS/SBC Ultralight 2.0 protocol. Step-by-step instructions are provided for registering models and devices and sending measurements and commands. Additional options for connecting IoT systems like MQTT and LWM2M are also mentioned.
The Synchronization GE provides a generic scene data model and real-time two-way synchronization mechanism for multi-user web applications. It uses an entity-component-attribute structure to represent synchronized data and WebSockets to transmit updates between clients and servers. Developers can leverage the GE's synchronization capabilities to add real-time collaboration features to their applications without building these components from scratch.
The document discusses connecting IoT devices to the FIWARE IoT platform. It provides steps to connect a device using the UltraLight 2.0 protocol:
1. Specify connection details for the IoT Agent (IDAS) like IP, ports and API key.
2. Create a device model or use an existing one for the sensor type.
3. Register the device by creating an asset using the REST API and specifying the model.
4. Send observations from the device to IDAS using the UL 2.0 API, including the asset ID and API key.
5. Read the measurements from the Context Broker using NGSI queries to the asset entity.
Developing your first application using FIWAREFIWARE
This document provides instructions for developing a first application using the FI-WARE platform. It discusses the FI-WARE architecture, including key components like the context broker and Wirecloud. It then describes how to create widgets using Wirecloud, connecting them to context broker and other FI-WARE services. The document also explains how to include IoT devices in a Z-Wave network and register them with the FI-WARE IoT backend.
Nuxeo allows leveraging the OpenSocial standard within its platform. OpenSocial is a common standard used in enterprises that allows for easy development through HTTP, XML, JavaScript and RESTful APIs. Nuxeo includes both a full GWT container and a lightweight JavaScript container for simple gadget integration. It supports OAuth authentication and uses the OpenSocial standard, allowing gadgets from other containers like iGoogle to be used. Nuxeo also provides an automation JavaScript library and templates to simplify building gadgets that interface with the Nuxeo platform.
WebNet Conference 2012 - Designing complex applications using html5 and knock...Fabio Franzini
This document provides an overview of designing complex applications using HTML5 and KnockoutJS. It discusses HTML5 and why it is useful, introduces JavaScript and frameworks like KnockoutJS and SammyJS that help manage complexity. It also summarizes several JavaScript libraries and patterns including the module pattern, revealing module pattern, and MV* patterns. Specific libraries and frameworks discussed include RequireJS, AmplifyJS, UnderscoreJS, and LINQ.js. The document concludes with a brief mention of server-side tools like ScriptSharp.
Spark IT 2011 - Simplified Web Development using Java Server Faces 2.0Arun Gupta
The document outlines new features in Java Server Faces (JSF) 2.0 including Facelets, composite components, integrated Ajax support, partial state saving, view parameters, system events, and resources. It provides examples of how these features can be used and notes they were inspired by other frameworks. The development and release of any features described remains at the sole discretion of Oracle.
[Srijan Wednesday Webinars] Ruling Drupal 8 with #d8rulesSrijan Technologies
Speaker: Josef Dabernig a.k.a Dasjo
This webinar takes a look at how to automate some powerful backend capabilities for your Drupal site, using the Drupal 8 Rules. Take a look at how D8 Rules can change the way we build sites. Also, learn how you can contribute to getting Rules closer to a stable release.
Jetpack, with new features in 2021 GDG Georgetown IO ExtendedToru Wonyoung Choi
Jetpack released new features in 2021 including:
- Compose integrations with libraries like Hilt, Paging, and Navigation.
- Improvements to CameraX, Room, DataStore, Navigation, and other libraries.
- New libraries like AppSearch, Macrobenchmark, and Google Shortcuts.
- Support for additional form factors with updates to libraries like Window and Wear.
- Many libraries reached stable versions or added new capabilities in alpha/beta stages.
Building the an End-to-End ASP.NET MVC 4, Entity Framework, HTML5, jQuery app...Dan Wahlin
This is a talk I gave at the spring 2013 AngleBrackets/DevIntersection conference in Las Vegas.
HTML5 is all the rage these days but where do you look to find robust examples of using it along with jQuery, client-side templates, Ajax calls, data access technologies, and more? In this session, Dan Wahlin will walk through an application that demonstrates how key HTML5 technologies can be integrated and used to present data to users in different ways. Topics covered include exposing data to the client using RESTful services created using the new ASP.NET Web API, using Handlebars templates to render data, JavaScript techniques for structuring code, the role of HTML5 semantic tags, as well as how technologies such as the canvas, SVG, and video can be used. If you want to learn server-side as well as client-side techniques and strategies then this session is for you.
TechDays 2013 Jari Kallonen: What's New WebForms 4.5Tieturi Oy
This document summarizes new features in ASP.NET WebForms 4.5, including strongly typed data controls, model binding, unobtrusive validation, HTML5 support, and asynchronous programming support. It provides code examples of using data binding, model binding with value providers, validation with data annotations and validation controls, and asynchronous code with the async and await keywords. The document demonstrates these new ASP.NET features.
Building Modern Apps using Android Architecture ComponentsHassan Abid
Android architecture components are part of Android Jetpack. They are a collection of libraries that help you design robust, testable, and maintainable apps. In this talk, We will cover LiveData, ViewModel, Room and lifecycle components. We will go through practical code example to understand modern android app architecture especially MVVM architecture.
Build powerfull and smart web applications with Symfony2Hugo Hamon
Symfony2 first stable release is scheduled for the first week of March 2011. During this session, we will have a look at the new framework architecture and most of its powerfull features.
We will show you how Symfony2 implements the MVC pattern and an HTTP request is processed and converted as a response for the end user. Of course, we will talk about the configuration principles and how it's easy to configure Symfony2 project parts like the routing system or the data model. We will also focus on other major components of the framework like the Doctrine2 integration, forms, security (authentication and authorizations) or HTTP cache management.
This document summarizes Joone Hur's presentation on web standards support in WebKit. It discusses several new and emerging web APIs including custom protocol and content handlers, AddSearchProvider, Navigation Timing, device APIs for battery status, contacts, and media capture. It also covers the Unified Storage Quota API, Shadow DOM API, and notes that WebCL and WebKit2 have been added to Samsung and Nokia browsers.
This presentation was given at DevFest Twin Cities in 2013, and introduces droidQuery - the Android port of jQuery, that allows UI manipulation and traversal of the Android layout, asynchronous REST client calls, event handling, animations, and much more.
The Best Way to Become an Android Developer Expert with Android JetpackAhmad Arif Faizin
This document discusses how to become an expert Android developer using Android Jetpack. It recommends using Android Jetpack, which is a collection of components and libraries that make it easier to build Android apps. It describes some key components of Jetpack like architecture components like ViewModel and LiveData for lifecycle-aware data management. It also discusses other topics like navigation, testing, and architecture patterns that are important for Android development. The document encourages learning through online courses and emphasizes the importance of continuous learning and skills development for IT careers and the digital industry.
Sling is a RESTful web framework for building applications on top of Apache Jackrabbit. It allows resources like content, configurations, code, and binaries to be accessed over REST URLs. Sling maps URLs to resources rather than commands, supports various scripting languages as servlets, and has a modular OSGi-based architecture powered by Apache Felix. Examples shown include building a blog and coffee ordering application on Sling to demonstrate how it supports RESTful content creation and management.
This document discusses building mobile applications using PhoneGap, jQuery, and Dreamweaver. It provides an overview of different mobile application types including mobile HTML, web apps, hybrid apps, and native apps. It then demonstrates how to create hybrid mobile apps with PhoneGap and jQuery Mobile, including accessing device APIs, building user interfaces with jQuery Mobile, and creating customizable PhoneGap plugins.
This document discusses building mobile applications using PhoneGap, jQuery, and Dreamweaver. It provides an overview of different mobile application types including mobile HTML, web apps, hybrid apps, and native apps. It then demonstrates how to create hybrid mobile apps with PhoneGap and jQuery Mobile, including accessing device APIs, building user interfaces with jQuery Mobile, and creating lists and charts with JavaScript plugins. It also covers how to package and deploy the app to different platforms using PhoneGap.
Dojo is a JavaScript framework that helps build dynamic web applications. It provides tools and techniques to handle data, user interfaces, internationalization, and accessibility. Dojo includes data stores to retrieve and manage data, widgets to display data, and templating to generate interface code on the client-side. It also offers utilities to optimize application loading, such as file merging and minification.
The document discusses enhancing the OpenStack Horizon dashboard user interface with AngularJS. It provides an overview of OpenStack and Horizon architectures, and then describes how to add a new panel to Horizon using AngularJS. Key aspects covered include creating RESTful APIs, controllers, views, and templates to integrate new dynamic and client-side functionality within the existing Horizon framework. The approach allows cleaner separation of client and server code for improved user experience, testing, and development velocity.
Similar to Developing your first application using FI-WARE (20)
Orion Context Broker introduction 20240227Fermin Galan
The document introduces the Orion Context Broker, which is a component of the FIWARE platform for managing context information at large scale. It discusses how the Context Broker allows applications to gather and manage context data through its NGSI API. It provides examples of using the Context Broker to create entities and attributes, retrieve and update context data, subscribe to notifications, and perform batch operations.
Orion Context Broker introduction 20240115Fermin Galan
The document provides an introduction to context management and the Orion Context Broker. It discusses:
- Implementing smart applications requires gathering and managing context information about entities and their attributes.
- The Orion Context Broker implements the NGSI API for managing context information and allows applications to create, retrieve, update, and delete entity attributes through RESTful operations.
- Context information can come from different sources like sensor networks, systems, and users, and the context broker acts as a common hub to integrate this information.
The document provides an introduction to context management and the Orion Context Broker. It discusses:
- Implementing smart applications requires gathering and managing context information about entities and their attributes.
- The Orion Context Broker implements the NGSI API for managing context information and allows applications to create, retrieve, update, and delete entity attributes through RESTful operations.
- Context information can come from different sources like sensor networks, systems, and users, and the context broker acts as a common hub to integrate this information.
The document introduces the Orion Context Broker, which is a component of the FIWARE platform for managing context information at large scale. It discusses how the Context Broker allows applications to gather and manage context data through its NGSI API. It provides examples of basic operations like creating and updating entities and attributes as well as more advanced operations like subscriptions and batch operations. The document recommends using Docker to easily install and run the Orion Context Broker for experimenting with its features and capabilities.
The document provides an introduction to context management and the Orion Context Broker. It discusses how context information from various sources can be gathered and managed to enable smart applications. The Orion Context Broker implements the NGSI API to allow easy management of context information through standard RESTful operations. Examples are given of creating, updating, and querying entity attributes to demonstrate basic usage.
Orion Context Broker NGSI-v2 Overview for Developers That Already Know NGSI-v...Fermin Galan
NGSIv2 is a simplified and enhanced version of NGSIv1 that follows RESTful principles. Key improvements in NGSIv2 include simplified URLs and payloads, support for native JSON data types, improved filtering capabilities, geolocation support, datetime attributes, transient entities, and improved subscriptions and registrations. NGSIv2 provides a more developer-friendly API for managing context data compared to the legacy NGSIv1 version.
The document introduces the Orion Context Broker, which is a component of FIWARE that provides an API for managing context information. It describes how the Context Broker can be used to store and retrieve sensor data and other context data from various sources. It provides examples of creating entities and attributes, updating and querying data, and setting up subscriptions to receive notifications when data changes. The document recommends using Docker to easily install and run the Orion Context Broker for experimenting with its features and API.
Orion Context Broker NGSI-v2 Overview for Developers That Already Know NGSI-v...Fermin Galan
- NGSIv2 is a revamped, simplified version of NGSIv1 that is designed to be more RESTful and developer-friendly.
- It supports native JSON data types for attributes, simplifies URLs and payloads, and improves capabilities for geolocation, datetime handling, and more.
- Some key enhancements in NGSIv2 include support for additional geoshapes beyond points, full datetime handling, and text-based operations for attribute values.
The document introduces the Orion Context Broker, which is a component of FIWARE that provides an API for managing context information. It describes how the Context Broker can be used to gather and share contextual data from various sources to enable smart applications. Key features of the Context Broker include allowing context producers to publish and update data, consumers to retrieve data through queries, and consumers to subscribe to receive notifications about data updates through subscriptions. Examples are provided for common operations like creating and updating entities, attributes, subscriptions, and using filters.
The document introduces the Orion Context Broker, which is a component of FIWARE that provides an API for managing context information. It describes how the Context Broker can be used to gather and share contextual data from various sources to enable smart applications. Key features of the Context Broker include allowing context producers to publish and update data, consumers to retrieve data through queries and subscribe to notifications, and batch operations for multiple updates. Usage examples demonstrate basic operations for managing entity attributes that represent contextual data.
Orion Context Broker NGSI-v2 Overview for Developers That Already Know NGSI-v...Fermin Galan
NGSIv2 is a simplified and enhanced version of NGSIv1 that follows RESTful principles. Key improvements in NGSIv2 include simplified URLs and payloads, support for native JSON data types, improved filtering capabilities, geolocation support, datetime attributes, transient entities, and improved subscriptions and registrations. NGSIv2 aims to make the API more developer-friendly while enhancing functionality.
Orion Context Broker NGSI-v2 Overview for Developers That Already Know NGSI-v...Fermin Galan
- NGSIv2 is a simplified and enhanced version of NGSIv1 that follows RESTful principles. It supports native JSON data types, simplified URLs and payloads, and improved filtering, subscriptions, and other features.
- NGSIv2 supports location attributes as point, line, box, polygon or GeoJSON objects. It also supports datetime attributes in ISO 8601 format with milliseconds precision and timezones.
- The document provides an overview of the key differences and improvements in NGSIv2 compared to the legacy NGSIv1 API.
The document introduces the Orion Context Broker, which is a component of FIWARE that provides an API for managing context information. It describes how the Context Broker can be used to gather and share contextual data from various sources to enable smart applications. Key features of the Context Broker include allowing context producers to publish and update data, consumers to retrieve data through queries, and consumers to subscribe to receive notifications about data updates through subscriptions. Examples are provided for common operations like creating and updating entities, attributes, subscriptions, and using filters.
Orion Context Broker NGSI-v2 Overview for Developers That Already Know NGSI-v...Fermin Galan
NGSIv2 is a simplified and enhanced version of NGSIv1 that follows RESTful principles. Key improvements in NGSIv2 include simplified URLs and payloads, support for native JSON data types, improved filtering capabilities, geolocation support, datetime attributes, transient entities, and improved subscriptions and registrations. NGSIv2 aims to make the API more developer-friendly while enhancing functionality.
The document introduces the Orion Context Broker, which is a component of FIWARE that provides an API for managing context information. It describes how the Context Broker can be used to gather and share contextual data from various sources to enable smart applications. Key features of the Context Broker include allowing context producers to publish and update data, consumers to retrieve data through queries and subscribe to receive updates, and batch operations for multiple entities. Usage examples are provided for common operations like creating, updating, and querying entity attributes.
Orion Context Broker NGSI-v2 Overview for Developers That Already Know NGSI-v...Fermin Galan
NGSIv2 is a simplified and enhanced version of NGSIv1 that provides a more RESTful API with simplified URLs and payloads. It supports native JSON data types, text-based attribute access, improved geolocation and datetime capabilities, and transient entities among other features. NGSIv2 is the recommended API to use going forward as it has been designed with REST principles in mind from the start.
The document provides an introduction to context management and the Orion Context Broker:
- It discusses how context information (entity attributes) must be gathered and managed to implement smart applications. Context is relevant across many domains like smart homes and cities.
- The Orion Context Broker uses the NGSI standard API to manage context information and acts as a hub to integrate information from different sources like sensors and existing systems.
- Basic operations of the Context Broker like creating, updating, and querying entities and attributes are described through examples using cars and rooms.
Orion Context Broker NGSI-v2 Overview for Developers That Already Know NGSI-v...Fermin Galan
NGSIv2 is a simplified and enhanced version of NGSIv1 that follows RESTful principles. Key improvements in NGSIv2 include simplified URLs and payloads, support for native JSON data types, direct text-based retrieval and setting of attribute values, improved geolocation and datetime handling, support for transient entities, and more powerful filtering capabilities for both queries and subscriptions. NGSIv2 is the recommended version going forward as it is more stable, scalable, and developer-friendly compared to the legacy NGSIv1 API.
The document provides an introduction to context management and the Orion Context Broker in FIWARE. It discusses how context information from various sources can be gathered and managed to enable smart applications. The Orion Context Broker implements the NGSI API to allow easy creation, retrieval, update and deletion of context entities and their attributes through RESTful operations. Examples demonstrate how to create entities and attributes, retrieve and update their values, create subscriptions to receive notifications, and use batch operations.
Delegation Inheritance in Odoo 17 and Its Use CasesCeline George
There are 3 types of inheritance in odoo Classical, Extension, and Delegation. Delegation inheritance is used to sink other models to our custom model. And there is no change in the views. This slide will discuss delegation inheritance and its use cases in odoo 17.
How to Add Colour Kanban Records in Odoo 17 NotebookCeline George
In Odoo 17, you can enhance the visual appearance of your Kanban view by adding color-coded records using the Notebook feature. This allows you to categorize and distinguish between different types of records based on specific criteria. By adding colors, you can quickly identify and prioritize tasks or items, improving organization and efficiency within your workflow.
How to Show Sample Data in Tree and Kanban View in Odoo 17Celine George
In Odoo 17, sample data serves as a valuable resource for users seeking to familiarize themselves with the functionalities and capabilities of the software prior to integrating their own information. In this slide we are going to discuss about how to show sample data to a tree view and a kanban view.
Front Desk Management in the Odoo 17 ERPCeline George
Front desk officers are responsible for taking care of guests and customers. Their work mainly involves interacting with customers and business partners, either in person or through phone calls.
How to Store Data on the Odoo 17 WebsiteCeline George
Here we are going to discuss how to store data in Odoo 17 Website.
It includes defining a model with few fields in it. Add demo data into the model using data directory. Also using a controller, pass the values into the template while rendering it and display the values in the website.
The Jewish Trinity : Sabbath,Shekinah and Sanctuary 4.pdfJackieSparrow3
we may assume that God created the cosmos to be his great temple, in which he rested after his creative work. Nevertheless, his special revelatory presence did not fill the entire earth yet, since it was his intention that his human vice-regent, whom he installed in the garden sanctuary, would extend worldwide the boundaries of that sanctuary and of God’s presence. Adam, of course, disobeyed this mandate, so that humanity no longer enjoyed God’s presence in the little localized garden. Consequently, the entire earth became infected with sin and idolatry in a way it had not been previously before the fall, while yet in its still imperfect newly created state. Therefore, the various expressions about God being unable to inhabit earthly structures are best understood, at least in part, by realizing that the old order and sanctuary have been tainted with sin and must be cleansed and recreated before God’s Shekinah presence, formerly limited to heaven and the holy of holies, can dwell universally throughout creation
Split Shifts From Gantt View in the Odoo 17Celine George
Odoo allows users to split long shifts into multiple segments directly from the Gantt view.Each segment retains details of the original shift, such as employee assignment, start time, end time, and specific tasks or descriptions.
AI Risk Management: ISO/IEC 42001, the EU AI Act, and ISO/IEC 23894PECB
As artificial intelligence continues to evolve, understanding the complexities and regulations regarding AI risk management is more crucial than ever.
Amongst others, the webinar covers:
• ISO/IEC 42001 standard, which provides guidelines for establishing, implementing, maintaining, and continually improving AI management systems within organizations
• insights into the European Union's landmark legislative proposal aimed at regulating AI
• framework and methodologies prescribed by ISO/IEC 23894 for identifying, assessing, and mitigating risks associated with AI systems
Presenters:
Miriama Podskubova - Attorney at Law
Miriama is a seasoned lawyer with over a decade of experience. She specializes in commercial law, focusing on transactions, venture capital investments, IT, digital law, and cybersecurity, areas she was drawn to through her legal practice. Alongside preparing contract and project documentation, she ensures the correct interpretation and application of European legal regulations in these fields. Beyond client projects, she frequently speaks at conferences on cybersecurity, online privacy protection, and the increasingly pertinent topic of AI regulation. As a registered advocate of Slovak bar, certified data privacy professional in the European Union (CIPP/e) and a member of the international association ELA, she helps both tech-focused startups and entrepreneurs, as well as international chains, to properly set up their business operations.
Callum Wright - Founder and Lead Consultant Founder and Lead Consultant
Callum Wright is a seasoned cybersecurity, privacy and AI governance expert. With over a decade of experience, he has dedicated his career to protecting digital assets, ensuring data privacy, and establishing ethical AI governance frameworks. His diverse background includes significant roles in security architecture, AI governance, risk consulting, and privacy management across various industries, thorough testing, and successful implementation, he has consistently delivered exceptional results.
Throughout his career, he has taken on multifaceted roles, from leading technical project management teams to owning solutions that drive operational excellence. His conscientious and proactive approach is unwavering, whether he is working independently or collaboratively within a team. His ability to connect with colleagues on a personal level underscores his commitment to fostering a harmonious and productive workplace environment.
Date: June 26, 2024
Tags: ISO/IEC 42001, Artificial Intelligence, EU AI Act, ISO/IEC 23894
-------------------------------------------------------------------------------
Find out more about ISO training and certification services
Training: ISO/IEC 42001 Artificial Intelligence Management System - EN | PECB
Webinars: https://pecb.com/webinars
Article: https://pecb.com/article
-------------------------------------------------------------------------------
Principles of Roods Approach!!!!!!!.pptxibtesaam huma
Principles of Rood’s Approach
Treatment technique used in physiotherapy for neurological patients which aids them to recover and improve quality of life
Facilitatory techniques
Inhibitory techniques
Credit limit improvement system in odoo 17Celine George
In Odoo 17, confirmed and uninvoiced sales orders are now factored into a partner's total receivables. As a result, the credit limit warning system now considers this updated calculation, leading to more accurate and effective credit management.
How to Handle the Separate Discount Account on Invoice in Odoo 17Celine George
In Odoo, separate discount account can be set up to accurately track and manage discounts applied on various transaction and ensure precise financial reporting and analysis
NLC English 7 Consolidation Lesson plan for teacher
Developing your first application using FI-WARE
1. Open APIs for Open Minds
Fermín Galán Márquez (fermin@tid.es), Miguel Jimenez (mjimenez@fi.upm.es), Carlos Ralli (ralli@tid.es), Juanjo Hierro (jhierro@tid.es)
Telefónica I+D, Universidad Politécnica de Madrid
Developing your first application using FI-WARE
6. The NGSI information model
5
Meta-data
• Name
• Type
• Value
Context Element attributes
• Name
• Type
• Value
Context Element
• EntityId
• EntityType
1 n 1 n
“has” “has”
(We are not fully supporting
metadata right now)
Node Lamps
Electrical Regulator
Vans
Technicians
Issues
location TimeInstant
severity batteryCharge
illuminance
presence
electricPotential
…and many more (look to app code)
7. Typical Orion broker utilization steps
registerContext
updateContext
queryContext
subscribeContext
Creating new
context elements
“Write” context
elements
information
To different ways
of “reading”
context elements
information
subscribeContext
Availability
Getting aware of new
context elements
discoverContext
Availability
Look for existing
context elements
NGSI9 operation (context availability)
NGSI10 operation (context information)
8. Context platform available at Campus Party
7
Context
Broker Echo
server
1026
1028
notify
Global instance at
orion.lab.fi-ware.eu
(at FI-LAB cloud)
(Only for
demonstration
purposes during the
workshop)
Context
Broker
LiveDemo testbed
Backend Device Management
Context
Broker
Context
Broker
Context
Broker…
notify
notify
updateContext
notify
Dedicated instances at
http://yourvm:1026
“FI-WARE Cloud: bringing
OpenStack to the next level”
workshop (Wed 10-12am)
Nodes
AMMS
Regulator
Vans
NGSI enabled
SensorsNGSI enabled
SensorsNGSI enabled
Sensors
Shared!!!
13. To create my own application mashup…
Widgets and operators:
• Widgets can be developed with any Web technology (HTML, Flash, SVG…) that supports
JavaScript.
• Operators are coded in JavaScript
Both widgets and operators can be easily adapted from existing ones, or created from scratch
Open Widget API
• JavaScript API
• Core Widgets Functionality:
› gain access to external resources (cross-domain problem)
› wiring
› preferences
› …
12
14. How to develop a widget?
Setting up the development environment
• Eclipse, VIM, etc...
• Creating the directory structure (WGT)
Creating the widget:
• Create the template of the widget (config.xml)
• Widget view: an HTML file + CSS
• Widget app logic: JavaScript (using Widget API)
Testing your widget
• Uploading the widget to Local Catalogue
› The WGT file is a ZIP file renamed to .wgt
• Add widget to a mashup
› Wiring, preferences, layout…
13
15. Widget structure
config.xml
• definition of the widget (based on WDL)
index.html
• main view file
• references JS and CSS resources
/js
• directory for JavaScript files
/css
• directory for CSS files
/images
• directory for images
/doc
• documentation
14
16. Config.xml
The mandatory config.xml file contains the WDL XML template needed to tell Wirecloud what the
widget looks like. This includes:
• Widget metadata (non-functional properties)
• User preferences
• Widget inputs and outputs (wiring)
• Link to the actual widget source code
• Default rendering information
15
17. Config.xml example (I)
<?xml version="1.0" encoding="UTF-8"?>
<Template xmlns="http://wirecloud.conwet.fi.upm.es/ns/template#">
<Catalog.ResourceDescription>
<Vendor>Company distributing the widget</Vendor>
<Name>Widget name</Name>
<Version>0.0.1</Version>
<DisplayName>Widget Example</DisplayName>
<Author>mjimenez</Author>
<Mail>mjimenez@fi.upm.es</Mail>
<Description>Full widget description to be shown in catalogue</Description>
<ImageURI>Absolute or relative path to display image</ImageURI>
<iPhoneImageURI>Path to imate to display on mobile devices</iPhoneImageURI>
<WikiURI>Path to widget doc</WikiURI>
</Catalog.ResourceDescription>
16
18. Config.xml example (II)
<Platform.Preferences>
<Preference name=”pref_name" type="text" description="…" />
</Platform.Preferences>
<Platform.Wiring>
<OutputEndpoint name="identifier"
type="text" label="Label to show on wiring"
description="description"
friendcode="same as compatible input endpoint friendcode"/>
<InputEndpoint name="identifier"
type="text" label="Label to show on wiring"
description="description"
friendcode="same as compatible output endpoint friendcode"/>
</Platform.Wiring>
<Platform.Link>
<XHTML href="index.html"/>
</Platform.Link>
<Platform.Rendering width="6" height="24"/>
</Template>
17
19. index.html example
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<script type="text/javascript" src="js/main.js"></script>
<link rel="stylesheet" type="text/css" href="css/style.css" />
</head>
<body>
<!– Create here or create by JavaScript ->
</body>
</html>
18
20. Using the Open Widget API
Accessing widget preferences
MashupPlatform.prefs.get("google_key")
MashupPlatform.prefs.set("color", "red")
MashupPlatform.prefs.registerCallback(callbackFunction)
Getting user login name
MashupPlatform.context.get("username");
19
22. Making a cross-domain HTTP request
Perform the invocation and register asynchronous call-backs:
MashupPlatform.http.makeRequest(url, {
method: 'GET',
onSuccess: function (transport) {
var response;
response = JSON.parse(transport.responseText);
...
},
onFailure: function (transport) {
onError();
}
});
21
23. Connecting a widget to NGSI
Register NGSI usage on config.xml
<Requirements> <Feature name="NGSI"/> </Requirements>
Send a notification through NGSI
var connection = new NGSI.Connection('http://orion.lab.fi-ware.eu');
connection.updateAttributes([{
entity: {
id: 'iss8',
type: 'Issue'
},
attributes:[{
name: 'technician',
contextValue: 'tech1'
}]
}], {
onSuccess: function () { //… },
onFailure: function () { //… }
});
22
24. Connecting a widget to NGSI
Subscribe for notifications on certain entities
var entityIdList = [
{type: 'Van', id: '.*', isPattern: true},
{type: 'Technician', id: '.*', isPattern: true}
];
var attributeList = null; var duration = 'PT3H'; var throttling = null;
var notifyConditions = [{
type: 'ONCHANGE', condValues: ['name', 'current_position']
}];
var options = {
flat: true,
onNotify: process_entities,
onSuccess: function (data) {
subscriptionId = data.subscriptionId;
refresh_interval = setInterval(refreshNGSISubscript, 1000*60*60*2);//2 hours
}
};
connection.createSubscription(entityIdList, attributeList, duration, throttling,
notifyConditions, options);
23
25. Using Object Storage from a widget
Register Object Storage usage on config.xml
<Requirements> <Feature name="ObjectStorage"/> </Requirements>
Upload a file
var object_storage = new ObjectStorageAPI(’<Object Storage instance url>');
var fileParts = ["<a id="a"><b id="b">hey!</b></a>"];
var myBlob = new Blob(fileParts, { "type" : "text/xml" });
object_storage.uploadFile('folder_name', myBlob, token, {
file_name: 'myFile.xml',
onSuccess: function () {
alert('File uploaded successfully');
},
onFailure: function () {
alert('Something went wrong while uploading the file');
}
});
24
26. Uploading your widget
Compress (zip) the widget contents
• Rename it as a .wgt file
Upload the WGT file to Local Catalogue through WireCloud web interface
25
28. Resources
You can always find the most updated documentation of Wirecloud in:
• http://conwet.fi.upm.es/wirecloud
User and Programmer Guide:
• https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Composition_Editor_-
_Wirecloud_Mashup_Platform_-_User_and_Programmer_Guide
Installation and Administration Guide:
• https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Composition_Editor_-
_Wirecloud_Mashup_Platform_-_Installation_and_Administration_Guide
Download from Github:
• Wirecloud source code: https://github.com/Wirecloud/wirecloud
• Widget's source code of FIWARE's Live Demo mashable application component):
https://github.com/wirecloud-fiware/live-demo-macs
Stuff for this workshop
• http://tinyurl.com/fiware-dropbox
27
https://mashup.lab.fi-ware.eu
29. Online videos
FIWARE Live Demo: http://www.youtube.com/watch?v=Wh_zPsLUg-8
ENVIROFI Demo: https://www.youtube.com/watch?v=yEXlLQYq7s4
Other videos:
• http://www.youtube.com/embed/d7_EG42AHJw - Building a mashup from Geowidgets linked to
geospatial services.
• http://www.youtube.com/embed/urDGWSnrbtE - Using operators in a mashup to allow widgets
to send tweets
• http://www.youtube.com/embed/kW0sXMxgMLI - An example of integration with the marketplace
and the catalogue GEs
28
34. Connecting a basic z-wave pack
http://m2m.telefonica.com
(A) SensorMLNGSI (B)
IDAS
CONTEXT
BROKER
Observations
Register
Obs.
Query
Download the PI image with FIGWAY software at: http://tinyurl.com/figway-img
35. HOW-TO Get Started - Z-wave basic pack
34
0) You need: a RaspberryPI + Razbian card plugged in its GPIO
1) Include your z-wave devices into your z-wave network
Complete your sensor details in our “IoT Challenge HUB doc”
https://docs.google.com/spreadsheet/ccc?key=0ArcymbqnpOfkdGNYUkpaTF9qRVhkOTFIYW14SkxaZ1E#gid=0
2) Edit "fizway_resgister” & "fizway" scripts
Update the Device_ID number of your sensors.
3) Edit the file SensorML/Register_SWITCH
Update the line containing the callback URL:
"<swe:value>http://1.0.0.1:9999</swe:value>”
-> Instead of 1.0.0.1 put the RaspberryPI public IP address
-> Instead of 9999 set the port the switch daemon will be listening (normally, 7777)
4) Check & Edit -if necessary- the figway "Config" file.
Normally, modifications aren't needed so you can skip (4).
A Config.example file is provided and comments should make this task really easy.
5) Register all your working sensors by executing
>./fizway_register
6) Launch the script to interconnect your sensors to FI-WARE IoT Backend:
>./fizway &
38. 1) Include devices into a z-wave Network
37
EXCLUDE
- Razberry exclusion mode
- Press 4IN1 inclusion button
INCLUDE
- Razberry inclusion mode
- Press 4IN1 Inclusion button
CONFIGURATION
- Select profile Aeon multisensor 1.18
- Press 4IN1 inclusion button 3 times
- Configure to send Group1 all obs (720s)
39. 1) Include devices into a z-wave Network
EXCLUDE
- Razberry exclusion mode
- Press KEYFOB 4 buttons 5sec (led slow blink)
- Press button “1”, (try twice if it doesn’t work)
INCLUDE
- Razberry inclusion mode
- Press KEYFOB 4 buttons 5sec (led slow blink)
- Press button “1”
CONFIGURATION
- Configure remote KeyFob
To apply config: WAKE-UP Device
Press KEYFOB 4 buttons 5sec
- Press button “2” (Try twice)
Buttons in pair mode(1-3, 2-4):
-> SEPARATELY
Groups to send:
-> SWITCH ON/OFF ONLY (SEND BASIC SET)
40. 1) Include devices into a z-wave Network
39
EXCLUDE
- Razberry exclude mode
- Switch ON
- Press ON/OFF 3 times between 1,5sec
INCLUDE
- Razberry inclusion mode
- Switch ON
- Press ON/OFF 3 times between 1,5sec
NO CONFIG is needed.
ALL DEVICES INCLUDED.
DEVICES IDs SHOWN:
2 (4IN1), 3 (KEYFOB) , 4 (SWITCH)
41. 1) Include devices into a z-wave Network
40
CONFIGURATION
- Select Zwave Description Record:
Wintop iLED
EXCLUDE
- Razberry exclude mode
- Switch ON (use a screw-driver)
- Press ON 3 times between 1,5sec
INCLUDE
- Razberry exclude mode
- Switch ON (use a screw-driver)
- Press ON 3 times between 1,5sec
42. 1) Include devices into a z-wave Network
41
Provide your sensors to all: “IoT Challenge HUB doc”
https://docs.google.com/spreadsheet/ccc?key=0ArcymbqnpOfkdGNYUkpaTF9qRVhkOTFIYW14SkxaZ1E#gid=0
SHARE SENSORs IS A MUST
SHARE SWITCHES IS OPTIONAL
43. 2) Edit "fizway_resgister” & "fizway" scripts
42
Update correct IDs of your z-wave network (only for Devices you have)
Actuators ports should be: 7777, 7778, etc.
-> Update scripts “fizway_resgister” and “fizway”.
44. 3) Configure the SWITCH to receive commands
43
Set the IPv4 Address of your Raspberry PI. Port is SWITCH one (7777).
45. 4) Check & Edit the figway "Config" file
44
Pre-configured for IoT Challenge. No modifications are needed.
46. 5) Register all working devices in the Backend
45
Launch de script “./fizway_resgister”
For every device you’ll see a similar output as shown above.
If it works, your devices are correctly register in the IDAS Backend.
If it fails, increasing DEBUG level in the “Config” file helps a lot.
47. 6) Launch fizway script
46
Launch de script “./fizway &”
You may redirect the output to a log file if you’ close the window:
“./fizway >> ./fizway_log &”
You’ll see:
- Devices you are listening to and their Device Number (z-wave network ID).
- Daemons listening for Actuators commands coming from the Backend.
48. 47
Building your Fi-WARE IoT Apps
47
1) IDAS ADMIN API – Check Services, Subscriptions & Details
2) IDAS ADMIN API – Check Devices & Details
3) IDAS ADMIN API – Send a command to a z-wave Switch
4) IDAS ADMIN API - Subscribe your App to Devices Notifications
5) IDAS (or Global Context Broker) NGSI API – Get last observations of a device
6) WIRECLOUD API - Connect a Wirecloud widget
49. 48
Building your Fi-WARE IoT Apps
48
1) IDAS ADMIN API – Check Services, Subscriptions to Service & Service Details
51. 50
Building your Fi-WARE IoT Apps
50
3) IDAS ADMIN API – Send a command to a z-wave Switch
COMMANDs TO SWITCHES/DIMMERS
Follow “sendcommand” example.
Send: “FIZCOMMAND N”
N: 0-255. 0 = off, 255 = on
59. Useful additional references
Workshop Homepage http://tinyurl.com/fiware-cp-ws1
• Long URL: http://www.fi-ware.eu/campus-party-europedeveloping-your-first-
application-workshop
The FI-WARE Catalogue http://catalogue.fi-ware.eu
• With information about FI-WARE GEis, e.g. Orion Context Broker, Wirecloud,
etc.
Dropbox for Workshop stuff: http://tinyurl.com/fiware-dropbox
Dropbox for Raspberry Pi image: http://tinyurl.com/figway-img
• Use the following as backup in case of problems: http://130.206.82.17
58