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
Any development still on? #28
Comments
Hey, I switched over to the telldus integration available in Home Assistant. works seemlessly with autodiscovery over mqtt. Required getting a developer key from Telldus to upload the custom plugin though. |
@odtgit, I assume you are not @molobrakos or any of the other contributors? I use OpenHAB, so Home Assistant does not cut it for me. -And OpenHAB's Teldus binding requires telldus-core library (even for Telldus Live access), which doesn't really seem to compile any more. Besides, using this, a separate script, connected through MQTT, not requiring cloud access, seems like a much more resilient solution to me. Firmware development has ceased for my old Tellstick.Net, and using Telldus Live, I would be vulnerable to Telldus changing any of their API, servers, or support for older Tellstick.Net devices :-) If development is not continuing here, what is the appropriate way to move on? To make my own fork, and (obviously) point back to this as the main source, or just suggest changes here, and see if I am allowed to approve my own changes? |
@olokna I'm not a contrubutor here, but I was in the same boat - maintaining my own fork of this repo and running a local docker build until I found https://github.com/quazzie/tellstick-plugin-mqtt-hass - give this a go, it says home assistant but I imagine if you configure your mqtt broker in OpenHAB to pick up the right topics, it works there aswell. i don't really see any reason to "continue" development on either of thos besides bugfixes ofc. anyway, can't recommend Home Assistant enough - it's out of beta just recently after 3 years of development and the second most active project on github with thousand of contributors. |
Thanks @odtgit! Unfortunately, My Tellstick.Net is the old 433-only version (V1), which has a very limited firmware. I do agree that it would probably be a very good solution if I really had such a new tellstick. Actually, I only use the solution for reporting temperatures, and controlling Christmas lights nowadays, so I feel investing in a newer stick (although cheap) just isn't worth it... |
@oklona I also have the older v1, and have tried running this codebase as a Python script. If you have a working version running in a docker container, I would be very interested in that. I'm not sure about the (most) appropriate way to proceed, either, but since there's still an open, uncommented pull request from May, I would guess that you'll have to fork this and move on in a separate repo. |
Ok, then I will create a fork, and upload my changes once the holidays are over. I also have ambitions to improve the documentation. I definitely haven't done anything revolutionary, but have gotten a Docker file working, I implemented the changes proposed in the May PR, I enabled "learn" mode, and fixed an issue that was referenced here, but not marked as fixed. |
Sorry for no response here. @oklona, feel free to submit any pull request with your changes, and I'll merge them. |
Hello.
I use this software for controlling my old Tellstick.net locally. I have made some minor modifications to the code, set up a working Dockerfile and scripts for running it off a Docker-container. I also set up the "learn" function, since I want to become completely independent of Internet for controlling my devices. Are these things something that would be interesting for other people to have added into this, or am I among the very few people still using these scripts?
The text was updated successfully, but these errors were encountered: