webthingsio / addon-list Goto Github PK

Hello,
It will be nice to see DMX support.

Thanks

I have an AKASO smartlock working with bluetooth and the TTLock app.
I was hoping to get it recognized by the rasp PI gateway using the mozilla-iot app, but I don't see it in the list of supported hardware. I installed the gateway successfully on the raspPI and indeed the scan does not return anything like a smart lock.
Also, the TTlock app is scanning for a gateway and does not find it (it's expecting a G1/G2 gateway type, such as Sifely gateway).
Any idea / suggestion, any chance to see this material supported by mozilla-iot anytime soon?

Thanks a lot

There's already mod mi home app can easilly get device token. so it'll be nice if gateway support xiaomi vacuum cleanner and other mi home devices

Is there any place I can read up on the changes to the add-on system? Questions I have are:

• What is the manifest file for? Should both package.json and manifest.json be maintained? Should the manifest.json file be in the file list inside package.sh? It seems manifest.json no longer stores a list of files associated with the add-on?
• How should data now be stored? Are the settings still stored in the Gateway database, but should the persistence files now move from the config folder to another folder within the add-on folder?
• Will the UI extension adapter type also gain a Python option/example?
• How could/should I change, for example, the Candle Manager add-on so that it will become a UX extending add-on in the next version? Can add-ons be all three types at the same time? For example, the Voco add-on is both a notifier and adapter, but could perhaps also have a UI. Is that possible?
• Will UI extending add-ons still need to deal with copy-pasting authorization codes if they want to have access to all the things? I se some mention of the internal API being available now, but I'm not sure what that all means/could mean.
• How/when could I prepare and pre-test the new system before Gateway 0.10 launches? Could I compile the beta myself? Or is there a test image available to prepare add-ons for the transition?
• Any other things I should be aware of? :-)

Sorry for the long list. It's just that with the exhibit coming up I have to manage time well, and would like to prepare the add-on as early as possible.

The Candle smart home project will be launched on the 19th of October. Is there a tentative date for when version 0.10 of the WebThings Gateway will be released? I would love to show the more integrated version of the add-ons at Dutch Design Week.

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please reach out to [email protected].

(Message COC001)

As a user, I'd like to control my Honeywell Wi-Fi thermostat via the WebThings Gateway.

Updated package/tag here: https://github.com/infincia/lifx-adapter/releases/tag/v0.1.5

Includes @mrstegeman's very helpful PRs for the capability system, display name and a fix for color bulbs.

I'd open a PR but the package itself goes on Mozilla's AWS S3 account, and I'm not sure the checksum on the tar generated by whoever packages+uploads it would match the one I generated anyway :)

Update package with lastest bugs corrected:

  {
    "name": "telegram-sender-adapter",
    "display_name": "Telegram notification Sender",
    "description": "Simple telegram sending actions. Needs to be configured with chatid and token.",
    "author": "Ne0bot",
    "homepage": "https://github.com/ne0bot/telegram-sender-adapter",
    "license": "https://github.com/ne0bot/telegram-sender-adapter/blob/master/LICENSE",
    "packages": [
      {
        "architecture": "any",
        "language": {
          "name": "nodejs",
          "versions": [
            "any"
          ]
        },
        "version": "0.0.2",
        "url": "https://github.com/ne0bot/telegram-sender-adapter/releases/download/v0.0.2-beta2/telegram-sender-adapter-0.0.2.tgz",
        "checksum": "425720f580d36ba86cc11a0057ac315bb04f9b2b71dd0fd3dc0e92953c562ae1",
        "api": {
          "min": 2,
          "max": 2
        }
      }
    ]
  }

Adapter using ConBee USB stick to access Zigbee devices.

{
    "name": "zigbee-conbee-adapter",
    "display_name": "Zigbee adapter ConBee USB stick",
    "description": "Adapter for Zigbee  using  ConBee USB stick",
    "version": "0.9.0",
    "url": "https://github.com/tomasy/zigbee-conbee-adapter/releases/download/0.9.0/zigbee-conbee-adapter-0.9.0.tgz",
     "api": {
      "min": 2,
      "max": 2
    }
}

PS.
Is it possible to change description for my DateTime Adapter
from A DateTime adapter to create more advanced rules to
A DateTime adapter to create more advanced rules, Supports e.g. sunrise, sunset, weekends,...

