Hi @maglo18 i have been using a current only version of emon for quite some time, i am interested in adding the ac-ac transformer to calculate the apparent power more accurately. Do you have a project page for your build with diagrams and specs? What type of transformers are you using (i can just about read it from picture) and how happy are you with the performance?
Thanks Gambituk
@tomkxy Any updates to this? my setup has been running well for a long time, but i am itchy to see if it will survive with 1.5.. i know i should just leave it alone :D but i cannot help but tinker with it.
I've been using a version of the mqtt gateway for about 6 months, i setup the LED's like it shows in the advanced build, and they all (3) run with on all the time, and off when activated, i assumed at the time that this was by design, and it's quite nice to have a clear visual indication that things are all ok, with the occasional blink when there is a message received. i quite like it now. my file was compiled with version 1.4.1 modified library. but i believe it was the same behavior with 1.4 also.
Just incase it helps.
Sorry, that's the one step i didn't do, i already had a Rpi, so i started from this step, but i think they should all be somewhat similar, maybe someone else has tried something but i can't offer any genuine advice.
@Sparkman (My last ping for tonight i promise :-) )
sensor started, id 22
send: 22-22-25-0 s=255,c=0,t=17,pt=0,l=3,st=ok:1.4
send: 22-22-25-0 s=255,c=3,t=6,pt=1,l=1,st=fail:25
send: 22-22-25-0 s=255,c=3,t=11,pt=0,l=12,st=ok:Power Sensor
send: 22-22-25-0 s=255,c=3,t=12,pt=0,l=3,st=ok:1.0
send: 22-22-25-0 s=0,c=0,t=13,pt=0,l=3,st=ok:1.4
send: 22-22-25-0 s=0,c=1,t=17,pt=2,l=2,st=ok:9278
send: 22-22-25-0 s=0,c=1,t=17,pt=2,l=2,st=ok:40
send: 22-22-25-0 s=0,c=1,t=17,pt=2,l=2,st=ok:39
send: 22-22-25-0 s=0,c=1,t=17,pt=2,l=2,s
Or just 4 minutes later :(
then deleted again the eeprom and then this
send: 22-22-255-255 s=255,c=3,t=7,pt=0,l=0,st=fail:
read: 25-25-22 s=255,c=3,t=8,pt=1,l=1:1
new parent=25, d=2
read: 0-0-22 s=255,c=3,t=8,pt=1,l=1:0
new parent=0, d=1
sensor started, id 22
send: 22-22-0-0 s=255,c=0,t=17,pt=0,l=3,st=ok:1.4
send: 22-22-0-0 s=255,c=3,t=6,pt=1,l=1,st=ok:0
read: 0-0-22 s=255,c=3,t=6,pt=0,l=1:M
send: 22-22-0-0 s=255,c=3,t=11,pt=0,l=12,st=ok:Power Sensor
send: 22-22-0-0 s=255,c=3,t=12,pt=0,l=3,st=ok:1.0
send: 22-22-0-0 s=0,c=0,t=13,pt=0,l=3,st=ok:1.4
send: 22-22-0-0 s=0,c=1,t=17,pt=2,l=2,st=ok:9278
I noticed looking above at what i've already posted that this could be an issue with nodes relaying data (or not).. it seems that at some point it decides that another node (25) will be used (it's about half way to gateway and very customised code) but this doesn't seem to be passing the message on.
So i will also try to stop this node from offering its relaying services..
Is there any way to insist that the node only speaks directly to the GW?
thanks in advance
@Sparkman Thanks, so i've just tried resetting to auto, and i was assigned a new value of 22, so i've then set this to a static value in my sketch and re-uploaded it to the nano, so i will test like this, and report back in a day or two ( or hopefully several weeks!).. after that i will experiment with commenting out the library and continue troubleshooting in this direction.
I did notice 1 more anomalie, in that my first reading after the presentation seems to be a value in watts of about 9000, and then after that i have normal and consistant readings from 100 - 4000 depending on whats running in the house.. so i was considering if something in my sketch logic is running wild on the first loops before the state of lastsend timer is valid... or something more.. but that's just an observation.
Thanks again.
Gambit
thanks for the reply @Sparkman , i had looked at that before posting but i can't seem to get my head around what i am supposed to do.... so for example i should erase.. then leave as auto so that it is assigned a value.. and then i can go back to my original static? or should i hard code the value that the controller gives me? (which isn't a major problem...)
Also any idea's for the reason for the actual crash?
Thanks
Gamb
Cloud is probably easiest to get started.. and then depending what you have available you could try mosquitto on windows as a test, assuming you have a windows box already running and then when you are happy with that and understand what is going on then i would suggest investing in something like a raspberry pi so you can have an always on broker on your home network...
I am running mosquito on a Rpi b+ without issues, and also openhab running on the same device, and a mysensors mqtt gateway and several sensor nodes for temp and a power meter that i am working on getting going.
Don't know if that helps.
Gambituk
Hello, i have recently returned to an old project i was working on 6 or more months ago, i modified a sketch to provide current only power readings from ct sensor only measuring current from sensor * typical 230v to get a power reading. It works fine except for the fact that it typically crashes after 1.5 days - 2 days.
So that's issue 1, issue 2 is that after the crash i cant seem to reestablish comms with GW unless i erase eeprom and start again. ( i am also assigning a static node id in sketch)
So my Sketch: (based on mysensors with open energy mteter lib)
#include <SPI.h>
#include <MySensor.h>
#include "EmonLib.h" // Include Emon Library
#define CHILD_ID_POWER 0
#define POWER_SENSOR_ANALOG_PIN 0
#include "EmonLib.h" // Include Emon Library
EnergyMonitor emon1; // Create an instance
unsigned long SLEEP_TIME = 15000; // Sleep time between reads (in milliseconds)
MySensor gw;
MyMessage msg(CHILD_ID_POWER, V_WATT);
int lastwatt;
void setup()
{
emon1.current(2, 60.2); // Current: input pin, calibration. 2 = A2
gw.begin(NULL,27,false);
// Send the sketch version information to the gateway and Controller
gw.sendSketchInfo("Power Sensor", "1.0");
// Register all sensors to gateway (they will be created as child devices)
gw.present(CHILD_ID_POWER, S_POWER);/////???????????????
}
void loop()
{
static unsigned long lastUpdate;
if (millis() - lastUpdate >= SLEEP_TIME) // If the current time - the last time we updated >= #SLEEP_TIME THEN:
{
double Irms = emon1.calcIrms(1480); // Calculate Irms only
int watt = (Irms*230.0);
// Serial.println(watt);
//if (POWERLevel != lastPOWERPOWERLevel) {
gw.send(msg.set(watt));
// lastPOWERLevel = POWERLevel;
//}
// gw.sleep(SLEEP_TIME);
lastUpdate += SLEEP_TIME; // Last update = lastupdate + SLEEP_TIME
}
}
and my ?presentation data? after failure..
sensor started, id 27
send: 27-27-25-0 s=255,c=0,t=17,pt=0,l=3,st=ok:1.4
send: 27-27-25-0 s=255,c=3,t=6,pt=1,l=1,st=fail:25
send: 27-27-25-0 s=255,c=3,t=11,pt=0,l=12,st=ok:Power Sensor
send: 27-27-25-0 s=255,c=3,t=12,pt=0,l=3,st=fail:1.0
send: 27-27-25-0 s=0,c=0,t=13,pt=0,l=3,st=ok:1.4
It seems!! as though i can restart as many times as i want until the "failure" with no issues in rebooting and reconnecting, but then something seems to happen during the failure to make in impossible to reconnect without eeprom flash..
and then after erase i have this.
sensor started, id 27
send: 27-27-0-0 s=255,c=0,t=17,pt=0,l=3,st=ok:1.4
send: 27-27-0-0 s=255,c=3,t=6,pt=1,l=1,st=ok:0
send: 27-27-0-0 s=255,c=3,t=11,pt=0,l=12,st=ok:Power Sensor
send: 27-27-0-0 s=255,c=3,t=12,pt=0,l=3,st=ok:1.0
send: 27-27-0-0 s=0,c=0,t=13,pt=0,l=3,st=ok:1.4
Please any ideas..??
I'm using codebender to uplaod and several different versions of the arduino ide over the last year but i never really had the time to ask for help here before now, i just got frustrated and turned it off for a while!.. I've also used several different power supplys with all good quality and decent 1A max. I am using also several different nano's as my arduino of choice. .. please help !! :dancer:
Group all
Group node1 (all)
Group node2 (all)
Group sketch (all)
Number node1_light "Light Level" (node1,all) {mqtt="<[mysensor:MyMQTT/20/0/V_LIGHT_LEVEL:state:default]"}
Try changing the first line of items like this above.. and in sitemap change node1_temp to node1_light
Also see if activating any of the switches in openhab publishes to myMQTT ?
@C.r.a.z.y. it sounds like he is getting as far as the mqtt broker, so the gateway must be working. ?
mosquitto_sub -h localhost -v -t '#'
This is what i use to see what is happening on mqtt broker, i am using a raspberry pi and mosquitto installed on the same pi. you can also swap localhost for ip address ie 192.168.0.5 etc
can you also please paste a sample of what you see in myMQTT or screenshot maybe? or it can be easier to copy and paste from a terminal window? are you using raspberry pi or something else?
Maybe if you can share your items, sitemap, and rules if any.
Hi, i would be interested in any more updates along this line. In my case my gateway is mostly stable as far as i can tell. several weeks without issues. My problem is that most of my nodes seem to lockup, so i would be totally interested in making them more robust either by software or if necessary with external chip as overlord watchdog
@nutcracker I think the best way to test the function of this battery pack would be to test it using it's designed purpose. So i suggest connecting a heavier load, (for example a smartphone) and see if it also turns off after the same time. or if as you (and I) suppose it stays on because of the extra current draw.
I also have a battery backup system for my phone and it turns off if the current draw drops below a certain level so as to stop my phone from trickle charging after it reaches 100%. (it has a button to start the charging function, it doesn't charge when i just connect the phone.)
Hope this helps.
Initial tests seem that it is now resolved with the fixed version of the mqttclient gateway as modified by fotofieber
http://forum.mysensors.org/topic/524/mqtt-client-gateway/29 There is a proposed solution in the following post, i will test and see if it helps, and report back.
@FotoFieber @ntruchsess i have a parallel post regarding this version of the controller, i did not know it was the same as this one when i opened the thread :8ball: but i am having some garbage issues, do you think this is the same problem as you have described 2 posts up? http://forum.mysensors.org/topic/921/strange-value-being-sent-from-controller-using-mixed-temp-relay-node thanks for any comments or pointers
Thanks @celonunes I eventually found that version of gateway via somebody else. i have another post with some issues i found with that version. http://forum.mysensors.org/topic/921/strange-value-being-sent-from-controller-using-mixed-temp-relay-node it's not really resolved, but i have some kind of workaround.