Page 1 of 1

Custom firmware problem

Posted: 04 May 2018, 15:04
by demonchok
Hi

im trying to create a esp mega firmware with this modul
https://github.com/letscontrolit/ESPEas ... usW266.ino

what I've done so far:

downloaded the whole pack, and downloaded the _P046_VentusW266.ino and put it into
the /src folder

then I've used atom to build it like it says in this guide
https://www.letscontrolit.com/wiki/inde ... platformio

but when I upload it, the ventus dont show up, in the end of the guide there is something I dont get
I've added the screenshot, could that be the thing im missing ?

Re: Custom firmware problem

Posted: 04 May 2018, 16:22
by grovkillen
Sorry, old info. You need to move the plugin to the stable list found here:

https://github.com/letscontrolit/ESPEas ... gin_sets.h

Re: Custom firmware problem

Posted: 04 May 2018, 16:36
by demonchok
um.... now im even more lost :D its not my plugin, but an exsisting one ;)
could u tell more specific what I need to do ?

Re: Custom firmware problem

Posted: 04 May 2018, 16:48
by grovkillen
You download the zip (green button on the main GitHub page) and just edit this file:
define_plugin_sets.h


In which you move the plugin name to the list where the rest of the stable plugins are found.

Re: Custom firmware problem

Posted: 04 May 2018, 18:42
by demonchok
hm
added the file _P124_Ventus_W266_RFM69.ino to /src

in define_plugin_sets.h, #define USES_P046 // W266 but still no show!

Re: Custom firmware problem

Posted: 04 May 2018, 18:43
by demonchok
shall i use another firmware instead of normal?

Re: Custom firmware problem

Posted: 04 May 2018, 19:33
by grovkillen
You shouldn't need to add anything except change that one file. P046 is already there in the src folder.

Re: Custom firmware problem

Posted: 04 May 2018, 19:49
by demonchok
ok im kinda lost, if I open define_plugin_sets.h from fresh and look in
line 449 and 450 :

#ifdef PLUGIN_SET_EXPERIMENTAL
#define USES_P046 // VentusW266

then its already there? but I can't see it,

Re: Custom firmware problem

Posted: 04 May 2018, 22:05
by grovkillen
You need to cut that row and place it under NORMAL (as of now it's under the EXPERIMENTAL definition).

Re: Custom firmware problem

Posted: 05 May 2018, 12:01
by demonchok
Ok putted it in

// STABLE #####################################

and compiled it, still it dont show up

heres my define_plugin_sets.h

https://hastebin.com/afowokavac.cpp

Re: Custom firmware problem

Posted: 05 May 2018, 12:31
by grovkillen
What did you compile, build normal?

You should really remove a lot of the other plugins to have enough memory left. You really don't need other plugins since that plugin is really specific to that weather station.

Re: Custom firmware problem

Posted: 05 May 2018, 17:46
by TD-er
Can you make a list of things required for that weather station?
And also the ESP type + size of flash memory.
Is that a custom built setup, or is commercially available?

Re: Custom firmware problem

Posted: 05 May 2018, 17:51
by grovkillen
It's available on Conrad.com as a renkforce product. Only generic categories and the W266 plugin is needed I believe.

Re: Custom firmware problem

Posted: 05 May 2018, 17:58
by TD-er
If you have a more descriptive text, I could add it as a pre-defined set to build.

Re: Custom firmware problem

Posted: 05 May 2018, 18:57
by grovkillen
P003 NORMAL Generic P003_Pulse.ino
P026 NORMAL Generic P026_Sysinfo.ino
P033 NORMAL Generic P033_Dummy.ino
P037 NORMAL Generic P037_MQTTImport.ino
P046 TESTING Hardware P046_VentusW266.ino

https://www.letscontrolit.com/wiki/index.php/VentusW266

Re: Custom firmware problem

Posted: 05 May 2018, 18:58
by grovkillen
Plus P001

Re: Custom firmware problem

Posted: 06 May 2018, 03:53
by Oxyandy
Did you do a clean before re/compile ?

Re: Custom firmware problem

Posted: 06 May 2018, 21:17
by demonchok
im kinda lost now Oo

could u sent an example file ?

Re: Custom firmware problem

Posted: 06 May 2018, 22:17
by TD-er
I assume you're using an ESP8266 with 1M flash?
Or is it 4M?
I will now add this version to the PlatformIO setup, so you can make a build of newer versions.

Re: Custom firmware problem

Posted: 06 May 2018, 22:31
by TD-er

Re: Custom firmware problem

Posted: 07 May 2018, 19:33
by demonchok
TD-er
im totally blank, dont know what u mean??

can't test it now, my MacBook Air won't connect to esp at all, so gone try when im back at the Mac mini

Re: Custom firmware problem

Posted: 07 May 2018, 19:51
by demonchok
i couldn't be more happy, my parents it gonna love it :D sooooo many tnx, but that did i do wrong ?

Re: Custom firmware problem

Posted: 07 May 2018, 20:20
by TD-er
You can see the changes I made over here:
https://github.com/letscontrolit/ESPEas ... 1378/files

Re: Custom firmware problem

Posted: 08 May 2018, 11:59
by demonchok
Who is responsible for this plugin?

the rain sensor isn't listed, and i can't get it to report inside temp / humidity to the mutt

Re: Custom firmware problem

Posted: 08 May 2018, 12:19
by grovkillen
Justme-nl is the writer of the online guide and I believe that he's the one who first created this plugin. I don't own a Ventus W266/RenkForce W205GU so I cannot fix this myself. Maybe someone else can? And I wouldn't say that "someone" is responsible for this, we're all in this together ;)

