Stream

Join this community to post or comment
Pinned by moderator

Blixa Morgan (MrMakeIt)
moderator

Discussion  - 
 
Anyone who has been following the Github group may have noticed a new report has popped up, cross-talk. After several days of discussion, I'm happy to reveal what cross-talk is, how it affects The Thing System, and what the road map for its existence is.

The purpose of cross-talk is to bridge different networks and gateways together, allowing devices on one network to talk and connect with devices on another network.

The initial networks that will be supported are z-wave, thought the open z-wave project, zigbee, and already documented TCP gateways.

The steward will become a TCP controller, and will have access to any devices cross-talk recognizes.

As the code develops, I'll release more details about the exact inner workings of Cross-talk, but feel free to ask questions now.

Github repo: https://github.com/TheThingSystem/cross-talk
2
Thomas Wiley's profile photoBlixa Morgan (MrMakeIt)'s profile photo
7 comments
 
+Thomas Wiley​ yes. Been looking into using root CA's to confirm that a device is permitted.
Add a comment...

Stephan Raidl

Installation  - 
 
does the diskimage for the B+ model still exist somewhere?
Can't seem to get the B code running on the B+ model...
Any ideas about that?
1
Add a comment...

Kilo Kee

Installation  - 
 
Hey gang. I just ran across this system and just by reading the website, i like this a lot. Is there a way to run this on a debian 8 system on a PC platform. If so, could you please steer me to this information. Thanks Kilo
1
Add a comment...

A. J. Wright

The Steward  - 
 
Hey all!

Has anyone had luck getting the steward working under Docker?

I've found a couple of Dockerfiles, but the steward seems to be expecting certain software and library versions (that I haven't figured out yet.)
1
Blixa Morgan (MrMakeIt)'s profile photoMarkus Larsson's profile photo
7 comments
 
Good to hear.
Great minds thinks like me :P
Add a comment...

Kevin Rattai

Discussion  - 
 
Just a "Hello, world!" comment.  Finished watching Alasdair's presentation at linux.conf.au 2015 and he was bang on.  Taking a look at The Thing System and hope to integrate it with my AEBL device as soon as possible and contribute back to the community, if possible.  :)  https://github.com/krattai/AEBL
1
Blixa Morgan (MrMakeIt)'s profile photo
 
Glad to hear. If there is anything I can help with to make it easier for you to integrate TTS with AEBL, let me know.
Add a comment...

Russell Nelson

Discussion  - 
 
I'm thinking that TTS has the wrong structure. It is basically a single executable that's running a big chunk of code. This imposes several requirements:
  o Everything has to be written in Javascript using node.js.
  o Everything runs at the same security level. If anything is broken into, everything is broken into.
  o It's impossible to restart one service without restarting all services.
  o There's not really any way (other than by contributing to TTS) for a manufacturer to write a TTS-compatible device driver.

What if TTS was broken up into a lot of small processes communicating via sockets? Each sensor or actuator would present an API via a socket. This addresses every point above: As long as the protocol being run over the socket complies with the TTS protocol, the device driver can be written in any language, by any party. New devices can be spun up or shut down without having to restart the TTS steward (the device would contact the TTS steward to say "this is my process number, this is my port at localhost).

The API would be very simple. A sensor would periodically spit out a report of the value being sensed (when it changed, or every ten seconds). An actuator would accept commands using a text protocol very much like FTP or SMTP. Values too complicated to go into a single line would be transferred in a JSON structure encapsulated like SMTP DATA.

In the short term, TTS could be split up this way with few changes to each device driver; just add the network layer between the TTS engine and each driver.
4
Blixa Morgan (MrMakeIt)'s profile photoMarkus Larsson's profile photo
5 comments
 
+Blixa Morgan​ great to hear that you guys are working at it. I understand the struggles of bringing a dead project back to life. Hopefully there will soon be a roadmap for how we make tts feel less like a prototype. If you guys need any input, just yell. I might be a small fish in the the IoT pond but I am an IT architect who count servers by the thousands so issues regarding maintainability is right up my alley ;)
Add a comment...

Scott H

The Steward  - 
 
