Git Product home page Git Product logo

vera-plugin-zibluegateway's Introduction

This plugin is no longer maintained

Vera-Plugin-ZiBlueGateway




Designed for Vera Control, Ltd. Home Controllers (UI7) and openLuup.

Introduction

This plugin is a gateway to the ZiBlue RFP1000, and brings compatibility with lots of 433 & 868Mhz protocols.




Please note these concepts first :

  • HAS: Home Automation System (Vera or openLuup)
    • UI: User Interface
    • Device: a device managed by the HAS (e.g. a Zwave motion detector).
  • Dongle: the ZiBlue RFP1000.
    • Equipment: a device exposed by the dongle (e.g. a 433 MHz temperature probe).
    • Transmitter: emits data/orders to dongle/HAS (e.g. a remote).
    • Receiver: reacts to transmitter orders, if pairing has been done (e.g. an outlet).
    • Virtual transmitter: simulates a transmitter and allows the HAS to control a receiver.

The plugin creates new devices (switches, dimmers, sensors, ...) in your HAS, corresponding to your equipments. These devices appear in the UI as the others (e.g. Z-wave devices) and can be used in scenes.

For specific manipulations (settings, association), the plugin has its own UI.

Requirements

Plug the dongle into an USB port of the HAS.

Installation on Vera

Get the plugin

  • Mios Marketplace

    This plugin is not available on the Mios Marketplace.

  • Alternate App Store on ALTUI

  • Github repository

    Upload the files in "luup files" in the Vera (by the standard UI in "Apps-->Develop Apps-->Luup files").

    Create a new device in "Apps-->Develop Apps-->Create device", and set "Upnp Device Filename" to "D_ZiBlueGateway1.xml".

Set the serial connection

Assign the serial port of the dongle to the plugin : go to "Apps/Develop Apps/Serial Port Configuration" and select from "Used by device" drop down list the "ZiBlue Gateway". Set the following parameters :

Baud Rate : 115200
Data bits : 8
Parity    : none
Stop bits : 1

Installation on openLuup

Get the plugin

  • Alternate App Store on ALTUI

  • Github repository

Set the serial connection

  1. Retrieve the usb device

With the command "dmesg", you will find the mounted point.

[    7.151351] usbcore: registered new interface driver usbserial
[    7.151525] usbcore: registered new interface driver usbserial_generic
[    7.151663] usbserial: USB Serial support registered for generic
[    7.230878] usbcore: registered new interface driver pl2303
[    7.231047] usbserial: USB Serial support registered for pl2303
[    7.231167] pl2303 1-1.3:1.0: pl2303 converter detected
[    7.323296] usb 1-1.3: pl2303 converter now attached to ttyUSB0

In this example, the USB device is reachable on /dev/ttyUSB0

  1. Install Serial to Network Proxy

Install ser2net

sudo apt-get update
sudo apt-get install ser2net
  1. Configuration

Edit the file "ser2net.conf"

sudo nano /etc/ser2net.conf

Add this line (it depends on your device)

3481:raw:0:/dev/ttyUSB0:115200 8DATABITS NONE 1STOPBIT
  1. Restart the deamon
sudo /etc/init.d/ser2net restart
  1. Declare the serial connection

Set the attribut "ip" to "127.0.0.1:3481", on the plugin instance.

Add your equipments

  1. The "Discovered equipments" tab displays the equipments exposed by the dongle and not yet known from the HAS.

  1. To be able to use the equipments on the HAS, you have to :
  • select a modeling (definition of the relationships between equipment and devices, by features).
  • the type of device can sometimes be chosen: this will not change the functionality but its representation in the UI.
  • have the HAS learn this modeling.

For example, an equipment measuring temperature and humidity will be associated with 2 devices on the HAS : a temperature sensor and a humidity sensor.

Known equipments

The equipments, exposed by the dongle and learned by the HAS, behave themselves as standard devices on the HAS.

You will find all the learned equipments in the "Managed equipments" tab.

Equipment/Device settings

  1. In the "Managed equipments" tab, click on the button "Action" of the device linked to the equipment.

  1. You can change the behavior of your device (e.g., change the parameters "Pulse" or "Toggle" of a transmitter).

Association

You can define a link between your device and another device in your HAS. It allows you to bind devices without having to use scenes.

From the tab "Managed equipments" in the plugin, click on the action "Associate" of the device you wish to link. Then select the compatible devices and validate.

Association means that changes on the device will be passed on the associated device (e.g. if the device is switched on, the associated device is switched on too).

Logs

You can control the plugin execution in the logs. Just set the variable "DebugMode" to 1. Then in a ssh terminal :

  • on Vera :
tail -f /var/log/cmh/LuaUPnP.log | grep "^01\|ZiBlueGateway"
  • on openLuup :
tail -F {openLuup folder}/cmh-ludl/logs/LuaUPnP.log | grep -a "ERROR\|ZiBlueGateway"

vera-plugin-zibluegateway's People

Contributors

vosmont avatar

Watchers

 avatar  avatar

Forkers

mikespoon

vera-plugin-zibluegateway's Issues

RTS shutter on Vera

I'm trying to add a Somfy RTSshutter to my VERAplus through the rfplayer. I followed your steps on the readme . with the remote control the shutter is discovered and added to managed devices et dashboard. But it still not works to open or close the shutter. did I missed something?

Pb avec Anémometre OREGON

Mon Anémometre Oregon semble être reconnu mais le plugin crée le Container avec des erreurs :
Command.deferredProcess Error: [string "--[[..."]:510: attempt to call field 'setWindSpeed' (a nil value)
Command.deferredProcess Error: [string "--[[..."]:514: attempt to call field 'setWindDirection' (a nil value)

les logs à la création du container :
08 10/27/18 13:42:55.317 JobHandler_LuaUPnP::HandleActionRequest device: 60 service: urn:upnp-org:serviceId:ZiBlueGateway1 action: CreateDevices <0x73902520> 08 10/27/18 13:42:55.318 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:upnp-org:serviceId:ZiBlueGateway1 <0x73902520> 50 10/27/18 13:42:55.324 luup_log:60: (ZiBlueGateway::createDevices) Create devices [{"protocol":"OREGON","equipmentId":41472,"deviceType":"WIND_SENSOR","featureNames":["direction","wind speed"],"settings":["transmitter"]}] <0x77974000> 50 10/27/18 13:42:55.333 luup_log:60: (ZiBlueGateway::createDevices) Equipment 'OREGON;41472' - Add device 'OREGON;41472;1', type 'WIND_SENSOR', file 'D_WindSensor1.xml' <0x77974000> 50 10/27/18 13:42:55.414 luup_log:60: (ZiBlueGateway::createDevices) Equipment 'OREGON;41472' - Device #78(OREGON 41472/1) has been created <0x77974000> 02 10/27/18 13:42:55.415 luup_log:60: (ZiBlueGateway::Device.getInfos) Can not get infos for device type '78' <0x77974000> 50 10/27/18 13:42:55.416 luup_log:60: (ZiBlueGateway::Equipments.add) Add equipment 'OREGON;41472', features [ "direction", "wind speed" ], device #78, type unknown <0x77974000>

les logs suivants
luup_log:60: (ZiBlueGateway::Network.receive) A 33: { "frame": { "header": { "rfLevel": "-92", "protocolMeaning": "OREGON", "protocol": "5", "dataFlag": "0", "infoType": "6", "cluster": "0", "frameType": "0", "rfQuality": "2", "floorNoise": "-100", "frequency": "433920" }, "infos": { "adr": "162", "id_PHYMeaning": "WGR800", "lowBatt": "0", "id_PHY": "0x1A89", "channel": "0", "measures": [ { "value": "0.0", "type": "wind speed", "unit": "m/s" }, { "value": "315", "type": "direction", "unit": "degree" } ], "qualifier": "48", "adr_channel": "41472", "subType": "0" } } } <0x743b8520> 50 10/27/18 19:03:04.480 luup_log:60: (ZiBlueGateway::Command.protectedProcess) Device #78 - Do command 'wind speed' with data '{ "value": "0.0", "type": "wind speed", "unit": "m/s" }' <0x75211520> 01 10/27/18 19:03:04.481 luup_log:60: (ZiBlueGateway::Command.deferredProcess) Error: [string "--[[..."]:509: attempt to call field 'setWindSpeed' (a nil value) <0x75211520> 50 10/27/18 19:03:04.482 luup_log:60: (ZiBlueGateway::UI.showError) Display message: Error (see tab) <0x75211520> 06 10/27/18 19:03:04.483 Device_Variable::m_szValue_set device: 60 service: urn:upnp-org:serviceId:ZiBlueGateway1 variable: LastMessage was: New equipment discovered now: <font color="red">Error (see tab)</font> #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x75211520> 50 10/27/18 19:03:04.492 luup_log:60: (ZiBlueGateway::Command.protectedProcess) Device #78 - Do command 'direction' with data '{ "value": "315", "type": "direction", "unit": "degree" }' <0x75211520> 01 10/27/18 19:03:04.493 luup_log:60: (ZiBlueGateway::Command.deferredProcess) Error: [string "--[[..."]:512: attempt to call field 'setWindDirection' (a nil value) <0x75211520> 50 10/27/18 19:03:04.494 luup_log:60: (ZiBlueGateway::UI.showError) Display message: Error (see tab) <0x75211520>

Pb Erreur

version 1.3.8
Erreur suivante récurrente :
Network.processFrame - equipmentId has to be greater than 0
Network.receive - Error with RF frame: ZIA33{ "frame" :{"header": {"frameType": "0", "cluster": "0", "dataFlag": "0", "rfLevel": "-96", "floorNoise": "-101", "rfQuality": "2", "protocol": "5", "protocolMeaning": "OREGON", "infoType": "4", "frequency": "433920"},"infos": {"subType": "1", "id_PHY": "0x0000", "id_PHYMeaning": "ProbeV1", "adr_channel": "0", "adr": "0", "channel": "0", "qualifier": "0", "lowBatt": "0", "measures" : [{"type" : "temperature", "value" : "-0.0", "unit" : "Celsius"}, {"type" : "hygrometry", "value" : "0", "unit" : "%"}]}}}

ne fonctionne pas avec mon installation x10

bonjour, j'ai acheté une box vera edge, un module rfplayer, mis à jour les firmwares , pour faire fonctionner mon installation x10. j'ai installé votre module ziblue gateway en suivant le tuto.

les modules x10 sont reconnus en mode discovery mais impossible de réaliser d'apprentissage, ni de créer de module. pour l'instant je suis incapable de me servir de ma box 👎 help !
merci.
tell me if traduction in english needed
arnaud

On Vera: Visonic Device is created but not triggered.

Hello,
thanks for the nice job.
On Vera Edge my Visonic door sensor (MTC 302) is seen in the discovered equipment and subsequently correctly created.
It is listed in the discovered and managed list.
Unfortunately in the Device page, in the Vera Interface, the device created never gets triggered.
In the plugin pages (both: the discovered and managed devices), the incoming signals from the hardware are received as I can see date/time stamp and signal strength changing.
If I go in the Vera interface in Advanced Settings, I can see that LastTrip is always the same and is the time of creation.
If I Assocciate, in the Managed List, the device with any other device, it does not work.
To checkout plugin functioning and as proof, I created an Oregon device and it works properly
On device Params id_parent is correct (plugin #).
No errors are detected in the plugin.

Erreur en intégration Oregon Rain_meter

Bonjour,

Mon pluviometre OREGON est bien détecté mais lorsque je clique sur Apprendre, et que je fais OK, j'ai une anomalie Error: [string "--[[..."]:1200: attempt to concatenate local 'name' (a nil value) et l'objet ne se créé pas.

Une idée ?

Cordialement,

Not working with RFPlayer with 1.23 firmware

I have just bought the RFPlayer, I have introduced 6 Parrot codes but when I want to add the device it fails, I do not know if I have to use the beta version or the 0.3 one.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.