Let's Control It

Instructions for usibg the Arduino IDE are on the main page. But have to change for the items listed in Martinus post. Also read the wiki and search the forum before asking, people appear to ignore questions which have been answered multiple times.

Currently at R117 on github.

1) Support for FHEM has been added, but can't test this in my testlab.

2) Support for evaluating the _C025 playground plugin, need testers with feedback on this one. Once settled it could replace _C008
Maybe this new HTTP plugin can also be used for Pimatic Home Automation platform (plugin playground) with the right template entered. Maybe the developer can have a look at this?

3) The pulse counter plugin can now be used with delta/total/time values towards controllers that support this (Not Domoticz, so don't try that option)
(remember that the "total" count is not persistent after a power cycle, but the pulsetime value could be useful in this scenario)

There's still one pull request pending: Power plugin for domoticz Electric (Inst+Cntr)
It's not clear to me if this provides a useful sensor as it seems to depend on total count. I guess that this will drop to zero after each ESP reset/power cycle.
I'm using the Domoticz incremental counter that works as expected regardless of power cycles because it is fed with delta values.

Currently at R118 on github:

1) Decided to add the Dummy Device that has often been used for testing. Can be used and controlled using the rules section to create a fictitious device.
2) Support the simple value DUAL sensortype, used by the Domoticz electric power counter that is added to the playground as Plugin 112.

Martinus wrote: .....
1) Support for FHEM has been added, but can't test this in my testlab.
.....

Hi Martinus,
I've just got an fhem setup....
Can u give some more detail on FHEM-side configuration ?
You have to define items in FHEM....

Is it an http connection ?

thanks & regards
Paolo

pppp33 wrote:

Martinus wrote: .....
1) Support for FHEM has been added, but can't test this in my testlab.
.....

Hi Martinus,
I've just got an fhem setup....
Can u give some more detail on FHEM-side configuration ?
You have to define items in FHEM....

Is it an http connection ?

thanks & regards
Paolo

I can't really help you out with the FHEM specifics. I know it's using HTTP. I think there's more info to be found on the FHEM forum.
Have a look at this: https://forum.fhem.de/index.php/topic,55728.0.html

Yet another bug fixed in R119. I could not test this at the moment, but as far as i could see, the pulse commands on PCF8574 could not have worked...

R120 has the formula fields removed from the Dummy Device. This can't work within the current framework and it is not so easy to change that.

If you need some simple calculations to set the dummy device values, you can specify this within the rule itself like:
In this case we have setup an analog device on task 1, named LDR with valuename LightValue.
We also setup the Dummy Device on task 2.

On every read on this analog device, the value will be multiplied with 1.5, 2 subtracted and stored in the Dummy Device in the first field.

R120 is considered to be the next stable ESP Easy.
We moved to Arduino Core 2.3.0, pubsubclient 2.6.0, ArduinoJson 5.6.4, fixed some bugs and added the HTTP controller for FHEM.

The package including firmware binaries, related libraries and source (as reference) can be downloaded from our website:
http://www.esp8266.nu/downloads/ESPEasy_R120.zip

The easiest way to upgrade your modules is using OTA (unless you have the classic 512k modules ). Just upgraded 15 modules, 100% success rate. If you're using the blue ESP-01 modules, consider to replace those with the newer black ones. I replaced all of my ESP-01's so i can use OTA. Makes life al lot easier...

Thanks guys for the really great work..
Flash some of my nodemcu with R120 ... [ not work with them yet ] flashing was simple as always..

I tried a sonoff-device, now I cannot reach it any more. It said, Update ok and then it dissapeared.

ambassadoro wrote:I tried a sonoff-device, now I cannot reach it any more. It said, Update ok and then it dissapeared.

That problem i had to when i diid a update on the fly..
Just the "old" way is the best in my eyes..

ambassadoro wrote:I tried a sonoff-device, now I cannot reach it any more. It said, Update ok and then it dissapeared.

SonOff devices usually have a 1 megaByte flash chip so if you make the binfile yourself you have to choose these values:

Board: Generic ESP8266 Module
FlashSize: 1M (64K SPIFFS)
Reset Method: "ck"

If you choose a different FlashSize/SPIFFS your ESP and OTA will not function anymore and you have to re-flash it with a USB/Serial converter using USB.

Lucky me that I tried first my modified plug and not one burried in the wall
So its just 4 screws away.

I used the bin-file 1M out of the package. Next time, I compile one myself.

i compiled r121 with this warings, but got a binary.