I recently started looking into home automation and the internet of things. I have an Ecobee3 thermostat and am already registered as a developer with them but am having issues connecting it to the steward. Can anyone lend me a hand?
1
Add a comment...

Alasdair Allan
owner

Discussion  - 
 
The people taking over the project seem to have a lot of good ideas for the direction of #TheThingSystem  and I'm looking forward to seeing what they do with it. +Marshall Rose and I will be hanging around as maintainers emeritus to offer advice.
 
friends - the proto-curators would like to announce that The Thing System is about to be adopted by a new set of curators... that is all.

actually, it's a lot! look forward to an introduction very soon now.

so, the period of hiatus is nearly over.

enjoy!
5
Add a comment...

Einaras Gravrock

Making Things  - 
 
Hello Everyone,

We built a home IoT security device and are looking for users with large IoT installations who want to try our beta. Our CUJO device will block attacks against IoT and other connected devices and improve performance when IoT or other devices spam your network. If you're interested, check out www.getcujo.com.

Here’s a youtube clip explaining CUJO: https://www.youtube.com/watch?v=Fr7b1u_TrEI  
Cheers,
Einaras Gravrock
1
Add a comment...

Alasdair Allan
owner

Discussion  - 
 
The arrival of the #ESP8266 SoC — which you can pick up for $2.50 a chip in only moderate volume — could have serious knock on affects for the #IoT  and especially for #wearables.
 
The first part of a three part series on the #ESP8266.
What if you could have an Arduino compatible board, with WiFi, for just $5? Well now you can, because the ESP8266 is now Arduino compatible.
10
4
Konrad Riedel's profile photoMike Vanderpool's profile photo
Add a comment...

Mauricio Dominguez

Installation  - 
 
i want install the thing system on a beagle bone black board, can help me ? 
1
Alasdair Allan's profile photo
 
See http://thethingsystem.com/dev/Installation.html where there is a disk image for the Beaglebone Black at the top of the page. Alternatively you can install from source by following these instructions, http://thethingsystem.com/dev/Bootstrapping-the-BeagleBone-Black-with-Debian.html on Debian.
Add a comment...

Delaji D'vil

Discussion  - 
 
Is this project dead in the water?

It would be a shame to let this project die out.
1
Anthony Roby's profile photoDelaji D'vil's profile photo
7 comments
 
Yeah I can't argue with you there. Just had a quick scan over the code.
Add a comment...

About this community

Your life and your house went from one computer to an Internet of things. From tablets to lightbulbs, from sensors to media boxes, everybody gets their own Internet. Today, you have to fight your things. They don't talk to each other, the apps don't work, it's a tower of babel. Our solution — the Thing System — is open source. We'll talk to anything, you can hack the system, it has an open API. With the Thing System, you can finally take control of your things.

Kilo Kee

The Steward  - 
 
Hey all. Is this awesome idea still in development and support? Just wondering.
1
Blixa Morgan (MrMakeIt)'s profile photoKilo Kee's profile photo
2 comments
 
Ok cool. Cant wait. In the meantime, Im going to try to get this to run on my PC since I found an article that has instructions on building it on that platform.
Add a comment...

Jason Fowler

Installation  - 
 
I've installed the pi image on my Revision 2 Raspberry Pi B. I can run
sudo /etc/init.d/stewart restart
and it says it ran fine, but the process doesn't actually start.
I have ran
sudo ./run.sh from /home/pi/steward/steward to no avail.
I have even run
sudo node index.js
and although the process runs, there is no websever for me to connect to.
Nothing shows up in netstat, I can't connect to port 8888 or port 8887.

Does anyone have any ideas?
1
Jason Fowler's profile photoBlixa Morgan (MrMakeIt)'s profile photo
5 comments
 
Glad to hear it worked out. I'll be sure to make a note of that on the website.
Add a comment...

Russell Nelson

Discussion  - 
 
I'm trying to build the steward from source. I can't get node-hid to work. It's required by the steward, and the steward works in the Raspberry Pi image that has been distributed, so how does node-hid not work?
1
Russell Nelson's profile photoMaxim Rubis's profile photo
4 comments
 
I made it run on Windows 10 by using latest nodejs and updating some of the dependencies. Plus I excluded a lot of library in configuration file because I mainly run Insteon network.
Add a comment...

