@miwhfjxiiwawshrmet Hi, CEP doesn’t support this HAT. But you are welcome to contribute to the project by adding the support of this HAT to CEP’s control module.

Hi @filip , we have fixed this issue now, please perform the update steps again to pull the latest code from the dev branch. After this, the USB webcam or CSI camera should appear in the connected camera list on the Device setup page. cd cep git checkout dev git pull sudo reboot

Hi @filip, we have implemented support for the USB webcam and Pi's CSI camera into the latest dev branch of CEP. Please check it out and have a test. You can get the latest update by: cd cep git checkout dev git pull sudo reboot Please note that the dev branch may contain bugs, feel free to reach out to us if you encounter any problems.

Hi @filip, we will add support for CSI-camera (HQ camera) and USB webcam to CEP to support your use case. It is going to take us a few days. We will let you know when we have implemented this feature. This way you don't have to use our deprecated CAIT project. Please let me know if this is what you are looking for.

That’s good to know. Regarding the CAIT’s “refused to connect“ issue you encountered earlier. I was not able to reproduce it today, I would need some logs to get more details, please perform the following steps on the device with CAIT: 1. In the Pi’s terminal type: sudo journalctl -u cait_components.service > /home/pi/cait_components.log 2. sudo journalctl -u cait_webapp.service > /home/pi/cait_webapp.log 3. please send me both cait_components.log and cait_webapp.log under /home/pi

Thanks for the information @filip , I will be setting up a Pi with the Raspberry OS lite to debug tomorrow. In the meantime, please try the above solution and let us know of any issues.

@filip After looking into the logs, the reason has been identified, the following line in the log indicates that some packages are missing in the OS: ImportError: libImath-2_2.so.23: cannot open shared object file: No such file or directory A similar issue can be found in here: https://github.com/EdjeElectronics/TensorFlow-Object-Detection-on-the-Raspberry-Pi/issues/18 The solution to this problem is to install the missing packages by typing the following in the Pi’s terminal: sudo apt-get install -y libilmbase-dev libopenexr-dev libgstreamer1.0-dev After the installation is finished, please reboot the device and test again. Can you also let me know which Raspberry OS you are using for the CEP? I would like to investigate further into this error, thanks. Michael

@filip I have received the log, thanks. I would like to get one more log from the Pi, please follow the steps below: 1. In Pi’s terminal type: sudo journalctl -u cait_webapp.service > /home/pi/cait_webapp.log 2. A log file called cait_webapp.log will be created under /home/pi, please send me this file. Cheers, Michael

@filip Thanks Filip, the errors are useful information, can you please copy the entire Chrome console log of that page and send it to me at michaelng@cortic.ca ?

Can you use Chrome to open http://<hostname>/setup, then go to the device page, and take a screenshot of that page with the developer console open (you can open the console by pressing F12)? An example screenshot is attached below:

@filip We only observed this behaviour when the Pi just booted up. There is a set of services that the CEP needs to start once the device is booted up. When the services were not fully started, we did observe the dropdown boxes became empty. However, the dropdown boxes eventually got filled with device information when we waited on that page for some time (in our tests, the time we waited for was less than 5 minutes). For the sake of testing, can you please do the following? Reboot the CEP device. After the device is booted up, go to http://<hostname>/setup and browse to the device page. If the dropdown boxes are empty, wait for 10 minutes and see if the device appears in the dropdown boxes.

Can you please take a screenshot of the device page in the setup process, for example, mine looks like this:

@filip Does http://<hostname>.local/setup work in CAIT?

@filip In addition to checking for the driver installation, please update the CEP project by running the following commands again: cd cep git pull sudo reboot We have updated the ReSpeaker installation instructions and pushed in a few bug fixes just now.

@filip There is also an option of buying the OAK-D (https://store.opencv.ai/products/oak-d) if you want to try the vision functions now.

@filip Yes, if the respeaker 4-mic array HAT is attached to the Pi and the driver is installed. The setup page will detect that and show it in the Connected microphone list. If you don't see that, it is likely the driver wasn't installed properly. Can you please check your output of arecord -L in the terminal of the Pi? If the driver is installed properly, you should see something similar to the following: sysdefault:CARD=seeed4micvoicec seeed-4mic-voicecard, bcm2835-i2s-ac10x-codec0 ac10x-codec0-0 Default Audio Device dmix:CARD=seeed4micvoicec,DEV=0 seeed-4mic-voicecard, bcm2835-i2s-ac10x-codec0 ac10x-codec0-0 Direct sample mixing device dsnoop:CARD=seeed4micvoicec,DEV=0 seeed-4mic-voicecard, bcm2835-i2s-ac10x-codec0 ac10x-codec0-0 Direct sample snooping device hw:CARD=seeed4micvoicec,DEV=0 seeed-4mic-voicecard, bcm2835-i2s-ac10x-codec0 ac10x-codec0-0 Direct hardware device without any conversions plughw:CARD=seeed4micvoicec,DEV=0 seeed-4mic-voicecard, bcm2835-i2s-ac10x-codec0 ac10x-codec0-0 Hardware device with all software conversions usbstream:CARD=seeed4micvoicec seeed-4mic-voicecard USB Stream Output If you don't see the seeed4micvoicec entries, it indicates the driver was not properly installed, please install the driver again by following our project's README. Best, Michael

Hi Filip, The gray screen problem is now fixed. You can perform the following steps to get the latest update: In the terminal of the Raspberry Pi, execute the following commands: cd cep git pull sudo reboot After the Pi reboots, you should be able to access the setup screen with http://<hostname>/setup.

Hi Filip, I was able to reproduce the gray screen problem on my end. I will push a fix for this later. In the meantime, you can use this link: http://<hostname>.local/setup in the browser, you should be able to see the setup screen this way. Michael

Hi Filip, For your first question regarding the hostname, can you take a screenshot of your browser with the gray screen? We can better debug and identify the problem this way. For the second question, currently, CEP supports the OAK device family running the DepthAI API (including both OAK-D and OAK-D-Lite). There is no support for the Raspberry Pi HQ camera yet. You can purchase an OAK-D if you want to use CEP. Alternatively, if you have a Logitech USB webcam (C270, C922, C615, C310), you can try another project created by us called CAIT (https://github.com/cortictechnology/cait). However, It doesn't have as many vision functions as CEP. If you have any other questions, please feel free to reach out to us. Best, Michael