-
Notifications
You must be signed in to change notification settings - Fork 42
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
Support Tasmota devices #356
Comments
Thank you very much for the suggestion. (Also, nice to hear from you!) IrScrutinizer is mainly a tool for analyzing and collecting IrSignals, and to help setting up home automation systems. The need to support a large number of input/output devices is therefore somewhat secondary, in particular since (currently) the addition of new hardware support to the GUI is not quite streamlined. However, for "IrScrutinizer as server", JGirs it is certainly desirable. See HarcHardware for implementation. Help most definitely welcome. Having said that, if the goal is to integrate IrScrutinizer (and/or JGirs), it may be a better idea to teach Tasmota Girs over TCP-sockets. (See also AGirs for an example.) That would mean no changes to IrScrutinizer would be necessary, and, as a free bonus, Lirc support would come in for free. (There is a Girs driver in the current officual Lirc; happens to be written by yours truly). Help most definitely welcome. |
Hi @bengtmartensson I understand that implementing a GIRS server in LIRC would be technically preferable, however since Tasmota is trying to cram as many different sensors and protocols into one firmware as possible I assume it is very unlikely that they will add another IR handling library in addition to what they are already using there (and I further assume that they have lots of existing users which are depending on the existing IR functionality to stay as it is). The advantage would be that IRScrutinizer would immediately become the tool for Tasmoa users for all things IR, and they have a very large user base in home automation, usually tech-savvy home automation enthusiasts. I think it would be a great multiplicator effect for this project. |
After some experimentation, this seems really easy to do. Let's say you have the following raw timings (protocol = NEC1, device = 0, obc = 10):
Replace the
Then GET it to the device like so: Works for me. I would be really happy if IrScrutinizer could send codes to Tasmota devices this way. User case: |
Tasmota now (also) uses a new IR Raw compact encoding: https://tasmota.github.io/docs/IRSend-RAW-Encoding/ |
Tasmota is a very popular open source firmware for ESP8266 based devices. It is used in many home automation systems.
It can send and receive IR codes via WLAN.
https://github.com/arendst/Tasmota/wiki/IRSend-RAW-Encoding has the technical details.
It would be cool if Tasmota devices could be supported in IrScrutinizer.
The text was updated successfully, but these errors were encountered: