Telegram Notification ... Chat ID = Per Device ?
If you could add in Per Device with Telegram Chat ID attributes in next Traccar release. Then I can save the two units of Raspberry Pi for my other projects.
It is because I need to use that single Admin profile but need multiple Telegram Chat ID attributes made available for Devices entity.
Still doesn't really answer the question. You could do the same thing just by adding 3 "dummy" users that would only be used for notifications. And still have your single admin for managing devices. Anyway, I think we can probably stop this thread now.
I tried the 3 dummy account idea for notification already but the problem is that once a Device ID is already registered in Admin Profile.
The same device id cannot be duplicate register again in the dummy id.
Also if I delete and already registered device id previously. It cannot be registered again.
Why do you need to register the same device twice? You just link the same device to both users.
I tried but dummy user unable to see device registered by admin user.
By the way this is how my Telegram Chat ID group is configured.
Since the dummy user was unable to see device registered by admin user.
Therefore the is no way I could link the same device from admin user to dummy user sadly.
Please advise?
I already commented that you have to link existing devices instead of trying to register the same device twice.
Bingo! I meditated on the powerful words you have advised and I manage to figured out the solution for my case used.
To my surprise all the necessary configuration for Telegram Notification is available for configuration setup.
Settings, Users, Create Dummy Notification Account for my tracker Devices as intended. Then login to the Dummy account to configure as per usual and it works! Telegram Chat ID attributes per user method. No need for per device method as proposed.
Thanks a million my dear guru @nton... You are the greatest teacher who makes his student thinks instead of spoon feeding. But this makes your student learn better via self exploration.
My heart health big thank you!
I am using an existing ADS-B Feeder on Raspberry Pi 3B+ sharing resources with a single instance of TracCar server.
Thanks a lot @nton ... :)
The previous 3 instance tier Traccar Raspberry Pi can now be reused for other projects.
Thanks a lot! For the resources consolidation guide techniques.
This thread can now be closed already since intended task is completed successful already. Thanks @nton :)
This thread origin from this previous posts ...
My custom build Raspberry Pi ADS-B AirPlane Tracker & TracCar GPS Tracker server.
Oh. Sorry I did not understand your question clearly earlier.
Here is the logic as to why I have 3 servers is because I need a single Admin user account.
And use the first instance server Telegram Chat ID attributes to trigger first device Telegram Group Notification by it's own to a certain Telegram char group members.
To have a seamless data flow I uses Server Forward features define in traccar xml to transfer the live data to second instant server.
At second instant server I make changes to another Telegram Chat ID attributes to trigger another device associated to another Telegram chat group.
I repeat the same for third instant server to achieve the same task.
So, what happens is that in order for me to trigger any intended device notification, I uses the same Admin profile Telegram Chat ID attributes.
It is because I need to use that single Admin profile but need multiple Telegram Chat ID attributes, I had to use 3 instant tier method utilising Server.Forward attributes mechanism. And this logical method works great!