Hey I'm new to ESP and am looking for some helping finalising my first mqtt button to Home assistant. Is there anyone on that knows ESPEasy well? MQTT tested and working, ESPEasy flashed (v2.0.0-dev8), it's on my wifi, mqtt details filled in, code from http://xbmcnut.blogspot.com.au/2016/08/using-espeasy-with-home-assistant.html., when I press the button the log shows:
65666 : ACT : gpio,13,0
65667 : SW : GPIO 13 Set to 0
65838 : SW : State 0
65838 : EVENT: relay#state=0.00
65907 : ACT : gpio,13,1
65907 : SW : GPIO 13 Set to 1
I subbed to Subscribed to: /ESP02/# as per the log book but I don't see anything publish
65666 : ACT : gpio,13,0
65667 : SW : GPIO 13 Set to 0
65838 : SW : State 0
65838 : EVENT: relay#state=0.00
65907 : ACT : gpio,13,1
65907 : SW : GPIO 13 Set to 1
I subbed to Subscribed to: /ESP02/# as per the log book but I don't see anything publish
ok I realised I subbed to ESP02/# not /ESP02/# and can now see it publishing
@brutzler i thought ESP07 and ESP12 have the same pinout... so you could desolder the ESP12 from a NodeMCU board and put an ESP07 there instead.
@tboss86 there is an #ESPEasy IRC channel on Freenode, it may suit your question better
thanks @igrr
hi folks , I did manually some change on Arduino ESP8266 setting and now the IDE can not find patch the xtensa compiler, any clue to how to re patch it again
exec: "/bin/xtensa-lx106-elf-g++": file does not exist
Error compiling for board Generic ESP8266 Module.
@igrr solder out a ESP12...
ever tried? ;-) perhaps there is a trick, but I didn't get it as I tried half a year ago, as I wanted to see what is printed on the backside of the ESP12. Not with a soldering iron, perhaps with a fan, but then I will loose the chicken food on the PCB......
ever tried? ;-) perhaps there is a trick, but I didn't get it as I tried half a year ago, as I wanted to see what is printed on the backside of the ESP12. Not with a soldering iron, perhaps with a fan, but then I will loose the chicken food on the PCB......
@brutzler there is no nodemcu board that I know of that has the esp07 on it. However if you don't use the lower pins of the esp12 you can replace it with an esp07. The trick to de solder or soldering it is using a heat gun or a hair dryer. The esp07 is also available to buy with an extension board https://m.banggood.com/ESP-07-ESP8266-Serial-WIFI-Module-with-IO-Adapter-Plate-p-980652.html?rmmds=search for example.
@brutzler I did! Exactly for the same purpose of replacing a module with trace antenna with the one with u.fl. This was on a Wemos D1 mini.
yep, hot air gun works well for this. cover the nearby components with kapton tape if you're worried about blowing them away.
I've also done it with some solder wick however this is not recommended
Beware that the cap of the module might get desoldered first
So take your time
oh yeah, that happens. on the other hand if you arent' planning to reuse the esp12, desoldering the cap isn't a big deal.
@igrr Talking about Wemos: They have a D1 mini Pro :-)
https://www.wemos.cc/product/d1-mini-pro.html
-> Already ordered.....
https://www.wemos.cc/product/d1-mini-pro.html
-> Already ordered.....
Thx for discussing.....
Yep, got the d1 mini pro a couple of weeks ago, i like the fact that they went for CP2102 instead ch340g.
was about to test 8M/16M support in #3215 with it
for it to work with SPIFFS a different approach needs to be taken
ESP system data has to be before SPIFFS, or you need two partitions
then Updater code needs to be changed to properly detect where it ends (currently at the start of SPIFFS)
just ordered some D1 pros as well ;)
Do I have to change something, if I want to use the onBoard ceramic-antenna or the pigtail?
What sort of external antenna do you use? I will make my first tries with a little antenna dismounted of a router.....
But I want to put an ESP in my fuse-cabinet, to monitor the electric-meter. This cabinet is of metal, with a visible front. It would be an optical failure to make a hole into the door and put into such a router-antenna. Has anybody an idea for a different solution. Perhaps only a wire, that i can put on the border of the cabinet?
there is a 0ohm resistor that you need to sitch
the one next to the antenna
ähh sorry...sitch?
R16, take off for pigtail.... I guess
ESP system data has to be before SPIFFS, or you need two partitions
what makes you think so @me-no-dev ? :)
in all current layouts SPIFFS goes before the system partition
and after where OTA is written
and I was not able to make the ESP put the system partitions after 4MB mark
that's what SDK 2.1.0 brings us
good then
should be all set
all except uploading. but i was about to fix that as well.
Ouch. formatting SPIFFS does take long...
Format took 329717 ms on 16 MB flash.
that could be maybe because we erase in 4K blocks?
I think we could go up to 64K at a time
True, need to expose the ROM function which erases blocks.
@igrr I intend to add flash setting 4M(2M SPIFF) to my local repo , can you tell which files should be changed , tnx
boards.txt and the ld script for this specific layout
Ivan , setting for 4M(2M SPIFF)
generic.menu.FlashSize.4M2M=4M (2M SPIFFS)
generic.menu.FlashSize.4M2M.build.flash_size=4M
generic.menu.FlashSize.4M2M.build.flash_ld=eagle.flash.4m22.ld
generic.menu.FlashSize.4M2M.build.spiffs_start=0x3FB000
generic.menu.FlashSize.4M2M.build.spiffs_end=0x5FB000
generic.menu.FlashSize.4M2M.build.spiffs_blocksize=8192
generic.menu.FlashSize.4M2M.upload.maximum_size=1044464ld file
/* Flash Split for 4M chips */
/* sketch 2028KB */
/* spiffs 2028KB */
/* eeprom 20KB */
MEMORY
{
dport0_0_seg : org = 0x3FF00000, len = 0x10
dram0_0_seg : org = 0x3FFE8000, len = 0x14000
iram1_0_seg : org = 0x40100000, len = 0x8000
irom0_0_seg : org = 0x40201010, len = 0xfeff0
}
PROVIDE ( _SPIFFS_start = 0x403FB000 );
PROVIDE ( _SPIFFS_end = 0x405FB000 );
PROVIDE ( _SPIFFS_page = 0x100 );
PROVIDE ( _SPIFFS_block = 0x2000 );
INCLUDE "../ld/eagle.app.v6.common.ld"generic.menu.FlashSize.4M2M.build.spiffs_start=0x1FB000
generic.menu.FlashSize.4M2M.build.spiffs_end=0x3FB000
tnx
ADDR_IN_LD = 0x40200000 + ADDR_IN_BOARDS;
we should BTW change the addresses in the LD scripts to be the same as in boards.txt. There is no point of the offset, and we substract it later in software anyway.
you mean following is correct ?
PROVIDE ( _SPIFFS_start = 0x403FB000 );
PROVIDE ( _SPIFFS_end = 0x405FB000 );
yes
@igrr I did get that bounty at the end. a couple of weeks late and had to pester the guy in charge a bit since it seems to be a manual process but I did got it, thanks!