Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sending remote data #4

Open
xeor opened this issue Aug 24, 2018 · 5 comments
Open

Sending remote data #4

xeor opened this issue Aug 24, 2018 · 5 comments

Comments

@xeor
Copy link

xeor commented Aug 24, 2018

Since the http plugin is waiting for scoder/lupa#84, can be get another way in the meantime to send remote-data in a more generic way..?

  • Will the mqtt plugin be available soon? Or is it possible to upload it myself?
  • Can the http plugin be made available using a zip that we can upload ourself, even tho it might be unstable? I'm willing to take the risk..
  • If I make a new generic plugin, almost like pushover, that sends data over http to a configurable url, will it be accepted as a pull-request?
@mickeprag
Copy link
Contributor

Will the mqtt plugin be available soon? Or is it possible to upload it myself?

This needs more work. Please help out to finish it. I am not using mqtt myself so I cannot continue since I don't know about the usage in a real world.

Can the http plugin be made available using a zip that we can upload ourself, even tho it might be unstable? I'm willing to take the risk..

Maybe we can disable the ability to get back the returned data for now? It will be "fire and forget" but at least the plugin will be somewhat useful.

If I make a new generic plugin, almost like pushover, that sends data over http to a configurable url, will it be accepted as a pull-request?

If it is generic and can be used by several people, then yes.

@xeor
Copy link
Author

xeor commented Aug 28, 2018

Thanks for the reply.

This needs more work. Please help out to finish it. I am not using mqtt myself so I cannot continue since I don't know about the usage in a real world.

I'll check it out and see if I can help out some time in the future. I've not used mqtt a lot my-self (saw this as a usecase), so I might end up stalling as well..

Maybe we can disable the ability to get back the returned data for now? It will be "fire and forget" but at least the plugin will be somewhat useful.

That would probably make it usefull for probably 80% of it's usecases! Fire-and-forget sounds like a good solution while we wait for lupa#84..

If it is generic and can be used by several people, then yes.

I'll add this to my project-list.. I did hit a problem tho when trying to make a tellstick plugin package.. I'll create a new issue for it if I can't find a good solution.

@jibdata
Copy link

jibdata commented Sep 8, 2018

Will it be possible to get the http plugin with the fire-and-forget workaround operational?
Would really like to get started with sending data to remote endpoint through http via LUA.

@philosomatica
Copy link

Maybe we can disable the ability to get back the returned data for now? It will be "fire and forget" but at least the plugin will be somewhat useful.

That would make the http-plugin useful to 98% for me! :)

@atchoo78
Copy link

@mickeprag: Speaking of which....I still haven't figured out how to configure a callback for responses through the HTTP plugin. LUA confuses me, I think. 😓

from the "HTTP" plugin description:

Due to technical reasons all calls are async. To retrieve the response from a http call a callback must be supplied.

Can you provide an example how to do this?

Also in the plugin description text:

More examples can be found here:
https://github.com/telldus/tellstick-lua-examples/tree/master/plugins/http

...but there seems to be some Jedi mind tricks blocking that particular url:
Skjermbilde 1

👾 Andreas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants