Re: uPyEasy
Posted: 21 Oct 2017, 19:51
+10!grovkillen wrote: ↑21 Oct 2017, 13:15 Lisa will release this when it is mature enough. She only use this thread to show current status and get feedback.
+10!grovkillen wrote: ↑21 Oct 2017, 13:15 Lisa will release this when it is mature enough. She only use this thread to show current status and get feedback.
uPyEasy uses the micropython hardware API: https://github.com/micropython/micropyt ... rdware-APIBertB wrote: ↑21 Oct 2017, 12:27 This is a realy great development.
But, I wonder how Easy it will be in the end to setup and use.
I also wonder how 'high speed' or 'real time' modules are handled.
And how portable modules will be across the various platforms. Will it be possible to develop a DS1820 module that can be uses on all platforms and if no, how does one cope with the differences.
How 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?
Code: Select all
On TurnOn do
gpio,12,1
EndOn
Code: Select all
if TurnOn:
gpio (12,1)
endif
The rules will still be there, the limitations are gone. The number of features will be almost limitless, only the limits imposed by micropython will apply.
I'm working towards the first test version, a couple of weeks left. Like i've said before, it will only contain the UI parts and is mainly for others to test to see if the program holds up in other environments then my testbeds. The first two platforms will be for pyboard+w5500 and the esp32. The nodemcu will require more testing because of the very tight free heap size, the free flash and stack size won't be a problem. If the free heap size is getting to small, i'll need to do some optimization first.
Better? That's a subjective opinion, here's an objective comparison:
It's an app build on Armbian, it might work on other linux versions or not. The reason to choose for Armbian is interrupts from the OS, the OS needs to be very light and small so it doesn't interrupt uPyEasy operation to much. To many interrupt means less reliable operation of uPyEasy since it might miss sensor values due to the interrupt. Also the dxpin library is a concern, for Armbian there is an pin library available for micropython. Other ports might not have that.budman1758 wrote: ↑16 Nov 2017, 07:13 Is uPyEasy running as an app on your Armbian boards or is it the complete OS?
No and yes. I run have raspbian on rpi's, but let's see if I can get it running ArmbianLisaM wrote: ↑15 Nov 2017, 15:59 Doesn't matter, because i don't care if it's a Raspberry or Orange. uPyEasy is running on Armbian and if the Raspberry is running Armbian, it's going to run there also (probably since it can't test it).
Are you running Raspberry Pi Zero - Armbian? If so, are you willing to test it?
Cheers,
Lisa
I love that you are thinking ahead while we're working on the current code base. Good work this far!LisaM wrote: ↑08 Dec 2017, 19:34 Finally i have created a working uPyEasy version that has working protocols (domoticz http/mqtt) and plugins (bme280, dht11/22, switch). The plugins pass fake values, not real ones. The reason for that, while the sensor code is already in place, is that i need to add sensors to my test platforms to be able to test the sensors and i want the values always to be the same for debugging purposes. So, while everything is functional it's not sending real values but fake values to domoticz.
Only the PyBoard firmware in the google drive section is updated! The ESP32 has run into a bug which i'm working on with the micropython developers.
The Orange PI/Raspberry PI version is next and i will post a message here if it's ready.
>>> import upyeasyCHK_BLN wrote: ↑10 Dec 2017, 23:44 Hi Lisa
with the new firmware for the ESP32, the WIFI configuration does not work anymore.
The following error message comes.
>>> upyeasy.setwifi('SSID', 'PASSSWORD','BACKUPSSID', 'BACKUPPW')
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
NameError: name 'upyeasy' is not defined
greeting
Probably are the tables not created yet can you try (after reboot):CHK_BLN wrote: ↑11 Dec 2017, 21:50 Hi Lisa
I tried your trick.
But unfortunately without success
Here is the result:
>>> import upyeasy
? [0; 32mI (99442) modsocket: Initializing? [0m
>>> upyeasy.setwifi ('SSID', 'PASSSWORD', 'BACKUPSSID', 'BACKUPPW')
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "upyeasy / __ init__.py", line 28, in setwifi
File "upyeasy / utils.py", line 60, in setwifi
NameError: local variable referenced before assignment
Best regards