Rules and Tones on older build

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Rules and Tones on older build

#1 Post by beic » 12 Dec 2020, 14:47

Hi there,

I'm using older build v2.0.0-dev7 with test and dev enabled:

Code: Select all

#define PLUGIN_BUILD_TESTING
#define PLUGIN_BUILD_DEV
The tone is working over commands or if I do it over the web interface or serial terminal, but they will not work at all if I do manual restart or putting on the power source.

The rules are:

Code: Select all

On System#Boot do
  gpio,14,0
  tone,15,1300,100
endon

On WiFi#Connected do
  tone,15,1300,200
endon

On AM2301#Temperature do
 If [AM2301#Temperature] > 29
  gpio,14,1
 Else
  gpio,14,0
 EndIf
endon
Any help would be highly appreciated,

Kind regards,
beic

User avatar
Ath
Normal user
Posts: 565
Joined: 10 Jun 2018, 12:06
Location: NL

Re: Rules and Tones on older build

#2 Post by Ath » 12 Dec 2020, 17:33

The best help here is to point you to a recent build to be downloaded from https://github.com/letscontrolit/ESPEasy/releases

These are called "nightly builds", but are actually built on demand only, and are the most stable and feature-rich builds available.

(And I'm assuming you've connected some kind of buzzer device to GPIO 15, as that's the only way to produce sound from an ESP, AFAIK)
/Ton

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#3 Post by beic » 12 Dec 2020, 17:57

Ath wrote: 12 Dec 2020, 17:33 The best help here is to point you to a recent build to be downloaded from https://github.com/letscontrolit/ESPEasy/releases

These are called "nightly builds", but are actually built on demand only, and are the most stable and feature-rich builds available.

(And I'm assuming you've connected some kind of buzzer device to GPIO 15, as that's the only way to produce sound from an ESP, AFAIK)
Unfortunately, I can't use any other build than v2.0.0-dev7.

Yes, I'm using WeMos D1 mini with dedicated Buzzer Shield.

User avatar
Ath
Normal user
Posts: 565
Joined: 10 Jun 2018, 12:06
Location: NL

Re: Rules and Tones on older build

#4 Post by Ath » 12 Dec 2020, 18:18

beic wrote: 12 Dec 2020, 17:57 Unfortunately, I can't use any other build than v2.0.0-dev7.
Please explain, ESPEasy runs just fine on a Wemos D1 Mini, and the buzzer is simply connected to a GPIO port, so nothing should hold you back to upgrade.
There is no reasonable way to be able to support such an old version, nor can anything be 'fixed' if it were broken, as many iterations have gone over the software in improvements and extensions.
/Ton

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#5 Post by beic » 12 Dec 2020, 19:09

Ath wrote: 12 Dec 2020, 18:18 Please explain, ESPEasy runs just fine on a Wemos D1 Mini, and the buzzer is simply connected to a GPIO port, so nothing should hold you back to upgrade.
There is no reasonable way to be able to support such an old version, nor can anything be 'fixed' if it were broken, as many iterations have gone over the software in improvements and extensions.
Above v2.0.0-dev7 it wont compile on Arduino IDE v1.8.2 and ESP Core 2.3.0, so, that is the reason, and also the plugin incompatibility.

User avatar
Ath
Normal user
Posts: 565
Joined: 10 Jun 2018, 12:06
Location: NL

Re: Rules and Tones on older build

#6 Post by Ath » 12 Dec 2020, 19:43

beic wrote: 12 Dec 2020, 19:09 Above v2.0.0-dev7 it wont compile on Arduino IDE v1.8.2 and ESP Core 2.3.0, so, that is the reason, and also the plugin incompatibility.
ESPEasy comes with a nice flash tool (ESP.Easy.Flasher.exe) and a bunch of .bin files (including a couple of test builds) that can be flashed on the ESP without a hitch, no need to a) self-compile, b) use that old an ESP Core version, and c) use Arduino IDE, VSCode with PlatformIO is a modern alternative for the Arduino IDE. The complete source for ESPEasy is also available as a .zip download and can be cloned from Github to your local system and built without issues.
/Ton

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#7 Post by beic » 12 Dec 2020, 19:55

