First release

First release

Vibell
30

After months of testing and tweaking the doorbell prototype I’m extremely happy to share it with you.
I would never be able to accomplish this task without help the open source community.
Especially I would like to thank my wife for all support and Anna Mazgula for creating this web page.

    1. Hi,

      At the moment we support only camera module. Actually it would be quite easy to support usb cam. You would have to change gstreamer command line on server side ( look at GStreamerSensors.js in sensors-io-rpi).

      There were few reasons why Vibell uses camera module:
      1. It gives very low latency ( less then 100ms). With usb camera you may get up to several seconds latency.
      2.Very low CPU overhead ( 1-2%), as you get already compressed h264.
      3. H264 compression gives very low network usage for full HD stream.

  1. Hi,
    Interesting project. i tested your system by curiosity. It is good. On my side, i use raspberry pi to do broadcast video from Ip camera and android phones that i turned on into IP Cam.
    I have tried, to use configure vibell camera settings to interface with my IP cams.
    However, it is not working. Does your app only support streaming of the RaspiCam ?

    Jeremy

    1. Hi Jeremy,

      I didn’t test it with IP Camera, but the Android app should work with this.
      The IP Cam should be configured to broadcast over UDP using H264 encoding and RTP protocol.
      Can you share code which is used to broadcast video? I can try testing it.

  2. Is it possible to get the source code for the android app?
    I want use your software for 3 households, can I installate 3 buttons for 3 devices?

    1. Do you want to see button for each device on 1 Android app? I’m planning to publish source code for the android app soon.

  3. I did it, but audio not working when I try to stream video and It didn’t display on Zenfone5 but work on Tablet. What should I do?

  4. You have a little bug in the Howto….

    pi@raspberrypi ~/vibell $ npm update
    /usr/local/bin/node: /usr/lib/arm-linux-gnueabihf/libstdc++.so.6: version `GLIBCXX_3.4.20′ not found (required by /usr/local/bin/node)
    /usr/local/bin/node: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.16′ not found (required by /usr/local/bin/node)
    pi@raspberrypi ~/vibell $

    You can fix it with…

    wget node-arm.herokuapp.com/node_archive_armhf.deb
    and
    sudo dpkg -i node_archive_armhf.deb

    Greeting Björn

  5. I have a USBSoundCard on my Raspberry. „aplay Vibell.wav“ works good.
    But the Samsung Tab can not get away (push to talk). Here the console log

    LOG—————————————
    ERROR – stderr: ERROR: from element /GstPipeline:pipeline0/GstAlsaSink:alsasink0: Could not open audio device for playback.
    Additional debug info:
    gstalsasink.c(851): gst_alsasink_open (): /GstPipeline:pipeline0/GstAlsaSink:alsasink0:
    Playback open error on device ‘plughw:Set’: No such device

    INFO – stdout: Setting pipeline to NULL …
    Freeing pipeline …

    info – Process exited with code:255
    DEBUG – State changed to: {“on”:false,”sensorAddress”:””,”port”:5002,”samplingRate”:8000,”volume”:1,”multicastIface”:”eth0″,”device”:”plughw:Set”,”client”:”224.1.1.1″,”buffer_size”:1000}
    INFO – stdout: Setting pipeline to PAUSED …

    ERROR – stderr: ERROR: Pipeline doesn’t want to pause.

    ERROR – stderr: ERROR: from element /GstPipeline:pipeline0/GstAlsaSrc:alsasrc0: Could not open audio device for recording.

    ERROR – stderr: Additional debug info:
    gstalsasrc.c(743): gst_alsasrc_open (): /GstPipeline:pipeline0/GstAlsaSrc:alsasrc0:
    Recording open error on device ‘plughw:Set’: No such device
    ————————————
    I hope you can help me

    1. On RPI execute aplay -L this will list all sounds cards. The Vibell server is configured to use by default plughw:Set, you can change it on sensors web page.

    1. Hi,

      I’ve prototype version working in Firefox ( this is only web browser supporting h264 encoding). This requires few code changes on server and client side.
      I’m finishing the Android code updated, that’s why I haven’t published it yet.

  6. Hi,
    Do you mind suggesting me how to write the code gstreamer for stream video and audio on an android application like you did it on your app?

  7. Great work, will try this project on the weekend. I am not a developer, but if you need any kind of assistance with your work email me. I use Vera home automation and will patiently wait until you get the home automation integration working.

    Thanks
    Zaher

  8. Hi,
    Nice project. but didnt work i followed step by step the “How to”
    but i dont have video and the doorbell sounds continusly.

    what i do wrong?
    Thanks,

  9. Installed it late last night i was able to stream successfully. I have not tested the audio yet. I have Pi 3, would audio work on Bluetooth? I am planning to mount cheap waterproof Bluetooth speaker/mic combo outside the door. All enclosed in a project box with camera and PIR sensor. 🙂

    1. Hi,

      Today I’ll be pushing new version which uses pulseaudio default source and sink. It’ll be enough to configure pulseaudio to use Bluetooth speaker/mic. I had a plan to do similar thing, please let us know how it worked.

  10. Error: Cannot find module ‘sensors-io’
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:278:25)
    at Module.require (module.js:365:17)
    at new require (module.js:384:17)
    at Object. (/root/vibell/app.js:6:21)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:501:10)
    root@orangepi:~/vibell#

    please help me to get out from this error

  11. hi i m trying to run vibell on orangepi with raspbian img
    but there is some error with sys/class/gpio/export

    can i change it with rpi-gpio
    please help me and guide me to solve this.

    thank you.

Leave a Reply

Your email address will not be published. Required fields are marked *