hello, how do i install the list.json to my gateway. i need to use the pushbutton but its not installed in my gateway. running on rasspberry pi

Blynk is a popular IoT service with apps for iOS and Android.

References:

• https://www.blynk.cc/

Hi,

I tried installing the voice controller but it seems to not be working.
The internal logs give this error:

2020-05-02 18:30:42.538 INFO : Successfully created new thing Snips 2020-05-02 18:30:42.557 INFO : date-time-adapter: AddonManagerProxy: recv: {'messageType': 8207, 'data': {'deviceId': 'voice-controller', 'device': {'title': 'Snips', '@context': 'https://iot.mozilla.org/schemas', '@type': ['OnOffSwitch'], 'description': 'Voice Controller', 'href': '/things/voice-controller', 'properties': {'on': {'title': 'On/Off', 'type': 'boolean', '@type': 'OnOffProperty', 'links': [{'rel': 'property', 'href': '/things/voice-controller/properties/on'}]}}, 'actions': {}, 'events': {'wakeword': {'description': 'A wakeword was deteced', 'type': 'string', 'links': [{'rel': 'event', 'href': '/things/voice-controller/events/wakeword'}]}, 'speechinput': {'description': 'A voice command was detected', 'type': 'string', 'links': [{'rel': 'event', 'href': '/things/voice-controller/events/speechinput'}]}, 'command': {'description': 'A web thing command was executed', 'type': 'string', 'links': [{'rel': 'event', 'href': '/things/voice-controller/events/command'}]}, 'training': {'description': 'Wakeword training started', 'type': 'string', 'links': [{'rel': 'event', 'href': '/things/voice-controller/events/training'}]}}, 'links': [{'rel': 'properties', 'href': '/things/voice-controller/properties'}, {'rel': 'actions', 'href': '/things/voice-controller/actions'}, {'rel': 'events', 'href': '/things/voice-controller/events'}, {'rel': 'alternate', 'mediaType': 'text/html', 'href': '/things/voice-controller'}], 'layoutIndex': 5, 'selectedCapability': 'OnOffSwitch', 'iconHref': None}, 'adapterId': 'date-time-adapter', 'pluginId': 'date-time-adapter'}} 2020-05-02 18:30:42.570 INFO : date-time-adapter: AddonManagerProxy: recv: {'messageType': 8207, 'data': {'deviceId': 'voice-controller', 'device': {'title': 'Snips', '@context': 'https://iot.mozilla.org/schemas', '@type': ['OnOffSwitch'], 'description': 'Voice Controller', 'href': '/things/voice-controller', 'properties': {'on': {'title': 'On/Off', 'type': 'boolean', '@type': 'OnOffProperty', 'links': [{'rel': 'property', 'href': '/things/voice-controller/properties/on'}]}}, 'actions': {}, 'events': {'wakeword': {'description': 'A wakeword was deteced', 'type': 'string', 'links': [{'rel': 'event', 'href': '/things/voice-controller/events/wakeword'}]}, 'speechinput': {'description': 'A voice command was detected', 'type': 'string', 'links': [{'rel': 'event', 'href': '/things/voice-controller/events/speechinput'}]}, 'command': {'description': 'A web thing command was executed', 'type': 'string', 'links': [{'rel': 'event', 'href': '/things/voice-controller/events/command'}]}, 'training': {'description': 'Wakeword training started', 'type': 'string', 'links': [{'rel': 'event', 'href': '/things/voice-controller/events/training'}]}}, 'links': [{'rel': 'properties', 'href': '/things/voice-controller/properties'}, {'rel': 'actions', 'href': '/things/voice-controller/actions'}, {'rel': 'events', 'href': '/things/voice-controller/events'}, {'rel': 'alternate', 'mediaType': 'text/html', 'href': '/things/voice-controller'}], 'layoutIndex': 5, 'selectedCapability': 'OnOffSwitch', 'iconHref': None}, 'adapterId': 'date-time-adapter', 'pluginId': 'date-time-adapter'}} 2020-05-02 18:30:43.277 INFO : weather-adapter: Adapter: WeatherAdapter id weather-adapter pairing cancelled 2020-05-02 18:30:43.278 INFO : thing-url-adapter: Adapter: ThingURLAdapter id thing-url-adapter pairing cancelled 2020-05-02 18:30:43.279 INFO : zigbee-adapter: Cancelling pairing mode 2020-05-02 18:30:43.284 INFO : voice-addon: VoiceAdapter: VoiceAdapter id VoiceAdapter pairing cancelled 2020-05-02 18:30:43.285 INFO : spotify-adapter: Adapter: SpotifyAdapter id SpotifyAdapter pairing cancelled 2020-05-02 18:30:43.287 INFO : internet-radio: Adapter: InternetRadioAdapter id internet-radio pairing cancelled 2020-05-02 18:30:43.293 INFO : date-time-adapter: AddonManagerProxy: recv: {'messageType': 4100, 'data': {'adapterId': 'date-time-adapter', 'pluginId': 'date-time-adapter'}} 2020-05-02 18:30:43.294 INFO : date-time-adapter: date_adapter.py:51 INFO cancel_pairing 2020-05-02 18:30:43.788 INFO : voice-addon: different set of things. retrain: 2020-05-02 18:32:17.075 INFO : voice-addon: spawn training 2020-05-02 18:32:17.098 INFO : voice-addon: setCachedValueAndNotify for property on from false to true for voice-controller 2020-05-02 18:32:17.118 INFO : voice-addon: ERROR: python2: can't open file 'script_recording.py': [Errno 2] No such file or directory 2020-05-02 18:32:17.119 INFO : voice-addon: 2020-05-02 18:32:17.121 INFO : voice-addon: process exit code 2

