Add initial support for Shiftr.io

[fabaff]

Description:

This component simply make the events from Home Assistant available in the communication infrastructure on shiftr.io. This allows one to share data and see the flows in a realtime graph that visualizes all events happening in a namespace.

Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.io#2827

Example entry for configuration.yaml (if applicable):

shiftr:
  username: 7879cb40
  password: 5e8bh7bebe4c0cc0

Checklist:

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

• Local tests with tox run successfully. Your PR cannot be merged unless tests pass
• New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
• New dependencies are only imported inside functions that use them ([example][ex-import]).
• New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
• New files were added to .coveragerc.

[robmarkcole]

Only small mods required for posting to Initial State
http://support.initialstate.com/knowledgebase/articles/590091-how-to-stream-events-via-restful-api

[pvizeli]

I don't sure if we should use our internal mqtt server object. They is also connect to dispatcher and that do not check from where the data a are comming. I think that is a bit a security hole.

Maby with a own paho client or hbmqtt we are better and any future change on our internal mqtt server object will not affect shiftr negative?

[pvizeli]

I think that need inside a yield from hass.async_add_job() to not block the loop.

[fabaff]

Thanks for the update. The idea was to use the internal MQTT object to be async but I will work that way too.