arduino 1.6.5, pubsub 2.6, core 2.3.

is this critical? doesnt look so..?

this thread "ESP Easy-Releases", the other "ESP EASY Development", the "FEATURE REQUEST" (and something about PLUGINS)
seems to me the skeleton to see whats going on with the firmware.

maybe i makes sense to pin them on top of the forum?
or have features and bugs in the github-issues with markers (which makes checking the development easier,
(and step down on degree with the importance of the "DEEP-SLEEP" pin?

R124 is available on github. We've done some code optimization to controllers for ThingSpeak, OpenHAB, PiDome and Generic HTTP.
A new controller for generic UDP has been added.
The dummy device can now send all 4 values on some generic controllers.

The IR TX plugin from the playground has been added to the main repository as P035, (contributed by cherowley). Because we also have IR receive for some time, it only makes sense to be able to send as well. I couldn't test this in my testlab so maybe someone else can do this? If you have used P106 from the playground, remove if from your project folder as it's no longer needed. You need to setup IR TX again because the plugin has been renumbered.

Martinus wrote:R124 is available on github. We've done some code optimization to controllers for ThingSpeak, OpenHAB, PiDome and Generic HTTP.
A new controller for generic UDP has been added.
The dummy device can now send all 4 values on some generic controllers.

The IR TX plugin from the playground has been added to the main repository as P035, (contributed by cherowley). Because we also have IR receive for some time, it only makes sense to be able to send as well. I couldn't test this in my testlab so maybe someone else can do this? If you have used P106 from the playground, remove if from your project folder as it's no longer needed. You need to setup IR TX again because the plugin has been renumbered.

Hi, I was waiting for this IR TX plugin for a long time, I've all the hardware needed to test it but can you just explain me how to use the plugin ?

Ok, find this on the forum :

ThinkPad wrote:I got the _P106_IRTX.ino plugin working! It works really good!

How to do it:
- Download ESPEasy source (from .zip or from GitHub)
- Download the plugin and place it in the same folder as 'ESPEasy.ino' and the other *.ino files
- Download the IRremoteESP8266.h and also put in same folder as above
- Compile & upload to your device (i used a Wemos D1 Mini board)
- Then under 'Devices' in ESPEasy, select 'Infrared Transmit' and choose the GPIO pin that you have the IR Transmitter connected to. For Wemos D1 Mini i connected the transmitter to pin 'D1', which is GPIO5 in ESPEasy.

You should then be able to send commands by calling the ESP url like this: http://192.168.4.138/control?cmd=IRSEND,NEC,4bb620df,32 (this command turns my Onkyo 5.1 receiver on)

Finding out the codes (and protocol and bits) that your remote uses is quite easy. I used a separate Arduino Nano which i loaded a sample sketch of 'IRrecvDumpV2' on.
As a transmitter i use two IR leds, a 2N2222 transistor and a 470 Ohm resistor. The transistor is driven from the GPIO and gives the IR leds 5V, to create a powerful transmitter. The ready to use IR transmitter boards from China are very weak, because they draw their power from the GPIO.

To have a sort of remote, i created this webpage on my webserver:

Code: Select all

<!DOCTYPE html>
<html>
<head>
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
</head>
<body>

<h1>ESP8266 IR Remote</h1>
<h2>Versterker</h2>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb620df,32')">Power on</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4b36e21d,32')">Power off</button><br><br>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb6d02f,32')">Input tuner</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb6f00f,32')">Input VIDEO1 (Laptop)</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb6906f,32')">Input CD (PC Coaxial)</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb6708f,32')">Input VIDEO2 (TV)</button><br><br>

<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb600ff,32')">Channel up</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb6807f,32')">Channel down</button><br><br>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb641be,32')">(Search) Up</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb6c13e,32')">(Search) Down</button><br><br>

<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb640bf,32')">Volume +</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb6c03f,32')">Volume -</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb6a05f,32')">Volume mute</button><br><br><br>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb632cd,32')">Listening mode up</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4b36a25d,32')">Listening mode down</button>
<hr>
<h2>TV</h2>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,SAMSUNG,E0E09966,32')">Power on</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,SAMSUNG,E0E019E6,32')">Power off</button><br><br>
Response: <b><p id="output"></p></b>

<script>
function loadDoc(url) {
  var xhttp = new XMLHttpRequest();
  xhttp.onreadystatechange = function() {
    if (xhttp.readyState == 4 && xhttp.status == 200) {
      document.getElementById("output").innerHTML = xhttp.responseText;
    }
  };
  xhttp.open("GET", url, true);
  xhttp.send();
}
</script>

