OpenRemote is an open source project operating in the field of Domotics. OpenRemote develops and distributes a standard based platform that is extensible and flexible with applications to Home Automation, Energy Management and Healthcare. This community based project integrates varied field protocols (such as KXN, X10 and Z-Wave) in a common framework and allows for easy creation of visual panels. Open Remote supports the leading standard platforms iOS, Android and web. OpenRemote offers a variety of cloud-based tools which are aimed at simplifying the work of professionals as well as hobbyists.
After a quick business introduction, covering the business model, the raison d'etre for a standards based, open source platform in the crowded field of home automation, this presentation will address:
- the global architecture of the OpenRemote ecosystem and its components
- a detail presentation of each components, their role and the technologies used
- a short video of the great applications the community has used OpenRemote for
- an overview of the iOS console application
- the OpenRemote community
For more information, please consult the openremote.org website.
This presentation was made on Mon March 19th at the NSConference 2012.
Video recording will be available in the future from iDeveloperTV.
119. Some tech info
Still using iOS 3.2 as deployment target
Mainly an XML renderer
NSURLConnection & NSXMLParser
120. Some tech info
Still using iOS 3.2 as deployment target
Mainly an XML renderer
NSURLConnection & NSXMLParser
Experiments with SIP integration using linphone
My fellow developers, we are gathered here today to celebrate a union, a match made in heaven between inexpensive hardware and open source software.\n
My fellow developers, we are gathered here today to celebrate a union, a match made in heaven between inexpensive hardware and open source software.\n
All the “stuff” in the house\nWe want to control : push button -> light on\nbut also automate : after sunset and no rain -> irrigate\n
All the “stuff” in the house\nWe want to control : push button -> light on\nbut also automate : after sunset and no rain -> irrigate\n
All the “stuff” in the house\nWe want to control : push button -> light on\nbut also automate : after sunset and no rain -> irrigate\n
All the “stuff” in the house\nWe want to control : push button -> light on\nbut also automate : after sunset and no rain -> irrigate\n
All the “stuff” in the house\nWe want to control : push button -> light on\nbut also automate : after sunset and no rain -> irrigate\n
All the “stuff” in the house\nWe want to control : push button -> light on\nbut also automate : after sunset and no rain -> irrigate\n
All the “stuff” in the house\nWe want to control : push button -> light on\nbut also automate : after sunset and no rain -> irrigate\n
All the “stuff” in the house\nWe want to control : push button -> light on\nbut also automate : after sunset and no rain -> irrigate\n
All the “stuff” in the house\nWe want to control : push button -> light on\nbut also automate : after sunset and no rain -> irrigate\n
All the “stuff” in the house\nWe want to control : push button -> light on\nbut also automate : after sunset and no rain -> irrigate\n
All the “stuff” in the house\nWe want to control : push button -> light on\nbut also automate : after sunset and no rain -> irrigate\n
All the “stuff” in the house\nWe want to control : push button -> light on\nbut also automate : after sunset and no rain -> irrigate\n
All the “stuff” in the house\nWe want to control : push button -> light on\nbut also automate : after sunset and no rain -> irrigate\n
All the “stuff” in the house\nWe want to control : push button -> light on\nbut also automate : after sunset and no rain -> irrigate\n
All the “stuff” in the house\nWe want to control : push button -> light on\nbut also automate : after sunset and no rain -> irrigate\n
All the “stuff” in the house\nWe want to control : push button -> light on\nbut also automate : after sunset and no rain -> irrigate\n
All the “stuff” in the house\nWe want to control : push button -> light on\nbut also automate : after sunset and no rain -> irrigate\n
All the “stuff” in the house\nWe want to control : push button -> light on\nbut also automate : after sunset and no rain -> irrigate\n
We talk about Home Automation so we usually think residential but this applies equally well to Hotels, Offices, ...\n
We talk about Home Automation so we usually think residential but this applies equally well to Hotels, Offices, ...\n
We talk about Home Automation so we usually think residential but this applies equally well to Hotels, Offices, ...\n
We talk about Home Automation so we usually think residential but this applies equally well to Hotels, Offices, ...\n
We talk about Home Automation so we usually think residential but this applies equally well to Hotels, Offices, ...\n
We talk about Home Automation so we usually think residential but this applies equally well to Hotels, Offices, ...\n
Platform to implement this\nConnect to devices\nRun the logic -> automate\nEnable user interaction -> control\n\nThat seems well defined and easy enough.\nWhy doesn’t this already exists ?\n
Platform to implement this\nConnect to devices\nRun the logic -> automate\nEnable user interaction -> control\n\nThat seems well defined and easy enough.\nWhy doesn’t this already exists ?\n
Platform to implement this\nConnect to devices\nRun the logic -> automate\nEnable user interaction -> control\n\nThat seems well defined and easy enough.\nWhy doesn’t this already exists ?\n
Issues in the HA industry\nAll the devices we want to control have different protocols\nSome of those are closed\nStandardization efforts in the industry, but fragmentation in those standards. Nearly similar problems, different variations to take care of.\nTouch panels in HA industry custom and expensive\nAnd if you look at the business side of things, the distribution channels are niche and extremely expensive\n
Issues in the HA industry\nAll the devices we want to control have different protocols\nSome of those are closed\nStandardization efforts in the industry, but fragmentation in those standards. Nearly similar problems, different variations to take care of.\nTouch panels in HA industry custom and expensive\nAnd if you look at the business side of things, the distribution channels are niche and extremely expensive\n
Issues in the HA industry\nAll the devices we want to control have different protocols\nSome of those are closed\nStandardization efforts in the industry, but fragmentation in those standards. Nearly similar problems, different variations to take care of.\nTouch panels in HA industry custom and expensive\nAnd if you look at the business side of things, the distribution channels are niche and extremely expensive\n
Issues in the HA industry\nAll the devices we want to control have different protocols\nSome of those are closed\nStandardization efforts in the industry, but fragmentation in those standards. Nearly similar problems, different variations to take care of.\nTouch panels in HA industry custom and expensive\nAnd if you look at the business side of things, the distribution channels are niche and extremely expensive\n
Issues in the HA industry\nAll the devices we want to control have different protocols\nSome of those are closed\nStandardization efforts in the industry, but fragmentation in those standards. Nearly similar problems, different variations to take care of.\nTouch panels in HA industry custom and expensive\nAnd if you look at the business side of things, the distribution channels are niche and extremely expensive\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
In summary, the industry is stuck in that vicious circle.\nWhere there is no standardization, everything is proprietary, very much secret and protected\nThis leads to a high cost of integration, where the number of hardware and software to take into account is high and the time to acquire knowledge on those is high\nA high cost means only a luxury market exists\nAnd so the market being small, there is little chance for growth\nWhich in turns means companies are not willing to share and standardized\nand on and on, leading to the current market situation of a status quo deadlock.\n
That’s not what we want\n
And we think we have a solution\n\nFirst, Open Source\n
So why open source ?\n\nFirst, it is our background, we know how it works and the benefit it can bring. Marc Fleury founded JBoss, Juha Lindfors was part of it from the start, we’ve all been using and contributing to open source one way or another.\n\nOpen Source leads to lower barrier to entry. It’s free.\n\nLowers the cost of integration and the knowledge acquisition costs.\nOpen source particularly well suited to the problem of protocol diversity.\nCommunity is important part of open source, bigger chance to address diversity issue than single company.\n
So why open source ?\n\nFirst, it is our background, we know how it works and the benefit it can bring. Marc Fleury founded JBoss, Juha Lindfors was part of it from the start, we’ve all been using and contributing to open source one way or another.\n\nOpen Source leads to lower barrier to entry. It’s free.\n\nLowers the cost of integration and the knowledge acquisition costs.\nOpen source particularly well suited to the problem of protocol diversity.\nCommunity is important part of open source, bigger chance to address diversity issue than single company.\n
So why open source ?\n\nFirst, it is our background, we know how it works and the benefit it can bring. Marc Fleury founded JBoss, Juha Lindfors was part of it from the start, we’ve all been using and contributing to open source one way or another.\n\nOpen Source leads to lower barrier to entry. It’s free.\n\nLowers the cost of integration and the knowledge acquisition costs.\nOpen source particularly well suited to the problem of protocol diversity.\nCommunity is important part of open source, bigger chance to address diversity issue than single company.\n
So why open source ?\n\nFirst, it is our background, we know how it works and the benefit it can bring. Marc Fleury founded JBoss, Juha Lindfors was part of it from the start, we’ve all been using and contributing to open source one way or another.\n\nOpen Source leads to lower barrier to entry. It’s free.\n\nLowers the cost of integration and the knowledge acquisition costs.\nOpen source particularly well suited to the problem of protocol diversity.\nCommunity is important part of open source, bigger chance to address diversity issue than single company.\n
Then we need some form of standard\n
Using a standard. Great idea but what kind of standard?\n\nProprietary standard : scary proposition, again close and slow to evolve.\n\nWith Open Source, the standard that anybody can make theirs. The rights to use, distribute and modify are royalty free.\nIt allows for faster evolution.\nThink about the way JBoss, Apache or Linux evolved.\n\nThis establishes a de facto standard with free access. This enables a new eco system to emerge. Where everybody can get access to the technology, protocols, specifications, solution.\n
Using a standard. Great idea but what kind of standard?\n\nProprietary standard : scary proposition, again close and slow to evolve.\n\nWith Open Source, the standard that anybody can make theirs. The rights to use, distribute and modify are royalty free.\nIt allows for faster evolution.\nThink about the way JBoss, Apache or Linux evolved.\n\nThis establishes a de facto standard with free access. This enables a new eco system to emerge. Where everybody can get access to the technology, protocols, specifications, solution.\n
Using a standard. Great idea but what kind of standard?\n\nProprietary standard : scary proposition, again close and slow to evolve.\n\nWith Open Source, the standard that anybody can make theirs. The rights to use, distribute and modify are royalty free.\nIt allows for faster evolution.\nThink about the way JBoss, Apache or Linux evolved.\n\nThis establishes a de facto standard with free access. This enables a new eco system to emerge. Where everybody can get access to the technology, protocols, specifications, solution.\n
And finally, we need inexpensive hardware\n
We’re lucky, because there are now tons of hardware available to implement all the components we need.\nYou might have recognized the Raspberry Pi logo on the first slide, we’re really excited about this small board coming from the UK.\niPhone and iPads are much cheaper than the usual proprietary equivalent.\nInexpensive IP cameras, Z-wave light switches, ...\n
And this now leads to a virtuous cycle, where open protocols and a de facto standard\nlead to a low cost of integration where access to information and industry specialists is easy\nthis in turn means lower prices to create the solution\nleading to a growing market, and more people participating in this evolution\nand we now have a positive feedback loop creating this new ecosystem\n
And this now leads to a virtuous cycle, where open protocols and a de facto standard\nlead to a low cost of integration where access to information and industry specialists is easy\nthis in turn means lower prices to create the solution\nleading to a growing market, and more people participating in this evolution\nand we now have a positive feedback loop creating this new ecosystem\n
And this now leads to a virtuous cycle, where open protocols and a de facto standard\nlead to a low cost of integration where access to information and industry specialists is easy\nthis in turn means lower prices to create the solution\nleading to a growing market, and more people participating in this evolution\nand we now have a positive feedback loop creating this new ecosystem\n
And this now leads to a virtuous cycle, where open protocols and a de facto standard\nlead to a low cost of integration where access to information and industry specialists is easy\nthis in turn means lower prices to create the solution\nleading to a growing market, and more people participating in this evolution\nand we now have a positive feedback loop creating this new ecosystem\n
And this now leads to a virtuous cycle, where open protocols and a de facto standard\nlead to a low cost of integration where access to information and industry specialists is easy\nthis in turn means lower prices to create the solution\nleading to a growing market, and more people participating in this evolution\nand we now have a positive feedback loop creating this new ecosystem\n
And this now leads to a virtuous cycle, where open protocols and a de facto standard\nlead to a low cost of integration where access to information and industry specialists is easy\nthis in turn means lower prices to create the solution\nleading to a growing market, and more people participating in this evolution\nand we now have a positive feedback loop creating this new ecosystem\n
And this now leads to a virtuous cycle, where open protocols and a de facto standard\nlead to a low cost of integration where access to information and industry specialists is easy\nthis in turn means lower prices to create the solution\nleading to a growing market, and more people participating in this evolution\nand we now have a positive feedback loop creating this new ecosystem\n
And this now leads to a virtuous cycle, where open protocols and a de facto standard\nlead to a low cost of integration where access to information and industry specialists is easy\nthis in turn means lower prices to create the solution\nleading to a growing market, and more people participating in this evolution\nand we now have a positive feedback loop creating this new ecosystem\n
And this now leads to a virtuous cycle, where open protocols and a de facto standard\nlead to a low cost of integration where access to information and industry specialists is easy\nthis in turn means lower prices to create the solution\nleading to a growing market, and more people participating in this evolution\nand we now have a positive feedback loop creating this new ecosystem\n
And this now leads to a virtuous cycle, where open protocols and a de facto standard\nlead to a low cost of integration where access to information and industry specialists is easy\nthis in turn means lower prices to create the solution\nleading to a growing market, and more people participating in this evolution\nand we now have a positive feedback loop creating this new ecosystem\n
And this now leads to a virtuous cycle, where open protocols and a de facto standard\nlead to a low cost of integration where access to information and industry specialists is easy\nthis in turn means lower prices to create the solution\nleading to a growing market, and more people participating in this evolution\nand we now have a positive feedback loop creating this new ecosystem\n
And this now leads to a virtuous cycle, where open protocols and a de facto standard\nlead to a low cost of integration where access to information and industry specialists is easy\nthis in turn means lower prices to create the solution\nleading to a growing market, and more people participating in this evolution\nand we now have a positive feedback loop creating this new ecosystem\n
And this now leads to a virtuous cycle, where open protocols and a de facto standard\nlead to a low cost of integration where access to information and industry specialists is easy\nthis in turn means lower prices to create the solution\nleading to a growing market, and more people participating in this evolution\nand we now have a positive feedback loop creating this new ecosystem\n
And this now leads to a virtuous cycle, where open protocols and a de facto standard\nlead to a low cost of integration where access to information and industry specialists is easy\nthis in turn means lower prices to create the solution\nleading to a growing market, and more people participating in this evolution\nand we now have a positive feedback loop creating this new ecosystem\n
And this now leads to a virtuous cycle, where open protocols and a de facto standard\nlead to a low cost of integration where access to information and industry specialists is easy\nthis in turn means lower prices to create the solution\nleading to a growing market, and more people participating in this evolution\nand we now have a positive feedback loop creating this new ecosystem\n
And this now leads to a virtuous cycle, where open protocols and a de facto standard\nlead to a low cost of integration where access to information and industry specialists is easy\nthis in turn means lower prices to create the solution\nleading to a growing market, and more people participating in this evolution\nand we now have a positive feedback loop creating this new ecosystem\n
And this now leads to a virtuous cycle, where open protocols and a de facto standard\nlead to a low cost of integration where access to information and industry specialists is easy\nthis in turn means lower prices to create the solution\nleading to a growing market, and more people participating in this evolution\nand we now have a positive feedback loop creating this new ecosystem\n
So that is our solution, open source, a de facto standard and off the self components.\n\nAnd that is what Open Remote is about.\n
So that is our solution, open source, a de facto standard and off the self components.\n\nAnd that is what Open Remote is about.\n
Let’s now take a look at the Open Remote ecosystem and the components that are part of it.\nThe bottom part of the drawing represents your LAN, the upper part is the cloud.\nAt the heart of the system is the OpenRemote controller or ORB, connected to the devices.\nThe panels (or consoles) handle the user interaction. They are available when you’re connected to your LAN but also from the internet.\nIn this case, the Remote Proxy is used, making it easy to connect without the need for difficult router / NAT / VPN configuration.\nTo create the configuration for the system, you use the Online Designer and the configuration is then stored into Beehive, our assets repository.\n
Let’s now take a look at the Open Remote ecosystem and the components that are part of it.\nThe bottom part of the drawing represents your LAN, the upper part is the cloud.\nAt the heart of the system is the OpenRemote controller or ORB, connected to the devices.\nThe panels (or consoles) handle the user interaction. They are available when you’re connected to your LAN but also from the internet.\nIn this case, the Remote Proxy is used, making it easy to connect without the need for difficult router / NAT / VPN configuration.\nTo create the configuration for the system, you use the Online Designer and the configuration is then stored into Beehive, our assets repository.\n
Let’s now take a look at the Open Remote ecosystem and the components that are part of it.\nThe bottom part of the drawing represents your LAN, the upper part is the cloud.\nAt the heart of the system is the OpenRemote controller or ORB, connected to the devices.\nThe panels (or consoles) handle the user interaction. They are available when you’re connected to your LAN but also from the internet.\nIn this case, the Remote Proxy is used, making it easy to connect without the need for difficult router / NAT / VPN configuration.\nTo create the configuration for the system, you use the Online Designer and the configuration is then stored into Beehive, our assets repository.\n
Let’s now take a look at the Open Remote ecosystem and the components that are part of it.\nThe bottom part of the drawing represents your LAN, the upper part is the cloud.\nAt the heart of the system is the OpenRemote controller or ORB, connected to the devices.\nThe panels (or consoles) handle the user interaction. They are available when you’re connected to your LAN but also from the internet.\nIn this case, the Remote Proxy is used, making it easy to connect without the need for difficult router / NAT / VPN configuration.\nTo create the configuration for the system, you use the Online Designer and the configuration is then stored into Beehive, our assets repository.\n
Let’s now take a look at the Open Remote ecosystem and the components that are part of it.\nThe bottom part of the drawing represents your LAN, the upper part is the cloud.\nAt the heart of the system is the OpenRemote controller or ORB, connected to the devices.\nThe panels (or consoles) handle the user interaction. They are available when you’re connected to your LAN but also from the internet.\nIn this case, the Remote Proxy is used, making it easy to connect without the need for difficult router / NAT / VPN configuration.\nTo create the configuration for the system, you use the Online Designer and the configuration is then stored into Beehive, our assets repository.\n
Let’s now take a look at the Open Remote ecosystem and the components that are part of it.\nThe bottom part of the drawing represents your LAN, the upper part is the cloud.\nAt the heart of the system is the OpenRemote controller or ORB, connected to the devices.\nThe panels (or consoles) handle the user interaction. They are available when you’re connected to your LAN but also from the internet.\nIn this case, the Remote Proxy is used, making it easy to connect without the need for difficult router / NAT / VPN configuration.\nTo create the configuration for the system, you use the Online Designer and the configuration is then stored into Beehive, our assets repository.\n
Let’s now take a look at the Open Remote ecosystem and the components that are part of it.\nThe bottom part of the drawing represents your LAN, the upper part is the cloud.\nAt the heart of the system is the OpenRemote controller or ORB, connected to the devices.\nThe panels (or consoles) handle the user interaction. They are available when you’re connected to your LAN but also from the internet.\nIn this case, the Remote Proxy is used, making it easy to connect without the need for difficult router / NAT / VPN configuration.\nTo create the configuration for the system, you use the Online Designer and the configuration is then stored into Beehive, our assets repository.\n
Let’s now take a look at the Open Remote ecosystem and the components that are part of it.\nThe bottom part of the drawing represents your LAN, the upper part is the cloud.\nAt the heart of the system is the OpenRemote controller or ORB, connected to the devices.\nThe panels (or consoles) handle the user interaction. They are available when you’re connected to your LAN but also from the internet.\nIn this case, the Remote Proxy is used, making it easy to connect without the need for difficult router / NAT / VPN configuration.\nTo create the configuration for the system, you use the Online Designer and the configuration is then stored into Beehive, our assets repository.\n
Let’s now take a look at the Open Remote ecosystem and the components that are part of it.\nThe bottom part of the drawing represents your LAN, the upper part is the cloud.\nAt the heart of the system is the OpenRemote controller or ORB, connected to the devices.\nThe panels (or consoles) handle the user interaction. They are available when you’re connected to your LAN but also from the internet.\nIn this case, the Remote Proxy is used, making it easy to connect without the need for difficult router / NAT / VPN configuration.\nTo create the configuration for the system, you use the Online Designer and the configuration is then stored into Beehive, our assets repository.\n
Let’s now take a look at the Open Remote ecosystem and the components that are part of it.\nThe bottom part of the drawing represents your LAN, the upper part is the cloud.\nAt the heart of the system is the OpenRemote controller or ORB, connected to the devices.\nThe panels (or consoles) handle the user interaction. They are available when you’re connected to your LAN but also from the internet.\nIn this case, the Remote Proxy is used, making it easy to connect without the need for difficult router / NAT / VPN configuration.\nTo create the configuration for the system, you use the Online Designer and the configuration is then stored into Beehive, our assets repository.\n
Let’s now take a look at the Open Remote ecosystem and the components that are part of it.\nThe bottom part of the drawing represents your LAN, the upper part is the cloud.\nAt the heart of the system is the OpenRemote controller or ORB, connected to the devices.\nThe panels (or consoles) handle the user interaction. They are available when you’re connected to your LAN but also from the internet.\nIn this case, the Remote Proxy is used, making it easy to connect without the need for difficult router / NAT / VPN configuration.\nTo create the configuration for the system, you use the Online Designer and the configuration is then stored into Beehive, our assets repository.\n
Let’s now take a look at the Open Remote ecosystem and the components that are part of it.\nThe bottom part of the drawing represents your LAN, the upper part is the cloud.\nAt the heart of the system is the OpenRemote controller or ORB, connected to the devices.\nThe panels (or consoles) handle the user interaction. They are available when you’re connected to your LAN but also from the internet.\nIn this case, the Remote Proxy is used, making it easy to connect without the need for difficult router / NAT / VPN configuration.\nTo create the configuration for the system, you use the Online Designer and the configuration is then stored into Beehive, our assets repository.\n
The controller is a runtime component, this is where the logic executes, where the I/O is handled.\nIt has a connection to all the devices in the system and it speaks their protocol.\nIt also handle interaction events from the panels.\n\nGoal is to have it as a standard J2SE application to minimize requirements on the platform but currently it is a web application usually deployed on Tomcat.\n\nRuns on off the shelf hardware where the Java environment can be installed. Has been installed on several NAS, on plug computer, on Alix board ...\n
The controller is a runtime component, this is where the logic executes, where the I/O is handled.\nIt has a connection to all the devices in the system and it speaks their protocol.\nIt also handle interaction events from the panels.\n\nGoal is to have it as a standard J2SE application to minimize requirements on the platform but currently it is a web application usually deployed on Tomcat.\n\nRuns on off the shelf hardware where the Java environment can be installed. Has been installed on several NAS, on plug computer, on Alix board ...\n
The controller is a runtime component, this is where the logic executes, where the I/O is handled.\nIt has a connection to all the devices in the system and it speaks their protocol.\nIt also handle interaction events from the panels.\n\nGoal is to have it as a standard J2SE application to minimize requirements on the platform but currently it is a web application usually deployed on Tomcat.\n\nRuns on off the shelf hardware where the Java environment can be installed. Has been installed on several NAS, on plug computer, on Alix board ...\n
The controller is a runtime component, this is where the logic executes, where the I/O is handled.\nIt has a connection to all the devices in the system and it speaks their protocol.\nIt also handle interaction events from the panels.\n\nGoal is to have it as a standard J2SE application to minimize requirements on the platform but currently it is a web application usually deployed on Tomcat.\n\nRuns on off the shelf hardware where the Java environment can be installed. Has been installed on several NAS, on plug computer, on Alix board ...\n
There currently is already quite a bit of protocols supported, big names in the Home Automation field such as KNX, X10, Lutron, Russound but also more generic ones like HTTP, TCP, UDP and Telnet.\nAlso, does not need to be hardware, can control software.\n
There currently is already quite a bit of protocols supported, big names in the Home Automation field such as KNX, X10, Lutron, Russound but also more generic ones like HTTP, TCP, UDP and Telnet.\nAlso, does not need to be hardware, can control software.\n
There currently is already quite a bit of protocols supported, big names in the Home Automation field such as KNX, X10, Lutron, Russound but also more generic ones like HTTP, TCP, UDP and Telnet.\nAlso, does not need to be hardware, can control software.\n
There currently is already quite a bit of protocols supported, big names in the Home Automation field such as KNX, X10, Lutron, Russound but also more generic ones like HTTP, TCP, UDP and Telnet.\nAlso, does not need to be hardware, can control software.\n
There currently is already quite a bit of protocols supported, big names in the Home Automation field such as KNX, X10, Lutron, Russound but also more generic ones like HTTP, TCP, UDP and Telnet.\nAlso, does not need to be hardware, can control software.\n
There currently is already quite a bit of protocols supported, big names in the Home Automation field such as KNX, X10, Lutron, Russound but also more generic ones like HTTP, TCP, UDP and Telnet.\nAlso, does not need to be hardware, can control software.\n
There currently is already quite a bit of protocols supported, big names in the Home Automation field such as KNX, X10, Lutron, Russound but also more generic ones like HTTP, TCP, UDP and Telnet.\nAlso, does not need to be hardware, can control software.\n
There currently is already quite a bit of protocols supported, big names in the Home Automation field such as KNX, X10, Lutron, Russound but also more generic ones like HTTP, TCP, UDP and Telnet.\nAlso, does not need to be hardware, can control software.\n
There currently is already quite a bit of protocols supported, big names in the Home Automation field such as KNX, X10, Lutron, Russound but also more generic ones like HTTP, TCP, UDP and Telnet.\nAlso, does not need to be hardware, can control software.\n
There currently is already quite a bit of protocols supported, big names in the Home Automation field such as KNX, X10, Lutron, Russound but also more generic ones like HTTP, TCP, UDP and Telnet.\nAlso, does not need to be hardware, can control software.\n
There currently is already quite a bit of protocols supported, big names in the Home Automation field such as KNX, X10, Lutron, Russound but also more generic ones like HTTP, TCP, UDP and Telnet.\nAlso, does not need to be hardware, can control software.\n
There currently is already quite a bit of protocols supported, big names in the Home Automation field such as KNX, X10, Lutron, Russound but also more generic ones like HTTP, TCP, UDP and Telnet.\nAlso, does not need to be hardware, can control software.\n
There currently is already quite a bit of protocols supported, big names in the Home Automation field such as KNX, X10, Lutron, Russound but also more generic ones like HTTP, TCP, UDP and Telnet.\nAlso, does not need to be hardware, can control software.\n
There currently is already quite a bit of protocols supported, big names in the Home Automation field such as KNX, X10, Lutron, Russound but also more generic ones like HTTP, TCP, UDP and Telnet.\nAlso, does not need to be hardware, can control software.\n
The ORB allows seamless integration of those different protocols. It acts as an aggregator for closed protocols and publish an open one.\nFor instance, on this picture we have an IP backbone in red, a wireless mesh network such as Z-wave in blue and a KNX field bus in green.\n
The panels (or consoles) allow interaction with the system through a rich GUI. \nORB provides a description of the user interface to render as an XML file and panels render appropriately.\n\nWhen the user triggers an action on a console, it calls back to the ORB through a REST API with data encoded as either XML or JSON.\nThe ORB will execute the appropriate action and eventually control the devices integrated in the system.\n\nThe ORB also sends information back to the panels so that feedback from the system is reported to the user.\n
The panels (or consoles) allow interaction with the system through a rich GUI. \nORB provides a description of the user interface to render as an XML file and panels render appropriately.\n\nWhen the user triggers an action on a console, it calls back to the ORB through a REST API with data encoded as either XML or JSON.\nThe ORB will execute the appropriate action and eventually control the devices integrated in the system.\n\nThe ORB also sends information back to the panels so that feedback from the system is reported to the user.\n
The panels (or consoles) allow interaction with the system through a rich GUI. \nORB provides a description of the user interface to render as an XML file and panels render appropriately.\n\nWhen the user triggers an action on a console, it calls back to the ORB through a REST API with data encoded as either XML or JSON.\nThe ORB will execute the appropriate action and eventually control the devices integrated in the system.\n\nThe ORB also sends information back to the panels so that feedback from the system is reported to the user.\n
We currently support Android, iOS (iPhone, iPod touches and iPad) and a rich web client (implemented using GWT).\nBut we are open to any implementation, as the API and data format are using REST/JSON/XML and are publicly defined.\n
We currently support Android, iOS (iPhone, iPod touches and iPad) and a rich web client (implemented using GWT).\nBut we are open to any implementation, as the API and data format are using REST/JSON/XML and are publicly defined.\n
We currently support Android, iOS (iPhone, iPod touches and iPad) and a rich web client (implemented using GWT).\nBut we are open to any implementation, as the API and data format are using REST/JSON/XML and are publicly defined.\n
We currently support Android, iOS (iPhone, iPod touches and iPad) and a rich web client (implemented using GWT).\nBut we are open to any implementation, as the API and data format are using REST/JSON/XML and are publicly defined.\n
We currently support Android, iOS (iPhone, iPod touches and iPad) and a rich web client (implemented using GWT).\nBut we are open to any implementation, as the API and data format are using REST/JSON/XML and are publicly defined.\n
We currently support Android, iOS (iPhone, iPod touches and iPad) and a rich web client (implemented using GWT).\nBut we are open to any implementation, as the API and data format are using REST/JSON/XML and are publicly defined.\n
We currently support Android, iOS (iPhone, iPod touches and iPad) and a rich web client (implemented using GWT).\nBut we are open to any implementation, as the API and data format are using REST/JSON/XML and are publicly defined.\n
We currently support Android, iOS (iPhone, iPod touches and iPad) and a rich web client (implemented using GWT).\nBut we are open to any implementation, as the API and data format are using REST/JSON/XML and are publicly defined.\n
These covered the runtime part of the system, let’s now take a look at how the system is configured.\nThe designer is a visual tool to configure everything required by the system at runtime. The tool is web based. It is available on openremote.org so you don’t have to install anything locally and you can access it from anywhere. But it can also be installed on your own private cloud (or machine) if you want.\n\nConfigure everything required at runtime, this includes the communication with the devices, the user interface rendered on the panels and soon the logic too.\n\nHowever, the configuration of devices and the creation of the user interface are cleanly separated in the modeler. There is clear separation of concerns and responsibilities. So for instance on bigger projects or in bigger organizations, a technician can configure the elements in the system, the communication protocols, ... and a graphic designer can take care of the UI. \n
These covered the runtime part of the system, let’s now take a look at how the system is configured.\nThe designer is a visual tool to configure everything required by the system at runtime. The tool is web based. It is available on openremote.org so you don’t have to install anything locally and you can access it from anywhere. But it can also be installed on your own private cloud (or machine) if you want.\n\nConfigure everything required at runtime, this includes the communication with the devices, the user interface rendered on the panels and soon the logic too.\n\nHowever, the configuration of devices and the creation of the user interface are cleanly separated in the modeler. There is clear separation of concerns and responsibilities. So for instance on bigger projects or in bigger organizations, a technician can configure the elements in the system, the communication protocols, ... and a graphic designer can take care of the UI. \n
Looking at an example for the device side (here for an example KNX project), we can define commands that control devices and sensor that provide information back from devices but also higher level construction such as switch, that embed the sensor feedback and commands to turn on and off the light.\n\nHaving those higher level constructs do facilitate the creation on the UI as now, those elements can be linked to widgets. This is basically an application of the MVC pattern.\n\nWe also have some wizards to automatically create all those commands. For instance for KNX, we can use an export from ETS to get all the group addresses in use for your system.\n
On the UI side, you can design you different screen and navigation between them.\nAnd you have a choice of widgets to select from, such as buttons, images, labels, sliders, tab bar ...\n
Stores the user profiles and the configuration defined in the modeler but also a database of templates, graphics, infra red codes.\n\nAvailable on openremote.org site but you can install locally (or in your private cloud)\n\nThe designer uses beehive as its backend but there is a REST API (or soon will be), so you can write other frontends for design or use the API for some automatic provisioning.\n
Stores the user profiles and the configuration defined in the modeler but also a database of templates, graphics, infra red codes.\n\nAvailable on openremote.org site but you can install locally (or in your private cloud)\n\nThe designer uses beehive as its backend but there is a REST API (or soon will be), so you can write other frontends for design or use the API for some automatic provisioning.\n
Stores the user profiles and the configuration defined in the modeler but also a database of templates, graphics, infra red codes.\n\nAvailable on openremote.org site but you can install locally (or in your private cloud)\n\nThe designer uses beehive as its backend but there is a REST API (or soon will be), so you can write other frontends for design or use the API for some automatic provisioning.\n
Stores the user profiles and the configuration defined in the modeler but also a database of templates, graphics, infra red codes.\n\nAvailable on openremote.org site but you can install locally (or in your private cloud)\n\nThe designer uses beehive as its backend but there is a REST API (or soon will be), so you can write other frontends for design or use the API for some automatic provisioning.\n
Let’s now talk a bit Apple specific\n
\n
\n
\n
\n
\n
Usually for AppStore, iOS 4.0 or above is fine. We try to keep iOS 3.2 as long as possible so users can re-use old devices lying around.\nNSURLConnection / NSXMLParser for historical reasons but still do most of the work required, not always need for specific frameworks.\n
Usually for AppStore, iOS 4.0 or above is fine. We try to keep iOS 3.2 as long as possible so users can re-use old devices lying around.\nNSURLConnection / NSXMLParser for historical reasons but still do most of the work required, not always need for specific frameworks.\n
Usually for AppStore, iOS 4.0 or above is fine. We try to keep iOS 3.2 as long as possible so users can re-use old devices lying around.\nNSURLConnection / NSXMLParser for historical reasons but still do most of the work required, not always need for specific frameworks.\n
Usually for AppStore, iOS 4.0 or above is fine. We try to keep iOS 3.2 as long as possible so users can re-use old devices lying around.\nNSURLConnection / NSXMLParser for historical reasons but still do most of the work required, not always need for specific frameworks.\n
Wishes for Apple\nApple TV : SDK to deploy on it e.g. notifications on AppleTV\nalso control, even if reversed engineered solutions exists\nSiri, client side solutions exists for voice recognition but would be cool to have Siri integrated\nNFC, not for payment only, small scale geo localization\nBetter access to H.264 hardware decoding\n
Wishes for Apple\nApple TV : SDK to deploy on it e.g. notifications on AppleTV\nalso control, even if reversed engineered solutions exists\nSiri, client side solutions exists for voice recognition but would be cool to have Siri integrated\nNFC, not for payment only, small scale geo localization\nBetter access to H.264 hardware decoding\n
Wishes for Apple\nApple TV : SDK to deploy on it e.g. notifications on AppleTV\nalso control, even if reversed engineered solutions exists\nSiri, client side solutions exists for voice recognition but would be cool to have Siri integrated\nNFC, not for payment only, small scale geo localization\nBetter access to H.264 hardware decoding\n
Wishes for Apple\nApple TV : SDK to deploy on it e.g. notifications on AppleTV\nalso control, even if reversed engineered solutions exists\nSiri, client side solutions exists for voice recognition but would be cool to have Siri integrated\nNFC, not for payment only, small scale geo localization\nBetter access to H.264 hardware decoding\n
Wishes for Apple\nApple TV : SDK to deploy on it e.g. notifications on AppleTV\nalso control, even if reversed engineered solutions exists\nSiri, client side solutions exists for voice recognition but would be cool to have Siri integrated\nNFC, not for payment only, small scale geo localization\nBetter access to H.264 hardware decoding\n
Besides the technical aspects that we covered, the community side of the project is important.\nOR is a fantastic platform for hobbyists, with a really low entry cost. This lead to a great active community, which contribute back additional protocols and provide feedback and support in the forums.\nWe’re always keen to see what user do with the platform, so don’t hesitate to come and show off your projects.\n\nAnd there are also lots of professionals in the community, and this fits perfectly in our business model.\n
Besides the technical aspects that we covered, the community side of the project is important.\nOR is a fantastic platform for hobbyists, with a really low entry cost. This lead to a great active community, which contribute back additional protocols and provide feedback and support in the forums.\nWe’re always keen to see what user do with the platform, so don’t hesitate to come and show off your projects.\n\nAnd there are also lots of professionals in the community, and this fits perfectly in our business model.\n
Besides the technical aspects that we covered, the community side of the project is important.\nOR is a fantastic platform for hobbyists, with a really low entry cost. This lead to a great active community, which contribute back additional protocols and provide feedback and support in the forums.\nWe’re always keen to see what user do with the platform, so don’t hesitate to come and show off your projects.\n\nAnd there are also lots of professionals in the community, and this fits perfectly in our business model.\n
