@tsimons78 That’s odd! The order of the payload shouldn’t matter in theory. Need to look up the code to see what’s what. So in Android 4.4 you first get the auth, and then the other data, and in recent Android versions you first get the data?
Hass NFC does not write a log anywhere right now. I can look into that if that would help.
@greyno It depends on how much data you’re gonna put on it. I have a tag that’s 716 bytes and currently 130 bytes are used for toggling a service. So it’s gonna be tight, but if you keep names of scripts etc short it should be fine.
For whoever left feedback in the play store thanks! But it would be great to have it in the public version. I don’t think other people can see beta feedback.
@tsimons78 yeah you can enroll again. But I’m not planning to release a beta specific release so you might as well stay in the public release channel. But you guys don’t have to do all this trouble if you don’t want to
I tried Hass NFC app, and like the easy way to select Services and run them, but I found that most of the tasks will require more than what the NFC tags can store.
I use this ones:
I also tried the app “NFC Tools PRO” and android app " HTTP Request Shortcuts" for easy running curl commands.
All work fine, but I still get issues because of lack of memory.
As of now I need NFC-tags that can store 234 Bytes to run any shortcuts I think.
Any suggestions how to start scenes and automations when I only have 144 bytes?
It would be great if the scenes and automations can be triggered as a url, without installing any additional apps on the device.
use Favorites in your browser, but should work only with GEt and not POST. I use a lot widget made with HTTP shortcut. Its just a tap on the screen, without opening the app
I’m planning to launch actions based on the ID of the NFC tag, so the payloads are stored on your device. The drawback will be that this only works on a specific device.
You can use the ‘simple write’ option. This stores less data on the tag. The drawback of this is that you can only run scripts from HASS. So this might be a workaround for now.
In my head, the solution must come in the lovelace frontend.
A easy way to call a entity or curl script and get a URL for it, as we can do with BADGES in lovelace.
If I havn’t missunderstood, this is allready posible today with
javascript and “extra_html_url:” where you can load a html page in lovelace.
Has anyone else had the problem that the app seems to load no data to choose entities or services from?
I am using http (not ‘s’) as I use Nabu Casa. Whether I enter http://hassio.local:8123 or http://192.168.20.18:8123, I seem to get no connection. No drop downs work, and if I try to manually enter ascript in the ‘simple’ write form, it will write to a tag, but them throw an error when reading.
Yep, definitely unchecked use https. I actually bought this app back when you very first released it. Have been playing with it on and off to try get it working, but no luck. Seeing as everyone else seems pretty good with it, there may be something perculiar about my set-up? The check config button you mentioned sounds like a great idea.
)