Esphome native and NDEF #52

jesserockz · 2020-10-12T00:17:33Z

This PR uses native esphome components that have been recently developed and requires that you use ESPHome 1.16.0.

closes #41

What is this?

This PR switches to use the ESPHome native version of pn532_i2c and also as an extension to that NDEF reading and writing.

I2C-version of the schematics screenshot Delete tag_reader_schematics_v1.png Update README.md Using relative links for schematics screenshot

RichieFrame · 2020-10-31T06:42:48Z

Testing this now with a custom yaml, working much better than the non-native i2c version, which would only read a tag if it was on the reader during boot, then not read anymore once it was removed (#54 on steroids).

Thanks to a bad reader board this took 2 days to get working, with the non-native code, there was no error, this actually reports the board bad:

[01:39:46][C][pn532:015]: Setting up PN532...
[01:39:46][W][i2c:076]: Unknown transmit error 4 for address 0x24
[01:39:46][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
..
[01:39:46][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[01:39:46][E][pn532:019]: Error sending version command
[01:39:46][E][component:092]: Component was marked as failed.

RichieFrame · 2020-10-31T08:33:06Z

ESP32 test did not go so hot, it did work using SPI, but this is what I get with native i2c:

[03:21:49][C][pn532:015]: Setting up PN532...
[03:21:49][D][pn532:030]: Found chip PN532
[03:21:49][D][pn532:031]: Firmware ver. 1.6

[03:21:49][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[03:21:49][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[03:21:49][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[03:21:49][E][esp32-hal-i2c.c:1426] i2cCheckLineState(): Bus Invalid State, TwoWire() Can't init sda=1, scl=0
[03:21:49]
[03:21:49][E][esp32-hal-i2c.c:1426] i2cCheckLineState(): Bus Invalid State, TwoWire() Can't init sda=1, scl=0
[03:21:49][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[03:21:50][E][esp32-hal-i2c.c:1426] i2cCheckLineState(): Bus Invalid State, TwoWire() Can't init sda=1, scl=0
[03:21:50][W][i2c:086]: Requesting 1 bytes from 0x24 failed!

[03:21:50][E][esp32-hal-i2c.c:1426] i2cCheckLineState(): Bus Invalid State, TwoWire() Can't init sda=1, scl=0
[03:21:50][W][i2c:076]: Unknown transmit error 5 for address 0x24
[03:21:50][E][esp32-hal-i2c.c:1426] i2cCheckLineState(): Bus Invalid State, TwoWire() Can't init sda=1, scl=0
[03:21:50][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[03:21:50][E][esp32-hal-i2c.c:1426] i2cCheckLineState(): Bus Invalid State, TwoWire() Can't init sda=1, scl=0
[03:21:50][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[03:21:50][W][pn532:087]: Requesting tag read failed!

With that final block of 7 lines repeating every second after until i kill the serial connection

I am using GPIO 21 and 22 for SDA and SCL, tested with 5V and 3.3V power, 100KHz and 200KHz
Not sure if that is a board issue or not, those were the same pins I was using for SPI CLK and MISO and they worked

jesserockz · 2020-10-31T09:56:08Z

Oh man, thats going to be hard to look into as I do not have an esp32 to test with...
A very quick google brings this: espressif/arduino-esp32#3079 Might need pullups on the esp32?

RichieFrame · 2020-10-31T11:54:43Z

Interesting, when I get time I will try that. I have 2.2K and 1K that I can put in series to get pretty close, or I can do 22K x 2 + 4.7K and that will get me to 3.293K

RichieFrame · 2020-10-31T14:51:15Z

Actually, I just went through the NXP electrical bus specs for I2C and the Espressif I2C driver parameters... there are pullups on those pins, but they are not sufficient for I2C, and they have to be enabled in the driver, and tuned to both the bus frequency and capacitance.

I calculated a minimum of 1K and a max of 3.6K @ 400KHz. 4.7K @ 200KHz is confirmed working now on a breadboard.

It might also be recommended to add an inline current limiting resistor, for the device, I cant find a board schematic but I can see resistors on the SPI bus pins only

balloob · 2020-11-03T08:47:24Z

tagreader.yaml

+              std::string uri = "https://www.home-assistant.io/tag/";
+              for (int i = 0; i < 8; i++)
+                uri += alphanum[random_uint32() % (sizeof(alphanum) - 1)];
+              uri += "-";


This is optional. For HA any random string works. I guess it makes it more readable / mimics what iOS and Android write.

balloob · 2020-11-03T08:50:03Z

Do we need to update the README to specify the version of ESPHome that is needed?

adonno · 2020-11-03T09:01:17Z

Do we need to update the README to specify the version of ESPHome that is needed?

Wouldn't hurt ?

balloob · 2020-11-03T15:34:04Z

This is not about hurting. This is about if the native integration requires a minimum version of ESPHome.

RichieFrame · 2020-11-04T22:47:23Z

I would suggest increasing the polling rate, with the old SPI it was always on and responded instantly, now there can be a delay that exceeds the amount of time someone is willing to hold when 'tapping' a card to the reader.

I would also suggest moving the polling rate control from static code in the driver python file and into the config yaml code, having a default of 500ms unless changed, (with 0 for no sleep), I set it to 250ms to test, and it is getting warmer (less than +10c), but not hot like SPI did (+30c)

jesserockz · 2020-11-04T23:14:22Z

Hi @RichieFrame
You can change the polling rate by using the below

pn532_i2c:
  update_interval: 500ms
  ...

RichieFrame · 2020-11-04T23:28:25Z

and that works!

I did do more testing, 350ms seems to be the best balance of power/responsiveness so far, temp is about +6.5c over ambient

RichieFrame · 2020-11-11T15:22:15Z

To confirm, the code is not in place to write MIME records correct? I assume it can read them with the correct esphome code?

What about checking the tag capacity prior to writing data? What happens if we try to write more data than the tag can hold?

jesserockz · 2020-11-11T17:25:31Z

At the moment, there are helpers in the NdefMessage in ESPHome to message.add_text_record and message.add_uri_record but you can always make a new NdefRecord(...) with the data that you want and just call message.add_record(record).

Currently there is no capacity check for a mifare classic card. The ultralight/type 2 cards do check the capacity first as they are known to be smaller. Im not sure what happens if you do try to write more

dcjona · 2020-11-26T08:23:02Z

hi, is it possible to install your branch on docker?

Added restore_state: true to both the Buzzer switch and the LED switch so the user doesn't have to create an automaton just to keep the visual and audible feedback on.

Added restore_state to the switches

jesserockz and others added 3 commits October 11, 2020 20:53

Use ESPHome native (branched) pn532_i2c and ndef reading

8ad7aba

Updated schematics project for I2C/5V

93cdd68

I2C-version of the schematics screenshot Delete tag_reader_schematics_v1.png Update README.md Using relative links for schematics screenshot

Switch the switches

53ea53a

jesserockz mentioned this pull request Oct 12, 2020

Unstable WiFi connection #44

Closed

jesserockz added 2 commits October 12, 2020 20:30

Merge branch 'master' into esphome-native

2d5f6db

Remove whitespace

bfc615e

jesserockz added the hacktoberfest-accepted label Oct 12, 2020

This was referenced Oct 16, 2020

D1 Mini won't boot with PN532 power connected #34

Closed

No scan after a few minutes #54

Closed

jesserockz marked this pull request as ready for review November 2, 2020 19:27

balloob reviewed Nov 3, 2020

View reviewed changes

balloob approved these changes Nov 3, 2020

View reviewed changes

balloob mentioned this pull request Nov 5, 2020

Utilize pn532_i2c from ESPHome dev #60

Merged

jesserockz changed the title ~~Esphome native~~ Esphome native and NDEF Nov 5, 2020

Merge branch 'master' into esphome-native

c77f957

insajd mentioned this pull request Nov 25, 2020

RFID Card and NFC Phone | Inconsistent behaviour #76

Closed

laithalsunni and others added 6 commits December 15, 2020 00:48

Added restore_state to the switches

2830dd1

Added restore_state: true to both the Buzzer switch and the LED switch so the user doesn't have to create an automaton just to keep the visual and audible feedback on.

Merge pull request #85 from laithalsunni/patch-1

4e74590

Added restore_state to the switches

Update README to point to ESPHome Beta

975a1b3

Merge branch 'master' into esphome-native

95cb3b3

Update README.md

bad2bc3

Remove continuous as it had an issue

d53a9b1

adonno merged commit 193dd73 into master Feb 4, 2021

jesserockz deleted the esphome-native branch October 18, 2021 20:38

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Esphome native and NDEF #52

Esphome native and NDEF #52

jesserockz commented Oct 12, 2020 •

edited

RichieFrame commented Oct 31, 2020 •

edited

RichieFrame commented Oct 31, 2020

jesserockz commented Oct 31, 2020

RichieFrame commented Oct 31, 2020

RichieFrame commented Oct 31, 2020

balloob Nov 3, 2020

balloob commented Nov 3, 2020

adonno commented Nov 3, 2020

balloob commented Nov 3, 2020

RichieFrame commented Nov 4, 2020

jesserockz commented Nov 4, 2020

RichieFrame commented Nov 4, 2020

RichieFrame commented Nov 11, 2020

jesserockz commented Nov 11, 2020

dcjona commented Nov 26, 2020

Esphome native and NDEF #52

Esphome native and NDEF #52

Conversation

jesserockz commented Oct 12, 2020 • edited

What is this?

RichieFrame commented Oct 31, 2020 • edited

RichieFrame commented Oct 31, 2020

jesserockz commented Oct 31, 2020

RichieFrame commented Oct 31, 2020

RichieFrame commented Oct 31, 2020

balloob Nov 3, 2020

Choose a reason for hiding this comment

balloob commented Nov 3, 2020

adonno commented Nov 3, 2020

balloob commented Nov 3, 2020

RichieFrame commented Nov 4, 2020

jesserockz commented Nov 4, 2020

RichieFrame commented Nov 4, 2020

RichieFrame commented Nov 11, 2020

jesserockz commented Nov 11, 2020

dcjona commented Nov 26, 2020

jesserockz commented Oct 12, 2020 •

edited

RichieFrame commented Oct 31, 2020 •

edited