Have never had issues with this before, but when I make a new template on the desktop site it automatically creates a device on the mobile app but when the device is connect the tile disappears from the mobile app and gives me the startup page not just a blank page, everything on desktop side is fine but can’t acess anything on mobile app.
If I click developer mode I can see my template as well as a quick start template but it will not allow me to view in the actual device tab…
Kinda Solved. So didn’t realize the template name and Id were used for the mobile app pairing… simple fix but defeats the purpose of fowarding with auth code if it won’t be able to pair to the mobile app too on just that . So if I were using a tzapu wifi manager setup would I need to foward id,template name, & auth code too??? Most examples i saw only relied on forwarding auth code so is this normal behavior or are those just bad examples @PeteKnight @Gunner
You need to clarify what you mean when you say:
Forwarding what, from where to where, and for what purpose?
Sorry I more meant for a new device in general. The forwarding is more arbitrary in this case, so basically I just mean for any new device to connect to the mobile app does it need all three parameters (auth, template name, id) prior to Blynk server connection.
I’m using tzapu wifi manager to allow user input wifi credentials and custom parameter slot for Blynk auth code to be sent to the device for start up.
I have no issue connecting to desktop with only auth code added but not the mobile app (it hides the tile on app if hardcoded template name & id doesn’t match auth code)
@PeteKnight just was wondering if this is normal behavior on Blynk end because I can have the user input template name and I’d if needed in start up.
But as of now was a headache to have the templates be hidden from use. Just to clarify I’m saying if I were to hardcode any template like the quick start template auth code but hardcoded a template name and Id of a different template it seems to delete the mobile tile associated with the auth code from being used. Still appears in the template for developer mode but not useable.
I’m really not following what you are saying or trying to achieve at all.
If you use the Edgent example then the device simply needs that two lines of firmware code from the template screen.
Then, when the device is powered-up it sits in “awaiting provisioning” mode.
You then open the app and choose “+ Add Device” and enter the WiFi credentials. At this point, an Auth token is dynamically assigned by the Blynk server and stored in the device’s NVRAM.
That’s it, you don’t need to do anything else.
But I think the disconnect we have is u say the auth code is linked but I’m saying I think they also need to link the template name and Id as well.
I technically I’m doing what the software already allows but with tzapu but since I’m not sending linking the template name and id the mobile side doesn’t work… @PeteKnight
Main objective was to have it easier to switch template with single device without setting up on computer side just restarting device with new auth code. Seems the mobile side is linked differently than the desktop side which is strange to me…
As I explained, these two lines of code from the template screen are hard-coded into the sketch.
I understand all of the individual words, but I have no idea what you mean in practice, especially the “sending” part, which I’ve already said I’m guts not understanding.
That’s not really possible, the template ID needs to be hard-coded as far as I know.
I don’t think they are “linked differently” but maybe behave differently when you make an unexpected change.
Well the mobile side relies on template name/id in addition to auth and the desktop seems to rely on solely auth. Makes sense based on how set up process is. By send I just mean a user input no specific way being sent just like non hardcoded user input parameters for logging in and connecting @PeteKnight.
But thanks for the help guess I’ll hard code template name and id wanted a generic software to avoid all that!
No, I don’t believe that this is correct.
Template ID is the primary link, and it’s a one to many relationship between template and devices.
Then Blynk term is Dynamic Provisioning. It’s well covered in the documentation.
Currently have it connected with invalid temp name and id as I switched auth code in the dynamic provisioning of the device but not the other two parameters from previous code. Everything works fine but the mobile app is non existent. That’s why I was confused seems to go against normal expected behavior. @PeteKnight
You’re going to have to make an effort to explain things in much more detail, as statements like…
make no sense to me.
I hardcoded the correct auth code, an incorrect template name, and an incorrect id. I wanted to test which parameters were actually needed for my program to run and connect to Blynk.
From my test I was able to connect Blynk and access via desktop but not the mobile app
(with only using the authentication code in my program…the other two parameters had random strings not the actual id and name)