Ath wrote: 12 Dec 2020, 19:43
beic wrote: 12 Dec 2020, 19:09 Above v2.0.0-dev7 it wont compile on Arduino IDE v1.8.2 and ESP Core 2.3.0, so, that is the reason, and also the plugin incompatibility.
ESPEasy comes with a nice flash tool (ESP.Easy.Flasher.exe) and a bunch of .bin files (including a couple of test builds) that can be flashed on the ESP without a hitch, no need to a) self-compile, b) use that old an ESP Core version, and c) use Arduino IDE, VSCode with PlatformIO is a modern alternative for the Arduino IDE. The complete source for ESPEasy is also available as a .zip download and can be cloned from Github to your local system and built without issues.
Yes, Ath, I know all what you just did wrote to me, and you are right about those propositions, but I asked a different question.

Why is that when I restart the the device over web interface the tone works, but if I restart the device with the reset button, the tone will not work (see Rules above in my first post).

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

Re: Rules and Tones on older build

#8 Post by TD-er » 12 Dec 2020, 20:38

Why do you need core 2.3.0? And/or a very specific Arduino version?
If memory serves me well, core 2.4.0 was used in ESPEasy around March 2018.

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#9 Post by beic » 12 Dec 2020, 21:47

TD-er wrote: 12 Dec 2020, 20:38 Why do you need core 2.3.0? And/or a very specific Arduino version?
If memory serves me well, core 2.4.0 was used in ESPEasy around March 2018.
Because, of the plugins compatibility from before...

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

Re: Rules and Tones on older build

#10 Post by TD-er » 12 Dec 2020, 21:57

Are there any plugins that will no longer work?
Or plugins you use from Playground that may be needed to updated to recent code?

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#11 Post by beic » 12 Dec 2020, 22:43

TD-er wrote: 12 Dec 2020, 21:57 Are there any plugins that will no longer work?
Or plugins you use from Playground that may be needed to updated to recent code?
Notifications are empty and there are no BME680 and SI1145 sensor plugin inside the test, dev build.
Last edited by beic on 12 Dec 2020, 22:47, edited 1 time in total.

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

Re: Rules and Tones on older build

#12 Post by TD-er » 12 Dec 2020, 22:47

BME680 is a pending PR.
Maybe you can test the test builds I linked here: https://github.com/letscontrolit/ESPEasy/pull/3386

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#13 Post by beic » 12 Dec 2020, 22:52

TD-er wrote: 12 Dec 2020, 22:47 BME680 is a pending PR.
Maybe you can test the test builds I linked here: https://github.com/letscontrolit/ESPEasy/pull/3386
Downloaded as we speak, will test it tomorrow, also can you see the SI1145 plugin too?

Thank you!

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

Re: Rules and Tones on older build

#14 Post by TD-er » 12 Dec 2020, 23:21


User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#15 Post by beic » 12 Dec 2020, 23:31

TD-er wrote: 12 Dec 2020, 23:21 This one you mean?
https://github.com/letscontrolit/ESPEas ... SI1145.ino
Exactly! 1+ ;)

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

Re: Rules and Tones on older build

#16 Post by TD-er » 12 Dec 2020, 23:39


User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#17 Post by beic » 12 Dec 2020, 23:47

TD-er wrote: 12 Dec 2020, 23:39 Made an issue for it to remember. https://github.com/letscontrolit/ESPEasy/issues/3426
Thank you!!!


User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#19 Post by beic » 13 Dec 2020, 01:09

Downloading... ;)

p.s. just noticed, can you maybe include both Sensor plugin into one same build?

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

Re: Rules and Tones on older build

#20 Post by TD-er » 13 Dec 2020, 01:27

Yep I can include both BME680 and this one.... but not "today" as it is already nearly 1:30 am and my eyes start to itch from sleep :)

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#21 Post by beic » 13 Dec 2020, 10:49

TD-er wrote: 13 Dec 2020, 01:27 Yep I can include both BME680 and this one.... but not "today" as it is already nearly 1:30 am and my eyes start to itch from sleep :)
Same here, but I already woke up,so, is there any chance to implement Email notification too?

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

Re: Rules and Tones on older build

#22 Post by TD-er » 13 Dec 2020, 15:38

For now both plugins, not yet the notification.
Still have to make it all fit a bit better.

https://www.dropbox.com/s/klmom5i6ee3sx ... 7.zip?dl=0
https://www.dropbox.com/s/b2ko0frxjw6fe ... 7.zip?dl=0

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#23 Post by beic » 13 Dec 2020, 22:02

TD-er wrote: 13 Dec 2020, 15:38 For now both plugins, not yet the notification.
Still have to make it all fit a bit better.

https://www.dropbox.com/s/klmom5i6ee3sx ... 7.zip?dl=0
https://www.dropbox.com/s/b2ko0frxjw6fe ... 7.zip?dl=0
This is just so confusing:

Tried ESP_Easy_mega_20201213_custom_beta_ESP8266_4M1M.bin (there are the BME680 and SI1145 plugins, but missing all the default plugins, also no Email, Buzzer notification), but with ESP_Easy_mega_20201213_normal_ESP8266_4M1M.bin (I get all the default plugins and Email, Buzzer notification, but without BME680 and SI1145 plugins).

So, which one I need to upload to get all of them, default plugins with BME680 and SI1145 included?

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

Re: Rules and Tones on older build

#24 Post by TD-er » 14 Dec 2020, 00:00

I'm still working on making it all fit and the new plugins are not at the "normal" plugin selection.

The "test" and "dev" builds have become too large to fit, so I had to disable some parts.
But like I said, it is literally taking all my time lately to find a way to make it all fit and find a proper alternative to suit everybody's needs as I'm building a build server for anyone to select what they need and build it on demand.

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#25 Post by beic » 14 Dec 2020, 01:13

TD-er wrote: 14 Dec 2020, 00:00 I'm still working on making it all fit and the new plugins are not at the "normal" plugin selection.

The "test" and "dev" builds have become too large to fit, so I had to disable some parts.
But like I said, it is literally taking all my time lately to find a way to make it all fit and find a proper alternative to suit everybody's needs as I'm building a build server for anyone to select what they need and build it on demand.
I understood, I'm here like from early R142 version, also contributed a few plugins, enhancements, essential and bug reports, fixes, so, I almost know everything.

Testing right now the BME680, it's working for now, but can you please tell me that the Gas readings are the IAQ Index or?

Also from the I2C scanner list, it's missing the BME680 name identifier (Supported devices).

Didn't had time to test the SI1145 yet, but I will do that tomorrow.

Also found a few little typo bugs, not a big deal but it's hurts my eyes, if you don't mind! ;)

In file ESPEasy_FactoryDefault.cpp find the line:

RESET: Succesful, rebooting. (you might need to press the reset button if you've justed flashed the firmware)

and change it to:

RESET: Successful, rebooting. (you might need to press the reset button if you've just flashed the firmware)

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

Re: Rules and Tones on older build

#26 Post by TD-er » 14 Dec 2020, 09:01

Done for the typo's.

And I have not written the BME680 plugin, I only moved it from the playground as it was apparently working according to some users.
Also had to patch it as it wasn't using the set I2C address and also had to adopt it to the more recent changes in the core of ESPEasy.

I do know that Bosch uses a closed source binary, which we are not allowed to distribute (I asked) if you want to use the more advanced features of the BME680.
So I don't know what the reliability is of the readings, nor if it is a true IAQ index.
I also have to look into the code for it.

These are the values set by the plugin:

Code: Select all

        UserVar[event->BaseVarIndex + 0] = P106_data->bme.temperature;
        UserVar[event->BaseVarIndex + 1] = P106_data->bme.humidity;
        UserVar[event->BaseVarIndex + 2] = P106_data->bme.pressure / 100.0;
        UserVar[event->BaseVarIndex + 3] = P106_data->bme.gas_resistance / 1000.0;
Here the very "elaborate" documentation on that last call: https://github.com/adafruit/Adafruit_BM ... #L100-L102

It states it is in Ohms, so I have no idea why someone thought it would be a good idea to divide it by 1000.

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#27 Post by beic » 14 Dec 2020, 11:36

TD-er wrote: 14 Dec 2020, 09:01 Here the very "elaborate" documentation on that last call: https://github.com/adafruit/Adafruit_BM ... #L100-L102

It states it is in Ohms, so I have no idea why someone thought it would be a good idea to divide it by 1000.
Maybe my logic was good, but how I see it now, maybe I'm wrong.

The Gas readings are showing between 102 and 146 (normal clean room with 26c temperature), but if I apply gas from the lighter (Butane) then the readings will go down to 15-45.

So, if you read this document and see the table 4 on the 9th page, then it's not reading the IAQ index.

https://cdn-shop.adafruit.com/product-f ... BME680.pdf

Image

What I found out after, is that if the:

Code: Select all

Concentration of VOCs is Higher then the resistance is Lower
Concentration of VOCs is Lower then the resistance is Higher
So, it's like contra / inverse reading...

Image

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

Re: Rules and Tones on older build

#28 Post by TD-er » 14 Dec 2020, 17:03

I can also have a look at what is needed to use the binary blob made by Bosch.
Then we can have a tutorial how to build it yourself (as the binary blob must be linked at compile time).
I think the AIQ is part of this closed source binary blob if my memory serves me well.

Really frustrating they don't allow me to distribute a prebuilt binary including this binary blob of them.
Maybe they will allow it if you upload the binary blob yourself on a build service I'm working on.
But I'm afraid it may lead to lots and lots of reported issues by users if they use the wrong binary etc.

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#29 Post by beic » 14 Dec 2020, 17:29

TD-er wrote: 14 Dec 2020, 17:03 I can also have a look at what is needed to use the binary blob made by Bosch.
Then we can have a tutorial how to build it yourself (as the binary blob must be linked at compile time).
I think the AIQ is part of this closed source binary blob if my memory serves me well.

Really frustrating they don't allow me to distribute a prebuilt binary including this binary blob of them.
Maybe they will allow it if you upload the binary blob yourself on a build service I'm working on.
But I'm afraid it may lead to lots and lots of reported issues by users if they use the wrong binary etc.
Yes, but you could use the BSEC Air Quality Library by Bosch Sensortec, no?, there is a fully working example and description! (nice little article) ;)
https://learn.adafruit.com/adafruit-bme ... ty-library
https://github.com/BoschSensortec/BSEC-Arduino-library

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

Re: Rules and Tones on older build

#30 Post by TD-er » 14 Dec 2020, 19:02

As far as I know is the BSEC library only available as binary blob.
But I will read your links.

Edit:
The are static linked binary blobs. See: https://github.com/BoschSensortec/BSEC- ... rc/esp8266

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#31 Post by beic » 14 Dec 2020, 21:37

After the first 25 second the SI1145 sensor stopped working and again after I restarted the device again stopped working after 9 hours 52 minutes.

Image

Image

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

Re: Rules and Tones on older build

#32 Post by TD-er » 14 Dec 2020, 22:02

OK, that's probably a simple fix.
Will make a change and a test build. (try to have one before midnight :) )

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#33 Post by beic » 14 Dec 2020, 22:04

