mars
February 21, 2018, 11:17am
21
sorry my muck up
As you can tell I’m getting confused between httpAPI and the direct comms from hardware sketch to local server.
So the blynk.config
default port is now 80 ? (] 8442 will be dropped soon as you noted). Would i need to place 8080 in Blynk.config
as per below or would the #define BLYNK_DEFAULT_PORT 8080
suffice ?
Blynk.config(auth_local_server, local_server, 8080);
Dmitriy
February 21, 2018, 11:18am
22
You may not. It is up to you. You may not update the server and apps and you are fine.
Because new hardware port is 8080 and not 8442
I don’t know. You have to decide for yourself.
Hi guys,
Port 80 isn’t going to work for me on my local server as it doubles as a web server.
Do I just need to do the following for the clients?
Blynk.config(auth_local_server, local_server, 8080);
Or will I have to also update the sever to:
#hardware plain tcp/ip port
hardware.default.port=8080
Scratch that, I see that the server is already listening for hardware on 8080
#http, plain web sockets and plain hardware port
http.port=8080
``
1 Like
Dmitriy
February 21, 2018, 4:11pm
25
@ThatGuy_ZA please read initial announcement again.
Gotcha, sorry, I was thrown off by this
wanek
February 21, 2018, 7:44pm
27
actually what is this? any info / docs?
Gunner
February 21, 2018, 7:46pm
28
wanek:
any info / docs?
Allows the MIN / MAX setting to be changed from the sketch via Blynk.setProperty(vPin, “property”, value)
Although the Docs are not real clear on proper syntax …
wanek
February 21, 2018, 7:49pm
29
before asking, i tried ctrl+f setMin on the blynk docs page, but it found nothing, this is why i asked…
Gunner
February 21, 2018, 7:52pm
30
Not critiquing … I also couldn’t find it via searching. I just kept looking in the area I thought most relevant. For all I know, the docs haven’t been updated yet with this “new” command
Gunner
February 21, 2018, 7:58pm
32
I think the documentation in general could use some touching up… needs to be technical in detail, but still understandable for the non-technical (use lots of crayons)… Hey @Pavel I can work for peanuts… as long as those peanuts are branded “Wemos”
https://github.com/blynkkk/blynkkk.github.io contains all the docs.
We’ll be really glad for some PRs for improvements!
1 Like
Gunner
February 21, 2018, 10:24pm
34
Nice… I have never messed with GitHub forking before… already submitted a small change request
Pavel
February 21, 2018, 11:42pm
35
DM me the total number of you need
I’m pretty sure we can make it work!
mars
February 22, 2018, 7:23am
37
hi
Quick question. If I wanted my local server to listed on both 8080 and 80 would would I need to edit within server.properties
file ?
#hardware plain tcp/ip port
hardware.default.port=8442
#http port MY note default is 8080]
http.port=8080
Dmitriy
February 22, 2018, 8:06am
38
You can’t. You need to choose. Either 80 or 8080. hardware.default.port
will be dropped in future.
Hi,
I’ve just upgrading to v0.5.1 and currently working after adding port: 8080 to my sketch
Blynk.begin(auth, ssid, pass, blynk_server,8080);
But now my terminal showing following text upon restart:
1384, room 16
tail 8
chksum sys⸮⸮⸮⸮param error, use last saved param!
fortunately the system is working fine, should I worried about this?
Thanks
Dmitriy
February 22, 2018, 4:27pm
40
@noersaleh please post your sketch. @vshymanskyy Do you know what that may be?
Emilio
February 22, 2018, 5:30pm
41
Is that from an ESP module? If so, it may be mem related. Google it…
opened 09:37AM - 19 Aug 15 UTC
closed 09:49PM - 14 Sep 15 UTC
After I flashed a new sketch through OTA one of my ESP-01E was stuck in a bootlo… op that was throwing a `system param error`. It took me quite some time to figure out what was going on and at some point I already had give up on the chip. All the time I was still able to flash NodeMCU and the latest Espressif SDK.
Long story short, I was getting the 'system param error' because I was flashing the chip with the wrong flash size (4Mbyte). That was still my default setting as I was also playing with the ESP-12E. The ESP-01E has a flash size of just 1Mbyte so at some point things had to go wrong.
Eventually the solution for me was pretty simple: **Make sure you set the flash size in the Arduino IDE to 1Mbyte when you flash the ESP-01E**. These are my complete settings for flashing the chip: `generic module / 80 Mhz / QIO / 40 MHz / 1M (64kb) / 230400`