any clues how to solve this issue?
cheers
Tobias

Hi,

Would be great if in the future you could support this, great work going on here!

https://en.tuya.com
https://pypi.org/project/pytuya/
https://github.com/codetheweb/tuyapi
https://github.com/codetheweb/homebridge-tuya

The adapter is still in beta (as in: not all MySensors types are supported). But the only people who will be tempted to use it right now are used to that.

The MySensors forum now has a Mozilla Webthings Gateway section, and news of this adapter is the first post there:
https://forum.mysensors.org/topic/10342/mozilla-webthings-mysensors-add-on-adapter

Things I don't know or am unsure about:

• I don't know if this is the correct architecture. I generated this .tgz on a Raspberry Pi 3B that was running the Mozilla Gateway 0.7 image, upgraded tot 0.8.
• I don't know if this is the correct link for a file on Github.
• I don't know that Gateway API version I should choose, so I just left it at 2 and 2. It's the same in the package.json
• I've added some config and schema things to the package.json. I've never seen it show up as options in the interface though? In the future I would like to use those configuration options to let the user select what type of radio/connection to make. For now the serial option is a fine first default. I could remove that bit since it's not currently used yet.
• How do I know if my package uses binaries?

{
  "name": "mysensors-adapter",
  "display_name": "MySensors adapter",
  "description": "Build your own smart home with this Arduino library",
  "author": "CreateCandle",
  "homepage": "https://github.com/createcandle/Webthings-mysensors-adapter",
  "license": "https://github.com/createcandle/Webthings-mysensors-adapter/blob/master/LICENSE",
  "packages": [
    {
      "architecture": "linux-arm",
      "language": {
        "name": "python",
        "versions": [
          "3.5", "3.6", "3.7"
        ]
      },
      "version": "0.0.1",
      "url": "https://github.com/createcandle/Webthings-mysensors-adapter/raw/master/mysensors-adapter-0.0.1.tgz",
      "checksum": "e04f99eb223e737ab2fd0205ee5363a794b128b1848b0bd1dd6b188d3f6758bf",
      "api": {
        "min": 2,
        "max": 2
      }
    }
  ]
}

I saw in WebThingsIO/gateway#165 that it's hard to get generic BLE support working because devices have different APIs behind the BLE connection. Niels Leenheer, creator of html5test, currently does a lot of presentations about WebBluetooth (e.g. the one at DACHFest I saw) and touting that e.g. MiPow Playbulb devices are nice to work with there. They have a nice collection of lights that work via BLE.
Niels has demo JS code (working with Chrome, which ships WebBluetooth) at https://github.com/BluetoothRocks/Lightbulb so following that it should not be hard to get an adapter done (and FWIW, he references the Open GATT Registry that has docs for more BLE devices).
I have got me some of those devices, so I'd be able to test, and as a Tech Speaker this would be great for doing demos as it works with what the RPi3 has on board by default - and the fewer pieces I need in a demo, the fewer points where things can fail. ;-)

