-
Notifications
You must be signed in to change notification settings - Fork 10
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
[Discussion] Tellstick.conf #17
Comments
I don't know much about autodiscover and raw events as I don't have a telldus duo. I have been meaning to create an interface for CRUD (create/edit/update/delete) devices and groups. As I mainly use Windows, I use Telldus Center. What is a shame is that from what I can see, every piece of software that has been written for Telldus has written its own logic for dealing with creating devices the multitude of protocols and models that are supported. I will be joining them! |
Ok, I have studied the Telldus Live API at Telldus and if I understand it correctly the aim of Tellprox is to provide rest-services of CRUD in the same way as Telldus Live. So you will have to use a client like Telldus Center to access the tellprox server? |
Yes, but there is a basic web front end which allows one to turn items on
|
Have you tried or received any comments on how well it works with http://remotestick.org/ nowadays? |
Yes, I use it with Remotestick most days and for what I use it for, have no
|
By the way, I have a duo and planning to buy a temp sensor, I might try it out later during spring :-) Is the login solution of tellprox compatible with telldus live i.e. if you enter login and password in remotestick it will work with tellprox? |
The method by which you authenticate with Tellprox is different to that of On 28 March 2014 19:21, engelvinter [email protected] wrote:
|
The biggest obstacle for a beginner is still to define a proper tellstick.conf.
It would be nice if tellprox was able to autodiscover devices - and user could give them names later on - tellprox writing directly to tellstick.conf.
I have not tried it out, but the raw event callback in the telldus-core might be a way to detect devices if putting them in learning mode.
The text was updated successfully, but these errors were encountered: