Custom Search

Sensing and 支配（する）／統制する for hobbyists and schools: ThingSpeak, son of Pachube?

Most of the content on this page was created 早期に in 2011. The main 支配する, Pachube, seems long gone... it became "Xively" and that was swallowed up by the maw of Google. 行為／法令／行動する as you see fit on that fact. Me? I no longer 信用 Google to be about "doing good". Big is NOT always better.

So why leave this page in place? Because it 会談 about an idea along the road to "today", be it 9 Apr 19 when I wrote this new preface, or 2050.

IfTTT, ThingSpeak, and others I don't even know about, grew up と一緒に Pachube. They are alive and 井戸／弁護士席, April 2019. They 株 せいにするs. Get your 長，率いる around Pachube, and it may help you understand what 現在／一般に 利用できる services 許す you to do.

April 2019 preface ends... most of the 残り／休憩（する） is the article as it stood, 2011....

Data from the Internet of Things

Oh dear... a new enthusiasm! So little time, so many 場所／位置s.

This time it is Pachube.com... a 広大な／多数の／重要な idea.

As I understand it, the 指名する is a combination of "Patch 閣僚" and "YouTube". (A "patch 閣僚" 存在 where telephone or data cables come together for interconnections.)

But what is it good for??

I like to call Pachube, and the 類似の service "ThingSpeak" (more on that later.. it, and IfTTT (another usefujl service) are alive, 井戸／弁護士席, and MATURE at Aril 2019. (円熟した, but not ossified!)) a "YouTube for data junkies". Like YouTube, the service lets you 地位，任命する things to a central server. Like YouTube, what you've 地位，任命するd becomes 利用できる... either to everyone, or to people you've 認めるd 接近 to. Unlike YouTube, what you 地位，任命する does not need to be static. As I understand Pachube, and my 見解（をとる） is as an 部外者, I've no 関係 with the company beyond 存在 a newbie 使用者, it 目的（とする）s to do for live data streams what YouTube has done for the world's ビデオ photographers.

Imagine a "new feature" at YouTube which would 許す you to 始める，決める up 器具／備品 to take a photo of a rose bush every 15 minutes. And then 追加する that でっちあげる，人を罪に陥れる to an ever-growing time-lapse ビデオ of "the life of my rose bush".

Once you imagine that, you are on the way to しっかり掴むing what Pachube is for. Instead of images in a time lapse series, Pachube is about data points... the brightness of the sun at a popular holiday 目的地, the water level in a river, the noise level from a 主要道路. Etc.

Here's an example of something made 平易な by Pachube. 平易な for the people 供給（する）ing the data. 平易な for me to 接近 it. 平易な for me to embed the graph in this web page. 公式文書，認める: I do not have the data on my server.... just a bit of simple HTML in my web page, which collects and 現在のs the data whenever someone 接近s my web page. It is a graph of 気温's 手段d in someone's home in Santiago, Chile. (It was accessible with just "https://pachube.com/料金d/7901"). The "thing" at the 底（に届く） 示すs the （期間が）わたる over which data is 利用できる, and portrays it in low 決意／決議. The upper part is the sub-（期間が）わたる you have chosen with the sliders, in greater 決意／決議. (It probably will 負担 最初 showing the 最大限 利用できる data, the data for the past 30 days... if you 昇格 to a paid-for account, you can save and 接近 the data from greater timespans.)

It いつかs takes a moment to 負担.... While you wait, here is the code that is in my web page to 挿入する the interactive graph. I didn't have to 工夫する it. The Pachube 場所／位置 told me what I needed.