Hi :)

I put together an Lifx smart bulb addon, available here:

https://github.com/infincia/lifx-adapter

Still needs some testing for color bulbs, and I haven't tested the color temperature stuff yet, but otherwise it is working well for my A19 bulb.

I wonder if my ESP Adapter might be removed now that there is a thing-url-adapter which I believe has the same/better functionality?

I would like to add my adapter for miLight WiFi controller and bulbs to the official add-on list:
https://github.com/atirage/miLight-adapter/releases/tag/v0.0.5.

Since my repo si not a fork of addon-list, I was not able to create a pull-request.

I've been poking around a bit after seeing https://hacks.mozilla.org/2019/04/introducing-mozilla-webthings/ and this list seems like it'd provide a good starting point for "what actually exists/works already", if one could a) easily find it and b) read it without reading JSON.

Candle Manager allows users to easily upload sketches to Arduino devices.

Source code: https://github.com/createcandle/Candle-manager-addon

It's part of the Candle project, which aims to show what a privacy friendly smart home could look like. Candle will be launched at the Dutch Design Week in October 2019.

https://www.createcandle.com (under construction)

This add-on should make it really easy to organize workshops in which people create their own privacy friendly smart home devices.

{
  "name": "Candle-manager",
  "display_name": "Candle manager",
  "description": "Candle manager allows you to easily upload sketches to an Arduino.",
  "author": "CreateCandle",
  "homepage": "https://www.createcandle.com",
  "license": "https://github.com/createcandle/Candle-manager-addon/blob/master/LICENSE",
  "packages": [
    {
      "architecture": "linux-arm",
      "language": {
        "name": "python",
        "versions": [
          "3.5", "3.6", "3.7"
        ]
      },
      "version": "0.0.2",
      "url": "https://github.com/createcandle/Candle-manager-addon/raw/master/Candle-manager-0.0.2.tgz",
      "checksum": "8dfe2ac05239f316571cca812e36b989724a354a47e478f80f4f141f23e747a8",
      "api": {
        "min": 2,
        "max": 2
      }
    }
  ]
}

No rush. This is release early, release often.

Things to think about:

• WebThingsIO/gateway-addon-python#49
• WebThingsIO/gateway-addon-python#50
• For now it creates its own 'external' interface (wizard) by launching a Flask server. Users can click on the link icon on the Create Candle thing, which this add-on creates, to visit that interface. In the future this might be replaced.
• The add-on initially downloads the Candle sketches, since that is its main purpose. Users can also add their own sketches by providing a link to an .ino file, which makes the add-on more generic.

Future versions may offer an 'advanced' setting, which will allow the 'external interface' to add sketches there, and perhaps allow users to copy-paste in their Arduino code.

Add support for Sonoff's DIY smart switches: https://sonoff.tech/product-category/wifi-diy-smart-switches

I' d like to request adding support to zmote IR transmitter devices:

• http://zmote.io/
• http://zmote.io/pro

This would bring control for many IR-devices in Mozilla WoT Gateway.

There is existing code and documentation that could probably be used for this:

• https://github.com/zmoteio
• Rest control over zmote
• https://github.com/alexmaret/openhab-binding-zmote
• openHAB forums discussions about zmote

The Google Home TTS adapter is broken and beyond useless. Consider removing it or at least making addon removal correctly clean up devices on removal.

Hi could you please update the mi flora adapter to the latest version 0.1.4

