I can understand why the Teltonika team may not wish to resolve an issue with something they clearly want to discontinue.
However, i’m not always getting emails as i should from the system.
When an event triggers a reboot in the scheduler, i don’t always get the email…
Question: when is the email actually created and sent? Is it created before shutdown? Is it sent before shutdown or after rebooting?
When a startup triggers an event report to send an email, i don’t always get the email…
Question: Is the generation of the first email above preventing the creation of the second email?
Question: If the 1st email is being sent before shutdown, is it not being sent because the system has disconnected the modem too early?
Question: If the emails are saved awaiting startup before being sent, is the system sending the emails before a stable connection is established, therefore failing and the system dumps the email and doesn’t try again.
Are the emails being sent too early, failing and being dumped?
Hello,
As you rightly suspected, since Event Reporting is being deprecated and replaced by Event Juggler, our R&D team is aware of the issue you’ve described regarding email action triggering and modem availability. It’s planned to be addressed and fixed in the 7.16 firmware release.
To clarify a few specific points:
- When using Event Reporting, the email is created and sent before device shutdown when the Event type is set to Reboot and Event subtype to All.
- If the modem disconnects too early during the reboot sequence, the email fails to send, as you suspected.
- Unfortunately, emails are not queued or saved to be sent after startup if they fail; currently, they’re discarded if no connection is available at the time of sending.
You’re also correct in observing that the system doesn’t retry sending failed emails upon reboot. However, as part of the Event Juggler / Reporting Service update in 7.16 firmware, this will be improved; hence, email notifications will be queued and scheduled to send once the connection is restored, with retry and timeout options added.
Best regards,
Thank you for the detailed reply.
What would be nice perhaps is to have an email and or an sms at any time.
If you have a reboot scheduled at 18:00hrs for example an email at 17:50hrs to say that the router will reboot in 1Omins at 18:00hrs. I’m happy to wait until 18:10hrs for an email and or an sms to say reboot was successful.
An email and or an sms at a set time of the day would be nice too.
I would be happy to wait 10mins to get an email and or an sms after an unexpected shutdown too. Move the task away from the reboot / restart process when the routers OS is busy doing other things more important and hasn’t settled down yet.