-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
IrReceive Data is HEX, IrSend needs Integer #1290
Comments
But for now you managed to convert from hex to decimal in node-red. Due to legacy compatibility a change to hex/hex kr decimal/decimal would be a problem. |
hi, regards M. |
Yes that would be the solution if users not already expected to send a number like 1234 as being hexadecimal. Unlucky choices made in the past are hard to fix. |
so if this is legacy compatibility affecting IR and RF i take it its not the libraries used for IR and RF but deeper into the arduino core? |
No it's tasmota legacy. |
im just looking at the xdrv_snfbridge.ino file in particular this section
just trying to work out how to add a cmnd RF_CODE# for example, so that the sending of a hex value can be triggered from the topic of mqtt rather than the payload. so the topic would be |
I'll change the way IRSend is processing the Data input field. Starting with version 5.12.0i it will accept both decimal like 1234567 and hexadecimal like 0x12345A. So the change is that it now supports the standard C notation for hexadecimal being 0x. This means that the default mode is decimal with optional hexadecimal when prefixed with 0x or 0X. |
5.12.0i * Add hexadecimal Data entry to command IrSend using 0x notation (arendst#1290, arendst#2314)
Hi,
it needs some time to get it, Receive sends IR data to mqtt/console in HEX format.
I tried to send that same data out, but failed.
then i realized that i have to convert it form HEX to DEC (unsigned integer).
Any idea why? Can irSend accept HEX as dataformat and send it out?
Makes IR handling much easier in my nodered.
regards M.
The text was updated successfully, but these errors were encountered: