tag:blogger.com,1999:blog-4922503085503427986.post4172061288931192955..comments2024-03-18T17:46:29.521-07:00Comments on Desert Home: Using the Google Charts API with Xively (Pachube -> Cosm -> Xively)davehttp://www.blogger.com/profile/11608589214882334649noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-4922503085503427986.post-86480470762492938192014-05-23T15:44:26.278-07:002014-05-23T15:44:26.278-07:00Sorry for seeing this late, you've probably fi...Sorry for seeing this late, you've probably fixed it already. Yes, you need to make a public read only key for it. If you prowl through the Xively documentation long enough you'll run across this.davehttps://www.blogger.com/profile/11608589214882334649noreply@blogger.comtag:blogger.com,1999:blog-4922503085503427986.post-43178543064150324252014-05-23T15:42:52.628-07:002014-05-23T15:42:52.628-07:00That sounds like a problem I had once where my con...That sounds like a problem I had once where my conversion of the date coming back was messed up. Take a look at the JSON you get back and then at the method used to reformat it for the chart. I severly messed that up a couple of times.davehttps://www.blogger.com/profile/11608589214882334649noreply@blogger.comtag:blogger.com,1999:blog-4922503085503427986.post-20981043907569237632014-05-23T15:15:38.149-07:002014-05-23T15:15:38.149-07:00Late to the party, but named datastreams do work. ...Late to the party, but named datastreams do work. ...&datastreams=Power_Usage,Back_Porch&... no problem. Interestingly, when I add a third datastream the chart has "gaps" of ~ 20 minutes where the line spans point-to-point even though Xively graphs show the "missing" data. Adding a fourth datastream increases the "gap" to ~120 minutes.Anonymoushttps://www.blogger.com/profile/00987095142263961055noreply@blogger.comtag:blogger.com,1999:blog-4922503085503427986.post-27893731373035241632014-03-31T23:47:14.504-07:002014-03-31T23:47:14.504-07:00Hi Dave,
have two problems with the html. I have t...Hi Dave,<br />have two problems with the html. I have tried to just change the feed ID and the API key. Then ask me to give user and password. (why? :) maybe should change the feed to public access? )<br />When HTML run under IE it says datastreams[0] is null or not an object...(without changing anything, your code run fine)<br />Can you help me with this?<br />Thanks!<br />GaborAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-4922503085503427986.post-86330373992807551012014-03-25T17:50:35.830-07:002014-03-25T17:50:35.830-07:00That should be all you need to get it going. Try ...That should be all you need to get it going. Try using the Chrome brower, and when it fails, right click on the screen and 'examine element'. When you get the element window open, click on console and it should show you an error message. See what that is and it will give you a clue.<br /><br />The code above needs at least 24 hours of data accumulated on Xively before it will work though. So, if you just started putting data up there for the feeds you're trying to read, just wait a day and try it again. I didn't realize I had that problem until recently because I've always had a years worth of data on Xively and never encountered the problem.davehttps://www.blogger.com/profile/11608589214882334649noreply@blogger.comtag:blogger.com,1999:blog-4922503085503427986.post-52842738844072543372014-03-25T12:11:15.806-07:002014-03-25T12:11:15.806-07:00I'm having trouble getting this to work for my...I'm having trouble getting this to work for my xively account. When I change the feed and key on the "var url" declaration to my device values, no graph appears.. I am very new to HTML, are there any other variables I need to change to make this code work for me?Anonymoushttps://www.blogger.com/profile/00899439273266528869noreply@blogger.comtag:blogger.com,1999:blog-4922503085503427986.post-61917913942832445172014-01-04T07:56:17.931-07:002014-01-04T07:56:17.931-07:00Actually, I don't think it will without muckin...Actually, I don't think it will without mucking around a bit. It's based on the way Xively worked back in the days when it was Pachube and their api was easier to understand. So, it goes after field 1, field 2, etc.<br /><br />You can try playing with the actual URL sent to Xively a bit and see what comes back though; at least that part's pretty easy to try out.davehttps://www.blogger.com/profile/11608589214882334649noreply@blogger.comtag:blogger.com,1999:blog-4922503085503427986.post-37362138885046853242014-01-03T20:30:58.442-07:002014-01-03T20:30:58.442-07:00Will this work with more descriptive channel names...Will this work with more descriptive channel names or just numeric identifiers? I've played with it a bit and haven't had much luck...Mike Yeagerhttps://www.blogger.com/profile/10624780968288639678noreply@blogger.com