</body>
</html>

But i am planning on using it with my home automation, 'Home Assistant'.

Let's try it !

EDIT:
Yes, it works !!! Now I feel powerfull
Tested on a amplifier (FX-Audio D802), soon with a projector (Benq W500) but I'm confident as it send 32 bits NEC code too.

Martinus wrote:R124 is available on github. We've done some code optimization to controllers for ThingSpeak, OpenHAB, PiDome and Generic HTTP.
A new controller for generic UDP has been added.
The dummy device can now send all 4 values on some generic controllers.

The IR TX plugin from the playground has been added to the main repository as P035, (contributed by cherowley). Because we also have IR receive for some time, it only makes sense to be able to send as well. I couldn't test this in my testlab so maybe someone else can do this? If you have used P106 from the playground, remove if from your project folder as it's no longer needed. You need to setup IR TX again because the plugin has been renumbered.

This is perfect timing for me as I was looking for a way to send IR. Please forgive me as I am a newbie, but will a binary for R124 be posted? I have never built a binary file to flash but certainly could try. Is there a guide available on doing this?

Yes see the wiki, also read the recent thread on compiling advice. I don't know if the tutorial is up to date. There are also a lot of threads on various problems related to compiling, but it generally works very well. Subscribe to this thread and look for changes to the requirements, they are also usually in the change log on Github (link on main page of wiki).

Enjoy!

I found out after the merge of my code that it may be necessary to re-save the device setting for BME280 after upgrade to R129. The setting for the address will be probably pre-set to address 0 otherwise. I wonder if there is a way how to auto-upgrade the values in such case (the alternative is to always use the option 0 for default value if we can ensure that all values in TaskDevicePluginConfig are pre-set to 0)?

zycker wrote:

Martinus wrote:R124 is available on github. We've done some code optimization to controllers for ThingSpeak, OpenHAB, PiDome and Generic HTTP.
A new controller for generic UDP has been added.
The dummy device can now send all 4 values on some generic controllers.

The IR TX plugin from the playground has been added to the main repository as P035, (contributed by cherowley). Because we also have IR receive for some time, it only makes sense to be able to send as well. I couldn't test this in my testlab so maybe someone else can do this? If you have used P106 from the playground, remove if from your project folder as it's no longer needed. You need to setup IR TX again because the plugin has been renumbered.

Hi, I was waiting for this IR TX plugin for a long time, I've all the hardware needed to test it but can you just explain me how to use the plugin ?

Ok, find this on the forum :

ThinkPad wrote:I got the _P106_IRTX.ino plugin working! It works really good!

How to do it:
- Download ESPEasy source (from .zip or from GitHub)
- Download the plugin and place it in the same folder as 'ESPEasy.ino' and the other *.ino files
- Download the IRremoteESP8266.h and also put in same folder as above
- Compile & upload to your device (i used a Wemos D1 Mini board)
- Then under 'Devices' in ESPEasy, select 'Infrared Transmit' and choose the GPIO pin that you have the IR Transmitter connected to. For Wemos D1 Mini i connected the transmitter to pin 'D1', which is GPIO5 in ESPEasy.

You should then be able to send commands by calling the ESP url like this: http://192.168.4.138/control?cmd=IRSEND,NEC,4bb620df,32 (this command turns my Onkyo 5.1 receiver on)

Finding out the codes (and protocol and bits) that your remote uses is quite easy. I used a separate Arduino Nano which i loaded a sample sketch of 'IRrecvDumpV2' on.
As a transmitter i use two IR leds, a 2N2222 transistor and a 470 Ohm resistor. The transistor is driven from the GPIO and gives the IR leds 5V, to create a powerful transmitter. The ready to use IR transmitter boards from China are very weak, because they draw their power from the GPIO.

To have a sort of remote, i created this webpage on my webserver:

Code: Select all

<!DOCTYPE html>
<html>
<head>
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
</head>
<body>

<h1>ESP8266 IR Remote</h1>
<h2>Versterker</h2>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb620df,32')">Power on</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4b36e21d,32')">Power off</button><br><br>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb6d02f,32')">Input tuner</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb6f00f,32')">Input VIDEO1 (Laptop)</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb6906f,32')">Input CD (PC Coaxial)</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb6708f,32')">Input VIDEO2 (TV)</button><br><br>

<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb600ff,32')">Channel up</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb6807f,32')">Channel down</button><br><br>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb641be,32')">(Search) Up</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb6c13e,32')">(Search) Down</button><br><br>

