Moderators: grovkillen, Stuntteam, TD-er
Code: Select all
curl -i -XPOST 'http://localhost:8086/write?db=mydb' --data-binary 'cpu_load_short,host=server01,region=us-west value=0.64 1434055562000000000'
Code: Select all
// SendToUDP <ip>,<port>,<message> sample: SendToUDP 192.168.0.123,65500,Hello 15
// SendToHTTP <ip>,<port>,<path> sample: SendToHTTP 192.168.0.8,8080,/json.htm
IP address posted in mqtt would save a lot of time fixing problems.pmayer wrote:Hi guys,
maybe I've overread it but is it possible to let espeasy drop the current IP/MAC and maybe the configured device number to mqtt? As the number of espeasy nodes rises it would be nice to know which device id's are already taken and which sensor has which IP. As I run the esp's in deep-sleep most of the time it also is possible, that they will get new IP's on reconnect.
Would be a very nice feature in my eyes, maybe inside the SystemInfo-Plugin?
regards,
Patrik
Code: Select all
if (strcasecmp_P(Command, PSTR("SendToPUT")) == 0) //ANTONI
{
success = true;
String strLine = Line;
String host = parseString(strLine,2);
String port = parseString(strLine,3);
int pathinipos = getParamStartPos(strLine,4);
int pathfinpos = getParamStartPos(strLine,5);
String path = strLine.substring(pathinipos,(pathfinpos-1));
String msgs = parseString(strLine,5);
WiFiClient client;
if (client.connect(host.c_str(), port.toInt()))
{
client.println("PUT " + path + " HTTP/1.1");
client.println("Connection: keep-alive");
client.println("Host: " + host);
client.println("Content-Type: text/plain;charset=UTF-8");
client.print("Content-Length: ");
client.println(msgs.length());
client.println();
client.println(msgs);
unsigned long timer = millis() + 200;
while (!client.available() && millis() < timer)
delay(1);
while (client.available()) {
String line = client.readStringUntil('\n');
if (line.substring(0, 15) == "HTTP/1.1 200 OK")
addLog(LOG_LEVEL_DEBUG, line);
delay(1);
}
client.flush();
client.stop();
}
}
Maybe you need to check the thermostat function of this ESP8266 board: https://github.com/openenergymonitor/ES ... elay_Boardpoe wrote:A PID Device.
Device needs 6 parameters P, I, D, setpoint, Device(actual value) and GPIO for output. A checkbox to determine if it is for heating or cooling would also be nice.
I am aware of the limited power of the processor, but for many purposes a cycle time of 5-10 seconds would be sufficient.
I think it could be done with rules and a couple of dummy devices. But would be nice to have room for DS18B20 (actual value) Switch(to monitor output) and Display.
I'm not ready to make it myself yet, but i'm more than willing to help testing.
Later a simple on/off device would be nice. Source device, Setpoint, hysteresis, GPIO for output and a heat/cool switch should be enough.
/Preben
There are two MAC address shown, Client and AP Mode...so, the ChipID would come from?!tozett wrote:Chip-id is the last 3 doubles of the MAC-Adress,
but shown on web-gui as integer. makes this doubling somehow invisible..
https://github.com/esp8266/Arduino/issues/921
for me i would be helpful, if the chip-id on the homepage of ESPeasy is
not only shown as integer, but also as HEX-Mac-portion.
this way i could see the analogy of the ID and more easy identify my devices.
as small wish on a long grown list..hope the dev still reads here..
I do, but available time is sometimes an issue.tozett wrote:hope the dev still reads here..
Is there any chance to give users the compiled binary releases like in previous versions (R108 and R120) as on Wiki page is?Martinus wrote:I do, but available time is sometimes an issue.tozett wrote:hope the dev still reads here..
Currently trying to investigate, build and test some ways to migrate my existing Nodo Small units to 'shared ESP solutions'. Lot's of ideas, so little time...
So i've launched my very own private 'Nodo Small revival project' some weeks ago. I'll launch a new topic today and see if someone else shares some interest. Likely only dutch or belgium citizens as the Nodo Project was a dutch project only. Checkout http://www.nodo-domotica.nl
on my esps, the last 3 segments are identical on both, CLIENT ant AP. (only the first parts are different)beic wrote: There are two MAC address shown, Client and AP Mode...so, the ChipID would come from?!
In my case, only the first part (first two characters) are different the rest of them are all identical.tozett wrote:on my esps, the last 3 segments are identical on both, CLIENT ant AP. (only the first parts are different)beic wrote: There are two MAC address shown, Client and AP Mode...so, the ChipID would come from?!
Similar looking here too...tozett wrote:i checked all my 8 wemos-boards. all the same.
only first part different, everything the same.
means: the same last 3 parts of the mac for STA+AP.
look:
Code: Select all
STA MAC: 5c:xx:xx:xx:xx:f8
AP MAC: 5e:xx:xx:xx:xx:f8
So, what will happen if in the future someone uses more ESPEasy and some devices will get the same MAC address?tozett wrote:ok. seems to be software configurable. riddle solved.
https://github.com/esp8266/Arduino/issu ... -167515482
). I think you have better odds for winning the lottery, even the Italian lottery.Thanks for clarifying it all!Drum wrote:No 2 devices should ever have the same MAC they are hard coded by the manufacturer. Because Espressif has more than 1 set of MAC addresses for the ESP8266 ( I have both 5C/5E and 60/62) it is possible to have 2 devices running ESPEasy with the same chipID. The chances are less than 1 in 281,474,976,710,656. ( feel free to check my math, I am not perfect
Where you may have a problem is your router may not be able to handle the number of IP addresses. A lot of carrier provided routers limit the number of connected devices, and really limit the number of manually assigned IP Addresses. If I remember correctly my current router(vodafone) is limited to 27 devices, and about 10 assigned addresses. Not enough, but the ESP devices do not need internet access so they can be on a separate network.
)Users browsing this forum: No registered users and 16 guests