((The に引き続いて may be fatally 時代遅れの... the code is from 2011, and wasn't working one day when I 実験（する）d it in 2019. Sigh. But ii still illustrates the "data server" idea!))

<script type="text/javascript" src="http://apps.pachube.com/google_viz/viz.js"></script>
<script type="text/javascript">createViz(7901,0,800,180,"FF0066");</script>

The numbers... 7901,0,800,180,"FF0066"... 明示する...

• The Pachube datastream to 陳列する，発揮する
• The channel from that datastream to 陳列する，発揮する
• The width of the image on the web page
• The 高さ of the image
• The color to use for the line

(One stream... the data from me, for instance... can have many channels... indoor 気温, outdoor 気温, etc. The first channel, as in many things computery, is called channel 無.)

Pretty simple, no? (I did have to edit "JavaScript" to "javascript" to make the code pass the excellent HTML validator from W3, but the script still 作品!)

((There SHOULD be a graph here... but the code is from 2011, and wasn't working one day when I 実験（する）d it in 2019. Sigh. (Code 無能にするd, 9 Apr 19, to 改善する page 負担 time.))

Be sure to play with the sliders at either end of the lower squiggly line, and when you have done that, with the 水平の scroll 妨げる／法廷，弁護士業! Not too shabby, I'd say!

Be advised: At Apr 2011, 使用者s of 解放する／自由な accounts are 限られた／立憲的な to one month's history 貯蔵. If you 昇格 to a プロの／賛成の account, the nice people at Pachube may be able to "生き返らせる" data you uploaded more than a month ago, but they make no 約束s on that 得点する／非難する／２０.

(If you want a different example, you could once also 接近 data from a ブイ，浮標 in the ocean NE of Hawaii. (式のs, April 2019, that 2011 料金d is 負かす／撃墜する, too. It was 利用できる with just "https://pachube.com/料金d/5692")). I believe the surfer dudes used to 接近 that to see if it was 価値（がある） 長，率いるing to the beach 権利 now! (They certainly did 接近 something like that. The ブイ，浮標s were run by NOAA, a US 政府 program. Who knows if it 生き残るs in the GOP 時代, 2019.)

There's a やめる nice 料金d finder on the 場所／位置. Pachube isn't just a bunch of n3rds 地位，任命するing the 気温 in their gardens. There's a 料金d with the 放射（能） levels 近づく the 妥協d 核の 工場／植物 in Japan, for instance. There are also 料金d for things like the 現在の (近づく real time) price of electricity from a 明確な／細部 供給者. The 料金d can be tagged, the 料金d finder can filter on さまざまな 基準.

(You can even put the script in a little text とじ込み／提出する, save it as tmp.htm on your PC, and 接近 the とじ込み／提出する with your browser. You will get a "quick and dirty" look at the 料金d of your choice. You get the 料金d's number from the 料金d's info box from the Pachube Google 地図／計画する at the Pachube 場所／位置.

Going 支援する to the YouTube example: With today's YouTube, when you upload a ビデオ, you upload a "finished 製品". You can't continually 追加する new 構成要素 to a given ビデオ.

Now take a step 支援する from the YouTube 平行の.

Imagine that it is summer, that you sell surfing gear in むちの跡s, and that you have a little "測候所" that 監視するs sea 気温, 空気／公表する 気温, and wave 高さs. Wouldn't you want the world to be able to see how good things are on your beach?

This is where Pachube comes in. Once you get 始める，決める up, your data is fetched from your computer every 15 minutes, and 追加するd to the 古記録s at Pachube. (That's one way to 始める，決める things up. A good way to start, I would 示唆する.) And as often as they like, people 接近 the data, without any 負担 on your server... They would fetching the data from the 古記録 at Pachube.

(Alternatively, you could, of course, have a FarWatch 取り付け・設備. It would be simpler, and would 伴う／関わる より小数の third parties. But FarWatch means having the world 接近 your server for the 蓄積するd data, and it has より小数の features, is いっそう少なく 柔軟な.)

代案／選択肢s?

Before I proceed with その上の 詳細（に述べる）s of the Pachube service, I would like to について言及する "ThingSpeak". (Neat 指名する, don't you think? Pachube and ThingSpeak let "things" (sensors) "speak" (to the internet world)). April 2019, Thingspeak (and the 類似の- but- different IfTTT) are alive, 井戸／弁護士席, and 井戸／弁護士席 設立するd.

If you visit the ThingSpeak home page, don't overlook the "Channels" and "Apps" links at the upper left, by "Home", under "ThingSpeak"

At September 2011, I'd been 審理，公聴会 について言及する of ThingSpeak for a while, and I'd become disenchanted with 面s of Pachube, so I had a quick look at ThingSpeak.

I was delighted to find (Home page → Documentation → Tutorials) Using an Arduino + Ethernet 保護物，者 to Update a ThingSpeak Channel, which seemed to be a real, "grown up" app... 完全にする with 監視者 timer to reset the 関係 when needed, even.

However, ThingSpeak was almost as annoying as Pachube. It was hard (2011!) (for me, anyway!) to discern what it was 現実に all about, how to do it, once you 人物／姿／数字d out the answer to the first question. But I liked the ThingSpeak 場所／位置 a little more than the Pachube 場所／位置. Both seem to 要求する that you know what the services do before you can make much sense of the 場所／位置s. But that, in large part, is why I've written this page. You, Gentle Reader, do (if I've done my 職業) know what the services do, so now you can enjoy the services' 場所／位置s! (The Pachube 場所／位置 seemed a bit more 使用者-friendly just now, September 2011, as I re-visited the page you are reading, to edit it.)

Anyway... I have spent about an hour (2011) digging around the ThingSpeak 場所／位置. I know next to nothing about it. From things I've read どこかよそで, it seems to 申し込む／申し出 more to 使用者s who don't want to 支払う／賃金 service 告発（する），告訴（する）／料金s.

My main questions at the moment (2011) are: How do I 見解（をとる） more than the most 最近の 24 hours of data from a 料金d? How do I re-規模 the x-axis on a graph of data? Is there a ThingSpeak 同等（の） of the Pachube 選択 of letting the ThingSpeak server 接近 a page you 供給する, to "収穫" new data as it arises, or does ThingSpeak only support the other 代案／選択肢, also 申し込む／申し出d by Pachube, under which you as data provider "押し進める" the data to the data 古記録? What are the 限界s on 解放する／自由な 参加 in the service. Does ThingSpeak, like Pachube if you choose to turn on the feature, also 申し込む／申し出 ways to send messages to the computer 供給するing the data stream? (Pachube lets you, for instance, turn the lights off at your home, if you find from the Pachube-connected light sensor in your living room that you left them on. (See "Dashboard", below.) This does, of course, 要求する some work on your part to 始める，決める things up!)

I imagine there are answers to the questions above somewhere on the ThingSpeak 場所／位置... I just didn't have time to dig その上の to find them. I'll leave ThingSpeak now, but as you read その上の, remember that what I say about Pachube may 井戸／弁護士席 also 適用する, at least in some form, to ThingSpeak.

How do you use Pachube to publish data?

I'm going to answer that question "backwards", because of the audience I ーするつもりである this for.

First: How can you read （警察などへの）密告，告訴（状） from the many, many people sending their data up to Pachube for the world's enjoyment?

At one point, you could just go to Pachube.com with your usual web browser and browse around the pins on the 地図／計画する. (At September 2011, the 地図／計画する was still there, with pins, but (when I tried, anyway) clicking on a pin didn't do anything.) 支援する in January 2011, when the 地図／計画する was interactive, it wasn't 完全に intuitive (for me), but with very little struggle, I could soon see a graph of 気温 and electricity usage at a 前提 いっそう少なく than 10 miles from where I sat typing this. Graphs were 利用できる for the past 3 months, in January 2011. By April 2011, the noose had 強化するd: only one month of history was 存在 saved for 非，不，無-"プロの／賛成の" 使用者s. (It costs $1.99/ month at Apr 11 to have a year's history saved.) (Click on a datastream's Google 地図／計画する pin to open a little pop-up about the datastream. 権利-click on the datastream's 指名する, in the pop-up, and click "Open in new tab" to see more than the past 24 hours easily.) (Gaps when the 料金d was 負かす／撃墜する were dealt with 井戸／弁護士席, by the way.) (You can learn more about that particular 料金d from http://www.vaugrat.co.uk/, which appears to be the work of a competent hobbyist. (Oddly enough, at the moment, that 場所／位置... the source of the Pachube 陳列する，発揮する... doesn't について言及する the Pachube 代案／選択肢.

That's the simple 選択. There seem to be many, many other ways to tap into the さまざまな data 料金d. You could, for instance, have an RGB LED connected to your computer which would change color between blue and red, depending on the 気温 at some remote place of 利益／興味 to you. You could even 連合させる the 気温 and windspeed at the remote place in your computer, and 陳列する，発揮する the "気温" as 訂正するd for 勝利，勝つd 冷気／寒がらせる. In other words, although you fetch the data from Pachube over the internet, you are not 制限するd to mere "browser window" use of the data. You can 接近 the raw numbers... and if you have the 計算するing 技術s, plug them into programs which use them in all sorts of ways. The Pachube 場所／位置, in my 見解（をとる）, 会談 so much about these things that it is hard to see the underlying 出資／貢献 from Pachube, on which the other, 非，不，無-Pachube, elements are built!

Moving on... How would you SEND data to Pachube?

First you 始める，決める up an account. Rather like having a YouTube account. Within your account, you define "料金d". So, the person with the electricity use/ 気温 陳列する，発揮するs has a 料金d. Within the 料金d, you 始める，決める up "datastreams". Each datastream has an ID, which, 連合させるd with the 料金d's ID, is how readers of the data 接近 the datastream(s) they want.

To be a 供給者 of data to Pachube, you arrange, at the simplest, to have something like the に引き続いて 利用できる "to the world", from a computer under your 支配（する）／統制する....

<?xml 見解／翻訳／版="1.0" encoding="UTF-8"?>
<eeml xmlns="http://www.eeml.org/xsd/005">
  <環境>
    <data id="0">
      <value>36.2</value>
    </data>
  </環境>
</eeml>

In other words, you need to 始める，決める up a web server. This isn't as hard as it might seem. There's 詳細（に述べる）s in my FarWatch essays.

Once you've 始める，決める up your server... you don't need a 直す／買収する，八百長をするd IP 演説（する）／住所, by the way... and you can "see" the above with a browser, you スピードを出す／記録につける into your Pachube account, 始める，決める up a "料金d" (基本的に, you give it the URL of the above. I used an .xml 拡張, by the way), define your datastream(s)... the code above can be used 不変の if you have just one stream, and you gave it "0" for an ID... And your Pachube data 料金d will be up and running!

Um. One little 詳細（に述べる）. I said you could use the above code "不変の"? One of the "tricky bits" is making the "36.2" in the code above change whenever your sensor "sees" different 条件s. There is a 広大な／多数の／重要な 取引，協定 of help... too much!!? with this 味方する of things at the Pachube 場所／位置. I say "too much", although of course there can never be too much. But at Jan 2011, I couldn't see the underlying 機械装置 of Pachube because the 詳細（に述べる）s were too 目だつ... for me. The stuff on the 場所／位置 is "GGRRReat!!, as Tony T would say... but it needs 組織するing! (But not as much as my essays and 場所／位置s need editing and 組織するing!)

I said you need to make the 構成要素 above "利用できる to the world". That will be a "tricky bit" for many people. If you have an "always on" internet 関係, and are willing to leave a PC running 24x7, it really isn't too frightful. You don't even need a static IP 演説（する）／住所. Almost everything I've published about my FarWatch system will be 直接／まっすぐに useful for someone wanting to 料金d data to Pachube. 支配する to the 必要物／必要条件s I've already given, you could be 供給（する）ing data to Pachube without spending any money. (The "hard" parts are 平易な... and 解放する／自由な, and explained in the FarWatch pages. The "平易な" part, sensing something, and 繰り返して updating the EEML is a little harder. I don't have an "off the shelf, 解放する／自由な" 解答 to that... but could come up with one, and I'm sure others already have.)

Once you have arranged the above, the Pachube servers visit your 場所／位置 every 15 minutes, and 追加する the 最新の data to the 古記録 of data from your 料金d.

I have sketched just one of the Pachube 可能性s here.... the one that most excites me! Yes, having a 公然と 明白な server running under your direct 支配（する）／統制する is not all that 平易な, the first time you try to do it. But it isn't too difficult, either. For many, many home 使用者s (and, of course, 商売／仕事s), there will be very little new to buy or subscribe to. In fact, the biggest 脅し I see to the whole 企業 is the 可能性 that Pachube, once they have 批判的な 集まり, will "get clever", and 告発（する），告訴（する）／料金 too much for 参加. At the moment, 参加 is 解放する／自由な. But they do have costs, and those costs will have to be met. And they are, I believe, creating a 価値のある 資源 for which they could 告発（する），告訴（する）／料金... but there would still be room... and a 推論する／理由... for 解放する／自由な accounts.

But!....

Blush. I must 収容する／認める that I don't know a lot about I'm talking about. Yes, I should probably have said that before now.

It's like this... remember the 批評s implicit in the text below were made 支援する 近づく the start of 2011. At September 2011, the 場所／位置 looks more professional, and it has stayed in 商売／仕事....

I （機の）カム across 言及／関連s to Pachube at the end of 2010. I've been playing with computers and online communities for many years. I have a fair bit of experience with what can be done, and how to 認める the "good" communities with a 未来 and the flashes in the pan.

I struggled (and struggled, and struggled!!) with the Pachube 場所／位置. I tried to 調印する up to "talk" in their 会議. Twice. On 2 January, 2011, I had an 自動車-返答 to my 登録 試みる／企てる 説 that my 使用／適用 for a Pachube Community account was 未解決の, that they are having problem with spammers, and that "this" (the 延期する between 使用／適用 and 是認?) was an 試みる／企てる to slow the tide. They already have a captcha filter in place!

On 14 January, I decided to try 令状ing to a different 場所／位置 which also seemed connected with the people I believe are 支援 Pachube, and may one day get the rewards they deserve if someone like Google buy it. すぐに after, an email arrived "out of the blue" from an 匿名の／不明の someone at support@pachube.com. No 言及／関連 to the separate organization I'd emailed, but I suppose whoever wrote the email might have reasonably 推定する／予想するd me to infer the 関係. In a その後の 交流 of emails, a reply （機の）カム 支援する from a 指名するd (上級の) individual at Pachube. Now... much of what I'm 説 in さまざまな parts of this page is 批判的な. Keep in mind that I am bothering to put the page up... I do like the whole idea of Pachube, what they've done already, the directions they are moving in, the 率 at which they are 改善するing the 製品. If you 選ぶ up on the fact that I 港／避難所't really liked my interactions with elements of the 操作／手術, you can put it 負かす／撃墜する to me 存在 an egotistical, socially inept nerd... or you can ask yourself how it is that I am やめる happy at many places I go. Could it be something on the other 味方する of the conversation? Probably a bit of both!

My 批評 of the 失敗 to 示す who was 答える／応じるing was "answered" with the 観察 that my email 演説（する）／住所 isn't "Joe.Smith@gmail.com" (as if that means it is Joe Smith's!). その上に, I was 令状ing as a 私的な individual to a public organization. Apart from anything else, there might be a need to follow something up, and it is a lot easier if you can say "When I talked to (指名する) on (date)...", isn't it? And lastly, when I walk into a shop that wants 商売／仕事, to enquire about the services 利用できる, the 従業員 取引，協定ing with 顧客s often has a 指名する badge or plaque, or will give a 指名する if asked (so that things can be followed up with the person you started with)... without me needing to identify myself. 顧客. 供給者. But! As I said... I like the 場所／位置. If they want to continue giving people small 推論する／理由s to go away, or if they think I'm the only one who might be annoyed, it's their 場所／位置! I welcome ideas from the 使用者s of my 場所／位置s... and reserve the 権利 to make changes or not as I see fit.

They （人命などを）奪う，主張するd that requests for community accounts are "usually 認可するd within a few hours". And went on to say that my request wasn't 認可するd because I had not 調印するd up for a Pachube account. 井戸／弁護士席, no, I hadn't. As I couldn't made sense of pachube.com's "explanation" of getting started, I 手配中の，お尋ね者 to ask a few questions in the 会議 ("at the community") to see if Pachube was something I 手配中の，お尋ね者 to spend time on. Why 要求する two separate 登録s and スピードを出す／記録につける ins, if you have to be a Pachube-登録（する）d person to use the Pachube 会議? On 最高の，を越す of not having a Pachube account, I had dared to have an email 演説（する）／住所 that "didn't look like a human-created email 演説（する）／住所". Don't they 信用 the 有効性 of their captcha 機械装置? Why not send me a "答える／応じる with an email with the 資本／首都 of フラン as the 支配する line" if they thought my 登録 （機の）カム from a computer? My pages are 接近d more than a thousand times a day. I don't need any more spam, and so my email 演説（する）／住所 isn't Joe.Smith@yahoo.com, thank you.

A その後の email on this 支配する told me that their 見解（をとる） was that very few people 手配中の，お尋ね者 to 調査する the 問題／発行するs before 調印 up for a 場所／位置. わずかに circular logic, seems to me. How do they know how many people went away because they weren't going to 登録（する） with Pachube.com when they'd not had any answer from community.pachube.com, after trying to 登録（する）? I also inferred that they thought everything was so 平易な that people wouldn't need to ask questions, they could just jump in. Again... circular logic. How do they know how many people looked at the Pachube "getting started" 構成要素, and went away thinking "I can't understand that". Those people might have been good Pachube contributors... but we won't know, will we? The 障壁 to 入ること／参加（者） to datastreaming isn't the 登録（する）ing a Pachube 料金d... it is knowing what to do with it. And I for one have やめる enough 登録s, each of which exposes my email 演説（する）／住所, etc, to the 危険 of 乱用, without doing 登録s "just to see what it's like".

After first email discussing why my 試みる／企てる to 登録（する） had failed, from which I inferred that I would be let into the community, I tried again- no joy. Waited a bit, to let things work their way through the system. Finally sent a new email on the 支配する, 15 Jan, 10am London time. Around 3pm on the 17th (a Monday, which may 井戸／弁護士席 explain the gap) a new email arrived... and with it... Ta! Da! What I needed to get into the community pages!

So... while "not impressed" on one level, I do have to give 十分な 示すs to the people at Pachube for "sticking with" the problem for me, and 結局 解決するing the 問題／発行する. And no, I don't have a spam filter 封鎖するing emails from unknown sources, etc, etc. My "passwords" 文書 runs to seven pages of two columns of 6pt text.... I have "been there, done that".. usually much more easily.

Speaking of the email I received the 17th: In 事例／患者 I have complained here about the Pachube 決定／判定勝ち（する） to have separate スピードを出す／記録につける-ins for datastreams and for the Pachube community, I would like to say that I had a good answer on that point. Yes, it would be marginally easier for Pachube 使用者s if there was just one スピードを出す／記録につける-in to manage. But it is much easier for the people at Pachube to 追加する extra 層s of 安全... a very good thing... to the datastream 味方する of things if the スピードを出す／記録につける-in for that is separate. If I 反対するd before, I 身を引く the 反対, and applaud the Pachube 決定／判定勝ち（する）. And the 成果／努力s to 保護する the community pages from spammers are much 高く評価する／（相場などが）上がるd. But I 参加する in a number of high 容積／容量 communities which keep spammers out (mostly... enough, anyway), without 存在 so hard to get into.

But... even though I hope the 場所／位置 will 発展させる, I think the whole idea is tremendously exciting. I think it is 価値（がある） "fighting" with it to get to the Good Stuff. Hence this page! And hence the 4 hours of work to 始める，決める up my first Pachube 料金d! I already had a 公然と 明白な data serving server in my home, so you'll need to 予算 some time for that. Part of the 4 hours was 令状ing a program to move periodically a datum from my 使用／適用 to my Pachube-feeding EEML. But, with the guide here, you should be able to get a Pachube 料金d up much more quickly than I was able to. At 15 January, my 料金d has been working 罰金 for just over 4 days. (It is やめる fun in your 早期に days, as you begin to build a "追跡する" of historical data on your 料金d's page. By the way, the "4 day" graph doesn't always 含む the 最新の data, and the 24 hour" graph doesn't always 含む the 最新の data... or so it seemed to me. But I also think I know why, and both have, for me, always 含むd ALMOST the 最新の data.) It seems to be working. There were few problems along the way. The 推論する／理由 I already had a data server was that I already had a FarWatch 取り付け・設備, which 現在のs a frequently updated page of "static" html to the world, with 気温s in it. Much of the four hours was spent 令状ing a program to run in the same computer, periodically visiting the .html from the first program, and 生成するing the EEML page that Pachube needs.

By all means, 特に if you DO know about Pachube, 令状 (see below for eddress) with comments. For now, though, I don't want to go beyond What Is The Basic Idea, which is what I tried to talk about above. Yes... I know there are other ways to 与える／捧げる and draw from Pachube. No... I don't want to get into... here... how you "料金d" the EEML page that I discussed above. No... I don't want to get into the ins and outs of fancier EEML pages.... yet.

Other 選択s

The more I read bits, the more I begin to believe that the "手動式の" 選択 for updating the data from your stream at Pachube is 不正に 指名するd. I believe the "手動式の" approach can be used as I imagined it... a human 穏健なd, from- time- to- time upload of new data... a bit like uploading to YouTube, by 手渡す, an 延長するd 見解／翻訳／版 of a ビデオ you did earlier. However, it also seems that if you understand TCP/IP programming better than I do, that you can create programs which will do the "手動式の" 過程 automatically, and send up data as often (within 推論する／理由), or as seldom as you see fit. With the necessary TCP/IP 技術s, you are not 制限するd to the "地位，任命する a page of EEML, and Pachube will fetch the data every 15 minutes" model.

And here's a thought to conjure with... To 引用する from Pachube's 場所／位置....

Clicking embed, history, 誘発する／引き起こすs also 明らかにする／漏らすs the 誘発する／引き起こす dashboard. 誘発する／引き起こすs
enable you to 監視する any public datastream (i.e. not just your own) and, when a
確かな  条件 is met (e.g. its value 越えるs a 確かな  量) Pachube will send
out an HTTP POST request to the URL that you 供給する. This might 誘発する／引き起こす a script that
sends an email; a web service that sends SMS 警報s; an actuator that の近くにs a window;
a 装置 that switches off 力／強力にする; etc.

When I understand this adequately, I look 今後 to trying some of these things! I use FarWatch to keep an 注目する，もくろむ on places where I don't want the heat failing in winter. Even with FarWatchWatcher, it would be nice to receive an SMS should a room get 冷淡な. (By the way... I didn't get the "誘発する／引き起こす dashboard" until my 料金d had been collecting data for about two hours.)

Ha! 設立する an excellent tutorial on using a Pachube 誘発する／引き起こす! Remember: you can 始める，決める 誘発する／引き起こすs on other people's datastreams, 同様に as your own. Remember the Welsh surf shop I について言及するd above? Once they have their Pachube data streams up and running, then I easily will be able to get an email (or SMS, I would think) when the 気温 at the beach is over 22 C, and an email when the waves are above 1m. Maybe one day, I could even 始める，決める up a 誘発する／引き起こす that would "and" those two 条件s, but that's only a "frill" which would be nice. I think it is reasonable if the Pachube people concentrate on the 核心 機能（する）／行事s for now.

By the way... more good news: The Pachube 場所／位置 goes off to the URL you 明示する each time the 誘発する／引き起こす is invoked. The Pachube 場所／位置 does not （武器などの）隠匿場所 the PHP the 誘発する／引き起こす 原因（となる）s to be run. This is good news because: As long as you don't change the URL of the PHP, you don't need to visit your Pachube 支配（する）／統制する パネル盤 each time you 改訂する the code in the page of PHP.

For other neophytes to TCP/IP, it seems one of the "secrets" (for one of the possible "answers" to using the 誘発する／引き起こすs that are so 平易な to 始める，決める up) is to have a PHP script on a server with PHP script serving enabled. If you want the script to send an email, it helps a lot if the same server is 有能な of sending mail... Getting a script to send mail 経由で a different server is possible, but now you probably have to 追加する authentication 層s, too. In my 事例／患者, I have a Linux account at 1&1.com, so I just put my .PHP there. In a stripped 負かす／撃墜する form, all I needed was....

<?
//Created by TKB 09 Jan 2011
//With help from 1&1...
//http://faq.1and1.com/scripting_languages_supported/php_mail_explained/2.html
//Calling this DIRECTLY  should not show anything... but if there are
//errors in the script, calling it 直接／まっすぐに (from a browser) may reward you
//with error messages!

$to = 'XXX@YY.com';
$subject = "Mail from Pachube 誘発する／引き起こすd script";

$message = "This from PHP invoked by Pachube, " . date('F jS Y, h:i A');

$email = "YOU@YOURS.COM";
$headers = 'From: ' . $email . "\r\n" .
            'Reply-To: ' . $email . "\r\n" .
          'X-Mailer: PHP/' . phpversion();

mail ($to, $subject, $message, $headers);
?>

(Change the "XXX@YY.com" to the eddress you want the 警報 to got to, and "YOU@YOURS.COM" to your eddress.)

Let's say my 1&1.com 場所／位置 is "MySite.com"

I could 簡単に 蓄える／店 my script as "MyMailer.php", and then in the "誘発する／引き起こす Dashboard" tell Pachube to 遂行する／発効させる...

http://MySite.com/MyMailer.php

... when the 誘発する／引き起こす 条件s were met. (That's what you fill in as the "誘発する／引き起こす URL", although it is really the URL to go to when the 誘発する／引き起こす "goes off". BE SURE TO CLICK THE "update" BUTTON when making changes at the "誘発する／引き起こす Dashboard".

Another 詳細（に述べる）: If you ask for the script to be sent to you when, say, the 気温 is 無, thinking you'll get one message when the 気温 goes 負かす／撃墜する, passing 無, and another when it rises again, remember.... if the sequence of 気温 readings does, say, 0.3., 0.1, -0.1, -0.3 then the 気温 will never 現実に EQUAL 無 at a time when your sensor is looking at it, will it? But the good news is that Pachube is clever, and only 行為／法令／行動するs once on the 誘発する／引き起こす, so you can 始める，決める it to 活動させる／戦時編成する when the 気温 becomes いっそう少なく than 無. It does "turn itself 支援する on again" somehow. I 港／避難所't worked out the exact 詳細（に述べる）s. I 推定する all it takes is a reading of 無, but maybe there's some hysteresis built in.

Hope that's helped?

And you can make it fancier! When I wrote complaining about my difficulties in 調印 up to 参加する in the community, I について言及するd the URL of the page you are reading. The person at support who dealt with my （民事の）告訴 went the extra mile and 現実に read this page, carefully, and 答える／応じるd with the に引き続いて to a question that used to be here....

Regarding your PHP question about how to get parameters in the URL - best
way is to have the POST url more like
"http://MySite.com/MyMailer.php?variable=TEST"

and then retrieve that variable using something like:

$myvariable = $_GET['variable'];
echo $myvariable;

I 港／避難所't 実験（する）d that yet, but it looks 完全に reasonable to me, and I look 今後 to using it, and thank the person at pachube.support for that （疑いを）晴らす answer.

Because I didn't know the above when I was taking my first steps with 誘発する／引き起こすs, just 始める，決める up four very 類似の PHP scripts which 異なるd only in the 支配する line of the email. The four scripts had, for the 支配する: "tture went below 10", "tture went below 5", "tture rose above 5", tture rose above 10", and 始める，決める up four different 誘発する／引き起こすs, each 誘発する／引き起こすing a different script. The beauty of putting the message in the 支配する line, which can be done in one script, using parameters, is that you don't even have to open the email to know what it arose from.

___________

Make you laugh? Murphy (of the Famous 法律) was watching me as I was 調査するing Pachube 誘発する／引き起こすs....

Because of all the things I'd done "bolting Pachube の上に" my FarWatch 取り付け・設備, I did a system reset. It was very nearly at the point 示すd by the red arrow on the に引き続いて screenshot of my FarWatch 陳列する，発揮する from about 3 days after the reset. (The vertical gray lines 示す when it was midnight.)

The "情熱" color line, up and 負かす／撃墜する to the left of the arrows, nearly flat to the 権利 of it. is outside 気温, the parameter my Pachube 料金d 監視するs.

Where I live, a constant outdoor 気温 is 極端に unusual. I thought I broken my sensor with the reset! What were the 半端物s against the period of constant 気温 starting at almost 正確に／まさに the time I did the reset? Why did the 気温 line go flat so 突然の? Very unkind of Mr. Murphy, I thought! (For 24 hours, the 気温 didn't wobble even half a Celsius degree!) The "sawtooth" in red and orange is the 気温 in the house... いっそう少なく stable than the outdoor 気温, during this 半端物 time!

So... does Pachube work for me? I must 収容する／認める that I've not paid much attention to my Pachube 料金d in the months it has been running. In September 2011, I revisited the page you are reading, and, along the way went, 経由で Pachube's 場所／位置, to the then-現在の 記録，記録的な／記録する of what my 場所／位置 had 記録，記録的な／記録するd. All seemed 井戸／弁護士席. The past month's data （機の）カム up without a fuss. In September 2011, I 追加するd the script to give you what should be a live 陳列する，発揮する below of what my 場所／位置 has 記録，記録的な／記録するd recently... But all I got was a blank パネル盤. It seems you are 許すd only one datastream 陳列する，発揮する per page. Oh 井戸／弁護士席. I guess I could create 多重の pages to 見解（をとる） 多重の streams. Sigh.

Another nice feature: The Dashboard

I 港／避難所't played with it much yet, but it looks 冷静な／正味の! Once you have a server with actuators 大（公）使館員d, e.g. a server which could turn a red LED on if the 気温 報告（する）／憶測d by a Pachube 料金d fell below 氷点の, then you can also 始める，決める up a "dashboard" which would give you a web-accessible 支配（する）／統制する パネル盤 for the actuators on your server. They can be 数字表示式の (on/off) or analog (high/ medium/ low)

I think they are essentially "事実上の 料金d", which have 誘発する／引き起こすs just like your ordinary 料金d, but 異なる in where the data comes from.

There is a page about Pachube Dashboards which tells you more, and comes from an 権威のある source!

I think that the "secret" of PHP driven actuators may be in the PHP "exec()" 命令（する）.

広告 from page's editor: Yes.. I do enjoy 収集するing these things for you... hope they are helpful. However.. this doesn't 支払う／賃金 my 法案s!!! If you find this stuff useful, (and you run an MS-DOS or Windows PC) please visit my freeware and shareware page, download something, and 循環させる it for me? At least (please) send an 'I liked the 平行の port use page, and I'm from (country/ 明言する／公表する)' email? (No... I don't do spam) Links on your page to this page would also be 高く評価する／（相場などが）上がるd!

Other 事業／計画（する）s

Page has been 実験（する）d for 同意／服従 with INDUSTRY (not MS-only) 基準s, using the 解放する／自由な, 公然と accessible validator at validator.w3.org. Mostly passes.

AND passes...