<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb640bf,32')">Volume +</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb6c03f,32')">Volume -</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb6a05f,32')">Volume mute</button><br><br><br>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4bb632cd,32')">Listening mode up</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,NEC,4b36a25d,32')">Listening mode down</button>
<hr>
<h2>TV</h2>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,SAMSUNG,E0E09966,32')">Power on</button>
<button type="button" onclick="loadDoc('http://192.168.4.138/control?cmd=IRSEND,SAMSUNG,E0E019E6,32')">Power off</button><br><br>
Response: <b><p id="output"></p></b>

<script>
function loadDoc(url) {
  var xhttp = new XMLHttpRequest();
  xhttp.onreadystatechange = function() {
    if (xhttp.readyState == 4 && xhttp.status == 200) {
      document.getElementById("output").innerHTML = xhttp.responseText;
    }
  };
  xhttp.open("GET", url, true);
  xhttp.send();
}
</script>

</body>
</html>

But i am planning on using it with my home automation, 'Home Assistant'.

Let's try it !

EDIT:
Yes, it works !!! Now I feel powerfull
Tested on a amplifier (FX-Audio D802), soon with a projector (Benq W500) but I'm confident as it send 32 bits NEC code too.

I've followed all these steps but I am not getting any output. I swapped the IR for a colored LED to see if I could make it come on with the command like above, but it will no work. I have the LED tied directly to GPIO-2 on an ESP-01 with the negative lead going to ground. Is this incorrect?

Pulling GPIO2 low with a LED is wrong, you should try to connect the led (with a current limiting resistor ! ) between Vcc and GPIO2. Or better do not use GPIO2 at all and use f.i. GPIO4
When GPIO2 is pulled low during start-up the ESP8266 will not boot-up with ESPEasy but in another sort of mode.

costo wrote:Pulling GPIO2 low with a LED is wrong, you should try to connect the led (with a current limiting resistor ! ) between Vcc and GPIO2. Or better do not use GPIO2 at all and use f.i. GPIO4
When GPIO2 is pulled low during start-up the ESP8266 will not boot-up with ESPEasy but in another sort of mode.

Forgive me as I'm a novice working with these chips. I am using an ESP-01. That device uses GPIO1 tied to ground to go into programming mode. I've specifically used GPIO2 to avoid this problem. The chip boots just fine and I am getting readings on my DHT22 that is using GPIO1 so I know that the chip is working.

My big question is how to wire the LED. Is GPIO2 sending a high every time it needs to blink the LED or is it sinking low? I have added a 1K resistor from GPIO2 to the LED and then the LED is tied to ground. Is this backwards? Should I be supplying 3.3V to the LED then have the 1K resistor tying the LED to GPIO2?

Discussions getting really off-topic here...
Maybe better to launch some new topics elsewhere and get back to discussion on new ESP Easy releases only...

So, on the Github I see all kind of releases only for sketches like R121, R124, R127, R131, etc.., but not for compiled binary...

When will be some new fully compiled firmware released?

Thank you!

You can compile the latest version if you like, it is pretty easy. Instructions are in the wiki and here: http://www.esp8266.nu/forum/viewtopic.php?f=4&t=1930

Here we go...about compiling and uploading the Firmware from the Github...

1. Built a new little dedicated PC for it
2. Installed Windows XP SP3,
3. Installed arduino-1.6.5-windows.exe,
4. Downloaded all Libraries from the Github (ArduinoJson, IRremoteESP8266, LiquidCrystal_I2C and pubsubclient-2.6) and extracted all to the libraries folder without "-master",
5. Added http://arduino.esp8266.com/stable/packa ... index.json to Aditional Boards Manager in Arduino IDE,
6. All compiled fine, without error,
7. Uploaded the binary with esptool successfully,
8. All went flawlessly,...(using ESP-01, BME280, BH1750 and OLED SSD1306) , but...

I'm NOT getting any readings anymore from the BME280 sensor (but the i2c scanner founding it)!

The BH1750 and the OLED SSD1306 Display is working like it should!

But, if I upload the R120 firmware version then all working just fine like before.

Some ideas?!

Thank you!

costo wrote: I wonder if there are other NTP related command like f.i. %sysdate% ?

Yeah, %sysdate% would be really awesome too!

beic wrote:Here we go...about compiling and uploading the Firmware from the Github...

1. Built a new little dedicated PC for it


I'm NOT getting any readings anymore from the BME280 sensor (but the i2c scanner founding it)!

Some ideas?!

Thank you!

Check the I2C address, there are 2 possibilities in the plugin. I just tested my adafruit BME280 and it works fine on 131.

Drum wrote: Check the I2C address, there are 2 possibilities in the plugin. I just tested my adafruit BME280 and it works fine on 131.

I will recheck it again...need to wait for more ESP-01 to arrive...!

R135 on github adds names and build numbers to the nodelist. More convenient when the number of units in your house starts to grow...

Nice, Martinus. Very helpfull.

A couple of thoughts
1. It wwould be good if each device could send a heartbeat message via mqtt. Ie every set period (say 12hrs) it sent a heartbeat message iindicating it was still alive. The device ccould have been a door input that hasn't opened for a week.
2. OH2 now has some auto device discovery and configuration. Perhaps the heartbeat could contain the auto discovery information as well or respond to a discovery poll.
3. It would be good if the device name and ip ccould also be obtained through mqtt.

Neil

Hello all

Any special reason why the R136 reports itself as R135?

Downloaded and compiled the R136, works nicely for me - just it shows as 135 at the main page and over the serial console when booting.

Shardan wrote:Hello all

Any special reason why the R136 reports itself as R135?

Downloaded and compiled the R136, works nicely for me - just it shows as 135 at the main page and over the serial console when booting.

Asking the same! "Resync", what is that mean?!?

Not sure if its my setup but on R137
within config tab the admin password seems to over right the wpa key?
A feature of the chrome browser

Today, I took my 1st Wemos d1 mini (ESPeasy, SI7021 + OLED 1306) in use. I connected the set with Domoticz, so far everything ok.

I'd also like the current time on the display. I did > press edit Display - OLED SSD1306 > filled line 8 > Tijd:%systime% > display shows Tijd: 0:00.

What's wrong?

Jan Jansen wrote:Today, I took my 1st Wemos d1 mini (ESPeasy, SI7021 + OLED 1306) in use. I connected the set with Domoticz, so far everything ok.

I'd also like the current time on the display. I did > press edit Display - OLED SSD1306 > filled line 8 > Tijd:%systime% > display shows Tijd: 0:00.

What's wrong?

You maybe need to enable and configure the NTP support!

Kind regards,
Viktor

Thanks Viktor, it works as desired!

Jan

Jan Jansen wrote:Thanks Viktor, it works as desired!

Jan

Anytime!

Hi
Anybody has FW in version Release v2.0.0-dev6 as file bin ?
Please upload becuase i can not build and upload to my NodeMCU.

Hello piokuc,

the binaries are included in the zip-file on github:

https://github.com/letscontrolit/ESPEasy/releases

Scroll down a bit and you will see the ESPEasy_v2.2.2_dev6.zip.

Unpack it, binaries are inside the zip.

Regards
Shardan

Very thanks. But can you write me stepo by step how i can build own bin ? I try and i have and error which i describe in this topic:
https://www.letscontrolit.com/forum/vie ... 6&start=10

Hello again,

I've tried to compile the 2.0.0 with the Arduino IDE and failed, it does not work atm.

I've asked if there will be a howto about how to compile the new versions with the
Arduino IDE, answer was there will be:

https://www.letscontrolit.com/forum/vie ... 7&start=40

Post #47

I asked again if there is some progress with that and sadly did not get an answer yet.

There is another toolchain used for it - platformio. There is a howto for using it in the wiki

https://www.letscontrolit.com/wiki/inde ... Platformio

To be honest it is a mess to install.
If you get a question about "enable - later - disable" for code optimization - disable it.
I tried to install the code optimizer, it''s just running into issues all the time.
If for any reason it does not work and you have to re-install, do an uninstall first.
Then search c:\users\<your username> for the .atom - folder - delete it.
After that, go to the appdata folder, subfolders local and roaming, search
for atom and platformio folders and delete them too.
These programs definitely do not cleanly install and uninstall.

I got it running at last, but honestly it took hours.
A github account is not needed. You may use the downloaded zip instead
even the HowTo focuses on github.

I definitely wish the Arduino IDE back for working - it worked for me for long time now.

Regards
Shardan

Sorry the Arduino IDE took so long, didnt had time to fix it earlier.

I just updated the Arduino IDE tutorial and release a new version with some needed fixed (v2.0.0-dev7)

Tutorial is still in the same place, but with changes/aditions: https://www.letscontrolit.com/wiki/inde ... are_Upload

I hope that helps and clears things up.

Edwin

I'll update the wiki to state that code linter should be disabled for now.