TD-er wrote: 14 Dec 2020, 22:02 OK, that's probably a simple fix.
Will make a change and a test build. (try to have one before midnight :) )
Nice! 1+ :twisted:


User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#35 Post by beic » 14 Dec 2020, 23:46

Yes, I will flash it right now!!! ;)

btw...where can I edit/modify the current SI1145 library, I wish to change the Device and the Values names to reflect to the normal/default naming?!

Code: Select all

SI1145 UV index (Adafruit-QA) to UV - SI1145
VISIBLE to Visible
INFRA to Infra
UV to Uv

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

Re: Rules and Tones on older build

#36 Post by TD-er » 14 Dec 2020, 23:58

See the pending PR: https://github.com/letscontrolit/ESPEas ... 8d1e025R15

But I can also change them and add it to the PR.

N.B. "UV" should remain in caps.

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

Re: Rules and Tones on older build

#37 Post by TD-er » 15 Dec 2020, 00:02

And the names are changed for the pending PR.
https://github.com/letscontrolit/ESPEas ... 3427/files#

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#38 Post by beic » 15 Dec 2020, 00:12

TD-er wrote: 14 Dec 2020, 23:58 N.B. "UV" should remain in caps.
Fair enough! ;)

Also, did you add BME680 to the I2C Scanners list in the I2C_Scanner.cpp file? ;)

You can just copy n' paste from below, I also reordered the models to be nicer!

Code: Select all

case 0x76:
 result =  F("BMP280,BME280,BME680,MS5607,MS5611,HT16K33,TCA9546a/8a I2C multiplexer");
 break;
case 0x77:
 result =  F("BMP085,BMP180,BMP280,BME280,BME680,MS5607,MS5611,HT16K33,TCA9546a/8a I2C multiplexer");
 break;
 

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

Re: Rules and Tones on older build

#39 Post by TD-er » 15 Dec 2020, 00:43

OK, done.
Now I'll go to bed and tomorrow you'll have the files ready for the ReadTheDocs for both plugins? ;)

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#40 Post by beic » 15 Dec 2020, 00:46

TD-er wrote: 15 Dec 2020, 00:43 OK, done.
Now I'll go to bed and tomorrow you'll have the files ready for the ReadTheDocs for both plugins? ;)
Thank you my Sempai and good night! ;)

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#41 Post by beic » 15 Dec 2020, 11:39

Oh, wait, I misread your last post, do you want me to write on the ReadTheDocs portal the Documentation and Description for those Sensors, ja?!
Last edited by beic on 15 Dec 2020, 11:43, edited 2 times in total.

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

Re: Rules and Tones on older build

#42 Post by TD-er » 15 Dec 2020, 11:42

