Hi Leon,
I tried to apply the guidelines described here (https://github.com/AnaviTechnology/anavi-docs/blob/master/anavi-infrared-phat/anavi-infrared-phat.md#chapter-3-software).

When executing this commande "sudo apt install -y ./liblirc0_0.10.1-6.2deb10u1_armhf.deb ./liblircclient0_0.10.1-6.2deb10u1_armhf.deb ./lirc_0.10.1-6.2~deb10u1_armhf.deb", I received the following error messages.

pi@RPI-LIRC-RX:/lirc-src/lirc-0.10.1 $ cd /lirc-src
pi@RPI-LIRC-RX:/lirc-src $ sudo apt install -y ./liblirc0_0.10.1-6.2deb10u1_armhf.deb ./liblircclient0_0.10.1-6.2deb10u1_armhf.deb ./lirc_0.10.1-6.2deb10u1_armhf.deb
Reading package lists... Done
E: Unsupported file ./liblirc0_0.10.1-6.2deb10u1_armhf.deb given on commandline
E: Unsupported file ./liblircclient0_0.10.1-6.2deb10u1_armhf.deb given on commandline
E: Unsupported file ./lirc_0.10.1-6.2~deb10u1_armhf.deb given on commandline

I tried on a RPI 3 B + and on a RPI 4 4 megs, with the latest version of the Raspberry OS (issued on 2021-03-04), after a fresh install.

I am wondering what I did wrong, since I mostly copied/pasted the command lines from you tutorial...

Thank you very much in advance for any suggestions that could come to your mind !

Best regards

Pierre Masson

https://github.com/AnaviTechnology/anavi-docs/blob/master/anavi-macro-pad-2/anavi-macro-pad-2.md#chapter-3-software

It's my understanding that I need to install the older QMK software v0.13.19 in order to use a GUI version of the Configurator on my local PC.

I'm using the steps documented here. I read Chapter 1 (overview), Chapter 2 (assembly) and I'm now on Chapter 3 (software).

1. "CHAPTER 3: Software Out of the box ANAVI Macro Pad 2 comes with the popular open source firmware QMK. Several different keymaps are supported. For details how to build and flash QMK firmware on ANAVI Macro Pad 2 please have a look at the README."

   This opening paragraph is confusing and I'm wondering if you could safely remove the "For details how to build..." because as far as I can tell the Macro Pad 2 already has the firmware installed. I'm attempting to go through Chapter 3 as a first time user.

2. Flashing: This part is confusing because I'm attempting to install QMK for Windows but this seems to apply to macOS or Linux. I looked ahead into other steps of Chapter 3 and learned I'd be installing QMK MSYS2, and I know MSYS2 provides a linux-like shell, which makes me wonder if the instructions are out of sequence -- on Windows I don't see how I can do "git clone [micronucleus] etc." and "make install" until after I install QMK MSYS2 which would give me the linux-like shell to do the clone/make install etc.

3. Continuing on in the Flashing section, I'm now at the "Instructions: Setup QMK" step. I go here and read the "Prerequisites" section. I've got a text editor I use on Windows so I don't do anything for that. The Toolbox sounds very useful so I follow it's link and download and install qmk_toolbox_install.exe version 0.1.1

4. I go back to here and proceed with section, "2. Prepare Your Build Environment :id=set-up-your-environment". Under "Windows/Prerequisites" I'm directed to "You will need to install QMK MSYS. The latest release is available here." Following the links I'm eventually taken to where I download and install QMK_MSYS.exe v1.5.1.

5. I see (edited for brevity):

     ...
     Welcome to QMK MSYS!
     ...
     If you have not already done so,
       run qmk setup to get started.
     ...

$ qmk setup

     ☒ Could not find qmk_firmware!
     Would you like to clone qmk/qmk_firmware to C:/Users/taa/qmk_firmware? [y/n] y
     Cloning into '/c/Users/taa/qmk_firmware'...
     Updating files:   0% (155/28431)
     ...
     Updating files: 100% (28431/28431), done.
     Submodule 'lib/chibios' (https://github.com/qmk/ChibiOS) registered for path 'lib/chibios'
     ...
     Submodule 'lib/vusb' (https://github.com/qmk/v-usb) registered for path 'lib/vusb'
     Cloning into '/c/Users/taa/qmk_firmware/lib/chibios'...
     ...
     Submodule path 'lib/vusb': checked out 'bdb53e4c043d089279d9891b68bea77614cb97ee'       
     Ψ Successfully cloned https://github.com/qmk/qmk_firmware to C:/Users/taa/qmk_firmware! 
     Ψ Added https://github.com/qmk/qmk_firmware as remote upstream.                         
     Ψ QMK Doctor is checking your environment.                                              
     Ψ CLI version: 1.0.0                                                                    
     Ψ QMK home: C:/Users/taa/qmk_firmware                                                   
     Ψ Detected Windows 10 (10.0.19043).                                                     
     Ψ Git branch: master                                                                    
     Ψ All dependencies are installed.                                                       
     Ψ Found arm-none-eabi-gcc version 10.1.0                                                
     Ψ Found avr-gcc version 8.4.0                                                           
     Ψ Found avrdude version 6.3                                                             
     Ψ Found dfu-util version 0.10                                                           
     Ψ Found dfu-programmer version 0.7.2                                                    
     Ψ Submodules are up to date.                                                            
     Ψ QMK is ready to go                                                                    

$

6. I return to here and continue with the section, "3. Run QMK Setup :id=set-up-qmk" where for Windows I'm instructed to do "qmk setup" but this doesn't make sense to me because I already did that (number 5 above).

7. I read "4. Test Your Build Environment" but so far the Anavi Macro Pad 2 steps haven't provided me with file names to put here. Since it's just a "Test" step, I skip it.

8. I read "5. Configure Your Build Environment (Optional)" but skip doing anything for the same reason as number 7, the Anavi Macro Pad 2 steps haven't provided file names to put here.

9. This completes the "Setup QMK" steps so I return to here and proceed to "Download QMK firmware version 0.13.19, for example:"

$ git clone -b 0.13.19 https://github.com/qmk/qmk_firmware.git

     fatal: destination path 'qmk_firmware' already exists and is not an empty directory.

$ git submodule update --init

     fatal: not a git repository (or any of the parent directories): .git

$  make anavi/macropad2:default

     make: *** No rule to make target 'anavi/macropad2:default'.  Stop.

$

Help!

Section CHAPTER 3: Software could use some clarification:

• skip Flashing when running on Windows
• after Instructions but before Recovery, shouldn't there be steps to run the Configurator?

I'm lost! :( Is it really necessary to flash the firmware before installing a local copy of the Configurator? Because flashing is what the docs seem to want me to do, as I've shown above.

I was able to compile BH1750 & HTU21D but I'm having an issue with BMP180

It's as if this include guard in BMP180.h isn't working?
#ifndef _BMP180_H_

I'm using:

• i2c-tools 4.2-1+b1
• python3-rpi.gpio 0.7.0-0.2+b1
• wiringpi 2.52

My Raspberry Pi is a 4 Model B Rev 1.2
running Raspbian GNU/Linux 11 (bullseye)

The ld linker logging the errors is version 2.35.2

Thank you in advance if anybody can help point me in the right direction!

I have installed following instructions
When running example script provided with ether 1 or 2 sensors attached, the result returns 100% moisture
This is on a pi zero w2.

I will re-run from a fresh install of bullseye to see if anything changes (this will be the 2nd time around)

Has anyone else had this issue?

Cannot get past this issue.
Error message:
Arduino: 1.8.9 (Mac OS X), Board: "Generic ESP8266 Module, 80 MHz, Flash, Disabled, ck, 26 MHz, 40MHz, DIO, 4M (1M SPIFFS), 2, v2 Lower Memory, Disabled, None, Only Sketch, 115200"

Sketch uses 263416 bytes (25%) of program storage space. Maximum is 1044464 bytes.
Global variables use 26848 bytes (32%) of dynamic memory, leaving 55072 bytes for local variables. Maximum is 81920 bytes.
warning: espcomm_sync failed
error: espcomm_open failed
error: espcomm_upload_mem failed
error: espcomm_upload_mem failed

This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.

https://github.com/AnaviTechnology/anavi-docs/blob/master/anavi-macro-pad-2/anavi-macro-pad-2-datasheet.pdf

I've tried a few different ways to retrieve this, including wget, but it seems to be an HTML document. Acrobat complains when it tries to open it.

Excerpt of first few lines, including several blank lines at the beginning.

<!DOCTYPE html>
<html lang="en" data-color-mode="auto" data-light-theme="light" data-dark-theme="dark">
  <head>
    <meta charset="utf-8">
  <link rel="dns-prefetch" href="https://github.githubassets.com">
  <link rel="dns-prefetch" href="https://avatars.githubusercontent.com">
  <link rel="dns-prefetch" href="https://github-cloud.s3.amazonaws.com">
  <link rel="dns-prefetch" href="https://user-images.githubusercontent.com/">
  <link rel="preconnect" href="https://github.githubassets.com" crossorigin>
  <link rel="preconnect" href="https://avatars.githubusercontent.com">

https://github.com/AnaviTechnology/anavi-docs/blob/master/anavi-thermometer/anavi-thermometer.md claims:

To verify that ANAVI Thermometer is up and running open a modern web browser and visit demo.anavi.technology. Enter your machine ID.

But when I do that, I only get a website for the ANAVI Light Controller. Should all references to the demo website be removed from the ANAVI Thermometer documentation, or will the website soon be updated to support the Thermometer as well?

I've been using Anavi pHat for one year, I've made a remote controller for my air conditioner and it worked fine. Some days ago I realised it's no longer transmitting IR to the AC and I noticed I'm getting "hardware does not support sending" when running irsend. I've taken a look to see if any update had broken the configuration, but only noticed that hardware.conf was removed, so I created it back and rebooted, but still getting the same error. (Other files as described in user manual still exist and have the right lines)
If I try to run # systemctl stop lircd and mode2 and mode2 -d /dev/lirc0 I'm getting "Cannot initiate device /dev/lirc0".
Meanwhile, I notice that temperature and humidity sensor, which is attached to the hat, keeps working fine as I'm getting correct data on my homemade app.
What can I do?

I'm having the following problem:

Oct 23 17:55:39 raspberrypi systemd-modules-load[773]: Failed to find module 'lirc_rpi gpio_in_pin=18 gpio_out_pin=17'
Oct 23 17:55:39 raspberrypi systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Oct 23 17:55:39 raspberrypi systemd[1]: Failed to start Load Kernel Modules.

This is a brand new, fresh install of Raspian with no additional software apart from those in your docs. Any ideas why I can't progress past this point?

Hi,
I'm on Raspbian Buster. I checked and applied all of the recommandations.
I can record remotes but when I test to send a IR Signal I've got -> transmission failed
Error running command: Input/output error.

/boot/config.txt:
dtoverlay=gpio-ir,gpio_pin=18
dtoverlay=gpio-ir-tx,gpio_pin=17

/etc/lirc/lirc_options.conf
driver = default
device = /dev/lirc0

Have you any idea ?

Anyone successfully inegrated Anavi Light Controller with Home Assistant? Show me your magic please!

Hello,

A customer submitted a support ticket to us and stated that they were missing some pieces for their item. Their ticket is below:

"Received ANAVI Fume Extractor (Developer Kit) yesterday. The project contains only enough screws/nuts for assembling circuit board, OLED display, and fan. Still missing screws to complete attaching light sensor and other modules. Can you ship remainder of screws and nuts?"

Is this something you can assist with? @leon-anavi

Thank you,
Tanner

Hello, just received the controller and very excited to integrate it into my system.

I've connected the controller to a mosquitto server running in my basement, and watching all the messages being sent with mosquitto_sub. I'm wondering how to manage the /config endpoint. Is this a protocol invented by Anavi, or a community standard? Either way, would you mind pointing me at some reading material so I can build something to parse those messages correctly and know how to use them. In this case, I suppose I'd want to change things about the lights and such, but I'm not using home assistant or other platform.

I have been following along with the ANAVI infrared pHAT readme and there are two packages that are supposed to be installed that are no longer available.
python-rpi.gpio & wiringpi

More info on why wiringpi is no longer maintained.

EDIT: I was able to install the last maintained version of wiringpi by following these instructions

I've just received my Anavi light controller and it is awesome, thank you!

Just a quick question, how can I specify a username and password for a custom mqtt connection (from the configuration page at 192.168.4.1).

Thanks!

Couldn't find the macro pad 2 video online anywhere for how to build it, the video points to the macro pad 8.

Also the firmware for the 2 pad keyboard does not seem to be upstream anywhere, is there a link to it somewhere online?

Hi @leon-anavi

Hoping you might be able to assist with troubleshooting irsend issue "Cannot configure the rc device for /dev/lirc0"

• I've tried different remotes
• boot_config and lirc_options.conf attached
  lirc_options.conf.conf.txt
  boot.txt
• Pi0w, Buster 10
• Followed the Github/PDF guide
• Created liblirc0_0.10.1-6.2deb10u1_armhf.deb, liblircclient0_0.10.1-6.2deb10u1_armhf.deb, lirc_0.10.1-6.2~deb10u1_armhf.deb
  PS: I didn't have to copy over xxx.dist configs as the config files were already there.
• Updated lirc_options.conf and updated /boot/config.txt to liblirc1 for recording.
• Ran the install again with --allow-downgrades
  PS: I got these messages but it seems to have re-installed.

Note, selecting 'liblirc0' instead of './liblirc0_0.10.1-6.2~deb10u1_armhf.deb'
Note, selecting 'liblircclient0' instead of './liblircclient0_0.10.1-6.2~deb10u1_armhf.deb'
Note, selecting 'lirc' instead of './lirc_0.10.1-6.2~deb10u1_armhf.deb'

After reboot, once again I am getting signals with mode2 -d /dev/lirc1 and now irrecord saves the remote config:

  name  sony
  bits            4
  flags SPACE_ENC|CONST_LENGTH
  eps            30
  aeps          100

  header       2427   585
  one          1219   579
  zero          619   579
  post_data_bits  8
  post_data      0x90
  gap          45031
  toggle_bit_mask 0x0
  frequency    38000

      begin codes
          KEY_VOLUMEUP             0x4
          KEY_VOLUMEDOWN           0xC
          KEY_POWER                0xA
      end codes

• I switch back to /dev/lirc0 and copy the new config across

pi@raspberrypi:~ $ irsend list sony ""

0000000000000004 KEY_VOLUMEUP
000000000000000c KEY_VOLUMEDOWN
000000000000000a KEY_POWER

Command:

irsend send_once sony KEY_POWER

LOGS:

Aug 21 03:20:23 raspberrypi lircd-0.10.1[468]: Warning: Running as root
Aug 21 03:20:23 raspberrypi lircd-0.10.1[468]: Info: Using remote: sony.
Aug 21 03:20:23 raspberrypi lircd-0.10.1[468]: Notice: lircd(default) ready, using /var/run/lirc/lircd
Aug 21 03:21:51 raspberrypi lircd-0.10.1[468]: Notice: accepted new client on /var/run/lirc/lircd
Aug 21 03:21:51 raspberrypi lircd-0.10.1[468]: Info: Cannot configure the rc device for /dev/lirc0
Aug 21 03:24:25 raspberrypi lircd-0.10.1[468]: Info: removed client
Aug 21 03:24:30 raspberrypi lircd-0.10.1[468]: Notice: accepted new client on /var/run/lirc/lircd
Aug 21 03:24:30 raspberrypi lircd-0.10.1[468]: Info: Cannot configure the rc device for /dev/lirc0
Aug 21 03:24:30 raspberrypi irsend: lirc_command_run: data:END, status:0
Aug 21 03:24:30 raspberrypi lircd-0.10.1[468]: Info: removed client

Hi. Thanks for the answer to my previous question.
Could I ask one more?

I have an ANAVI Infrared pHAT (Advanced Kit) for my Raspberry Pi 3.
It works great to get temperature, humidity, etc. I'm totally happy with it!
I'd like to also visualize CO2 level and bought a MH-Z19B sensor which supports UART.
I successfully got it to work when directly connected to my Rasp via GPIO (/dev/serial0) with a Python module like so:

pi@raspberrypi:~ $ gpio readall
 +-----+-----+---------+------+---+---Pi 3---+---+------+---------+-----+-----+
 | BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |
 +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
 |     |     |    3.3v |      |   |  1 || 2  |   |      | 5v      |     |     |
 |   2 |   8 |   SDA.1 | ALT0 | 1 |  3 || 4  |   |      | 5v      |     |     |
 |   3 |   9 |   SCL.1 | ALT0 | 1 |  5 || 6  |   |      | 0v      |     |     |
 |   4 |   7 | GPIO. 7 |   IN | 1 |  7 || 8  | 1 | ALT5 | TxD     | 15  | 14  |
 |     |     |      0v |      |   |  9 || 10 | 1 | ALT5 | RxD     | 16  | 15  |
 |  17 |   0 | GPIO. 0 |   IN | 0 | 11 || 12 | 0 | IN   | GPIO. 1 | 1   | 18  |
 |  27 |   2 | GPIO. 2 |   IN | 0 | 13 || 14 |   |      | 0v      |     |     |
 |  22 |   3 | GPIO. 3 |   IN | 0 | 15 || 16 | 0 | IN   | GPIO. 4 | 4   | 23  |
 |     |     |    3.3v |      |   | 17 || 18 | 0 | IN   | GPIO. 5 | 5   | 24  |
 |  10 |  12 |    MOSI |   IN | 0 | 19 || 20 |   |      | 0v      |     |     |
 |   9 |  13 |    MISO |   IN | 0 | 21 || 22 | 0 | IN   | GPIO. 6 | 6   | 25  |
 |  11 |  14 |    SCLK |   IN | 0 | 23 || 24 | 1 | IN   | CE0     | 10  | 8   |
 |     |     |      0v |      |   | 25 || 26 | 1 | IN   | CE1     | 11  | 7   |
 |   0 |  30 |   SDA.0 |   IN | 1 | 27 || 28 | 1 | IN   | SCL.0   | 31  | 1   |
 |   5 |  21 | GPIO.21 |   IN | 1 | 29 || 30 |   |      | 0v      |     |     |
 |   6 |  22 | GPIO.22 |   IN | 1 | 31 || 32 | 0 | IN   | GPIO.26 | 26  | 12  |
 |  13 |  23 | GPIO.23 |   IN | 0 | 33 || 34 |   |      | 0v      |     |     |
 |  19 |  24 | GPIO.24 |   IN | 0 | 35 || 36 | 0 | IN   | GPIO.27 | 27  | 16  |
 |  26 |  25 | GPIO.25 |   IN | 0 | 37 || 38 | 0 | IN   | GPIO.28 | 28  | 20  |
 |     |     |      0v |      |   | 39 || 40 | 0 | IN   | GPIO.29 | 29  | 21  |
 +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
 | BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |
 +-----+-----+---------+------+---+---Pi 3---+---+------+---------+-----+-----+

pi@raspberrypi:~ $ sudo python -m mh_z19
{"co2": 1917}

But when I connect it with the UART of the Infrared pHAT, it doesn't work.
Is it possible to do so?
Here is the manual for MH-Z19B.
Thanks in advance!

I received two of the Anavi handles the last day or so and after trying a couple of nunchucks which do connect successfully, I noticed that each has a slight joystick drift that makes the cursor slowly drift upwards. It functions just fine outside of that. Is there a way to calibrate the joystick via the device itself or is that handled by the OS?

https://github.com/AnaviTechnology/anavi-docs/blob/master/anavi-macro-pad-2/anavi-macro-pad-2.md#anavi-macro-pad-2-developer-kit

I'm too embarrassed to attach a photo of what my assembled Macro Pad 2 looked like. Something felt off when I put my fingers on it. I didn't figure it out until I took my glasses off and held the Macro Pad 2 just inches from my face. :( Suffice it to say it looked like it was put together by someone under the influence of... something. I had the keycaps rotated 90* differently from each other.

The ANAVI Macro Pad 2 Developer Kit Assembly Guide - YouTube doesn't say anything about how to orient the keycaps.

1. I wonder if you could update the assembly steps at the link at the top of this post, to include how to orient the keycaps?

2. Could you also update the datasheet for the Macro Pad 2 to include the keycap manufacturer or profile family (Keycaps 101) or part number?

I'm trying to get started with the Anavi Infrared pHAT on my PI. I was able to learn the IR codes, but I can't send. When I try to send a code via irsend SEND_ONCE HunterDouglasBlinds KEY_UP it says:

hardware does not support sending
Error running command: Input/output error

I have this in my config files:

pi@piir:~ $ grep -v ^\# /etc/modules
i2c-dev
lirc_dev
lirc_rpi gpio_in_pin=18 gpio_out_pin=17 

pi@piir:~ $ grep -v ^\# /etc/lirc/hardware.conf 
LIRCD_ARGS="--uinput"
LOAD_MODULES=true
DRIVER="default"
DEVICE="/dev/lirc0"
MODULES="lirc_rpi"
LIRCD_CONF=""
LIRCMD_CONF=""

pi@piir:~ $ grep -v ^\# /boot/config.txt
dtparam=audio=on
[pi4]
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
[all]
dtoverlay=gpio-ir,gpio_pin=18
dtoverlay=gpio-ir-tx,gpio_pin=17

pi@piir:~ $ grep -v ^\# /etc/lirc/lircd.conf.d/HunterDouglasBlinds.lircd.conf 


begin remote

  name  HunterDouglasBlinds
  driver devinput
  bits           56
  eps            30
  aeps          100

  one             0     0
  zero            0     0
  pre_data_bits   8
  pre_data       0x0
  gap          29867
  toggle_bit_mask 0x0
  frequency    38000

      begin codes
          KEY_UP                   0xE501000000262D
          KEY_DOWN                 0xC2010000000646
      end codes

end remote

When following the directions here, https://github.com/AnaviTechnology/anavi-docs/blob/master/anavi-gardening-uhat/anavi-gardening-uhat.md#examples, apt spits out the following.

sudo apt install -y git git-core vim python-dev python-rpi.gpio  wiringpi i2c-tools
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'git' instead of 'git-core'
Note, selecting 'python-dev-is-python2' instead of 'python-dev'
Package wiringpi is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package python-rpi.gpio is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'python-rpi.gpio' has no installation candidate
E: Package 'wiringpi' has no installation candidate

This is on a brand new pi install:

pi@hedy:~ $ uname -a
Linux hedy 5.10.92-v7+ #1514 SMP Mon Jan 17 17:36:39 GMT 2022 armv7l GNU/Linux

pi@hedy:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

Hello!

I left my assembled fume extractor in a box with bubblewrap for a while and I just unpacked it and the OLED display is not displaying anything upon boot.

It used to work fine. All wiring is still intact and looks OK, correct pins for the display. Did it just die? How can I check that easily?

Thanks

First of - thanks for making the ANAVI Infrared hat - it's made it so easy to get into sending/receiving IR using a rpi zero!

By following the ANAVI instructions for setting up transmitting with LIRC, and then using the "using multiple devices" part of the LIRC docs, I have managed to get two instances of LIRC running, the normal one for sending on /dev/lirc0 and the new socket at /var/run/lirc/lircd-lirc1 for receiving on /dev/lirc1. They work when I use them at different times:

# Works! Sends IR signal to disable my hifi
$ irsend SEND_ONCE logitech_z906 POWER POWER

$ irw /var/run/lirc/lircd-lirc1
00000000e0e0a659 00 KEY_LEFT SAMSUNG_BN59-01178B
00000000e0e046b9 00 KEY_RIGHT SAMSUNG_BN59-01178B
00000000e0e006f9 00 KEY_UP SAMSUNG_BN59-01178B
00000000e0e006f9 01 KEY_UP SAMSUNG_BN59-01178B
00000000e0e08679 00 KEY_DOWN SAMSUNG_BN59-01178B
00000000e0e08679 01 KEY_DOWN SAMSUNG_BN59-01178B

However, something seems to go wrong when I try to receive and send at the the same time. If I run irw to receive in the background:

$ irw /var/run/lirc/lircd-lirc1 &
[1] 3111

And then try and send a command:

# Does nothing! Not recognised.
$ irsend SEND_ONCE logitech_z906 POWER POWER
# Also doesn't work
$ irsend SEND_ONCE SAMSUNG_BN59-01178B KEY_RIGHT KEY_RIGHT

However, if I then kill the background irw receiving process:

$ kill -15 %1
[1]+  Terminated              irw /var/run/lirc/lircd-lirc1

Sending works again!

# Works again!
$ irsend SEND_ONCE logitech_z906 POWER POWER

Weirdly enough, in this "broken" state of sending and receiving at the same time, the IR leds still flash (checked with my phone camera) and if you run mode2 in the background:

$ mode2 -d /dev/lirc1 & 
[2] 3121
Trying device: /dev/lirc1
Using device: /dev/lirc1

you get the pulse/space data:

space 14962268
space 2053667
pulse 114
space 14454
pulse 207

but nothing shows up from the irw process in the background (and my hifi/tv do not recognise the signals either).

I assume the two instances of lirc are interfering with each other somehow. The LIRC docs say you may need to have two kernel drivers with different names, if the driver can only handle one device at a time:

The only situation where the described procedure will not work is when you have two devices that both use a kernel driver that can only handle one device at once like e.g. lirc_serial, lirc_sir or lirc_parallel. Resolving this requires recompiling the kernel drivers with different names and device numbers. Lifting this limitation is one of the todo items for future releases.

I also found this wiki page about rebuilding a separate version of the backing driver for LIRC.

But both are referring to the lirc_serial driver that I can't find with lsmod, where as the phat uses the default driver.

Any idea what's going wrong?

Missing Schematics

I miss a drawing of how the hardware is screwed together.
Can you add a schematics as an image file to Github?

https://github.com/AnaviTechnology/anavi-docs/blob/master/anavi-macro-pad-2/anavi-macro-pad-2.md#prerequisites

On my Debian-based linux distro, I first needed to do:

sudo apt-get install libusb-dev

Without this step, the 'make install' fails:

$ sudo make install

     /bin/bash: libusb-config: command not found
     Building library: library/micronucleus_lib.c...
     gcc  -Ilibrary -O -g -D LINUX -c library/micronucleus_lib.c
     In file included from library/micronucleus_lib.c:32:
     library/micronucleus_lib.h:35:10: fatal error: usb.h: No such file or directory
      #include <usb.h>
               ^~~~~~~
     compilation terminated.
     make: *** [Makefile:72: micronucleus_lib.o] Error 1

The revised prerequisites becomes:

     sudo apt-get install libusb-dev
     git clone https://github.com/micronucleus/micronucleus.git
     cd micronucleus/commandline/
     sudo make install

So I've bouht this nice remote-controlled LED candle and the first thing I thought once home was trying to map the two simple buttons right into the IR HAT.

I mapped them as raw signals since this worked fine with my air conditioner and the signals appear to be pretty basic. When I try it with irsend, the signal is correctly sent but the candle won't turn on (I've tried an air conditioner command right before and it works fine). Here's my config file.
Do you have any clues on what it might be?
(I'm sorry if this comes out to be off-topic, I remember you assisted me finely months ago)

i have raspberry pi 3 runing raspian buster .
i followed the instructions in
https://github.com/AnaviTechnology/anavi-docs/blob/master/anavi-infrared-phat/anavi-infrared-phat.md
but when i type patch -p0 -i lirc-gpio-ir-0.10.patch
i get :
pi@raspberrypi:~/lirc-src $ patch -p0 -i lirc-gpio-ir-0.10.patch
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:

|diff -ruN lirc-0.10.1.orig/lib/config_file.c lirc-0.10.1/lib/config_file.c
|--- lirc-0.10.1.orig/lib/config_file.c 2017-09-10 17:52:19.000000000 +0900
|+++ lirc-0.10.1/lib/config_file.c 2019-06-26 00:39:45.734320696 +0900

File to patch:
`
how can i fix this problem?

I am using the ANAVI ir recorder on Buster on my Raspberry Pi 4. I have installed all patches as detailed by the installation guides in this repo.

I am able to complete the irrecord process, however, all commands are saved as 0x0. I have tried with 3 different IR remotes.

Please help me, I have been trying this for days.

My /etc/lirc/lirc_options.conf:
[lircd]
nodaemon = False
driver = default
device = /dev/lirc1
output = /var/run/lirc/lircd
pidfile = /var/run/lirc/lircd.pid
plugindir = /usr/lib/arm-linux-gnueabihf/lirc/plugins
permission = 666
allow-simulate = No
repeat-max = 600

Here is my config file:

/boot/config.txt

Uncomment some or all of these to enable the optional hardware interfaces

dtparam=i2c_arm=off
#dtparam=i2s=on
#dtparam=spi=on

Uncomment this to enable the lirc-rpi module

dtoverlay=lirc-rpi
#dtoverlay=lirc-rpi,gpio-in_pin=18,gpio_out_pin=17
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18
#dtoverlay=gpio-ir,gpio_out_pin=17,gpio_in_pin=18,gpio_in_pull=up

Additional overlays and parameters are documented /boot/overlays/README

Enable audio (loads snd_bcm2835)

dtparam=audio=on
#audio_pwm_mode = 2

[pi4]

Enable DRM VC4 V3D driver on top of the dispmanx display stack

dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d
#dtoverlay=lirc-rpi,gpio_in_pin=18,gpio_out_pin=17

NOOBS Auto-generated Settings:

hdmi_force_hotplug=1
dtparam=spi=on

#dtoverlay=lirc-rpi,gpio_in_pin=18,gpio_out_pin=17
dtoverlay=gpio-ir,gpio_pin=18