Jump to content


Photo
- - - - -

[download] Module: Obihai OBi110 Driver


  • Please log in to reply
9 replies to this topic

#1 123

123

    Cocoonut

  • Registered
  • PipPipPipPip
  • 1978 posts
  • Location:Montreal, QC
  • Experience:average
  • Software:Premise
  • Hardware:Elk M1

Posted 10 March 2012 - 03:38 PM

Posted Image

File Name: Module: Obihai OBi110 Driver
File Submitter: 123
File Submitted: 10 Mar 2012
File Updated: 10 Mar 2012
File Category: Premise
Author: 123
Contact: 123
Version: 1.7

The Obihai OBi110 Driver allows Premise Home Control to receive data from an Obihai OBi110 VOIP ATA device. It reports the following:
  • Inbound call number and name
  • Outbound call number
  • Ring status
  • Hook status
  • Number of new voicemail messages
It also allows you to use any house phone to enter a command code, a “Task Command”, which can:
  • activate lights
  • change thermostat temperature
  • perform other automation tasks
The OBi110 driver is designed to work with the CallMonitor module but can also work with a Premise’s existing Telephone object. The driver collects its data from the OBi110's syslog facility.


NOTE:
The ability to report the number of voicemail messages depends on the specifics of your VOIP provider. This driver was tested using SIP service provided by http://voip.ms/.

Click here to download this file

#2 123

123

    Cocoonut

  • Registered
  • PipPipPipPip
  • 1978 posts
  • Location:Montreal, QC
  • Experience:average
  • Software:Premise
  • Hardware:Elk M1

Posted 10 March 2012 - 04:08 PM

FYI: The zip archive contains the Module and full documentation.

The initial release is V1.7. The first uploaded file was mislabelled as 2.6.

Edited by 123, 10 March 2012 - 04:08 PM.


#3 etc6849

etc6849

    Cocoonut

  • Registered
  • PipPipPipPip
  • 1604 posts
  • Location:Irmo, SC
  • Experience:average
  • Software:Premise
  • Hardware:Elk M1
  • Tech:X10-RF, Z-Wave, Custom
  • Phone:OBi100/110

Posted 11 March 2012 - 03:30 AM

FYI: if you are using google voice and want outbound calls to be recorded in Premise, you must revert back to an older firmware build for the OBi110 before build 2669.

http://www.obitalk.c...hp?topic=2445.0

The catch is if you do this, the message waiting indicator may not work on your phone if you use an older firmware version (this was fixed in build 2675).

#4 123

123

    Cocoonut

  • Registered
  • PipPipPipPip
  • 1978 posts
  • Location:Montreal, QC
  • Experience:average
  • Software:Premise
  • Hardware:Elk M1

Posted 11 April 2012 - 12:02 PM

As per etc6849's post, firmware build 2669 eliminated the syslog message that reported the Outbound call. As a result, drivers that relied on this message (like the ObiHai OBi110 driver) were left empty-handed.

To compensate for what was removed in build 2669, I now extract the Outbound call from a message reported by the SIP provider (voip.ms). I have no idea if this message is reported by all SIP providers but I do know it works with voip.ms.

Simply replace your current version of the OBihaiServer perl script with the attached file (OBihaiServer_V1.2).

Attached Files



#5 w84no1

w84no1

    Dedicated Cocooner

  • Registered
  • PipPipPip
  • 110 posts
  • Location:Central Virginia
  • Experience:average
  • Software:EventGhost, Premise
  • Tech:Z-Wave
  • Audio:AirPlay
  • Video:XBMC
  • CCTV:ip
  • Phone:OBi100/110

Posted 12 April 2012 - 01:17 PM

Freecnam has changed to use an API.
This needs to be changed
my $url = "http://freecnam.org/dip?q=$CIDNumber";
to
my $url = https://api.opencnam.com/v1/phone/" . $CIDNumber . "?format=text";


#6 123

123

    Cocoonut

  • Registered
  • PipPipPipPip
  • 1978 posts
  • Location:Montreal, QC
  • Experience:average
  • Software:Premise
  • Hardware:Elk M1

Posted 12 April 2012 - 03:30 PM

Thanks for that! I don't use the phone number lookup feature (CID supplied by my SIP provider) but it is useful to anyone who uses Google Voice because they don't supply CID.

I'll add it to the script and post an updated version after I incorporate another update from etc6849.

#7 w84no1

w84no1

    Dedicated Cocooner

  • Registered
  • PipPipPip
  • 110 posts
  • Location:Central Virginia
  • Experience:average
  • Software:EventGhost, Premise
  • Tech:Z-Wave
  • Audio:AirPlay
  • Video:XBMC
  • CCTV:ip
  • Phone:OBi100/110

Posted 12 April 2012 - 03:52 PM

Right now I just use perl to monitor the Obi's syslog. When I get a call, the CID info is sent to all my Windows Media Center machines running VMC Controller and displayed on the screen for 10 seconds. I use Google Voice so I need the lookup.

I am interested in using Premise for my home automation and that is how I found this thread. Glad I could help.

#8 etc6849

etc6849

    Cocoonut

  • Registered
  • PipPipPipPip
  • 1604 posts
  • Location:Irmo, SC
  • Experience:average
  • Software:Premise
  • Hardware:Elk M1
  • Tech:X10-RF, Z-Wave, Custom
  • Phone:OBi100/110

Posted 13 April 2012 - 05:30 PM

Awesome, welcome aboard! Let us know if we can help sway you towards using it as we need more members!

VMC Controller can work with Premise too (I use it with a make shift windows media center module I never completed), using this work around:
http://cocoontech.co...post__p__111854

#9 w84no1

w84no1

    Dedicated Cocooner

  • Registered
  • PipPipPip
  • 110 posts
  • Location:Central Virginia
  • Experience:average
  • Software:EventGhost, Premise
  • Tech:Z-Wave
  • Audio:AirPlay
  • Video:XBMC
  • CCTV:ip
  • Phone:OBi100/110

Posted 13 April 2012 - 07:45 PM

Cool, I am looking at getting a wireless IP controlled thermostat. Can I use the same trick to send commands to the thermostat? Or does premise already support ip thermostats?

Downloading premise as I type this :)

#10 123

123

    Cocoonut

  • Registered
  • PipPipPipPip
  • 1978 posts
  • Location:Montreal, QC
  • Experience:average
  • Software:Premise
  • Hardware:Elk M1

Posted 14 April 2012 - 03:10 PM

I'm unaware of any Premise drivers for IP-based thermostats. However, it doesn't mean one cannot be written as a Module. Premise supports TCP IP communications. The OBi110 uses UDP IP and that's why perl was employed to convert UDP to TCP.

Once you've selected the thermostat, post a new thread listing the model and we can help you write a driver for it.

FWIW, I have a driver for a HAI Omnistat2 thermostat (not IP-based).

Edited by 123, 14 April 2012 - 03:11 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users