RE•WORK

Discussion  - 
 
Hi, I just wanted to let you know about our conference taking place in San Francisco on 12-13 November. At the RE.WORK Connect Summit we’ll be exploring IoT, connected devices, machine learning, future cities and more. 

Check out all the details here: https://www.re-work.co/events/iot-sanfrancisco

Tickets available include a discounted pass for startups, academia & students. Use the discount code IOT20 for 20% off! 

Hope to see you there!
RE.WORK events combine entrepreneurship, technology and science to solve some of the world's greatest challenges using emerging technology. We showcase the opportunities of exponentially accelerating technologies and their impact on business and society
1
Add a comment...

Blixa Morgan (MrMakeIt)
moderator

Discussion  - 
 
Hello Thing Makers and System Builders. I am glad to announce that Brendan Hill and myself are now officially becoming the new curators!
We have several thing planned for TTS and are excited to be working with this wonderful community. We will be announcing the new planing guide soon, but in the meantime we are hard at work getting v1.11 "roast chicken" ready for you. The big change with 1.11 will be a native rpi2 image, but there will be several smaller bug fixes as well.
At the same time, we are brewing up some big events to coincide with the restart of TTS and we want to get your opinion. If you have any ideas on global events we could do, let us know!
Thanks again for being a part of this community, and we hope you guys are excited as we are!

Sincerely:
Blixa Morgan & Brendan Hill
 
friends - the proto-curators would like to announce that The Thing System is about to be adopted by a new set of curators... that is all.

actually, it's a lot! look forward to an introduction very soon now.

so, the period of hiatus is nearly over.

enjoy!
3
Jason DeVelvis's profile photoBlixa Morgan (MrMakeIt)'s profile photo
4 comments
 
Thanks +Jason DeVelvis, I have had an email discussion with one of the Broadcom developers in relation with a Sonos issue, but if there is anything else they need, I'm always available.
In terms of direction, I have a group of 5 people currently discussing where and how we can further TTS.  Since we're still in the middle of discussion, I can't give a detailed timeline, but I can say we are looking into the following things, and are welcoming any feedback the community may have.
First, with the growing number of things on the market, how will TTS handle supporting them without requiring they all be installed from the beginning.  Currently, if a device does not use the Simple Thing Protocol (STP), the connection code must be built into the core.  This is slowly making the load time longer and longer, and is using more memory than it should be.
Second, the current method of using cloud services is difficult at best.  We are looking into either an easier local setup system or a web service that will tunnel the service connections.

Also, we are looking at making a hardware kit for both developers and end consumers. something that can easily be modified to suit a developers needs, but can be used out of the box, with no additional programming knowledge.

All of this is subject to change, but once we have a more solid plan, we will post here.

We also are looking into a big community event, but that is still under wraps for now. ;)
Add a comment...

Marshall Rose
moderator

Discussion  - 
 
friends - the proto-curators would like to announce that The Thing System is about to be adopted by a new set of curators... that is all.

actually, it's a lot! look forward to an introduction very soon now.

so, the period of hiatus is nearly over.

enjoy!
6
2
Russell Nelson's profile photoMarshall Rose's profile photoAlasdair Allan's profile photoBlixa Morgan (MrMakeIt)'s profile photo
4 comments
 
thank you!

my best regards,

/mtr
Add a comment...

Alasdair Allan
owner

Discussion  - 
 
Coming to +O'Reilly Solid and want to play with #BLE ..?
 
Want to get hands on with #Bluetooth Low Energy in a couple of weeks with me, +Don Coleman, and +Sandeep Mistry at +O'Reilly Solid? We're running a tutorial, and yes, you get to keep the hardware. http://bit.ly/solid-ble-tutorial #BLE   #IoT
1
Add a comment...

Alasdair Allan
owner

Discussion  - 
 
Interesting. The first Javascript board with a full node.js stack, including the capability to run modules using native C and C++. I wonder if we could get the steward up and running on it... 
 
Real +node.js on a board, including modules that use native C and C++ code. This is a big step forward... 
Earlier today Technical Machine, the people behind the Javscript-driven Tessel, released the Tessel 2 their next generation board.
7
1
Fabio Cigliano's profile photo
Add a comment...