uPyEasy
Moderators: Voyager, BertB, grovkillen, Stuntteam, LisaM
Re: uPyEasy
Hi again Lisa,
Some progress now although not yet there ....
Discovered that my microUSB connector was not secure in the ESP32, it now looks like this was the main cause of my recent problems, so please ignore my post earlier this evening.
Repeated the whole process from the start with a better usb connection.
This time, no errors from upyeasy.main(). Went on to configure wifi settings.
Rebooted, and repeated import upyeasy, upyeasy.main() as per latest advice.
ESP32 started and showed a connection to my wifi (briefly) .... but then crashed out with OSerror 128.
This is the log (although I'm sure that some lines have now disappeared, including the wifi connection!?)
2000-01-01T00:00:56.005 [debug] uPyEasy: Protocol: domoticz http contruction
2000-01-01T00:00:56.005 [debug] uPyEasy: Protocols: Create protocol Record: domoticz_http
2000-01-01T00:00:57.005 [debug] uPyEasy: Plugins: Load
2000-01-01T00:00:57.005 [debug] uPyEasy: Plugins: Delete plugin records
2000-01-01T00:00:57.005 [debug] uPyEasy: Plugins: Load frozen plugin gpio
2000-01-01T00:00:57.005 [debug] uPyEasy: Plugin: gpio contruction
2000-01-01T00:00:57.005 [debug] uPyEasy: Plugins: Create frozen plugin Record: gpio
I (58379) wifi: pm start, type:0
2000-01-01T00:00:57.005 [debug] uPyEasy: Plugins: Load frozen plugin dht
2000-01-01T00:00:57.005 [debug] uPyEasy: Plugin: dht contruction
2000-01-01T00:00:57.005 [debug] uPyEasy: Plugins: Create frozen plugin Record: dht
2000-01-01T00:00:58.005 [debug] uPyEasy: Plugins: Load frozen plugin bme
2000-01-01T00:00:58.005 [debug] uPyEasy: Plugin: bme280 contruction
2000-01-01T00:00:58.005 [debug] uPyEasy: Plugins: Create frozen plugin Record: bme
2000-01-01T00:00:58.005 [debug] uPyEasy: Utils: Sys hostname
2000-01-01T00:00:58.005 [debug] uPyEasy: Utils: uPyEasy Name
Set syslog hostname 0.0.0.0
reloaded sink syslog
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: Entering SetTime
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: Entering GetNtpTime
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: network Table
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: Using NTP Hostname: pool.ntp.org
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: TimeZome offset: 60
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: Received UTC NTP Time: 566430409
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: Timezone corrected NTP Time: 566434009
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: DST corrected NTP Time: 566434009
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: Received NTP Time: 566434009
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: StartTime: 566434009
2017-12-12T22:46:49.001 [debug] uPyEasy-uPyEasy: Main: Pre-loading home page
2017-12-12T22:46:49.001 [debug] uPyEasy-uPyEasy: Main: get_ip_address AttributeError
2017-12-12T22:46:49.001 [debug] uPyEasy-uPyEasy: Main: uPyEasy Main Async Loop
* Running on http://0.0.0.0:80/
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "upyeasy/__init__.py", line 56, in main
File "picoweb/__init__.py", line 240, in run
File "uasyncio/core.py", line 124, in run_forever
File "uasyncio/core.py", line 88, in run_forever
File "uasyncio/__init__.py", line 229, in start_server
OSError: 128
>>>
Getting closer now! Hope this helps.
AndrewJ
Some progress now although not yet there ....
Discovered that my microUSB connector was not secure in the ESP32, it now looks like this was the main cause of my recent problems, so please ignore my post earlier this evening.
Repeated the whole process from the start with a better usb connection.
This time, no errors from upyeasy.main(). Went on to configure wifi settings.
Rebooted, and repeated import upyeasy, upyeasy.main() as per latest advice.
ESP32 started and showed a connection to my wifi (briefly) .... but then crashed out with OSerror 128.
This is the log (although I'm sure that some lines have now disappeared, including the wifi connection!?)
2000-01-01T00:00:56.005 [debug] uPyEasy: Protocol: domoticz http contruction
2000-01-01T00:00:56.005 [debug] uPyEasy: Protocols: Create protocol Record: domoticz_http
2000-01-01T00:00:57.005 [debug] uPyEasy: Plugins: Load
2000-01-01T00:00:57.005 [debug] uPyEasy: Plugins: Delete plugin records
2000-01-01T00:00:57.005 [debug] uPyEasy: Plugins: Load frozen plugin gpio
2000-01-01T00:00:57.005 [debug] uPyEasy: Plugin: gpio contruction
2000-01-01T00:00:57.005 [debug] uPyEasy: Plugins: Create frozen plugin Record: gpio
I (58379) wifi: pm start, type:0
2000-01-01T00:00:57.005 [debug] uPyEasy: Plugins: Load frozen plugin dht
2000-01-01T00:00:57.005 [debug] uPyEasy: Plugin: dht contruction
2000-01-01T00:00:57.005 [debug] uPyEasy: Plugins: Create frozen plugin Record: dht
2000-01-01T00:00:58.005 [debug] uPyEasy: Plugins: Load frozen plugin bme
2000-01-01T00:00:58.005 [debug] uPyEasy: Plugin: bme280 contruction
2000-01-01T00:00:58.005 [debug] uPyEasy: Plugins: Create frozen plugin Record: bme
2000-01-01T00:00:58.005 [debug] uPyEasy: Utils: Sys hostname
2000-01-01T00:00:58.005 [debug] uPyEasy: Utils: uPyEasy Name
Set syslog hostname 0.0.0.0
reloaded sink syslog
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: Entering SetTime
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: Entering GetNtpTime
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: network Table
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: Using NTP Hostname: pool.ntp.org
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: TimeZome offset: 60
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: Received UTC NTP Time: 566430409
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: Timezone corrected NTP Time: 566434009
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: DST corrected NTP Time: 566434009
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: Received NTP Time: 566434009
2000-01-01T00:00:58.005 [debug] uPyEasy-uPyEasy: Hal: StartTime: 566434009
2017-12-12T22:46:49.001 [debug] uPyEasy-uPyEasy: Main: Pre-loading home page
2017-12-12T22:46:49.001 [debug] uPyEasy-uPyEasy: Main: get_ip_address AttributeError
2017-12-12T22:46:49.001 [debug] uPyEasy-uPyEasy: Main: uPyEasy Main Async Loop
* Running on http://0.0.0.0:80/
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "upyeasy/__init__.py", line 56, in main
File "picoweb/__init__.py", line 240, in run
File "uasyncio/core.py", line 124, in run_forever
File "uasyncio/core.py", line 88, in run_forever
File "uasyncio/__init__.py", line 229, in start_server
OSError: 128
>>>
Getting closer now! Hope this helps.
AndrewJ
Re: uPyEasy
OSError is an indication that port 80 is still locked, while upyeasy tries to open port 80. A hard reset (power down, wait 10s, power on) is required.
Then same two steps: import upyeasy, upyeasy.main()
Cheers,
Lisa
Then same two steps: import upyeasy, upyeasy.main()
Cheers,
Lisa
Re: uPyEasy
Hi Lisa,
Thanks for the reply. I just tried again unplugging the ESP32, with a long period (several minutes) before restarting, but sadly it's still not working.
After all the [debug] messages I see it running, for about 5 secs, then it throws an error...
* Running on http://0.0.0.0:80/
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "upyeasy/__init__.py", line 56, in main
File "picoweb/__init__.py", line 240, in run
File "uasyncio/core.py", line 124, in run_forever
File "uasyncio/core.py", line 88, in run_forever
File "uasyncio/__init__.py", line 229, in start_server
OSError: 128
>>>
Any ideas?
Cheers
Andrew
Thanks for the reply. I just tried again unplugging the ESP32, with a long period (several minutes) before restarting, but sadly it's still not working.
After all the [debug] messages I see it running, for about 5 secs, then it throws an error...
* Running on http://0.0.0.0:80/
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "upyeasy/__init__.py", line 56, in main
File "picoweb/__init__.py", line 240, in run
File "uasyncio/core.py", line 124, in run_forever
File "uasyncio/core.py", line 88, in run_forever
File "uasyncio/__init__.py", line 229, in start_server
OSError: 128
>>>
Any ideas?
Cheers
Andrew
Re: uPyEasy
I've been googling the error messages I saw. Nothing much for File "upyeasy/__init__.py, but I did find something which sounds similar for File picoweb/__init__.py -- see this link, hope it may help ...
https://forum.micropython.org/viewtopic.php?t=3651
https://forum.micropython.org/viewtopic.php?t=3651
Re: uPyEasy
OSError 128 points to a occupied port 80 by a previous program. A hard reset (power down-wait 10s-power up) should do the trick. Then import upyeasy, upyeasy.main() should work.
Re: uPyEasy
Hi Lisa,
You may have missed it in my earlier post, but i had already tried the procedure you suggested. Anyway, I've just had another go, and in fact for good measure I went right back to the beginning, erased the ESP32 and reflashed it, the done the extra commands in the REPL. At each step where a reboot is needed, I was careful to unplug it and wait at least 10 secs.
However, I'm sorry to say that the result is still the same... it starts to run ("Running on http://0.0.0.0:80/") but then after about 5 secs it falls over with OSError 128.
I'm at a loss now, hope you may be able to suggest something please?
Cheers
AndrewJ
You may have missed it in my earlier post, but i had already tried the procedure you suggested. Anyway, I've just had another go, and in fact for good measure I went right back to the beginning, erased the ESP32 and reflashed it, the done the extra commands in the REPL. At each step where a reboot is needed, I was careful to unplug it and wait at least 10 secs.
However, I'm sorry to say that the result is still the same... it starts to run ("Running on http://0.0.0.0:80/") but then after about 5 secs it falls over with OSError 128.
I'm at a loss now, hope you may be able to suggest something please?
Cheers
AndrewJ
Re: uPyEasy
In the Google drive uPyEasy section is a new version of uPyEasy for ESP32, it has these new features:
- Autostart after flash
- Autoconnect to the strongest open wifi AP after a fresh install
- 2 working controllers (domoticz http/mqtt)
- 2 working plugins (switch/ds18b20)
- Ability to disable GPIO pins in the hardware section which are not present or being used by the board itself (every board is different)
- Tools/Wifi Scan is operational
Since it has a lot of new features, please erase your ESP32 before flashing the new firmware version (so the database is rebuild):
esptool.py --port /dev/ttyUSBx erase_flash
(x for your USB port).
The DS18B20 plugin must be save first, before you can select the romid. I'm working on that to get that fixed.
Autoconnect to the strongest open wifi AP after a fresh install? Beware that this might be your guest network which is isolated from your normal network, you'll need to forward a port on your public ip-address to port 80 of your ESP32.
@AndrewJ, can you try this version if the OSError 128 is also popping up? If it does, i'll compile a special version for you.
This will be the LAST alpha version, the next version will be the first BETA version. The beta version is stable enough for everyone to download, initially it will be binary only. When the code is stable enough, it will become a github repository.
Attached is the protocol and plugin source code. Beware that they might be changed in the next releases.
- Autostart after flash
- Autoconnect to the strongest open wifi AP after a fresh install
- 2 working controllers (domoticz http/mqtt)
- 2 working plugins (switch/ds18b20)
- Ability to disable GPIO pins in the hardware section which are not present or being used by the board itself (every board is different)
- Tools/Wifi Scan is operational
Since it has a lot of new features, please erase your ESP32 before flashing the new firmware version (so the database is rebuild):
esptool.py --port /dev/ttyUSBx erase_flash
(x for your USB port).
The DS18B20 plugin must be save first, before you can select the romid. I'm working on that to get that fixed.
Autoconnect to the strongest open wifi AP after a fresh install? Beware that this might be your guest network which is isolated from your normal network, you'll need to forward a port on your public ip-address to port 80 of your ESP32.
@AndrewJ, can you try this version if the OSError 128 is also popping up? If it does, i'll compile a special version for you.
This will be the LAST alpha version, the next version will be the first BETA version. The beta version is stable enough for everyone to download, initially it will be binary only. When the code is stable enough, it will become a github repository.
Attached is the protocol and plugin source code. Beware that they might be changed in the next releases.
- Attachments
-
- protocols_plugins.zip
- (7.33 KiB) Downloaded 813 times
- grovkillen
- Core team member
- Posts: 3621
- Joined: 19 Jan 2017, 12:56
- Location: Hudiksvall, Sweden
- Contact:
Re: uPyEasy
Great news Lisa!
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
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you
Re: uPyEasy
Hmm, that sounds great and quite quick development as you're already approaching beta status.
I will try it myself also during the holidays. The ESP32's are already "in stock"
I will try it myself also during the holidays. The ESP32's are already "in stock"
Re: uPyEasy
Thanks, Lisa. Excellent work!
I'll give the new version a try on my Doit board and I'll let you know about oserror 128.
Since the previous alpha I've received a Wemos Lolin Lite ESP32. I'll try that as well.
Cheers
AndrewJ
I'll give the new version a try on my Doit board and I'll let you know about oserror 128.
Since the previous alpha I've received a Wemos Lolin Lite ESP32. I'll try that as well.
Cheers
AndrewJ
Re: uPyEasy
Just tried the latest version from Google Drive on my DOIT Devboard V1. I temporarily removed security on my wireless network to allow it to connect.
Unfortunately still getting errors a few seconds after restart. This is from the log after the long series of startup messages....
* Running on http://0.0.0.0:80/
2000-01-01T00:00:09.005 [debug] uPyEasy-uPyEasy: Protocols: Async processing protocols
2000-01-01T00:00:09.005 [debug] uPyEasy-uPyEasy: Plugins: Async processing plugins
Traceback (most recent call last):
File "boot.py", line 2, in <module>
File "upyeasy/__init__.py", line 57, in main
File "picoweb/__init__.py", line 240, in run
File "uasyncio/core.py", line 127, in run_forever
File "uasyncio/core.py", line 88, in run_forever
File "uasyncio/__init__.py", line 241, in start_server
OSError: 128
OSError: [Errno 2] ENOENT
MicroPython v1.9.3-181-g02d2a0f-dirty on 2017-12-19; ESP32 module with ESP32
Type "help()" for more information.
Actually two OSErrors this time!
Hope the above info helps.
As with the earlier version, I see the ESP32 with an IP address in my router, so its "nearly" working.
BTW I have noticed that it says "* Running on http://0.0.0.0:80/" - this IP address puzzles me a bit (probably an ignorant question).
If you have time to make a special firmware version to get round this, I'd be most grateful.
I haven't checked it on my Wemos LOLIN LITE yet. I'll try to do that later this evening.
Cheers,
AndrewJ
Unfortunately still getting errors a few seconds after restart. This is from the log after the long series of startup messages....
* Running on http://0.0.0.0:80/
2000-01-01T00:00:09.005 [debug] uPyEasy-uPyEasy: Protocols: Async processing protocols
2000-01-01T00:00:09.005 [debug] uPyEasy-uPyEasy: Plugins: Async processing plugins
Traceback (most recent call last):
File "boot.py", line 2, in <module>
File "upyeasy/__init__.py", line 57, in main
File "picoweb/__init__.py", line 240, in run
File "uasyncio/core.py", line 127, in run_forever
File "uasyncio/core.py", line 88, in run_forever
File "uasyncio/__init__.py", line 241, in start_server
OSError: 128
OSError: [Errno 2] ENOENT
MicroPython v1.9.3-181-g02d2a0f-dirty on 2017-12-19; ESP32 module with ESP32
Type "help()" for more information.
Actually two OSErrors this time!
Hope the above info helps.
As with the earlier version, I see the ESP32 with an IP address in my router, so its "nearly" working.
BTW I have noticed that it says "* Running on http://0.0.0.0:80/" - this IP address puzzles me a bit (probably an ignorant question).
If you have time to make a special firmware version to get round this, I'd be most grateful.
I haven't checked it on my Wemos LOLIN LITE yet. I'll try to do that later this evening.
Cheers,
AndrewJ
Re: uPyEasy
I'm waiting for the ordered Lolin32 Pro, it has the ESP32-WROVER module with 4MB PsRam, Bluetooth and SD card.
I'm working on including bluetooth, SD card and thread based support functionality in uPyEasy. I'll have everything running on one core and all plugins on another, performance should be awesome then. For latency the pyboard will be much better, for functionality the ESP32. With 4MB PsRam stack and heap space are no longer an issue and lots of new functionality will be possible. All of this is costing $9!
Many sensor already have python drivers, so make them should be simple. I've tried to make the plugin and protocol coding as simple and reliable as possible, it should be very easy to convert existing plugin/protocol code to uPyEasy.
Scripting is also something i'm working on, plan is to have the first scripting possible at the first beta.
I'm also working on the python driver for grovkillen's senseair co2 measuring device, i'll need that for a prototype hardware device i'm developing for the business markets.
Besides all of this, i also have a very busy job as (the only) Data Architect for the largest insurance corporation here.. Sometimes it's hard to balance all of this, so please have some patience if development progress is slow at some weeks..
Re: uPyEasy
Just gave it a try on the Wemos LOLIN LITE.
Unfortunately, I get the same two errors, 128 then 2/ENOENT
Unfortunately, I get the same two errors, 128 then 2/ENOENT
Re: uPyEasy
Line 214 is:AndrewJ wrote: ↑20 Dec 2017, 20:56 Just tried the latest version from Google Drive on my DOIT Devboard V1. I temporarily removed security on my wireless network to allow it to connect.
Unfortunately still getting errors a few seconds after restart. This is from the log after the long series of startup messages....
* Running on http://0.0.0.0:80/
2000-01-01T00:00:09.005 [debug] uPyEasy-uPyEasy: Protocols: Async processing protocols
2000-01-01T00:00:09.005 [debug] uPyEasy-uPyEasy: Plugins: Async processing plugins
Traceback (most recent call last):
File "boot.py", line 2, in <module>
File "upyeasy/__init__.py", line 57, in main
File "picoweb/__init__.py", line 240, in run
File "uasyncio/core.py", line 127, in run_forever
File "uasyncio/core.py", line 88, in run_forever
File "uasyncio/__init__.py", line 241, in start_server
OSError: 128
OSError: [Errno 2] ENOENT
MicroPython v1.9.3-181-g02d2a0f-dirty on 2017-12-19; ESP32 module with ESP32
Type "help()" for more information.
Actually two OSErrors this time!
Hope the above info helps.
As with the earlier version, I see the ESP32 with an IP address in my router, so its "nearly" working.
BTW I have noticed that it says "* Running on http://0.0.0.0:80/" - this IP address puzzles me a bit (probably an ignorant question).
If you have time to make a special firmware version to get round this, I'd be most grateful.
I haven't checked it on my Wemos LOLIN LITE yet. I'll try to do that later this evening.
Cheers,
AndrewJ
Code: Select all
s2, client_addr = s.accept()
Can you send the entire log?
Re: uPyEasy
New version on google drive, can you load that one in the ESP32?
After the error do:
>>> Import uos
>>> uos.remove('boot.py')
Then power cycle.
After reboot, on repl prompt:
>>> import wstest
And let me know what happens...
Ps wstest.py is just this test program:
Code: Select all
import socket
from machine import Pin
#led_pin = Pin(5, Pin.OUT)
CONTENT = """\
HTTP/1.0 200 OK
Content-Type: text/html
<html>
<head>
</head>
<body>
<p>Hello #%d from MicroPython!</p>
<a href="/toggle">Click here to toggle LED hooked to pin 5</a>
</body>
</html>
"""
def main():
s = socket.socket()
ai = socket.getaddrinfo("0.0.0.0", 80)
print("Bind address info:", ai)
addr = ai[0][-1]
s.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
s.bind(addr)
s.listen(5)
print("Listening, connect your browser to http://<this_host>:80/")
counter = 0
while True:
sock, addr = s.accept()
print("Client address:", addr)
stream = sock.makefile("rwb")
req = stream.readline().decode("ascii")
method, path, protocol = req.split(" ")
print("Got", method, "request for", path)
if path == "/toggle":
led_pin.value(1-led_pin.value())
while True:
h = stream.readline().decode("ascii").strip()
if h == "":
break
print("Got HTTP header:", h)
stream.write((CONTENT % counter).encode("ascii"))
stream.close()
sock.close()
counter += 1
print()
main() # Press Ctrl-C to stop web server
Re: uPyEasy
Hi Lisa,
Ok, I followed the steps
I (26302) modsocket: Initializing
Bind address info: [(2, 1, 0, '0.0.0.0', ('0.0.0.0', 80))]
Listening, connect your browser to http://<this_host>:80/
Not sure what to make of this...
In my router, I'm not seeing the ESP32 now. (even with wireless security disabled again).
Think I'm missing something but not sure what.
Ok, I followed the steps
and I got
I (26302) modsocket: Initializing
Bind address info: [(2, 1, 0, '0.0.0.0', ('0.0.0.0', 80))]
Listening, connect your browser to http://<this_host>:80/
Not sure what to make of this...
In my router, I'm not seeing the ESP32 now. (even with wireless security disabled again).
Think I'm missing something but not sure what.
Re: uPyEasy
Hi Andrew,
Very interesting, because the test program is doing exactly the same as uPyEasy:
wstest:
uPyEasy (actually uasyncio):
So, something is different because of the uasyncio error at line 241. I'll read some docs to find out what the difference is.
Can you get me a complete log?
Very interesting, because the test program is doing exactly the same as uPyEasy:
wstest:
Code: Select all
sock, addr = s.accept()
Code: Select all
s2, client_addr = s.accept()
Can you get me a complete log?
Re: uPyEasy
Having trouble attaching file here. It keeps saying invalid extension. I'll email it to you.Can you get me a complete log?
AndrewJ
Re: uPyEasy
This is my ESP32 testmachine: https://nl.aliexpress.com/item/Official ... 21054.htmlAndrewJ wrote: ↑20 Dec 2017, 23:03 Hi Lisa,
Ok, I followed the stepsand I got
I (26302) modsocket: Initializing
Bind address info: [(2, 1, 0, '0.0.0.0', ('0.0.0.0', 80))]
Listening, connect your browser to http://<this_host>:80/
Not sure what to make of this...
In my router, I'm not seeing the ESP32 now. (even with wireless security disabled again).
Think I'm missing something but not sure what.
Isn't that the same as your ESP32?
Re: uPyEasy
Yes, it looks the same as mine. Yours could possibly be a different version of the ESP32 chip if it is recently purchased. Mine was bought about 6 months ago, also from Aliexpress.This is my ESP32 testmachine: https://nl.aliexpress.com/item/Official ... 21054.html
Isn't that the same as your ESP32?
The chip version shows when you do an erase or download to it, when it detects the chip type. Mine is ESP32DOWDQ6 (revision 0). I think I have read somewhere that there is a revision 1 about by now.
Have you already received your ESP32 or is it in transit?
Cheers
AndrewJ
Re: uPyEasy
I have these 3:AndrewJ wrote: ↑22 Dec 2017, 17:44Yes, it looks the same as mine. Yours could possibly be a different version of the ESP32 chip if it is recently purchased. Mine was bought about 6 months ago, also from Aliexpress.This is my ESP32 testmachine: https://nl.aliexpress.com/item/Official ... 21054.html
Isn't that the same as your ESP32?
The chip version shows when you do an erase or download to it, when it detects the chip type. Mine is ESP32DOWDQ6 (revision 0). I think I have read somewhere that there is a revision 1 about by now.
Have you already received your ESP32 or is it in transit?
Cheers
AndrewJ
https://www.aliexpress.com/item/Officia ... 21054.html -> Chip is ESP32D0WDQ6 (revision 1)
https://www.aliexpress.com/item/ESP32-B ... 25963.html
https://nl.aliexpress.com/item/LOLIN32- ... 82537.html
With the last one, the Lolin32, is on it's way to me. The Lolin32 has 4MB PsRam, so uPyEasy could then also run in ram instead of flash.
uPyEasy wil support all if not most ESP32 version, including ssd1306 en the ILI9341 touch tft screen.
What's the second ESP32 chip version you have?
One way or another, we will fix this...
Re: uPyEasy
It's a Wemos LOLIN LITE32 (v1.0.0) board (seems to be a cut-down LOLIN32 with less GPIOs exposed).What's the second ESP32 chip version you have?
https://www.aliexpress.com/item/WEMOS-L ... 0.0.DIgzf6
This apparently comes with Micropython loaded - but I didn't realise until -after- I'd erased and loaded upyeasy!
Chip is ESP32DOWDQ6 (revision 1).
Absolutely. I'll be glad to help any way I can. I can certainly do more testing when you are ready, and I'm keen to learn Micropython too, although I'm starting from ground zero.One way or another, we will fix this...
Best regards
AndrewJ
Re: uPyEasy
Python is King of the Hill: https://www.ibm.com/developerworks/comm ... ce?lang=en
Re: uPyEasy
The already installed ESP32 micropython version was probably an old one, they migrated the ESP32 micropython branch back into the master branch just a week ago and the master branch is the one we're using.
Since the chip is the same, the OSError 128 error shouldn't happen... Continuing search...
Re: uPyEasy
Topic moved to dedicated uPyEasy subforum
Re: uPyEasy
Yes, it's good to have a dedicated area of the forum for uPyEasy
Re: uPyEasy
hey guys,
many thanks for your great efforts bringing espeasy to the next Level!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
As I am not a pro on all that stuff I would appreciate having a FlashESPxxx tool as with ESP Mega in order to install upyeasy...
Maybe you did already and I am just too dumb to have it seen.
many thanks, great work!
karl
many thanks for your great efforts bringing espeasy to the next Level!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
As I am not a pro on all that stuff I would appreciate having a FlashESPxxx tool as with ESP Mega in order to install upyeasy...
Maybe you did already and I am just too dumb to have it seen.
many thanks, great work!
karl
Re: uPyEasy
Tool & instructions: viewtopic.php?f=22&t=3906karl222 wrote: ↑06 Jan 2018, 20:28 hey guys,
many thanks for your great efforts bringing espeasy to the next Level!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
As I am not a pro on all that stuff I would appreciate having a FlashESPxxx tool as with ESP Mega in order to install upyeasy...
Maybe you did already and I am just too dumb to have it seen.
many thanks, great work!
karl
Re: uPyEasy
when might there be support for MQTT for openhab?
Re: uPyEasy
Scripts have grown to become almost normal, but changeable, micropython programs. Despite it's great benefit, everything is now possible with scripts, it has a big downside: you'll need to program Python.LisaM wrote: ↑22 Oct 2017, 12:55How about an example script that resembles the old rules script as close as possible? It will basically act as a template for rule based scripting, simple but leaving the option open of making it complex. Will something like that help you?
For example this old rule part:will be turned into this:Code: Select all
On TurnOn do gpio,12,1 EndOn
Code: Select all
if TurnOn: gpio (12,1) endif
So... i've kept Scripts, but re-introduced rules.
Rule example:
Code: Select all
if event['test#temperature'] > 15 :
gpio('d12',1)
event['timer1'] = 60 # seconds
Code: Select all
if timer1:
gpio('d12',0)
Code: Select all
if turnon:
gpio('d12',1)
event['timer1'] = 60 # seconds
Is that still exceptable?
Re: uPyEasy
See the Rules: /forum/viewtopic.php?f=23&t=4732
Re: uPyEasy
uPyEasy beta-1 is also having the menu's Scripts, Rules and Notifications hidden by default to make the menu bar less complex. They can be enabled in the advanced menu:
Re: uPyEasy
Hi Lisa,
very nice work.
Is there an alpha version compatible with Wemos D1 Mini with ESP 8266 and/or D1 Mini Lite ESP 8285?
thanks
very nice work.
Is there an alpha version compatible with Wemos D1 Mini with ESP 8266 and/or D1 Mini Lite ESP 8285?
thanks
Re: uPyEasy
Hi LisaM,
I would also love to test it on a WeMOS D1 mini ...
I would also love to test it on a WeMOS D1 mini ...
Re: uPyEasy
any version for ESP8266 to try yet?
Re: uPyEasy
Lisa what ever happened to this? Will you be releasing an ESP8266 version? I think this firmware would be perfect for a project i have
Re: uPyEasy
Hi iiot,
The source code has grown to such a size that it's using to much heap memory to be able to use it on a ESP8266, so minimal requirements is still the ESP32.
Cheers,
Lisa
Who is online
Users browsing this forum: No registered users and 14 guests