update to mega-Git v2.0-20180126, missing options ?

Moderators: rtenklooster, Voyager, BertB, Stuntteam

Forum rules
You have entered the experimental forum, beware!!!
Post Reply
Message
Author
User avatar
pwassink
Normal user
Posts: 60
Joined: 31 Oct 2016, 08:33
Location: Vorden NL

update to mega-Git v2.0-20180126, missing options ?

#1 Post by pwassink » 29 Jan 2018, 16:38

Hello,

I have been busy updating a lot of mainly esp-12 based nodes in and around the house last couple of days,
moved them all up to Mega, version GIT version: mega-20180104, with a manual rebuild of the config on the nodes,
backing up several times, and yesterday went on with version GIT version: v2.0-20180126.

i did some testing with GlobalSync, which did not work wen using long device-variable-name COMING OFF the sending node,
renamed that device on the local device name and it started working, was able to display the outside temp on livingroom-esp.
that is working, nice feature !

when comparing two Esp's which were both updated over the air with the same GIT version:v2.0-20180126 4096 normal bin file several
of the mega options were missing on a nodemcu-v2 based esp.
The whole screen of the config screen is different, for instance the IP acceslimitation for only localsubnet which i loved was not there.
that esp also reports Build 20000 - Mega (core 2_3_0) GIT version mega-20180104 Plugins 48 [Normal]
when you ask for info in the info option under tools menu. so took the laptop, flashed it via usb, with te same new file, it seemed blanco,
enterred the basic settings via the 192.168.4.1 ap-mode menu and still not the extra Mega options for Ip restriction .. ?
I tried to solve this by entering a Reset command in the serial console which should format and default all settings, but it did not solve anything,
yes the esp came back as a freshly flashed item, but still several of the mega options were missing as i wrote before..

Getting a bit confused on this esp, anyone with the same experiences ?

Peter

#edit, made clear what happened. underlined
Last edited by pwassink on 30 Jan 2018, 09:04, edited 1 time in total.

TD-er
Core team member
Posts: 8643
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: update to mega-Git v2.0-20180126, missing options ?

#2 Post by TD-er » 30 Jan 2018, 01:50

I guess you got confused by the naming convention we use.
And I won't blame you.

In short, we have the v2.0 branch and the Mega branch.
And to make things even worse, it indeed appears the description in the v2.0 branch calls itself the "Mega".

The v2.0 branch already has a feature freeze for several months now (and sometimes even small new features are also backported, to make the inconsistency even more apparent :) )
So all the nice new features are in the "Mega" branch (based on the filenames, not what is shown in the web interface)
The web interface does make some kind of distinction on version numbers. 20000 vs. 20100 if I'm correct. So that's a clear give away on the differences ;)

Well I think we have to look into that tomorrow, but @pyz0r already told me about an hour ago, I was going to bed... an hour before that.
So I guess that will actually be fixed later this week.

Now the nice part is, we just mention @grovKillen and ask him to create an issue for that and then we devs know what to pick up next :)

User avatar
pwassink
Normal user
Posts: 60
Joined: 31 Oct 2016, 08:33
Location: Vorden NL

Re: update to mega-Git v2.0-20180126, missing options ?

#3 Post by pwassink » 30 Jan 2018, 07:50

Ah, Ok, that brings some light in this !

Thanks for the explanation and the job ahead ,
i will wait impatiently and be one of the first testers :-)

Updating to mega-20180130 now, Got all the options i was missing
and it does mention version 20100 in the nodelist also ..

Unit 8 hub08 20000 ESP Easy Mega
Unit 9 hub09 20100 ESP Easy Mega

peter
Last edited by pwassink on 30 Jan 2018, 08:31, edited 1 time in total.

User avatar
grovkillen
Core team member
Posts: 3621
Joined: 19 Jan 2017, 12:56
Location: Hudiksvall, Sweden
Contact:

Re: update to mega-Git v2.0-20180126, missing options ?

#4 Post by grovkillen » 30 Jan 2018, 08:00

ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you :idea: :idea: :idea:

User avatar
pwassink
Normal user
Posts: 60
Joined: 31 Oct 2016, 08:33
Location: Vorden NL

Re: update to mega-Git v2.0-20180126, missing options ?

#5 Post by pwassink » 30 Jan 2018, 09:13

great,

Sorry for the unclear description off the global-sync fault, tried to make it more clear.

I was unable to use the device name which was automatically created on the receiver and coming off the sending node,
tried to display the temp with that device name on a Lcd, oled and oled framed, nogo.
Tested all with the same esp-easy version GIT version:v2.0-20180126 using 4096 binary from the server.

Started some fiddling and when i renamed the local device name on the receiving node, and it worked fine.

TD-er
Core team member
Posts: 8643
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: update to mega-Git v2.0-20180126, missing options ?

#6 Post by TD-er » 30 Jan 2018, 10:28

Hmm, it's good that Jimmy (grovKillen) was also reading, since I overlooked your real issue (apart from the naming part of the releases)

Were you using more than one device? (e.g. all with the same "esp_easy" name)
Last edited by TD-er on 30 Jan 2018, 13:43, edited 1 time in total.

User avatar
pwassink
Normal user
Posts: 60
Joined: 31 Oct 2016, 08:33
Location: Vorden NL

Re: update to mega-Git v2.0-20180126, missing options ?

#7 Post by pwassink » 30 Jan 2018, 10:41

One remote esp12 sender, and two receivers were used, every esp has an unique name / nodeid
one with an lcd, one with oled for displaying the temperature outside the house in this testcase
both do work simultaneous now, using the workaround by defining a local device name on the receiving ESP
(effectively renaming the local device name on the receiver that was created by the globalsync activity i mean )
and use that in a [localdevicename#Temperature] entry to get it on a display

Post Reply

Who is online

Users browsing this forum: No registered users and 12 guests