Archived Forum

The emonTH knows nothing about time, it should send only internal temperature, external temperature, humidity and battery state. Which software did you download (exact link please)?

I have downloaded the software here:

https://github.com/openenergymonitor/emonTH/tree/master/emonTH_DHT22_DS1...

I did not mean it sends the time, it sends only once at startup an then never. Sorry. I have to work on my english.

That sketch appears to have been changed recently. I do not know whether Glyn Hudson knows about the changes, and I have not tested that version.

The biggest change is the reading is now made once every 5 minutes, NOT every minute as in the original sketch. Did you wait 5 minutes?

If you want the readings every 1 minute, change line 59:
const int time_between_readings=5;

That link goes to 1 sketch and 4 hex files, can we assume you used the .ino? and only changed the nodeid?

How do you know it only sends once? did you receive any data or did you just see the led flash? 

How long are you waiting for a second flash or send ? default interval is 5 mins.

​Paul

Hello Tommi, I have come across this issue before with an emonth but could not get to the bottom of why its was happening, it seemed to get stuck at the rfm12 sleep command https://github.com/openenergymonitor/emonTH/blob/master/emonTH_DHT22_DS1....

It may be a faulty emonth, if you can get in contact with the shop here support@openenergymonitor.zendesk.com with your order number we will sort out a replacement for you

Edit, assuming its not posting after 5mins as above? you can change it to one minute if you prefer

Yes i take the .ino file. I only changed the node id.

I waited longer than 5 minutes, as i found this line 59. I receive the data with emoncms locally and with emoncms.org. Data is incoming correctly at node id 20.

The sensor sends actually only once at startup.

My other unmodified sensor sends once per minute at node id 19.

In arduino software i have set arduino uno board. Is this ok?

The modified (v1.4.1 - Philipp Lopaur) sketch is working for me with a delay of 4' 46" (Node 19, RF=868 MHz), or 59" with time_between_readings=1.

Arduino Uno is correct.

Something ist strange...

I can't see my last post here, but Robert is answering that Arduino uno is correct, what was my question...

"Something ist strange...

I can't see my last post here, but Robert is answering that Arduino uno is correct, what was my question..."

Your post was queued for moderation, there should have been a message to tell you this when you posted. Unfortunately, I can see posts that are queued, but there is nothing on the post to tell me that it is queued, I must go and look at a different list!

Ohhh. Sorry! I didn't see this message with the moderation. :-)

This is seldom in a forum, but a good thing!
 

I just came across the same problem. The sensor only sent once data - whether I had 1 or 5 min delay specified. All of a sudden it worked once I disabled blinkled using

#define BLINKLED 0

I'm not familiar enough with the openmonitor to spot why BLINKLED is causing an issue - if at all.

The only reason I can see for that behaviour would be that the batteries had a fairly high internal impedance, or there was a high contact resistance somewhere, and the additional LED current was enough lower the voltage so that the processor or the radio module stopped working. Which radio module do you have, RFM12B or RFM69CW? (The '69 draws more current at full power, so this is more likely to be the explanation with that radio module.)

I'm using 2 NiMh rechargeable Batteries and a '69 Module on 868MHZ. Actually this happened when I was powering the th over the usb programmer.

There are a lot of 'maybe's here. The NiMh cells do of course give a lower voltage than primary cells, and while I'd have expected your programmer and USB port would output enough current, we don't know that for certain. Have you tried with a set of primary (alkaline) cells?