Replies: 2 comments 1 reply
-
|
If it is not recognized after being connected and configured correctly, that would suggest that swapping SCL/SDA positions is not the "only difference" to the APDS9960. The Tasmota driver code does suggest at least a "minor" additional difference, the APDS9930 having a different chip id. Tasmota/tasmota/tasmota_xsns_sensor/xsns_27_apds9960.ino Lines 58 to 63 in cf739e9 While the "we will check" comment sounds "encouraging", those two constants are not used anywhere in the code. It would be a reasonable experiment to have the existing check for the chip id include the chip ids for APDS9960. |
Beta Was this translation helpful? Give feedback.
-
|
I would definitely test it what lines do I need to compile in Tasmota.
#define APDS9930_CHIPID_1 0x12 // we will check, if someone got an incorrect sensor
#define APDS9930_CHIPID_2 0x39 // there are case reports about "accidentially bought" 9930's
With the lines of the APDS9960 it did not work, it was recognised by the address but nothing was displayed on the Gui and in the log.
Holen Sie sich Outlook für Android<https://aka.ms/ghei36>
…________________________________
From: sfromis ***@***.***>
Sent: Sunday, January 12, 2025 4:00:08 PM
To: arendst/Tasmota ***@***.***>
Cc: Smarthome ***@***.***>; Author ***@***.***>
Subject: Re: [arendst/Tasmota] Support for gesture sensor APDS9930 I2C Bus (Discussion #22806)
If it is not recognized after being connected and configured correctly, that would suggest that swapping SCL/SDA positions is not the "only difference" to the APDS9960. The Tasmota driver code does suggest at least a "minor" additional difference, the APDS9930 having a different chip id.
https://github.com/arendst/Tasmota/blob/cf739e9522ab1a3a388375f9b6d8c1d659657da2/tasmota/tasmota_xsns_sensor/xsns_27_apds9960.ino#L58-L63
#define APDS9960_CHIPID_1 0xAB
#define APDS9960_CHIPID_2 0x9C
#define APDS9960_CHIPID_3 0xA8
#define APDS9930_CHIPID_1 0x12 // we will check, if someone got an incorrect sensor
#define APDS9930_CHIPID_2 0x39 // there are case reports about "accidentially bought" 9930's
While the "we will check" comment sounds "encouraging", those two constants are not used anywhere in the code. It would be a reasonable experiment to have the existing check for the chip id include the chip ids for APDS9960.
https://github.com/arendst/Tasmota/blob/cf739e9522ab1a3a388375f9b6d8c1d659657da2/tasmota/tasmota_xsns_sensor/xsns_27_apds9960.ino#L1818
—
Reply to this email directly, view it on GitHub<#22806 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOBCMCRM5OODB34FR6DYTNL2KJ7PRAVCNFSM6AAAAABVBBZXEGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBRGIZTONQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
You need to have a setup where you can change source code, and then alter the last line I mentioned to have it test for the two chip id from the lines above. Without downloading/installing anything (if you prefer), that can be done using the browser-based Gitpod compile setup linked from https://tasmota.github.io/docs/Compile-your-build/#online-compilers |
Beta Was this translation helpful? Give feedback.
-
Is there a way to compile the APDS9930 gesture sensor in Tasmota? This should not be very different from the APDS9960. The only difference is that SDA and SCL are swapped on the board. The sensor is recognized by the I2C bus in Tasmota. But unfortunately it does not output any data.
I would be happy if someone could integrate the sensor, I would also be.
https://www.broadcom.com/products/optical-sensors/integrated-ambient-light-proximity-sensors/apds-9930
https://github.com/depau/APDS9930
https://www.makerguides.com/apds-9930-proximity-and-light-sensor-with-arduino/
Beta Was this translation helpful? Give feedback.
All reactions