New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need To Know Device Ping For Expired Devices #5238
Comments
Hi, I would like to be able to collaborate with this feature since I have already done it a couple of times for custom servers |
How can we help you? If you need more information please mention it here. |
The UI doesn't really look very good. It also seems unrelated to the request. Request is about the backend changes. |
That's right, friend Antom, that's why I took it as an example since it's a totally different website from Modern, I just want to take it as a reference if that's what you're requesting, the example is a website that works with Traccar through Websockect |
Dear Anton, Many many thanks for your great project.
when a device was expired we don't know the device is in working condition or not.
An Example: A device was expired 2 months ago and in this time the device power connection was broken.
Now an user pay 1 month subscription fee and device is now active in server side but in device side device power connection was broken.
Now this user one month subscription will be wasted.
So if our server show a ping icon in every device then customer know this device has a problem and they not make a payment for this type of device.
In above picture there are two devices in expired condition. Now as a customer we don't know this devices are in active condition and make a payment then device will be in Online condition.
In above picture we make payment for both device and "Car-01" is now online but "Car-02" is offline because of the "Car-02" physical wiring connection was broken.
So As a customer we want to know about device condition before make a payment.
Thanks a lot for your great work.
The text was updated successfully, but these errors were encountered: