@funky81 it’s done now. If you don’t have same meters than i have you can still adapt things and make it works with your meters
-
ESP8266 ESP-201 : a great piece of hardware for a great app (monitor gas and electricty consumption)
pimatic rocks!
-
Here in holland we have a digital out serial (like the phone connector) the connection is called P1 or something like that. Could be possible also? It gives electric and gas consumtion.
On the right:
-
@sweebee don’t know how P1 works and the protocol used behind, but should work if you can decrypt the protocol
pimatic rocks!
-
@Yves911 There are sketches for arduino. The output of the P1 port is connected to the arduino pin 0 (RX), I guess the ESP could do the same on the RX pin?
-
@Yves911 thanks…this is really cool!!
-
@leader21 dropbox image should be ok now
pimatic rocks!
-
Improved version of the skecth https://github.com/Yves911/PimaticClient/blob/master/PimaticClient2.ino
pimatic rocks!
-
@Yves911 why do you don’t use the api of pimatic to transmitte the values.
Look at sweetpi homeduino-esp8266-node sketch.
With an curl post you don’t need to use an extra server.pimatic rocks!!!
-
@Icesory right now i am sending info every 2 seconds and the message that i send is really short
Moving to the API way could be too much for the ESP8266 (and maybe also for pimatic on a raspberry)
I did that with an extra server for the moment also because it’s more easy to debug (you can really see what you send/receive).
But yes for a mid term perspective i will move to API or MQTT messagespimatic rocks!
-
@Yves911 Do you have zero-values for all attributes of logwatcher after pimatic started? I have.
After some minutes this situation changes and the real values are read and shown but the zero values are logged and make silly glitches in the graphs. So every restart of pimatic for config changes destroys the graphical presentation of the logwatcher attributes.
nc is started by cron to listen and appending to logfile continuously with the command “nc -d -k -l 8888 >/tmp/netcat.log”. My logfile read by logwatcher exists already when pimatic starts.
In another thread is written that log reader plugin higher than version 0.8.1 would read the logfile on pimatic startup to start with real values.But this doesn’t work for me (log reader plugin 0.8.5).
Possibly further discussion should be in another thread about log reader plugin. But it seems that this use with ESP8266 is the most used application for log reader plugin. That’s why I ask here.
-
@Yves911 Thank you. Now I found again the comment about the log reading at pimatic startup. It is on github - issue #431. If I understand it right it’s a problem how pimatic includes log reader plugin at startup. Issue is closed so @sweetpi possibly had a solution in v. 0.8.1 and it got lost in further versions.
So I will jump over to github and try my chance there. -
See: pimatic/pimatic#743
-
@sweetpi Hi, thanks it seems to fix the issue (as far that i can see)
pimatic rocks!