Home

Welcome! Log in or Join us

Forums SEGmeter DS18B20 Temperature Stream

Subscribe to DS18B20 Temperature Stream 22 posts, 5 voices

Reply to topic
 

 
Dargs_medium
Oct 29, 2010 9:29am
44 posts

Hi

So I’ve added on a DS18B20 1-wire temp sensor and 4k7 pullup resistor to my SEGmeter board.

I tested it on a seperate arduino and was getting readings with OneWire examples @ arduino.cc

Looking at the aiko_segmeter.pde it looks like it might send out a “temperature <value>” globalstring. * I haven’t had a chance to check the serial output of the board  before it gets to the SEGbox yet.

I’ve added a Thermometer device under my devices, but it wouldn’t let me name the nodename the same as my SEGmeter, I couldn’t see anywhere in the arduino sketch where I would lable the stream or node.

Any tips to get my SEG page receiving the temperature values?

Thanks in advanced!

Dargs

 

 
Dargs_medium
Oct 30, 2010 12:20am
44 posts

I had a look at the serial output:

(node dargs ? (p_1 0.00)(e_1 0.00)(p_2 0.00)(e_2 0.00)(p_3 0.00)(e_3 0.00))
(node dargs ? (temperature 23.56 C))

So yay, it’s reading the temp sensor ok (albit only every 2nd time, as per notes in the sketch).

I’ve also tried to add a stream to my “3channel SEGmeter” device, with ‘temperature’ as the stream name, but it just shows a “I’m all set for celsius data” message and a spot to manually input data.

- Is it possible to see the serial messages by logging into the SEGBox ? (instead of opening up box and connecting usb to laptop etc)

- Do I need to tell AIKO/SEGbox to send the temp readings to the supplied api/token ?  

ta

Dargs

 

 

 
Kayno_medium
Oct 30, 2010 2:22am
37 posts

i think you just need to add a stream to your seg meter device as follows:

  • go to https://smartenergygroups.com/devices
  • click on your seg meter device
  • click the “edit” icon, top right corner
  • click the “add stream” link
  • give the stream any name, eg “Temperature”
  • Type of data: “Temperature, C”
  • Then down the bottom, in the “Technical” section, add the stream name, as it is in your serial output – “temperature”
  • click the add stream button
that should be it!

 
Dargs_medium
Oct 30, 2010 2:47am
44 posts

Thanks Kayne! I was about to say I’d tried all that and it didn’t work, then I checked my streams and it had magically started working 10 minutes ago! – Exactly the same time I power cycled my ADSL modem/wap (and you’d posted your comment!)

Interesting that did the trick, maybe having a new wan ip address trigggered the Seg API to start doing its thing.

Sweet.. now to decide if it’s worth sending the SEGmeter/box more data (ie outdoor temp via zigbee) and how it deals with multiple incoming serial messages, or if the zigbees would work that out themselves..

and to get myself some relay power control to pop all those black ballons when there’s no one around.

Thanks again, and as they say, ‘have you tried turning it off and on again’

dargs

 

 

 

 
Icon_missing_medium
Nov 14, 2010 5:39am
31 posts

Hi all

Having got my first temperature measurement running with a little help from the above (thanks guys), I thought I would get brave and have a go at getting multiple temperatures measured and added two more 18B20 sensors to my OneWire system.

I found that only one temperature point would register on the site after adding the two extra streams. I checked out the data stream coming from the board by killing the aiko_gateway.lua process and ran

telnet localhost 2000

and saw correct looking data from 3 temperature sensors (as well as the current sensors):
node sol_adv ? (p_1 1221.47)(e_1 2.58)(p_2 468.26)(e_2 1.54)(p_3 0.00)(e_3 0.00))
(node sol_adv ? (temperature 21.31 C))
(node sol_adv ? )
(node sol_adv ? (p_1 292.03)(e_1 2.21)(p_2 471.25)(e_2 1.54)(p_3 0.00)(e_3 0.00))
(node sol_adv ? (temperature 21.00 C))
(node sol_adv ? )
(node sol_adv ? (p_1 818.34)(e_1 2.72)(p_2 456.47)(e_2 1.52)(p_3 0.00)(e_3 0.00))
(node sol_adv ? )
(node sol_adv ? (p_1 853.83)(e_1 2.23)(p_2 448.41)(e_2 1.48)(p_3 0.00)(e_3 0.00))
(node sol_adv ? (temperature 41.50 C))
(node sol_adv ? )
(node sol_adv ? (p_1 823.87)(e_1 2.17)(p_2 439.62)(e_2 1.45)(p_3 0.00)(e_3 0.00))
(node sol_adv ? (temperature 21.31 C))
(node sol_adv ? )
(node sol_adv ? (p_1 256.60)(e_1 1.85)(p_2 427.68)(e_2 1.42)(p_3 0.00)(e_3 0.00))
(node sol_adv ? (temperature 21.00 C))
(node sol_adv ? )
(node sol_adv ? (p_1 221.19)(e_1 1.55)(p_2 422.13)(e_2 1.38)(p_3 0.00)(e_3 0.00))
(node sol_adv ? )
(node sol_adv ? (p_1 718.31)(e_1 2.12)(p_2 410.41)(e_2 1.35)(p_3 0.00)(e_3 0.00))
(node sol_adv ? (temperature 41.56 C))

I tried changing the stream name for the first temp data to “temperature_1” from the original “temperature” since the extra streams had become “temperature_2” and “temperature_3”.

But it seems like the data from the three 18B20’s is all arriving at the the one stream since the chart is showing all three.

It would appear to be a site setup issue. Any ideas?

Thanks

Rob.

 

 
Samotage_300_medium
Nov 14, 2010 5:45am
565 posts

Hey Rob,

The magic in the Arduino code only supports a single temperature probe at this time.  It’s possible to get in there and hack it to work, however you would need to ensure the correct probe hooked up to the one wire interface outputs to the appropriate stream.

Under your device (in SEG), just setup multiple streams for each probe, e.g:

(node sol_adv ? (temperature_1 21.00 C))

(node sol_adv ? (temperature_2 41.50 C))

(node sol_adv ? (temperature_3 12.00 C))

And then proceed to go to town!

The only limitation here is the Arduino code.

Sam.

 

 

 
Dargs_medium
Nov 23, 2010 2:31am
44 posts

With all this talk about multiple sensors, I thought maybe the next version of the SEGmeter PCB could have some extra pinouts for 2nd sensor ?

My SEGmeter sits with my fusebox, just inside my front door, I’m planning to run a 2nd sensor another 2metres away to measure outdoor temp.

Just a thought…

Dargs

 

 

 
Samotage_300_medium
Nov 23, 2010 2:44am
565 posts

A second sensor could be hacked on using the prototype area easy enough.  :D

The more elegant way would be to have the codez handle the proper one wire protocol that Rob’s working on.  It shouldn’t be too hard.

The other thing, we’ve run these sensors on long leads and they work ok.  I think 50m of Cat 5 is the longest run with success, 2m should be a cinch!

Sam.

 

 
Icon_missing_medium
Nov 23, 2010 7:35am
31 posts

I have my code working to generate the correct format output but it is not yet free of bugs. I will post the code when it is giving me stable results.

I can generate output as follows:-

(node sol_adv ? (temp_1 32.93 C)(temp_2 23.93 C)(temp_3 22.43 C))

for the three sensors I am using. I need to work out if I am better off with normal power mode or parasitic power mode.

More to follow soon I hope.

 

Rob

 
Icon_missing_medium
Jan 5, 2011 8:46am
31 posts

 finally have three temperature data streams running sucessfully to the SEGmeter site.

The keys bits of code are :

void temperatureSensorHandler(void) { // total time: 33 milliseconds

byte address[8];
byte data[12];

byte index;

    if (!oneWire.search(address)) { // time: 14 milliseconds
        //  Serial.println("(error 'No more one-wire devices')");
        oneWire.reset_search(); // time: <1 millisecond
        index=0;
        return;

and

globalString.begin();
globalString = "(temp_";
if (signBit) globalString += "-";
globalString += (address[7] & 0x0f) + '0' -58;
globalString += " ";
globalString += temperature_whole;
globalString += ".";
if (temperature_fraction < 10) globalString += "0";
globalString += temperature_fraction;
globalString += " C)";

 

Let me know if you want the full code detail.

 

Sam

Could you please have a look at my data streams. There is a problem with the last 2 temperature streams stopping (i.e. the streams contain no data) after several hours. Telnet localhost 2000 seems to indicate the data continues to be sent but it is not arriving on the site streams. This has been happening for the past 3 days or so and has improved (taken longer before the problem arises) since I turned off the device address data used for troubleshooting. I can't see anything not right with the data at my end. The weird thing is that the data stream can re-start without my intervention after some hours - see data 14:38 to 19:14 today for stream A Room Temperature.

 

Regards

Rob

 
Samotage_300_medium
Jan 7, 2011 9:06pm
565 posts

Hey Rob,

I've fixed your post with the correct array index references.  This should work ok in the future.  It probably needs a <code> option too...

I also checked out your data feed, and there is data arriving on the API for the other two streams, though the first temperature sensor is reporting a lot more regularly.  I'd suggest it's likely some issue in the Arduino that needs attention?

What does the output look like in the Arduino IDE seem like?  Run this for some hours, perhaps it's ok to begin with then it stops reguarly reporting the other temperature sensors?

Good luck!

Sam.

 

 
Samotage_300_medium
Jun 8, 2011 1:13am
565 posts

Hey Rob,

In case you were still stuck on the multiple one wire DS18B20 temperature sensing, we've done some updates to the SEGmeter sketch in version 18 that has the DallasTemperature library.  This greatly simplifies the temperature handler code, with the added benifit of multiple sensor support.  Check it out here:

https://github.com/samotage/Aiko

Sam.

@samotage

 
Dargs_medium
Jun 8, 2011 2:15am
44 posts
Hey Sam, Just having a look at v18, and was waiting for a good reason to update the version running on my segmeter.. this might be it! :) Quick Q - where is the 'sensor.begin'/'sensors.requestTemperatures' etc code that the temperatureSensorHandler function calls? Thanks ! I'm looking forward to measure more temps around the house/outside to show where insulation could be better.. cheers dargs
 
Samotage_300_medium
Jun 8, 2011 4:13am
565 posts

Hey Simon,

The sensors.begin() is inside the handler.  That way it automatically picks up the sensors without a reboot.

There aren't any significant changes to the energy measurement stuff, so the only thing is the DallasTemperature library that does the magic.

Sam.

 
Dargs_medium
Jun 8, 2011 4:52am
44 posts

Ah yep there it is..

 

DallasTemperature sensors(&oneWire);

 

Don't know much about Classes and how they work, but this is looking like a good example to learns from.

cheers

dargs

 
Dargs_medium
Jun 19, 2011 1:01pm
44 posts

Wow, just updated to SEGmeter v0.18, and how good does that dallas library work! Nice work Sam. I like how you can now pretty much plug'n'play with the one wire sensors! Got 3 running, all in the same location at the moment, testing accuracy.. out of interest what's the max number of sensors that people have got off one bus?

thanks!

 
Samotage_300_medium
Jun 19, 2011 11:45pm
565 posts

Sweet!  That Dallas Lib certainly makes the temperature handler trivial :D  It's also pretty neat under the hood, and there are heaps of useful methods inside for custom stuff.

We have run 3 on about a 50m length of cat6.  We did need to reduce the 4.7hom to something smaller to boost the power of the long leads, but it's fine.

Acording to the theory, 100's of sensors coudl be used on the bus, however there is then the limitations of the serial message that is output by the SEGmeter.  it could get too big for the buffers!  But then again, that can be coded around.

Sam.

 
Icon_missing_medium
Jan 19, 2012 9:35am
31 posts

 

Hi Sam

Finally got the time and courage up to have a go at v0.18 with the Dallas Library. Not a lot of success initially with 3 sensors. See data attached. ÿ(node sol_adv ? (temp_1 26.37) (temp_2 26.37) (temp_3 26.37) (temp_4 26.37) )
(node sol_adv ? (p_1 523.29)(e_1 0.84)(p_2 82.74)(e_2 0.13)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 606.03)(e_a 0.97))
(node sol_adv ? (temp_1 -127.00) )
(node sol_adv ? (p_1 493.76)(e_1 0.65)(p_2 90.85)(e_2 0.12)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 584.61)(e_a 0.77))
(node sol_adv ? (temp_1 26.31) )
(node sol_adv ? (p_1 514.80)(e_1 0.65)(p_2 84.69)(e_2 0.11)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 599.49)(e_a 0.75))
(node sol_adv ? (temp_1 -127.00) (temp_2 -127.00) (temp_3 -127.00) )
(node sol_adv ? (p_1 522.41)(e_1 0.76)(p_2 85.65)(e_2 0.13)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 608.06)(e_a 0.89))
(node sol_adv ? (temp_1 26.25) (temp_2 26.25) )
(node sol_adv ? (p_1 528.66)(e_1 0.69)(p_2 89.41)(e_2 0.11)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 618.08)(e_a 0.80))
(node sol_adv ? (temp_1 26.19) )
(node sol_adv ? (p_1 514.02)(e_1 0.66)(p_2 82.10)(e_2 0.11)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.0(node sol_adv ? (temp_1 -127.00) (temp_2 26.25) )
(node sol_adv ? (p_1 511.20)(e_1 0.72)(p_2 84.69)(e_2 0.12)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 595.89)(e_a 0.84))
(node sol_adv ? (temp_1 26.19) )
(node sol_adv ? (p_1 513.22)(e_1 0.63)(p_2 88.71)(e_2 0.10)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 601.93)(e_a 0.73))
(node sol_adv ? (temp_1 26.25) (temp_2 26.25) )
(node sol_adv ? (p_1 505.89)(e_1 0.65)(p_2 88.58)(e_2 0.11)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 594.47)(e_a 0.77))
(node sol_adv ? (temp_1 26.25) )
(node sol_adv ? (p_1 511.71)(e_1 0.81)(p_2 83.73)(e_2 0.13)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 595.44)(e_a 0.94))
(node sol_adv ? (temp_1 -127.00) (temp_2 -127.00) )
(node sol_adv ? (p_1 514.73)(e_1 0.76)(p_2 80.70)(e_2 0.12)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 595.43)(e_a 0.88))
(node sol_adv ? )
(node sol_adv ? (p_1 533.17)(e_1 0.76)(p_2 81.51)(e_2 0.12)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 614.67)(e_a 0.87))
(node sol_adv ? (temp_1 -127.00) (temp_2 -127.00) )
(node sol_adv ? (p_1 518.45)(e_1 0.67)(p_2 81.12)(e_2 0.11)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 599.57)(e_a 0.78))
(node sol_adv ? )
(node sol_adv ? (p_1 511.00)(e_1 1.04)(p_2 89.44)(e_2 0.19)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 600.44)(e_a 1.23))
(node sol_adv ? (temp_1 26.25) (temp_2 -127.00) (temp_3 26.25) (temp_4 -127.00) (temp_5 -127.00) (temp_6 26.25) (temp_7 26.25) (temp_8 -127.00) (temp_9 26.25) (temp_10 26.25) (temp_11 26.25) )
(node sol_adv ? (p_1 1278.78)(e_1 6.49)(p_2 76.01)(e_2 0.42)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1354.79)(e_a 6.92))
(node sol_adv ? (temp_1 26.25) )
(node sol_adv ? (p_1 1277.68)(e_1 1.69)(p_2 88.79)(e_2 0.12)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1366.47)(e_a 1.81))
(node sol_adv ? )
(node sol_adv ? (p_1 1286.33)(e_1 1.60)(p_2 86.24)(e_2 0.11)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1372.56)(e_a 1.71))
(node sol_adv ? (temp_1 -127.00) (temp_2 -127.00) )
(node sol_adv ? (p_1 1276.64)(e_1 1.75)(p_2 85.94)(e_2 0.12)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1362.58)(e_a 1.87))
(node sol_adv ? (temp_1 26.31) (temp_2 26.31) )
(node sol_adv ? (p_1 1272.93)(e_1 1.70)(p_2 88.10)(e_2 0.11)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1361.03)(e_a 1.82))
(node sol_adv ? (temp_1 -127.00) )
(node sol_adv ? (p_1 1250.07)(e_1 1.64)(p_2 80.47)(e_2 0.10)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1330.53)(e_a 1.74))
(node sol_adv ? )
(node sol_adv ? (p_1 1295.66)(e_1 1.54)(p_2 82.54)(e_2 0.10)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1378.20)(e_a 1.64))
(node sol_adv ? )
(node sol_adv ? (p_1 1261.51)(e_1 1.53)(p_2 82.44)(e_2 0.09)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1343.95)(e_a 1.63))
(node sol_adv ? (temp_1 -127.00) (temp_2 -127.00) (temp_3 26.31) (temp_4 26.31) (temp_5 -127.00) (temp_6 26.31) (temp_7 26.31) (temp_8 -127.00) (temp_9 26.31) )
(node sol_adv ? (p_1 1276.90)(e_1 2.32)(p_2 84.61)(e_2 0.15)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1361.52)(e_a 2.48))
(node sol_adv ? (temp_1 26.31) (temp_2 -127.00) )
(node sol_adv ? (p_1 1248.68)(e_1 1.77)(p_2 79.82)(e_2 0.11)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1328.50)(e_a 1.88))
(node sol_adv ? (temp_1 26.31) (temp_2 26.31) )
(node sol_adv ? (p_1 1279.84)(e_1 1.93)(p_2 81.07)(e_2 0.12)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1360.90)(e_a 2.05))
(node sol_adv ? (temp_1 26.31) (temp_2 26.31) (temp_3 26.31) )
(node sol_adv ? (p_1 1255.54)(e_1 1.69)(p_2 87.31)(e_2 0.12)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1342.85)(e_a 1.80))
(node sol_adv ? (temp_1 26.31) (temp_2 -127.00) (temp_3 26.31) (temp_4 43.56) (temp_5 26.31) )
(node sol_adv ? (p_1 1285.21)(e_1 3.37)(p_2 87.96)(e_2 0.23)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1373.18)(e_a 3.60))
(node sol_adv ? (temp_1 26.31) )
(node sol_adv ? (p_1 1265.27)(e_1 7.50)(p_2 79.05)(e_2 0.46)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1344.32)(e_a 7.97))
(node sol_adv ? (temp_1 26.31) (temp_2 -127.00) (temp_3 26.31) (temp_4 26.31) (temp_5 43.50) (temp_6 -127.00) (temp_7 26.31) )
(node sol_adv ? (p_1 1272.24)(e_1 2.71)(p_2 79.37)(e_2 0.17)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1351.61)(e_a 2.89))
(node sol_adv ? (temp_1 26.31) )
(node sol_adv ? (p_1 1280.14)(e_1 1.67)(p_2 84.27)(e_2 0.12)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1364.41)(e_a 1.79))
(node sol_adv ? (temp_1 26.31) )
(node sol_adv ? (p_1 1248.71)(e_1 4.06)(p_2 78.49)(e_2 0.27)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1327.20)(e_a 4.33))
(node sol_adv ? (temp_1 26.25) )
(node sol_adv ? (p_1 1256.04)(e_1 1.81)(p_2 85.57)(e_2 0.12)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1341.60)(e_a 1.93))
(node sol_adv ? (temp_1 26.25) )
(node sol_adv ? (p_1 1244.78)(e_1 1.96)(p_2 78.89)(e_2 0.12)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1323.67)(e_a 2.09))
(node sol_adv ? (temp_1 26.25) (temp_2 26.25) )
(node sol_adv ? (p_1 1240.73)(e_1 1.70)(p_2 84.39)(e_2 0.11)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1325.12)(e_a 1.81))
(node sol_adv ? (temp_1 26.19) )
(node sol_adv ? (p_1 1261.15)(e_1 1.63)(p_2 79.97)(e_2 0.11)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1341.12)(e_a 1.74))
(node sol_adv ? )
(node sol_adv ? (p_1 1139.30)(e_1 1.35)(p_2 77.73)(e_2 0.10)(p_3 0.00)(e_3 0.00)(p_4 0.00)(e_4 0.00)(p_a 1217.03)(e_a 1.45))
(node sol_adv ? (temp_1 26.19) (temp_2 26.19) (temp_3 43.50) )

It seems to lose track of the number of sensors and does not cocnsistently allocate the data to the particular sensor. Any thoughts on what's happenign here? My guess is to try a lower resistor value. I know that using the onewire library it was a challenge but it was working. You can see the difference in my trends in the last 24 hours.

Regard

 

 
Samotage_300_medium
Jan 30, 2012 9:30am
565 posts

Hey Rob,

They way the Dallas library works is that it returns the sensors in the order of their own unique id.  This means that if one of your sensors was to go down, or the cable run is tooo long then it's likely one can fade in and out.  This will caue havoc, but likely a hardware problem.

I do know that reducing the 4.7k resistor value can give the sensors some more electrons at the end of the cable run :D  Test and see!

Sam.

 
Icon_missing_medium
Jan 31, 2012 9:16am
31 posts

Thanks Sam. Works a treat with a 3k3 resistor. Cable lengths must be getting up there a bit.

A little data smithing to do now.

 
Icon_missing_medium
Dec 28, 2017 2:25am
10 posts

Hey Sam,

 

Super old thread, I know, but I have been resurrecting my SEG setup recenlty and have started to streamline a few things I had put together previously with a bit of bailing wire and duct-tape.

Current project: I have 6 one-wire DS18B20 temp sensors currently wired up in my house dumping data into a seperate DB on a raspi. Last time I looked, it was not possible to do multiple one-wires into SEG, or I did not look hard enough. Anyway,  I see SEGMeter v 18 on github supports mulitple one wire devices now.  I'd like to start using SEGmeter 2.5 to capture the temp readings instead of my seperate system. 

Questions: How do I know what version I am running locally? How do i flash or upgrade to the latest? I'm pretty familiar with arduino and raspi/python coding but am rusty on lua and never touched aiko event-based code before. I have an FTDI USB I can use to connect to the SEGduino if needed but not sure what to do then.

thanks,

-matt

 
Icon_missing_medium
Dec 28, 2017 2:57am
10 posts

aha! figured it out, just needed to rediscover devices, now have one-wire data!

Log in to reply to this topic

Forums SEGmeter DS18B20 Temperature Stream

copyright © 2008 Smart Energy Groups pty ltd