Re: Custom firmware problem

Posted: 08 May 2018, 13:01
by demonchok
yar thats why we are help ;D will glady help others to ;)

but are u sure about the name ? Justme-nl i can't find him :D

Re: Custom firmware problem

Posted: 08 May 2018, 13:24
by grovkillen

Re: Custom firmware problem

Posted: 09 May 2018, 07:57
by HomeJCL
I’m not 100% but I think I did read in the plugin readme Tint and RHint are not “interfaced” to the plugin due to hardware reasons.

For the rain maybe read more of the project data, as I changed course I stopped my interest in the W266

Re: Custom firmware problem

Posted: 09 May 2018, 11:28
by demonchok
yar read that after, and got the rain and outside temp enabled :D
hope they can fix the in temp to :D

Re: Custom firmware problem

Posted: 28 Sep 2019, 13:41
by alexander44
Help,

I do not get displayed values, have no idea where the problem could be. In the log you can see that there is a connection!

i am using an esp8266 notemcu, is there anything functional to install?


3931717: WD : Uptime 66 ConnectFailures 0 FreeMem 21536 WiFiStatus 3
3961717: WD : Uptime 66 ConnectFailures 0 FreeMem 23416 WiFiStatus 3
3991717: WD : Uptime 67 ConnectFailures 0 FreeMem 23224 WiFiStatus 3
4021717: WD : Uptime 67 ConnectFailures 0 FreeMem 21728 WiFiStatus 3
4051717: WD : Uptime 68 ConnectFailures 0 FreeMem 23416 WiFiStatus 3
4081717: WD : Uptime 68 ConnectFailures 0 FreeMem 23416 WiFiStatus 3
4111717: WD : Uptime 69 ConnectFailures 0 FreeMem 23416 WiFiStatus 3
4141717: WD : Uptime 69 ConnectFailures 0 FreeMem 23416 WiFiStatus 3
4171717: WD : Uptime 70 ConnectFailures 0 FreeMem 23416 WiFiStatus 3
4201717: WD : Uptime 70 ConnectFailures 0 FreeMem 23416 WiFiStatus 3
4231717: WD : Uptime 71 ConnectFailures 0 FreeMem 23416 WiFiStatus 3
4261717: WD : Uptime 71 ConnectFailures 0 FreeMem 23416 WiFiStatus 3
4291717: WD : Uptime 72 ConnectFailures 0 FreeMem 23416 WiFiStatus 3
4321717: WD : Uptime 72 ConnectFailures 0 FreeMem 23416 WiFiStatus 3
4351717: WD : Uptime 73 ConnectFailures 0 FreeMem 23416 WiFiStatus 3
4381718: WD : Uptime 73 ConnectFailures 0 FreeMem 22520 WiFiStatus 3
4385549: Ventus W266 Rcvd(00:00:00) 7FB1:60:1B:C40000D400:03:00000000:880000:12:3FB1:0000D9 > EE
4411717: WD : Uptime 74 ConnectFailures 0 FreeMem 23416 WiFiStatus 3
4416549: Ventus W266 Rcvd(00:00:00) 7FB1:60:1A:D40000D400:03:00000000:800000:01:3FB1:000197 > C2
4441718: WD : Uptime 74 ConnectFailures 0 FreeMem 23416 WiFiStatus 3
4447549: Ventus W266 Rcvd(00:00:00) 7FA1:60:1A:9C0000D400:03:00000000:880000:10:3FB1:0000D9 > C5
4471718: WD : Uptime 75 ConnectFailures 0 FreeMem 23416 WiFiStatus 3
4478550: Ventus W266 Rcvd(00:00:00) 7FB1:40:1A:F40000D400:03:00000000:880000:12:3FB1:0000D9 > 36