Support for Kleverness devices (http://www.kleverness.com/) would be nice

New install where network-presence-detection-adapter was added, with the result of taking all the CPU for hours with no sign of even finishing.

12089 root       20   0  923M 26528 10724 S 100.  0.3  2h14:36 python3 /root/.mozilla-iot/addons/network-presence-detection-adapter/main.py
12197 root       20   0  923M 26528 10724 R 100.  0.3  2h14:28 python3 /root/.mozilla-iot/addons/network-presence-detection-adapter/main.py
12102 root       20   0 1254M 68480 24004 S  0.7  0.9  1:50.30 node /root/os/gateway/src/addon-loader.js /root/.mozilla-iot/addons/systeminfo-adapter

The console does not show a huge amount of activity but still few things are not ok:

2019-12-04 15:34:01.911 INFO   : network-presence-detection: Saving updated list of found devices to json file
2019-12-04 15:34:01.911 INFO   : network-presence-detection: Error doing light arpa scan: name '_id' is not defined
2019-12-04 15:34:01.911 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.912 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: name 'key' is not defined
2019-12-04 15:34:01.912 INFO   : network-presence-detection: Saving updated list of found devices to json file
2019-12-04 15:34:01.913 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.913 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.913 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.913 INFO   : network-presence-detection: Error doing light arpa scan: name '_id' is not defined
2019-12-04 15:34:01.914 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.914 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.914 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.914 INFO   : network-presence-detection: Error doing light arpa scan: name '_id' is not defined
2019-12-04 15:34:01.915 INFO   : network-presence-detection: Error doing light arpa scan: name '_id' is not defined
2019-12-04 15:34:01.915 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.915 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.915 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.916 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.916 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.916 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.916 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.917 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.917 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.917 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.917 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.917 INFO   : network-presence-detection: Saving updated list of found devices to json file
2019-12-04 15:34:01.918 INFO   : network-presence-detection: Saving updated list of found devices to json file
2019-12-04 15:34:01.918 INFO   : network-presence-detection: Saving updated list of found devices to json file
2019-12-04 15:34:01.918 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.918 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: name 'key' is not defined
2019-12-04 15:34:01.919 INFO   : network-presence-detection: Saving updated list of found devices to json file
2019-12-04 15:34:01.919 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.919 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.919 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.920 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.920 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.920 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.920 INFO   : network-presence-detection: Error doing light arpa scan: name '_id' is not defined
2019-12-04 15:34:01.921 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.921 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.921 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.921 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.922 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.922 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.922 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.922 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.932 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.933 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.933 INFO   : network-presence-detection: Saving updated list of found devices to json file
2019-12-04 15:34:01.934 INFO   : network-presence-detection: Saving updated list of found devices to json file
2019-12-04 15:34:01.934 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.934 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:01.935 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: name 'key' is not defined
2019-12-04 15:34:01.935 INFO   : network-presence-detection: Saving updated list of found devices to json file
2019-12-04 15:34:01.935 INFO   : network-presence-detection: Brute force scan: error updating items in the previously_found dictionary: 'name'
2019-12-04 15:34:48.045 INFO   : getValue for property cpuTemperature for: CPU returning -1

Play internet radio stations.

• Uses ffplay, which is already built into the WebThings gateway. There are no other dependencies.
• It comes with a few default radio stations, but you can substitute and add your own.

It creates a thing with a few properties:

• Select the desired station from a drop-down.
• You can set the audio volume
• You can turn the radio on and off

It uses persistence to remember the previous state (e.g. selected radio station, volume, playing)

It has been designed to work well with the Voco voice add-on - e.g. is has easy and logical names for properties.

{
  "name": "internet-radio",
  "display_name": "Internet radio",
  "description": "Play your favourite online radio stations",
  "author": "Flatsiedatsie",
  "homepage": "https://github.com/flatsiedatsie/internet-radio",
  "license": "https://github.com/flatsiedatsie/internet-radio/blob/master/LICENSE",
  "type": "adapter",
  "packages": [
    {
      "architecture": "linux-arm",
      "language": {
        "name": "python",
        "versions": [
          "3.5",
          "3.6",
          "3.7",
        ]
      },
      "version": "0.0.2",
      "url": "https://github.com/flatsiedatsie/internet-radio/raw/master/internet-radio-0.0.2.tgz",
      "checksum": "c3a3489e121aebde8422316b40a1fdb67eeeacbbf8b2c6daa9087fdb79b8c023",
      "api": {
        "min": 2,
        "max": 2
      }
    }
  ]
}

As a user, I would like to control my Lutron Caséta devices.

Homebridge integration is available via the Lutron Caséta Smart Bridge Pro. The code for that plugin can potentially be reused for an adapter. See here: https://github.com/smockle/homebridge-lutron-caseta

The Voco Add-on allows users to control their smart home with their voice. It builds on the adapter/ideas from Andre Natal (but at the same time changes quite a bit).

The full capabilities are described at:
https://github.com/createcandle/voco

It has a built-in notifier, you may want to look at how that's been implemented.

Some questions:

• Currently the json below ("type": "adapter",) assumes a creation can only be one type at a time? If it's useful, I could open an issue to better allow hybrids adapter+notifiers?
• I noticed the new versions of the plugin infrastructure have some support for setting a minimum version of the WebThings Gateway? Since it uses a notifier, it would be best to set that to a minimum of 0.9.

The voco-X.X.X.tgz file is hosted on the domain of the project for which this add-on was developed. Github doesn't allow me to upload files that are bigger than 25Mb.

Designed for - and only tested on - a Raspberry Pi 4.

{
  "name": "voco",
  "display_name": "Voco",
  "description": "Privacy friendly voice control. Say 'Hey Snips' to start a voice command.",
  "author": "CreateCandle",
  "homepage": "https://github.com/createcandle/voco",
  "license": "https://github.com/createcandle/voco/blob/master/LICENSE",
  "type": "adapter",
  "packages": [
    {
      "architecture": "linux-arm",
      "language": {
        "name": "python",
        "versions": [
          "3.5",
          "3.6",
          "3.7",
        ]
      },
      "version": "0.0.7",
      "url": "https://www.candlesmarthome.com/assistant/voco-0.0.7.tgz",
      "checksum": "b6f0db7b8af89282d67253ba11955079a0db2beab2be93e6877a87620639956f",
      "api": {
        "min": 2,
        "max": 2
      }
    }
  ]
}

This project has received funding from the European Union’s Horizon 2020 research and innovation programme, under grant agreement No 786641.

https://github.com/snorp/insteon-adapter/releases/tag/v1.0.1

Hi,
I appreciate the work people do to make the Mozilla iot gateway work. My 7.0 ver. is working perfectly. Downloading 8.0 this morning. My request is for support for the Geeni/Merkury devices. These are doorbells, cameras and smart plugs selling at Wal-Mart and other places and from my experience seem to be well made and reasonably priced. I'm looking at the Merkury doorbell. I'd like to set up so motion detection to turns on the tp-link hs200 switched porch light on the gateway rather than go to ifttt. Would that keep all the processing local?

I have created an adapter to make it easier to create rules. This adapter contains the following properties

• sunset
• sunrise
• weekend
• dark
• hour
• minutes
• even hour

Latitude, longitude, timezone and horizon is configurable

With those properties you can create a rule like
Turn the bedroom lamp on only on weekdays
if the time of day is 06:13 and DateTime is not weekend, turn BedroomLamp on
or
To start the fan every second hour when it is dark
if DateTime is dark and DateTime minutesS is 20 and DateTime is even_hour, turn Fan on

The built package is not tested, but I hope it works.

   "name": "date-time-adapter",
   "display_name": "DateTime Adapter",
   "description": "A DateTime adapter to create more advanced rules",
   "version": "0.9.1",
   "url": "https://github.com/tomasy/date-time-adapter/releases/download/0.9.1/date-time-adapter-0.9.1.tgz",
    "api": {
     "min": 2,
     "max": 2
   }
}```

This is my first project in node. It is an adapter to send Telegram notifications.
Thanks!!

  {
    "name": "telegram-sender-adapter",
    "display_name": "Telegram notification Sender",
    "description": "Simple telegram sending actions. Needs to be configured with chatid and token.",
    "author": "Ne0bot",
    "homepage": "https://github.com/ne0bot/telegram-sender-adapter",
    "license": "https://github.com/ne0bot/telegram-sender-adapter/blob/master/LICENSE",
    "packages": [
      {
        "architecture": "any",
        "language": {
          "name": "nodejs",
          "versions": [
            "any"
          ]
        },
        "version": "0.0.0",
        "url": "https://github.com/ne0bot/telegram-sender-adapter/releases/download/v0.0.2-beta1/telegram-sender-adapter-0.0.2.tgz",
        "checksum": "f42c765ef7aec8b7a1a5f94751b90e15d7d54e4bdb9446a333036d9f660a249a",
        "api": {
          "min": 2,
          "max": 2
        }
      }
    ]
  }

Now that there are changes in the protocol will there be a new API version?

I've created an adapter which can play sound files on a raspberry pi.
Can you add it?

{
    "name": "sound-player-adapter",
    "display_name": "Sound Player",
    "description": "A Mozilla IoT Adapter for playing soundfiles on a raspberry pi",
    "version": "0.1.1",
    "url": "https://github.com/lmnch/sound-player-adapter/releases/download/v0.1.1/sound-player-adapter-0.1.1.tgz",
     "api": {
      "min": 1,
      "max": 2
    }
}

I could have sworn I saw a zigbee2mqtt add-on in the add-on list once. I bought all the required hardware, and then couldn't find the add-on in the list anymore.

The add-on did have some issues.

• Did not also install the zigbee2mqtt daemon on which it depended.
• Did not handle my devices properly

I hope I have fixed both issues. In this implementation zigbee2mqtt is not a daemon but just a node program in a sub-directory that gets started as a sub-process of the add-on.

This does require a git clone to take place before the add-on starts. I have created a build.sh file that does the git-pull. Is that the 'bootstrap.py' equivalent for node plugins?

I have tried to reach out to the original maker but have not had any response. Therefore I thought I'd share what I have created and leave it to debate if it should be added.

{
  "name": "zigbee2mqtt",
  "display_name": "Zigbee2MQTT adapter",
  "description": "Allows you to connect to a wide range of Zigbee devices with a single cheap dongle.",
  "author": "Kabbi and Flatsiedatsie",
  "homepage": "https://github.com/flatsiedatsie/zigbee2mqtt-adapter",
  "license": "https://github.com/flatsiedatsie/zigbee2mqtt-adapter/blob/master/LICENSE",
  "type": "adapter",
  "packages": [
    {
      "architecture": "linux-arm64",
      "language": {
        "name": "nodejs",
        "versions": [
          "57"
        ]
      },
      "version": "0.3.0",
      "url": "https://github.com/flatsiedatsie/zigbee2mqtt-adapter/raw/master/zigbee2mqtt-adapter-0.3.0.tgz",
      "checksum": "25b40a895c3e5371cac3250cf00757be12ec6da4fd60a4925853794352bf0e18",
      "api": {
        "min": 2,
        "max": 2
      }
    }
  ]
}

References WebThingsIO/gateway#1910

Hello Mozilla-IoT team,

I was thinking that having Kafka client integration in the gateway might be awesome. A Kafka client will allow the gateway to publish IoT data that later can be used for processing and storing.

I would love to contribute and have studied the gateway backend codebase fairly. I have some experience in using Kafka with Node.js.
With little guidance, I'll be able to make this idea into a feature.

How soon can I start with this?

Can you add an addon that I created?
Here is some infomation for this addon.

  {
    "name": "broadlink-adapter",
    "display_name": "Broadlink",
    "description": "Support ir devices with broadlink",
    "version": "0.1.0",
    "url": "https://github.com/sogaani/broadlink-adapter/releases/download/0.1.0/broadlink-adapter-0.1.0.tgz",
    "api": {
      "min": 1,
      "max": 1
    }
  }

Please add suport for standard modbus RTU (and ASCII) protocol.
A lot of sensors and gadgets handle it.
Issue can be related to https://github.com/mozilla-iot/gateway/issues/1459, as both Modbus RTU and DMX512 use RS485

Automatic detection of Sensibo devices

It would be terrific to see integration of an adapter for the Orvibo S20 Wifi switch product. There has been lots of success with these on Home Assistant and OpenHAB. I believe these platforms have working modules based on this python code from @cherezov:
https://github.com/cherezov/orvibo

I've made an adapter than scans a range of IP addresses for devices that respond with a json "Thing" response at http://IPAddress/thing during pairing. The devices found are configured with Properties from this response. "ESP" refers to the initial device I targeted, the Wemos Mini (ESP8266). I've included an example Arduino sketch and also PHP code that runs on an Apache web server. If you would like to incude it, it is

{
"name": "ESP-adapter",
"display_name": "ESP",
"description": "Support any web device that can accept/respond with json data",
"version": "0.3.0",
"url": "https://github.com/fiz1962/ESP-adapter/archive/0.3.tar.gz",
"api": {
"min": 1,
"max": 1
}
}

As a user I want to add devices to my gateway which use the OCF protocol

Specifications: https://openconnectivity.org/developer/specifications
Reference implementation: https://iotivity.org/
List of certified products: https://openconnectivity.org/certified-products