config.lua 4.0 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091
  1. return {
  2. -- 通知类型, 支持配置多个
  3. -- NOTIFY_TYPE = {"custom_post", "telegram", "pushdeer", "bark", "dingtalk", "feishu", "wecom", "pushover", "inotify", "next-smtp-proxy", "gotify", "serial"},
  4. NOTIFY_TYPE = "custom_post",
  5. --
  6. -- 角色类型, 用于区分主从机, 仅当使用串口转发 NOTIFY_TYPE = "serial" 时才需要配置
  7. -- MASTER: 主机, 可主动联网; SLAVE: 从机, 不可主动联网, 通过串口发送数据
  8. ROLE = "MASTER",
  9. --
  10. -- custom_post 通知配置, 自定义 POST 请求, CUSTOM_POST_BODY_TABLE 中的 {msg} 会被替换为通知内容
  11. CUSTOM_POST_URL = "https://sctapi.ftqq.com/<SENDKEY>.send",
  12. CUSTOM_POST_CONTENT_TYPE = "application/json",
  13. CUSTOM_POST_BODY_TABLE = {["title"] = "这里是标题", ["desp"] = "这里是内容, 会被替换掉:\n{msg}\n{msg}"},
  14. --
  15. -- telegram 通知配置, https://github.com/0wQ/telegram-notify 或者自行反代
  16. TELEGRAM_API = "https://api.telegram.org/bot{token}/sendMessage",
  17. TELEGRAM_CHAT_ID = "",
  18. --
  19. -- pushdeer 通知配置, https://www.pushdeer.com/
  20. PUSHDEER_API = "https://api2.pushdeer.com/message/push",
  21. PUSHDEER_KEY = "",
  22. --
  23. -- bark 通知配置, https://github.com/Finb/Bark
  24. BARK_API = "https://api.day.app",
  25. BARK_KEY = "",
  26. --
  27. -- dingtalk 通知配置, https://open.dingtalk.com/document/robots/custom-robot-access
  28. -- 如果是加签方式, 请填写 DINGTALK_SECRET, 否则留空为自定义关键词方式, https://open.dingtalk.com/document/robots/customize-robot-security-settings
  29. DINGTALK_WEBHOOK = "",
  30. DINGTALK_SECRET = "",
  31. --
  32. -- feishu 通知配置, https://open.feishu.cn/document/ukTMukTMukTM/ucTM5YjL3ETO24yNxkjN
  33. FEISHU_WEBHOOK = "",
  34. --
  35. -- wecom 通知配置, https://developer.work.weixin.qq.com/document/path/91770
  36. WECOM_WEBHOOK = "",
  37. --
  38. -- pushover 通知配置, https://pushover.net/api
  39. PUSHOVER_API_TOKEN = "",
  40. PUSHOVER_USER_KEY = "",
  41. --
  42. -- inotify 通知配置, https://github.com/xpnas/Inotify 或者使用合宙提供的 https://push.luatos.org
  43. INOTIFY_API = "https://push.luatos.org/XXXXXX.send",
  44. --
  45. -- next-smtp-proxy 通知配置, https://github.com/0wQ/next-smtp-proxy
  46. NEXT_SMTP_PROXY_API = "",
  47. NEXT_SMTP_PROXY_USER = "",
  48. NEXT_SMTP_PROXY_PASSWORD = "",
  49. NEXT_SMTP_PROXY_HOST = "smtp-mail.outlook.com",
  50. NEXT_SMTP_PROXY_PORT = 587,
  51. NEXT_SMTP_PROXY_FORM_NAME = "Air780E",
  52. NEXT_SMTP_PROXY_TO_EMAIL = "",
  53. NEXT_SMTP_PROXY_SUBJECT = "来自 Air780E 的通知",
  54. --
  55. -- smtp 通知配置(可能不支持加密协议)
  56. SMTP_HOST = "smtp.qq.com",
  57. SMTP_PORT = 25,
  58. SMTP_USERNAME = "",
  59. SMTP_PASSWORD = "",
  60. SMTP_MAIL_FROM = "",
  61. SMTP_MAIL_TO = "",
  62. SMTP_MAIL_SUBJECT = "来自 Air780E 的通知",
  63. SMTP_TLS_ENABLE = false,
  64. --
  65. -- gotify 通知配置, https://gotify.net/
  66. GOTIFY_API = "",
  67. GOTIFY_TITLE = "Air780E",
  68. GOTIFY_PRIORITY = 8,
  69. GOTIFY_TOKEN = "",
  70. --
  71. -- 定时查询流量间隔, 单位毫秒, 设置为 0 关闭 (建议检查 util_mobile.lua 文件中运营商号码和查询代码是否正确, 以免发错短信导致扣费, 收到查询结果短信发送通知会消耗流量)
  72. QUERY_TRAFFIC_INTERVAL = 0,
  73. --
  74. -- 定时基站定位间隔, 单位毫秒, 设置为 0 关闭 (定位成功后会追加到通知内容后面, 基站定位本身会消耗流量, 通知内容增加也会导致流量消耗增加)
  75. LOCATION_INTERVAL = 0,
  76. --
  77. -- 定时上报间隔, 单位毫秒, 设置为 0 关闭 (定时触发消息上报)
  78. REPORT_INTERVAL = 0,
  79. --
  80. -- 开机通知 (会消耗流量)
  81. BOOT_NOTIFY = true,
  82. --
  83. -- 通知内容追加更多信息 (通知内容增加会导致流量消耗增加)
  84. NOTIFY_APPEND_MORE_INFO = true,
  85. --
  86. -- 通知最大重发次数
  87. NOTIFY_RETRY_MAX = 20,
  88. --
  89. -- 本机号码, 优先使用 mobile.number() 接口获取, 如果获取不到则使用此号码
  90. FALLBACK_LOCAL_NUMBER = "+8618888888888",
  91. }