Well since you're using them, and requested them to be moved from the Playground... :)

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#43 Post by beic » 15 Dec 2020, 11:43

TD-er wrote: 15 Dec 2020, 11:42 Well since you're using them, and requested them to be moved from the Playground... :)
Okay, but what is wrong with Lets Control It Wiki to start all over on the ReadTheDocs?!

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

Re: Rules and Tones on older build

#44 Post by TD-er » 15 Dec 2020, 13:16

beic wrote: 15 Dec 2020, 11:43
TD-er wrote: 15 Dec 2020, 11:42 Well since you're using them, and requested them to be moved from the Playground... :)
Okay, but what is wrong with Lets Control It Wiki to start all over on the ReadTheDocs?!
The reason we started converting it to RTD is that the source of the docs is included in the same repository as the code.
This means we can generate version dependent documentation.

Also it is way more easy to keep references to other parts working in Sphinx/RTD as you "compile" the documentation.
And you are forced to keep plugin/controller specific documentation accessible in the same structure, which allows (later) to directly include the specific documentation in the web UI.
This is made possible since you can also generate the same documentation in a new form/template if needed to fit in the layout of the UI.
A wiki is less suitable for this and also needs quite a lot of maintainance to keep the look and feel consistant and internal references up-to-date.
Right now it is already hard to keep changes documented, let alone to keep the whole structure up-to-date which takes more work on a wiki compared to using Sphinx.

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#45 Post by beic » 15 Dec 2020, 14:08

TD-er wrote: 15 Dec 2020, 13:16
beic wrote: 15 Dec 2020, 11:43
TD-er wrote: 15 Dec 2020, 11:42 Well since you're using them, and requested them to be moved from the Playground... :)
Okay, but what is wrong with Lets Control It Wiki to start all over on the ReadTheDocs?!
The reason we started converting it to RTD is that the source of the docs is included in the same repository as the code.
This means we can generate version dependent documentation.

Also it is way more easy to keep references to other parts working in Sphinx/RTD as you "compile" the documentation.
And you are forced to keep plugin/controller specific documentation accessible in the same structure, which allows (later) to directly include the specific documentation in the web UI.
This is made possible since you can also generate the same documentation in a new form/template if needed to fit in the layout of the UI.
A wiki is less suitable for this and also needs quite a lot of maintainance to keep the look and feel consistant and internal references up-to-date.
Right now it is already hard to keep changes documented, let alone to keep the whole structure up-to-date which takes more work on a wiki compared to using Sphinx.
Oh, I understand you now, but there was and has a lot of changes over a short period, and I think it's not so good. (lack of contributors, developers and most importantly the time putting into).

So, you wanted something like this for the current plugins too or? (+ the pinouts and connection diagram)

Image

Image

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

Re: Rules and Tones on older build

#46 Post by TD-er » 15 Dec 2020, 14:12

Just take a look at how the documentation for other plugins is made.
And perhaps also make sure you can build the docs yourself, otherwise it is not really useful.

See for starters: https://espeasy.readthedocs.io/en/lates ... ation.html
I find it the easiest way to compile the docs in the IDE, as you have the Python environment present in the IDE. (I use VS code)

Not sure if it is really needed to describe in depth how to solder a module to the ESP, as that's rather generic info.
And it is also quite a lot of work to do it for all plugins.
If it is already present on the wiki docs, then please use it.

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Rules and Tones on older build

#47 Post by beic » 15 Dec 2020, 18:56

TD-er wrote: 15 Dec 2020, 14:12 Just take a look at how the documentation for other plugins is made.
And perhaps also make sure you can build the docs yourself, otherwise it is not really useful.

See for starters: https://espeasy.readthedocs.io/en/lates ... ation.html
I find it the easiest way to compile the docs in the IDE, as you have the Python environment present in the IDE. (I use VS code)

Not sure if it is really needed to describe in depth how to solder a module to the ESP, as that's rather generic info.
And it is also quite a lot of work to do it for all plugins.
If it is already present on the wiki docs, then please use it.
Omg, I tried it, it's not for me to learn another type of platform! :o

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

Re: Rules and Tones on older build

#48 Post by TD-er » 16 Dec 2020, 00:05

beic wrote: 14 Dec 2020, 23:46
Yes, I will flash it right now!!! ;)
[...]
How stable is the plugin now it has been running for about 24h?

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

Re: Rules and Tones on older build

#49 Post by TD-er » 19 Dec 2020, 13:28

Hmm running for 5 days now, without any complaint?
So it is now stable?

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 27 guests