You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
the AS3935 from DFRobot Link not be found under ESPHome.
On the same board with ESPEasy and Tasmota this sensor is found with an I2C scan. On Tasmota the sensor works fine.
Board: ESP32DEV
Interface: I2C
Which version of ESPHome has the issue?
v2022.3.0
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2021.12.1
What platform are you using?
ESP32
Board
DEV
Component causing the issue
I2C
Example YAML snippet
i2c:
sda: 21scl: 22scan: true# Example configuration for I²C (decide for one!)as3935_i2c:
address: 0x3irq_pin: 14indoor: false# Example shared configurationsensor:
- platform: as3935lightning_energy:
name: "Lightning Energy"distance:
name: "Distance Storm"binary_sensor:
- platform: as3935name: "Storm Alert"
Anything in the logs that might be useful for us?
NO
Additional information
No response
The text was updated successfully, but these errors were encountered:
I have a similar problem. Same hardware. Can't get it to 'register'.
Slightly different for me: I even have issues in tasmota: arendst/Tasmota#8130 (comment)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
The problem
Hello,
the AS3935 from DFRobot Link not be found under ESPHome.
On the same board with ESPEasy and Tasmota this sensor is found with an I2C scan. On Tasmota the sensor works fine.
Board: ESP32DEV
Interface: I2C
Which version of ESPHome has the issue?
v2022.3.0
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2021.12.1
What platform are you using?
ESP32
Board
DEV
Component causing the issue
I2C
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: