Do you have a link of tag with NDEF technology? What do you use? Can you Modify something to include 213 tag in your app?
1 Like
It’s a limitation I can’t work around.
Just look for NFC tags that support ndef. Not any mifare tags.
Unfortunately Mifare tags seems to be the vast majority out there (also I do seem to remember that the Mifare UltraLight tags were among the tags supported by your app in a post from the 17th Feb).
Having checked the tags, both Ntag213 and Ntag215 support Ndef, so unfortunately we can’t just rely on the Ndef compatibility, as that’s clearly not the reason why they are not being read by the app.
The Ndef explanation makes little sense to me as the tag clearly shows that Ndef is supported.
I’ve stepped down from hasnfc and made due with tasker instead.
However if you could somehow find a way to make these work with your app then that would be great. As someone mentioned before, the majority of nfc tags for sale are NTAG213 or 215
Believe me or not, but this is what I keep finding:
But note that this only works on devices with NXP chipset (MIFARE Classic is proprietary NXP technology. While NXP licenses the card-side to other manufacturers, they do not license the reader-side. Consequently, only1 NXP’s reader products read MIFARE Classic.). On devices with Broadcom chipset, MIFARE Classic cards2 are not detected as MIFARE Classic.
The Mifare tags have been enabled since the start of this app in my code, so they’re on the list of supported tags. If they don’t work then the above quote applies. There’s one last thing that I found and that is to remove these Mifare entries, and replace them with NfcA support, since they should support that. But again, there’s a big chance this will not work because of the above quote.
This is what I use in the app. If this action is not triggered this means there’s a limitation in either Android, the tag, or the way the tag is currently written or formatted.
Yes, that’s correct, but that limitation mainly applies to the Classic ones. I have a OnePlus and several models are somehow incompatible with the Classic ones. That being said, the Ntag 213 and 215 are both UltraLight (not Classic), and they are both compatible with the chipset and the telephone. Another proof is the fact that pretty much any other NFC app is able to work with them (NFC Tools, generic NFC tag readers, etc.), so it can’t be a compatibility problem. I think that, for some reason (I could be wrong, I’m not a programmer) your app doesn’t recognise the tag type correctly. Or could it be that the app is actually incompatible with the way this phone handles NFC communications rather than the tag itself?
I’m on Android 10 if that makes any difference whatsoever.
The apps you mentioned can read the tags in the foreground. They don’t do it in the background while reading the ndef message. That’s the difference. I’m reading the data from the tags in the background in the only way that’s possible on Android with the provided link I found. If anyone knows more about it and thinks it’s possible let me know.
Ok, something that does happen on my phone when I touch the NFC tag with your app open is that the phone vibrates and then a window comes up saying New Tag detected or something like that. That is the same Android app that comes up even if your app is closed. So another explanation could be that Android gives priority to its own NFC tag “detector” over your app. That doesn’t happen with other NFC apps. For example, when I’m in NFC Tools, the default Android NFC Tag “opener” doesn’t activate and the phone leaves NFC Tools to deal with the NFC communications.
I read somewhere that there is a logic behind which app Android opens when it detects NFC tags.
Hope this makes sense to you.
So I managed to find some mifare classic tags and have the same issue. I hope to find some time tomorrow to try and reproduce and fix the issue.
I have just launched Hass NFC 1.2.4 in the store! This should fix the issue some people with Mifare tags have. Sorry for the inconvenience. May take a few hours before it will arrive in your update list.
Thanks, that’s good news! Unfortunately here in the UK the app is still on version 1.2.3
Same here unfortunately. I guess Google is a little slower than usual during the pandemic.
I have just installed the update, it works, thanks!
1 Like
I’m struggling to log in to my HA instance with the app.
I’m using nabu casa, and have also tried it with my local address, but no joy. I get a message saying ‘there seems to be an error: null’
Any pointers?
Additionally, I get this error in the log:
Log Details (WARNING)
Logger: homeassistant.components.http.ban
Source: components/http/ban.py:75
Integration: HTTP (documentation, issues)
First occurred: 2:46:19 (2 occurrences)
Last logged: 2:46:19
Login attempt or request with invalid authentication from 127.0.0.1
So it seems like your address is correct. Most likely your long lived access token is wrong. I assume you’re on a recent version of HA? You have to create a access token from the UI in HA and copy -> paste that in the app.
Yes I’m on the latest HA.
Re the token, that’s exactly what I’ve done too. I’ve actually tried two different tokens.
Anything else that you can think of?
The SSL option isn’t enabled right? (enabled: no SSL).
Can you first try your internal IP-address to be 100% sure there’s nothing on the outside that’s blocking it? So have your phone on the WiFi and then try to connect. If you’re sure there’s no spaces or anything in the token it should work. I have heard from someone that removing the app and installing it again fixed it aswell (maybe clear cache and data?). Let me know if any of that works.
1 Like
Not quite sure what worked, but I created a new token, removed the app, reinstalled the app and pasted the details again (tried with both local and external address).
All looking good now. Just waiting for some NFC tags to be delivered to have a play.
1 Like
Just in terms of the actual tags. I’m not well educated on these and just ordered the first thing that popped up on Amazon.
Are these likely to work?
Never used that type, but I believe they should be fine. A quick search tells me they support NDEF messages, so that’s what’s needed.
2 Likes