Python program to run on eisy

[jjsmd]

How do i go about running a python program and storing the data in a variable and the having eisy use that data in an event?

[paulbates]

Do you have an eisy and a functioning python dev environment set up to work in? Here are some things to review to get started, assuming you answered "yes", twice, above:

There's an python API that defines communication with the eisy resources and formatting of data appropriately:

https://wiki.universal-devices.com/index.php?title=ISY_Developers:API:Python

[Javi]

You could also create your own nodes with python by creating a Python Node Server. See https://docs.isy.io/

[leonpc]

On 11/9/2023 at 11:51 AM, paulbates said:

Do you have an eisy and a functioning python dev environment set up to work in? Here are some things to review to get started, assuming you answered "yes", twice, above:

 

What happens if you only have the eisy?  How do i setup the Python dev environment on eisy.  Obviously I am missing it in the docs.

Thanks

[sjenkins]

If you read and reread the developer docs, my suggestion is to set up eisy samba server so you can use it as a drive. Then you can develop from your computer & test often on the Eisy. Some develop using eisy as the computer, I like doing above & ssh so I can sit in my chair in my living room and code. How to do all the above is in the developer docs, which are even starting to look good (not sure who on the team @Javi is responsible for that).

[larryllix]

I write and test all my python3 programs on a Win 11 laptop.

After testing, I port it over to my polISY and it runs just fine, exactly the same as the laptop compiler/interpreter.

I have found a few times that updates to my polisy has left my own software on the polisy slightly confused somehow and it needs a reboot.

However, that didn't happen the last polisy update. I am not sure something in the python threading I use, may not be completely happy under freeBSD, rather than Win 11.

[Michel Kohanim]

@leonpc,

On 1/21/2024 at 9:30 PM, leonpc said:

What happens if you only have the eisy?  How do i setup the Python dev environment on eisy.  Obviously I am missing it in the docs.

Python is already installed on eisy. 

On 1/22/2024 at 5:43 AM, larryllix said:

However, that didn't happen the last polisy update. I am not sure something in the python threading I use, may not be completely happy under freeBSD, rather than Win 11.

About a year ago, phyton had a major release. That may have been the cause. For now, we are sticking with python3 regardless of any updates. That is till we make sure nothing is going to break.

On 1/22/2024 at 4:01 AM, sjenkins said:

which are even starting to look good (not sure who on the team @Javi is responsible for

That would be me! Since I started developing plugins myself, I can see that it still needs a lot of work. Many things are confusing and not well explained. It's on my list to make it better.

With kind regards,
Michel

[sjenkins]

@Michel Kohanim thanks for working on the docs!  They really are starting to bring together the disbursed info (both over space and time).  It does currently make it quite a treasure hunt to find stuff.  It is nice when other plugin developers leave their code public as well.  I have learned a tonne off of them. I know the incentives don't align, but would many people "steal" and not pay for a plunin? Some would I know. 

If I could request, knowing you are busy, to continue rounding up the explanation of the interface.  I have started going through it function by function myself, but always helpful if it is commented well.

Again, thanks to the whole team!

[Michel Kohanim]

@sjenkins,

Are you referring to udi_interface?

With kind regards,
Michel

[sjenkins]

@Michel Kohanim, 

I was.  The docs are really coming together lately as far as requirements to make a plug-in work and resources to make it better.  I find as I write programs I like to dig into the library routines I am calling / relying on.  In this case udi_interface.  Helps a lot to know what it's doing (it's actually commented not too bad).  Maybe it is somewhere but any more self documentation of the libs & system helps me get the big picture as well as perhaps generating ideas for improvement in the minutia. As I say it may be in some of the files I haven't dug around in yet.

Looking back on this paragraph I know I am not clear in my ask.  I think it's just a "keep going, the docs are getting much better".  It really helps the better they are to speed development but also to help us part-timers go deeper too ; and maybe help make the system better.  This stuff is a lot of fun & me/we would love to help make it better.

 

[Michel Kohanim]

@sjenkins,

I totally agree with you. To be frank, when I started plugin dev about a month ago, I was flabbergasted by the level of difficulty and the learning curve. I think we went too far with flexibility and made things more complicated. In essence, the platform is as flexible as being able to define anything but makes it very difficult to make a simple thing especially going back and forth between nodedef, editor, and nls. I hate that. The, you will have to use these definitions and work on your python code (going back and forth between files) because udi_interface does not know anything about those files except for uploading them to IoX. It's just way too complicated. 

This being said, it's now our top priority to add a layer in between so that everything (including udi_interface) are all tied together with one file.

And, yes, will definitely include more documentation on the interface.

Thank you so very much for the feedback.

With kind regards,
Michel