1
Users / Re: USBUIRT How Many Devices Can it Control
« on: February 17, 2009, 06:19:16 am »
Has anyone hooked up two USBUIRT's to the same machine?
News:
Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
LinuxMCE sponsor
open.home.automation
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
Installation issues / Re: Ademco/Honeywell entire Vista series via VistaICM
« on: February 17, 2009, 05:55:22 am »
+= is likely the concatenation operator that connects strings together. (I have no Ruby experience, just C, Python, C++, Java, Perl, BASH, etc...)
The r and n is a carriage return and line feed combination. This looks like it is sending RAW http requests over the wire. When you type stuff into a web browser, email client, or ftp server-- the URL or request you type in the little window is not what is sent. What is sent is converted by the web browser into the raw protocol being used. In this case your are contacting the server with the GET protocol of HTTP. So you see the GET... The rest of the stuff you are seeing is the protocol in its raw form being sent over the wire.
In this example it looks like auth_s is being used to transform some data held in auth_a. I am not familiar enough with RUBY to tell you what this is doing exactly.
conn_.Recv(256, 5000)
My guess is that 256 is the buffer size used. 5000 could be the socket. A good Ruby manual or API would clarify this bit.
ecv = recv + buff //What the heck is this?
You are building recv from the buffer of 256 bytes by appending the buffer to the contents of recv as long as data is received.
The r and n is a carriage return and line feed combination. This looks like it is sending RAW http requests over the wire. When you type stuff into a web browser, email client, or ftp server-- the URL or request you type in the little window is not what is sent. What is sent is converted by the web browser into the raw protocol being used. In this case your are contacting the server with the GET protocol of HTTP. So you see the GET... The rest of the stuff you are seeing is the protocol in its raw form being sent over the wire.
In this example it looks like auth_s is being used to transform some data held in auth_a. I am not familiar enough with RUBY to tell you what this is doing exactly.
conn_.Recv(256, 5000)
My guess is that 256 is the buffer size used. 5000 could be the socket. A good Ruby manual or API would clarify this bit.
ecv = recv + buff //What the heck is this?
You are building recv from the buffer of 256 bytes by appending the buffer to the contents of recv as long as data is received.
3
Users / Re: Blu Ray please
« on: February 07, 2009, 01:28:20 am »
I thought the BD+ vm was cracked a few months ago? Am I mistaken, or is there some other obstacle?
4
Feature requests & roadmap / Re: Integrated Recipes Module
« on: January 24, 2009, 03:48:22 am »
Hopefully I am not barging in here, I have been lurking for quite a while.
It seems like several things would be of benefit here:
1. Recipe database. (recipe's ingredients cross referenced to UPC codes whenever possible).
2. foodstuff inventory of all food in house with UPC codes whenever possible.
3. Lookup of foodstuff's to find closet location, lowest price.
4. Generation of shopping list and map to mobile orbiter. Shopping list based on low inventory, expired perishables, and selected recipe's queued.
5. Orbiter support for built in camera eye or for laser bar code reader to manage inventory (Simply scan bar code on usage or purchase and update or decrement inventory).
If anyone is to implement this it would of great value to hook it up to a web service such as Google base or http://en.barcodepedia.com. These are used by Compare Everywhere and Shop Savvy. These apps (on the G-Phone) take a bar code from the camera input and then return the price of the item at local stores and internet stores.
On the home automation system, something like this would keep your foodstuff inventory, then when you generate your shopping list, you can be told where you can buy the items in your current list, with preferences given to the closest location to you, or the cheapest price in town, quality of fresh foods, etc. When your list is generated, you get a handy map showing where to buy each item and the shopping list and map are uploaded to the smart phone your orbiter is installed on. Mark off the products as you buy them by scanning them with your camera eye and then your local database is updated with the new inventory. Scan something using your phone's camera and if it is not in your local database, or known about by Google bases, you can choose to add the info manually.
It seems like several things would be of benefit here:
1. Recipe database. (recipe's ingredients cross referenced to UPC codes whenever possible).
2. foodstuff inventory of all food in house with UPC codes whenever possible.
3. Lookup of foodstuff's to find closet location, lowest price.
4. Generation of shopping list and map to mobile orbiter. Shopping list based on low inventory, expired perishables, and selected recipe's queued.
5. Orbiter support for built in camera eye or for laser bar code reader to manage inventory (Simply scan bar code on usage or purchase and update or decrement inventory).
If anyone is to implement this it would of great value to hook it up to a web service such as Google base or http://en.barcodepedia.com. These are used by Compare Everywhere and Shop Savvy. These apps (on the G-Phone) take a bar code from the camera input and then return the price of the item at local stores and internet stores.
On the home automation system, something like this would keep your foodstuff inventory, then when you generate your shopping list, you can be told where you can buy the items in your current list, with preferences given to the closest location to you, or the cheapest price in town, quality of fresh foods, etc. When your list is generated, you get a handy map showing where to buy each item and the shopping list and map are uploaded to the smart phone your orbiter is installed on. Mark off the products as you buy them by scanning them with your camera eye and then your local database is updated with the new inventory. Scan something using your phone's camera and if it is not in your local database, or known about by Google bases, you can choose to add the info manually.
Pages: [1]