Re: Custom firmware problem

Posted: 28 Sep 2019, 15:02
by TD-er
I have no experience myself with this plugin.
But considering the labels of the GPIO functions, it looks like it is using SPI.
The pins you're showing in your config are not the pins connected to the hardware SPI in the ESP.

Signal IO index ESP8266 pin
HSPI CLK 5 GPIO14
HSPI /CS 8 GPIO15
HSPI MOSI 7 GPIO13
HSPI MISO 6 GPIO12

See: https://nodemcu.readthedocs.io/en/master/modules/spi/

I would suggest to reconnect your device to these pins. I have not looked at the code of that plugin, so I'm not sure if the code does try to address the hardware SPI. (your mileage may vary so to speak)

Re: Custom firmware problem

Posted: 29 Sep 2019, 13:21
by alexander44
I tested, unfortunately, nothing helped.
In the log, data arrives, but nothing is displayed. Everything stays at 0. Perhaps something has been changed by the manufacturer. With the app USES_P124 have the same result or worse, it does not do anything in the log!

854305: Ventus W266 Rcvd(00:00:00) 7FB0:57:1A:EF0000EE00:0F:00004C00:880000:12:3FB0:010076 > D2

83950: Ventus W266 Rcvd(16:22:43) 7FB1:58:1A:E50000E400:01:02003600:980000:12:3F31:0100CB > EF

Data stays at 0

Re: Custom firmware problem

Posted: 29 Sep 2019, 22:25
by TD-er
You are running multiple instances of the plugin.
Not sure if that plugin is capable of handling multiple instances. It is just that a lot of other plugins can't.

I don't know that plugin myself, so I cannot help here without diving into the code myself.

Re: Custom firmware problem

Posted: 30 Sep 2019, 10:13
by alexander44
With one instance I had the same result. It looks to me as if the data can no longer be decrypted by the APP. My device is version V4. Possibly. something has changed in the data and would have to be adapted by the developer. How to contact the developer?

Re: Custom firmware problem

Posted: 30 Sep 2019, 10:40
by TD-er
I don't have such a device, nor am I the developer of that plugin.
So I don't think I can be of much help, especially since I don't have something to test with.

Re: Custom firmware problem

Posted: 30 Sep 2019, 20:29
by alexander44
:twisted: have an old espeasy from 22:04:18, now works :!:

viewtopic.php?t=5075 :D