[{"data":1,"prerenderedAt":8200},["ShallowReactive",2],{"blog-scenario-four-iot-timer-modes":3,"other_blogs":979},{"id":4,"title":5,"automation":6,"body":7,"buy":6,"category":6,"categorySlug":6,"createdAt":967,"description":968,"deviceRefs":6,"difficulty":6,"estimatedTime":6,"extension":969,"headpic":17,"image":6,"industry":6,"industrySlug":6,"keywords":6,"links":6,"meta":970,"model":6,"name":6,"navigation":971,"path":972,"protocol":6,"scenario":6,"scenarioSlug":6,"seo":973,"stem":974,"tagSlugs":975,"tags":6,"vendor":6,"website":6,"__hash__":978},"content/blog/scenario-four-iot-timer-modes.md","四种物联网定时模式，覆盖农业、市政、工业、能源全场景",null,{"type":8,"value":9,"toc":934},"minimark",[10,18,24,27,32,40,43,59,65,72,75,77,81,84,159,170,177,180,182,186,192,197,200,211,219,223,230,236,243,247,250,258,261,333,341,343,347,358,362,365,374,380,387,391,394,402,406,412,415,487,494,496,500,510,514,517,524,533,540,544,547,555,559,562,567,570,639,646,648,652,662,666,669,674,680,687,691,694,699,703,706,712,715,785,792,794,798,801,862,868,870,873,879,882,885,888,890,895],[11,12,13],"p",{},[14,15],"img",{"alt":16,"src":17},"articles/2024/20260516212326_090feb3c87b7e5129d5ae68d833aea48.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260516212326_090feb3c87b7e5129d5ae68d833aea48.png",[19,20,21],"blockquote",{},[11,22,23],{},"ThingsCloud 内置四种定时属性类型——定点触发、区间持续、延时关闭、间歇循环，配合列表管理轻松应对多组定时策略。在多用户体系下，平台方一次配置，终端用户即可在 App 中自主管理，无需平台介入。",[25,26],"hr",{},[28,29,31],"h2",{"id":30},"定时是物联网最被低估的能力","定时，是物联网最被低估的能力",[11,33,34,35,39],{},"说起物联网，很多人第一反应是远程控制、实时监测、数据大屏。但对于真正跑在一线的项目而言，",[36,37,38],"strong",{},"\"定时\"才是那个每天被调用最频繁、最能帮客户省钱省力的核心功能","。",[11,41,42],{},"想象一下这些场景：",[44,45,46,50,53,56],"ul",{},[47,48,49],"li",{},"农场主凌晨 5 点起床去大棚手动卷膜通风，中午 12 点再跑去关——风雨无阻，一年 365 天。",[47,51,52],{},"物业师傅每天骑着电动车巡检路灯，手动开关控制箱，夏天 7 点开灯，冬天 6 点就得开，全靠经验。",[47,54,55],{},"污水处理厂的操作工三班倒，只为在特定时段启停曝气设备，电费单子一出来，老板直摇头。",[47,57,58],{},"储能电站的管理员盯着峰谷电价表，到点手动切换充放电模式，稍不留神就错过最佳窗口。",[11,60,61,62],{},"这些场景有一个共同特征：",[36,63,64],{},"设备需要按照预设的时间规律自动运行，而不是靠人现场操作。",[11,66,67,68,71],{},"传统的解决方案往往是在设备本地写死定时逻辑，或者用 PLC 编程。问题是，一旦养殖周期变了、季节更替了、政策调整了，修改定时策略就得派人去现场刷固件或改程序，耗时耗力还容易出错。更麻烦的是，当项目面向",[36,69,70],{},"多终端用户","时，平台方根本不可能为每个用户单独维护一套定时策略。",[11,73,74],{},"而利用 ThingsCloud 平台，您只需在设备类型中配置好定时属性，并将其绑定到 ThingsX App 的对应组件上。此后，每台设备的定时策略由终端用户自己在手机上管理——添加、修改、删除、启用、禁用，全部即时生效，完全不需要平台方介入。无论是 100 台设备还是 10 万台设备，平台端的配置工作量是一样的。",[25,76],{},[28,78,80],{"id":79},"四种定时模式一次讲清楚","四种定时模式，一次讲清楚",[11,82,83],{},"ThingsCloud 将设备定时抽象为四种核心模式，每种都有\"单条\"和\"列表\"两种形态。单条适合固定策略，列表则让用户可以自主添加、删除、编辑多组定时，灵活度拉满。",[85,86,87,103],"table",{},[88,89,90],"thead",{},[91,92,93,97,100],"tr",{},[94,95,96],"th",{},"模式",[94,98,99],{},"一句话理解",[94,101,102],{},"适用场景关键词",[104,105,106,120,133,146],"tbody",{},[91,107,108,114,117],{},[109,110,111],"td",{},[36,112,113],{},"每日定时器",[109,115,116],{},"到点执行一次",[109,118,119],{},"定点开关、定时投喂、准点提醒",[91,121,122,127,130],{},[109,123,124],{},[36,125,126],{},"每日定时区间",[109,128,129],{},"从 A 点到 B 点持续生效",[109,131,132],{},"照明时段、通风窗口、营业模式",[91,134,135,140,143],{},[109,136,137],{},[36,138,139],{},"每日定时时长",[109,141,142],{},"到点触发，持续 N 秒后自动停止",[109,144,145],{},"延时关闭、定量运行、临时任务",[91,147,148,153,156],{},[109,149,150],{},[36,151,152],{},"每日间歇定时",[109,154,155],{},"在区间内每隔 N 分钟执行 M 分钟",[109,157,158],{},"循环喷淋、间歇曝气、定时采样",[11,160,161,162,165,166,169],{},"四种模式都支持",[36,163,164],{},"按周天重复","和",[36,167,168],{},"多时区设置","——你可以让设备工作日和周末跑不同策略，也可以让部署在东京、迪拜、纽约的设备各自遵循本地时间运行。",[11,171,172,173,176],{},"更重要的是，",[36,174,175],{},"四种定时类型都配有 ThingsX App 专用组件","。在多用户体系下，这意味着终端用户不需要理解技术概念，也不需要联系平台管理员，直接在手机上就能完成查看、添加、修改、删除定时策略的全部操作。无论是养殖户在塘口调整投喂时间，还是物业经理在办公室修改路灯策略，动动手指即可完成，真正实现了定时管理的去中心化。",[11,178,179],{},"下面，我们分行业看看这四种定时模式如何在真实项目中创造价值。",[25,181],{},[28,183,185],{"id":184},"智慧农业让设备替人守大棚","智慧农业：让设备替人守大棚",[11,187,188,189,39],{},"农业物联网的本质，是用自动化替代重复性农事劳动。而定时功能，恰恰是自动化的基石。更关键的是，农业项目通常面向成百上千的种植/养殖户，",[36,190,191],{},"每个用户的养殖周期、作物类型、大棚环境都不同，定时策略不可能由平台方统一预设",[193,194,196],"h3",{"id":195},"定时投喂精准到分钟","定时投喂，精准到分钟",[11,198,199],{},"水产养殖中，饲料投喂时间和频次直接影响鱼虾的生长速度和饵料系数。传统靠人工投喂，不仅凌晨、深夜得有人守着，还容易过量或不足。",[11,201,202,203,206,207,210],{},"使用",[36,204,205],{},"每日定时器列表","，养殖户可以直接在 ",[36,208,209],{},"ThingsX App"," 上设置一天多组投喂时间——清晨 6:30、中午 11:00、傍晚 17:00 各一次，系统到点自动触发投料机。随着养殖周期推进，用户自己在手机上就能增减投喂频次、调整时间点，不需要联系平台管理员，也不用跑塘口。",[19,212,213],{},[11,214,215,218],{},[36,216,217],{},"多用户价值","：平台方只需在设备类型中配置一个定时器列表属性，所有养殖户各自在 App 上管理自己的投喂计划。A 用户养虾需要一天 4 餐，B 用户养鱼只需 2 餐，C 用户进入育肥期临时加一餐——全部自主完成，平台端零干预。",[193,220,222],{"id":221},"间歇灌溉节水又护根","间歇灌溉，节水又护根",[11,224,225,226,229],{},"大棚滴灌最怕\"一灌到底\"。土壤持续过湿会导致根系缺氧、病害滋生。智慧灌溉的正确做法是",[36,227,228],{},"间歇进行","：在白天 8:00 到 18:00 之间，每隔 2 小时灌溉 15 分钟。",[11,231,232,233,235],{},"这正是",[36,234,152],{},"的典型用例。设置起始时间 08:00、结束时间 18:00、间隔 2 小时（7200 秒）、单次持续 15 分钟（900 秒），系统会自动生成 8:00、10:00、12:00、14:00、16:00 五个执行点。相比持续灌溉，间歇模式可节水 30% 以上，作物长势反而更好。",[19,237,238],{},[11,239,240,242],{},[36,241,217],{},"：不同作物对灌溉节奏的需求差异很大。叶菜类需高频短时，果树类需低频长时。平台方无需为每种作物预制模板，用户自己在 App 上调整间隔和时长即可，千棚千面。",[193,244,246],{"id":245},"卷膜通风分时段自动调节","卷膜通风，分时段自动调节",[11,248,249],{},"温室大棚的卷膜机需要在中午高温时段通风降温，傍晚再关闭保温。不同季节，通风的起止时间差异很大。",[11,251,202,252,254,255,257],{},[36,253,126],{},"，夏季设置 10:00-16:00 自动开膜，冬季调整为 12:00-14:00，春秋再另设一档。几组区间配置在 ",[36,256,209],{}," 里一目了然，换季时用户在手机上自行切换即可。",[193,259,260],{"id":260},"农业场景价值总结",[85,262,263,276],{},[88,264,265],{},[91,266,267,270,273],{},[94,268,269],{},"痛点",[94,271,272],{},"传统方式",[94,274,275],{},"ThingsCloud 定时方案",[104,277,278,289,300,311,322],{},[91,279,280,283,286],{},[109,281,282],{},"凌晨/深夜需人工投喂",[109,284,285],{},"专人守塘，人工投料",[109,287,288],{},"定时器列表自动触发，精准无遗漏",[91,290,291,294,297],{},[109,292,293],{},"持续灌溉导致烂根",[109,295,296],{},"凭经验手动开关阀门",[109,298,299],{},"间歇定时自动循环，节水护根",[91,301,302,305,308],{},[109,303,304],{},"季节变化需频繁调整策略",[109,306,307],{},"现场改 PLC 程序",[109,309,310],{},"App 远程修改，即时生效",[91,312,313,316,319],{},[109,314,315],{},"一人管理多个大棚",[109,317,318],{},"逐个巡检，疲于奔命",[109,320,321],{},"所有设备定时策略集中管理",[91,323,324,327,330],{},[109,325,326],{},"多用户策略差异大",[109,328,329],{},"平台需为每个用户定制",[109,331,332],{},"用户自主配置，平台一次配置全网复用",[19,334,335],{},[11,336,337,340],{},[36,338,339],{},"价值量化","：以一个 50 亩的水产养殖基地为例，接入自动投喂和增氧定时系统后，人工巡检频次从每天 4 次降至每周 2 次，每年节省人工约 2.4 万元；间歇灌溉方案节水 30%，按水费+电费折算，每年再省 1-2 万元。",[25,342],{},[28,344,346],{"id":345},"智慧城市让公共设施学会自己上班","智慧城市：让公共设施学会\"自己上班\"",[11,348,349,350,353,354,357],{},"城市里的路灯、景观照明、公园灌溉、交通诱导屏——这些数量庞大、分布零散的基础设施，最大的管理成本不是电费，而是",[36,351,352],{},"人力巡检和现场操作","。当智慧路灯项目覆盖多个城区、由不同物业分管时，",[36,355,356],{},"统一的平台配置 + 分权分域的用户自主管理","变得尤为重要。",[193,359,361],{"id":360},"路灯多组策略一年四季各不同","路灯多组策略，一年四季各不同",[11,363,364],{},"很多城市的路灯管理至今仍靠\"光控+时控箱\"，夏天天黑得晚、冬天黑得早，时控箱需要物业师傅定期去调。如果遇上暴雨天能见度低，还得手动提前开灯。",[11,366,202,367,370,371,373],{},[36,368,369],{},"每日定时区间列表","，可以预先配置多套照明策略：夏季模式（19:30-次日 5:30）、冬季模式（17:30-次日 7:00）、节能模式（深夜 0:00-5:00 半功率运行）。换季时，物业人员直接在 ",[36,372,209],{}," 上切换策略模板即可，不需要跑现场，也不需要找平台技术支持。",[11,375,376,377,39],{},"更精细的做法是，将路灯分组管理，主干道、次干道、背街小巷各自配置不同的定时区间，实现",[36,378,379],{},"分区分时照明控制",[19,381,382],{},[11,383,384,386],{},[36,385,217],{},"：一个智慧路灯平台可能同时服务多个区县、多家物业。各区段的照明策略由辖区负责人自行在 App 上管理，平台方只需要做好初始设备接入和权限分配，后续的季节调整、临时加开等日常操作完全下沉到一线管理员。",[193,388,390],{"id":389},"公园智能灌溉深夜自动作业","公园智能灌溉，深夜自动作业",[11,392,393],{},"城市绿化灌溉如果白天进行，既影响行人又加剧蒸发损耗。最好的时间是凌晨 2 点到 5 点。但让园林工人凌晨去开水阀，既不现实也不人道。",[11,395,396,398,399,401],{},[36,397,139],{},"非常适合这个场景：设置凌晨 2:00 自动开启，持续灌溉 45 分钟后自动关闭。不同季节调整单次灌溉时长，夏季 60 分钟、春秋 45 分钟、冬季 20 分钟，园林工人自己在 ",[36,400,209],{}," 上就能完成调整。",[193,403,405],{"id":404},"交通诱导屏分时段发布信息","交通诱导屏，分时段发布信息",[11,407,408,409,411],{},"早晚高峰显示拥堵提示，平峰时段切换为公益宣传，深夜关闭背光节能。这背后是",[36,410,369],{},"在支撑：工作日设置 7:00-9:00 早高峰模式、17:00-19:00 晚高峰模式、其他时段常规模式；周末则自动切换为节假日策略。",[193,413,414],{"id":414},"智慧城市价值总结",[85,416,417,430],{},[88,418,419],{},[91,420,421,424,427],{},[94,422,423],{},"场景",[94,425,426],{},"管理难题",[94,428,429],{},"定时方案效果",[104,431,432,443,454,465,476],{},[91,433,434,437,440],{},[109,435,436],{},"路灯开关",[109,438,439],{},"季节变化需频繁调整时控箱",[109,441,442],{},"定时区间列表远程切换，全年免现场维护",[91,444,445,448,451],{},[109,446,447],{},"绿化灌溉",[109,449,450],{},"夜间作业人力成本高",[109,452,453],{},"定时时长自动启停，节水节人力",[91,455,456,459,462],{},[109,457,458],{},"交通诱导屏",[109,460,461],{},"内容需随时段手动切换",[109,463,464],{},"多组定时区间自动轮播",[91,466,467,470,473],{},[109,468,469],{},"景观照明",[109,471,472],{},"全年统一运行浪费电能",[109,474,475],{},"分时段区间控制，节能 20%-40%",[91,477,478,481,484],{},[109,479,480],{},"多区域统一管理",[109,482,483],{},"各辖区策略不同，协调困难",[109,485,486],{},"平台统一配置，辖区自主管理",[19,488,489],{},[11,490,491,493],{},[36,492,339],{},"：一座中等城市（10 万盏路灯）采用分时分组定时控制后，照明能耗可降低 25%-35%，按每盏灯年均电费 200 元计算，全市每年节省电费 500-700 万元。同时，路灯运维人员的现场巡检工作量减少 60% 以上。",[25,495],{},[28,497,499],{"id":498},"工业排污让治污设备聪明地干活","工业排污：让治污设备\"聪明地干活\"",[11,501,502,503,506,507,39],{},"工业污水处理、废气治理、固废处置等环保设施，有一个共同特点：它们必须",[36,504,505],{},"在正确的时间做正确的事","，但现场环境恶劣，不宜长期驻人。当环保设备以 SaaS 模式服务多个污水处理厂时，",[36,508,509],{},"每个厂的水质、水量、工艺参数都不同，定时策略必须交给厂方操作工自主管理",[193,511,513],{"id":512},"间歇曝气省电又达标","间歇曝气，省电又达标",[11,515,516],{},"活性污泥法处理污水，需要向曝气池持续供氧。但\"持续全开\"是最笨的做法——夜间进水量减少时，过高的溶解氧反而破坏菌群平衡，还浪费大量电能。",[11,518,519,520,523],{},"正确的策略是",[36,521,522],{},"按需间歇曝气","：在污水高峰期（8:00-22:00）每隔 1 小时曝气 45 分钟；在低谷期（22:00-次日 8:00）降低频次，每隔 2 小时曝气 30 分钟。",[11,525,526,529,530,532],{},[36,527,528],{},"每日间歇定时列表","完美匹配这个需求。更妙的是，你可以为不同曝气池设置不同的间歇策略，A 池处理生活污水高频曝气，B 池处理工业废水低频长周期。操作工在 ",[36,531,209],{}," 上一屏可管所有策略，随时根据进水量变化调整频次，不需要回控制室操作。",[19,534,535],{},[11,536,537,539],{},[36,538,217],{},"：同一套环保设备可能部署在数十个污水厂。各厂的进水 COD、氨氮浓度差异巨大，曝气节奏不可能统一。ThingsCloud 的多用户体系让每个厂的操作工自主优化本厂的间歇策略，平台方只需维护一套设备固件和 App 组件，运营效率大幅提升。",[193,541,543],{"id":542},"定时加药精准投放不浪费","定时加药，精准投放不浪费",[11,545,546],{},"污水处理中的絮凝剂、消毒剂、酸碱调节剂，投放时机直接影响处理效果和药剂成本。例如，消毒剂需要在出水前 30 分钟投加，絮凝剂则需在沉淀池进水时同步加入。",[11,548,202,549,551,552,554],{},[36,550,205],{},"，可以将加药泵的启停时间精确到分钟。6:00 投加絮凝剂、6:30 投加助凝剂、8:00 投加消毒剂……多组定时独立管理，互不干扰。遇到水质波动需要临时调整加药时间，操作工在 ",[36,553,209],{}," 上随时自行修改，不需要联系管理员。",[193,556,558],{"id":557},"自动清淤避开生产高峰","自动清淤，避开生产高峰",[11,560,561],{},"沉淀池、调节池需要定期清淤排泥。排泥过程会短暂影响处理水量，最好安排在用水低谷的凌晨进行。",[11,563,564,566],{},[36,565,139],{},"适合这个场景：凌晨 3:00 自动开启排泥泵，持续运行 20 分钟后自动关闭。排泥频率根据季节和进水含泥量调整，冬季每周 2 次、雨季每天 1 次，策略远程下发，无需下井操作。",[193,568,569],{"id":569},"工业排污价值总结",[85,571,572,582],{},[88,573,574],{},[91,575,576,578,580],{},[94,577,269],{},[94,579,272],{},[94,581,275],{},[104,583,584,595,606,617,628],{},[91,585,586,589,592],{},[109,587,588],{},"曝气 24h 全开电费高",[109,590,591],{},"人工分时段调节风机频率",[109,593,594],{},"间歇定时自动启停，节电 25%-40%",[91,596,597,600,603],{},[109,598,599],{},"加药时机靠经验",[109,601,602],{},"操作工定时巡检手动加药",[109,604,605],{},"定时器列表精准触发，药剂浪费减少 15%",[91,607,608,611,614],{},[109,609,610],{},"排泥需夜间下井操作",[109,612,613],{},"安排夜班专人值守",[109,615,616],{},"定时时长自动完成，安全又省心",[91,618,619,622,625],{},[109,620,621],{},"环保检查缺运行记录",[109,623,624],{},"手工台账，容易遗漏",[109,626,627],{},"平台自动记录每次定时执行日志",[91,629,630,633,636],{},[109,631,632],{},"多厂策略差异化",[109,634,635],{},"平台需逐厂定制方案",[109,637,638],{},"各厂自主配置，平台统一能力输出",[19,640,641],{},[11,642,643,645],{},[36,644,339],{},"：一座日处理量 1 万吨的污水厂，通过间歇曝气智能控制，年节省电费约 15-25 万元；精准加药系统年节省药剂费用 5-10 万元。更重要的是，设备自动运行产生的完整操作日志，成为环保执法检查的合规证据链。",[25,647],{},[28,649,651],{"id":650},"能源管理把峰谷电价变成你的利润","能源管理：把峰谷电价变成你的利润",[11,653,654,655,658,659,39],{},"储能系统、充电桩、空调机组、产线设备——这些\"电老虎\"的运行时段直接决定了电费账单上的数字。在分时电价政策全面推开的背景下，",[36,656,657],{},"\"什么时候用电\"比\"用多少电\"更重要","。当储能设备面向工商业客户销售时，",[36,660,661],{},"每家企业都有自己独特的峰谷时段和用电习惯，定时策略必须由客户自主掌控",[193,663,665],{"id":664},"储能系统定时充放电吃透峰谷价差","储能系统定时充放电，吃透峰谷价差",[11,667,668],{},"工商业储能的核心盈利模式是\"低谷充电、高峰放电\"。以某省电价为例，低谷 0.3 元/度、高峰 1.0 元/度，每度电有 0.7 元的套利空间。",[11,670,202,671,673],{},[36,672,369],{},"配置充放电策略：低谷时段 00:00-08:00 充电，高峰时段 09:00-12:00 和 14:00-17:00 放电，尖峰时段 19:00-22:00 再次放电。不同时段对应不同的功率策略，全部通过定时属性自动执行，不需要人工每天操作 EMS 系统。",[11,675,676,677,679],{},"夏季和冬季的峰谷时段不同？电站管理员在 ",[36,678,209],{}," 上直接切换策略模板即可，不需要平台方介入。",[19,681,682],{},[11,683,684,686],{},[36,685,217],{},"：储能设备厂商将设备卖给不同行业的客户——工厂、商场、充电站、数据中心。每个客户的峰谷电价时段、生产作息、用电负荷曲线都不同。ThingsCloud 的多用户体系让每个客户在 App 上自主配置充放电策略，厂商只需保证硬件和平台能力，无需陷入每个客户的策略定制中。",[193,688,690],{"id":689},"充电桩定时启停保护电网也保护利润","充电桩定时启停，保护电网也保护利润",[11,692,693],{},"充电站如果在电网晚高峰时段大功率充电，不仅电费贵，还可能触发需量罚款。聪明的运营商会在低谷时段引导充电，高峰时段限制功率甚至暂停服务。",[11,695,696,698],{},[36,697,126],{},"可以帮助实现这个策略：设置 0:00-8:00 为全功率开放时段，8:00-22:00 为限功率时段，22:00-24:00 再次全功率开放。配合电价信号自动调整，让充电站在\"用户体验\"和\"运营成本\"之间找到最佳平衡点。",[193,700,702],{"id":701},"空调机组预冷预热少花钱多办事","空调机组预冷预热，少花钱多办事",[11,704,705],{},"商业建筑的中央空调如果等到上班时间才开启，室内温度长时间降不下来；如果提前 1 小时开，又担心浪费电。",[11,707,708,709,711],{},"用",[36,710,139],{},"设置预冷策略：夏季工作日 7:30 提前开启制冷，持续运行 30 分钟到员工到岗时正好达到舒适温度。相比 7:00 就开始持续运行，这 30 分钟的精准预冷每年能省下数万元电费。",[193,713,714],{"id":714},"能源管理价值总结",[85,716,717,728],{},[88,718,719],{},[91,720,721,723,726],{},[94,722,423],{},[94,724,725],{},"核心诉求",[94,727,429],{},[104,729,730,741,752,763,774],{},[91,731,732,735,738],{},[109,733,734],{},"储能峰谷套利",[109,736,737],{},"精准捕捉充放电窗口",[109,739,740],{},"定时区间列表自动执行，吃满价差",[91,742,743,746,749],{},[109,744,745],{},"充电站功率管理",[109,747,748],{},"避开电网惩罚性电价",[109,750,751],{},"分时段区间控制，降本不丢客",[91,753,754,757,760],{},[109,755,756],{},"空调预冷预热",[109,758,759],{},"舒适与节能兼得",[109,761,762],{},"定时时长精准控制，不多开一分钟",[91,764,765,768,771],{},[109,766,767],{},"产线避峰运行",[109,769,770],{},"非核心工序移至谷段",[109,772,773],{},"定时区间自动切换生产模式",[91,775,776,779,782],{},[109,777,778],{},"多客户策略自主",[109,780,781],{},"不同行业峰谷时段不同",[109,783,784],{},"客户 App 自管，厂商专注产品",[19,786,787],{},[11,788,789,791],{},[36,790,339],{},"：一个 2MW/4MWh 的工商业储能项目，通过精准的定时充放电策略，年套利收益约 40-60 万元。如果充放电时段偏差仅 1 小时，年收益可能缩水 10%-15%。定时策略的精准执行，直接等于真金白银。",[25,793],{},[28,795,797],{"id":796},"四种定时模式如何为你的项目选型","四种定时模式，如何为你的项目选型？",[11,799,800],{},"看完四个行业的应用案例，你可能已经在想：\"我的项目应该用哪种定时模式？\"这里给出一个简单的选型指南。",[85,802,803,816],{},[88,804,805],{},[91,806,807,810,813],{},[94,808,809],{},"如果你的需求是...",[94,811,812],{},"选择这种模式",[94,814,815],{},"举例",[104,817,818,829,840,851],{},[91,819,820,823,826],{},[109,821,822],{},"\"每天 X 点执行一次\"",[109,824,825],{},"每日定时器 / 列表",[109,827,828],{},"6:30 投喂、22:00 熄灯",[91,830,831,834,837],{},[109,832,833],{},"\"每天从 A 点到 B 点一直开着\"",[109,835,836],{},"每日定时区间 / 列表",[109,838,839],{},"路灯 18:00-6:00、空调 8:00-18:00",[91,841,842,845,848],{},[109,843,844],{},"\"每天 X 点打开，持续 N 分钟后自动关\"",[109,846,847],{},"每日定时时长 / 列表",[109,849,850],{},"灌溉 30 分钟、排泥 20 分钟",[91,852,853,856,859],{},[109,854,855],{},"\"每天在 A-B 点之间，每隔 N 分钟执行 M 分钟\"",[109,857,858],{},"每日间歇定时 / 列表",[109,860,861],{},"滴灌每 2 小时 15 分钟、曝气每 1 小时 45 分钟",[11,863,864,867],{},[36,865,866],{},"列表型 vs 单条型的选择原则","：如果你的设备定时策略是固定的（比如路灯只在一组时段开关），用单条即可；如果策略需要用户自主增减（比如插座随时加一组定时、养殖随周期调整投喂次数），用列表型更灵活。",[25,869],{},[28,871,872],{"id":872},"写在最后",[11,874,875,876],{},"物联网的价值，最终要回到一个简单的问题：",[36,877,878],{},"它是不是真的帮客户省了心、省了力、省了钱？",[11,880,881],{},"ThingsCloud 的四种定时模式，正是为了解决这个实际问题而设计的。从定点触发到间歇循环，从单条策略到列表管理，每一种模式都对应着真实场景中反复出现的需求。通过将定时能力属性化，平台方只需一次配置，终端用户就能在 App 上自主管理，策略调整分钟级生效。",[11,883,884],{},"在多用户体系下，这种设计带来的价值尤为明显。无论是千家万户的智慧农业设备，还是遍布城市的公共设施，亦或是服务众多企业的工业和能源系统，ThingsCloud 都能让每台设备拥有独立、灵活、可自主管理的定时策略。平台方专注能力建设，终端用户专注业务运营，双方各司其职，项目才能持续规模化发展。",[11,886,887],{},"如果你的项目正面临\"设备需要按时自动运行\"的需求——无论是农业大棚的第一台风机，还是城市路灯的第十万个控制节点——ThingsCloud 的定时能力都准备好了。",[25,889],{},[11,891,892],{},[36,893,894],{},"延伸阅读：",[44,896,897,906,913,920,927],{},[47,898,899],{},[900,901,905],"a",{"href":902,"rel":903},"https://www.thingscloud.xyz/blog/feature-task-daily-timer-attribute/",[904],"nofollow","用户如何在 ThingsX 设置定时任务？",[47,907,908],{},[900,909,912],{"href":910,"rel":911},"https://www.thingscloud.xyz/blog/feature-task-daily-timer-range-attribute/",[904],"用户如何在 ThingsX 设置定时开关？",[47,914,915],{},[900,916,919],{"href":917,"rel":918},"https://www.thingscloud.xyz/blog/feature-task-daily-timer-list-attribute/",[904],"用户如何在 ThingsX 设置多组定时任务？",[47,921,922],{},[900,923,926],{"href":924,"rel":925},"https://www.thingscloud.xyz/blog/feature-task-daily-timer-interval-attribute/",[904],"用户如何在 ThingsX 设置间歇定时任务？",[47,928,929],{},[900,930,933],{"href":931,"rel":932},"https://www.thingscloud.xyz/docs/guide/device-type/data-types.html",[904],"数据类型 - 定时属性详细文档",{"title":935,"searchDepth":936,"depth":936,"links":937},"",2,[938,939,940,947,953,959,965,966],{"id":30,"depth":936,"text":31},{"id":79,"depth":936,"text":80},{"id":184,"depth":936,"text":185,"children":941},[942,944,945,946],{"id":195,"depth":943,"text":196},3,{"id":221,"depth":943,"text":222},{"id":245,"depth":943,"text":246},{"id":260,"depth":943,"text":260},{"id":345,"depth":936,"text":346,"children":948},[949,950,951,952],{"id":360,"depth":943,"text":361},{"id":389,"depth":943,"text":390},{"id":404,"depth":943,"text":405},{"id":414,"depth":943,"text":414},{"id":498,"depth":936,"text":499,"children":954},[955,956,957,958],{"id":512,"depth":943,"text":513},{"id":542,"depth":943,"text":543},{"id":557,"depth":943,"text":558},{"id":569,"depth":943,"text":569},{"id":650,"depth":936,"text":651,"children":960},[961,962,963,964],{"id":664,"depth":943,"text":665},{"id":689,"depth":943,"text":690},{"id":701,"depth":943,"text":702},{"id":714,"depth":943,"text":714},{"id":796,"depth":936,"text":797},{"id":872,"depth":936,"text":872},["Date","2026-05-16T00:00:00.000Z"],"定点触发、区间持续、延时关闭、间歇循环，配合 ThingsX 定时组件，轻松管理多组定时策略。","md",{},true,"/blog/scenario-four-iot-timer-modes",{"title":5,"description":968},"blog/scenario-four-iot-timer-modes",[976,977],"features","industries","H90ukJ7pGA1ReogQMCa6hDGkwKbYWul2KZbKB2Dq0GA",[980,1432,1789,2067,2888,3500,4202,4813,5249,5791,6258,6936],{"id":981,"title":926,"automation":6,"body":982,"buy":6,"category":6,"categorySlug":6,"createdAt":1423,"description":1424,"deviceRefs":6,"difficulty":6,"estimatedTime":6,"extension":969,"headpic":989,"image":6,"industry":6,"industrySlug":6,"keywords":6,"links":6,"meta":1425,"model":6,"name":6,"navigation":971,"path":1426,"protocol":6,"scenario":6,"scenarioSlug":6,"seo":1427,"stem":1428,"tagSlugs":1429,"tags":6,"vendor":6,"website":6,"__hash__":1431},"content/blog/feature-task-daily-timer-interval-attribute.md",{"type":8,"value":983,"toc":1412},[984,990,1001,1004,1010,1013,1016,1019,1057,1060,1063,1124,1131,1134,1137,1144,1150,1158,1164,1177,1180,1183,1191,1197,1204,1210,1223,1229,1237,1243,1246,1249,1258,1265,1271,1277,1280,1283,1287,1294,1297,1301,1304,1318,1321,1332,1335,1338,1341,1344,1351,1398,1401,1404],[11,985,986],{},[14,987],{"alt":988,"src":989},"articles/2024/20260516180758_6e3ab210f8fedd343c9372d2355ffe9d.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260516180758_6e3ab210f8fedd343c9372d2355ffe9d.png",[11,991,992,993,996,997,1000],{},"ThingsCloud 近期上线了 ",[36,994,995],{},"每日间歇定时（DailyTimerInterval）"," 和 ",[36,998,999],{},"每日间歇定时列表（DailyTimerIntervalList）"," 两种全新的属性类型，配套 ThingsX App 间歇定时组件，帮助您在物联网项目中高效实现设备的周期性循环控制。",[28,1002,1003],{"id":1003},"什么是间歇定时",[11,1005,1006,1007,39],{},"间歇定时解决的是一个经典调度问题：",[36,1008,1009],{},"在指定的每日时间区间内，按照固定间隔周期性执行任务，每次执行持续一定时长",[11,1011,1012],{},"与单一定时器（到点执行一次）和定时区间（到点开、到点关各一次）不同，间歇定时可以在一个区间内自动产生多个执行周期。例如：在 8:00 ~ 18:00 之间，每隔 2 小时执行一次，每次持续 10 分钟——系统会自动在 8:00、10:00、12:00、14:00、16:00 各触发一次任务。",[28,1014,1015],{"id":1015},"典型应用场景",[11,1017,1018],{},"间歇定时适用于需要周期性循环运行、而非一次性启停的设备控制场景：",[44,1020,1021,1027,1033,1039,1045,1051],{},[47,1022,1023,1026],{},[36,1024,1025],{},"智慧农业","：大棚滴灌、水肥一体化系统在白天灌溉窗口内每隔 1 至 2 小时灌溉 10 至 20 分钟，避免持续浇水导致的土壤板结和根系缺氧。相比全天连续灌溉，间歇模式可节水 30% 以上，同时保证作物获得均匀的水分供给。",[47,1028,1029,1032],{},[36,1030,1031],{},"水产养殖","：增氧机在高温季节每隔 1 至 2 小时运行 15 至 30 分钟，兼顾溶氧补充和能耗控制。夏季夜间和午后是缺氧高危时段，通过间歇增氧可在关键时段维持溶解氧浓度，避免翻塘事故。",[47,1034,1035,1038],{},[36,1036,1037],{},"工业环境","：车间除尘设备在工作时段内每隔 20 至 40 分钟自动运行 5 至 10 分钟，平衡空气质量与滤芯寿命。间歇运行既能及时清除粉尘，又可显著延长滤材更换周期，降低维护成本。",[47,1040,1041,1044],{},[36,1042,1043],{},"污水处理","：曝气池按工艺要求在特定时段内周期性供氧，避免连续曝气的高能耗或间隔过长的微生物失活。合理的间歇曝气节奏可使处理效率保持稳定，同时将能耗控制在连续曝气模式的 40% 至 60%。",[47,1046,1047,1050],{},[36,1048,1049],{},"商业设施","：户外喷雾降温系统在高温时段每隔 15 至 20 分钟喷雾 2 至 3 分钟，兼顾降温效果与路面干爽。间歇喷雾既能有效降低局部环境温度，又避免行人通行区域长期湿滑。",[47,1052,1053,1056],{},[36,1054,1055],{},"楼宇通风","：新风系统在工作时段内每隔 1 小时换气 10 分钟，维持室内空气流通同时降低空调负荷。通过精确控制换气节奏，可在保证室内空气质量的前提下，将新风系统的能耗影响降至最低。",[28,1058,1059],{"id":1059},"相比传统方案的优势",[11,1061,1062],{},"在没有间歇定时之前，您通常需要采用堆叠多个单一定时器的方式来模拟周期性循环——8:00 一个、10:00 一个、12:00 一个…… 这种方式存在明显的维护负担：",[85,1064,1065,1078],{},[88,1066,1067],{},[91,1068,1069,1072,1075],{},[94,1070,1071],{},"对比项",[94,1073,1074],{},"堆叠单一定时器",[94,1076,1077],{},"间歇定时",[104,1079,1080,1091,1102,1113],{},[91,1081,1082,1085,1088],{},[109,1083,1084],{},"配置方式",[109,1086,1087],{},"为每个执行点创建独立属性",[109,1089,1090],{},"一个属性，配置区间+间隔+时长即可",[91,1092,1093,1096,1099],{},[109,1094,1095],{},"数量调整",[109,1097,1098],{},"需增删属性、修改平台配置",[109,1100,1101],{},"您直接在 App 中调整参数",[91,1103,1104,1107,1110],{},[109,1105,1106],{},"间隔修改",[109,1108,1109],{},"需重新计算所有时间点并逐个修改",[109,1111,1112],{},"修改一个间隔值，系统自动重算",[91,1114,1115,1118,1121],{},[109,1116,1117],{},"App 体验",[109,1119,1120],{},"分散在多个组件中",[109,1122,1123],{},"集中在同一个组件中管理",[11,1125,1126,1127,1130],{},"间歇定时列表在此基础上进一步支持",[36,1128,1129],{},"多组策略管理","，您可以在同一个组件中添加、编辑或删除多组间歇定时，每组拥有独立的时段和周期参数，所有条目共用统一时区。",[11,1132,1133],{},"本篇博客将以污水处理系统为例，介绍如何在 ThingsCloud 平台端完成间歇定时配置，并让您通过 ThingsX App 自主管理间歇策略。",[28,1135,1136],{"id":1136},"添加每日间歇定时列表属性",[11,1138,1139,1140,1143],{},"首先在设备类型中，添加属性定义，数据类型选择 ",[36,1141,1142],{},"DailyTimerIntervalList（每日间歇定时列表）","，如下图：",[11,1145,1146],{},[14,1147],{"alt":1148,"src":1149},"articles/2024/20260516172944_e96845aa66691b68cb2467ad60223264.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260516172944_e96845aa66691b68cb2467ad60223264.png",[11,1151,1152,1153,1157],{},"我们添加一个间歇定时列表属性 ",[1154,1155,1156],"code",{},"timer_interval_list","，用于管理污水处理系统的多组间歇曝气策略。",[11,1159,1160],{},[14,1161],{"alt":1162,"src":1163},"articles/2024/20260516173020_6bfdd931aff6a9fae9e256ce4e218cb0.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260516173020_6bfdd931aff6a9fae9e256ce4e218cb0.png",[11,1165,1166,1167,1172,1173,1176],{},"这里我们在创建间歇定时列表属性时，",[900,1168,1171],{"href":1169,"rel":1170},"https://www.thingscloud.xyz/docs/guide/device-type/attributes-types.html",[904],"属性类型","选择了 ",[36,1174,1175],{},"云端私有属性","，表示这些定时器属性不会被下发到设备，而只是存在于平台端，用来保存定时器参数。您也可以根据实际需求选择不同的属性类型。",[11,1178,1179],{},"一个每日间歇定时列表属性，可以容纳多组间歇定时设置，每组设置包含独立的起始时间、结束时间、单次运行时长和间隔时长，用户可以在 ThingsX App 中自由添加、编辑或删除其中的定时设置，所有条目共用统一的时区设置。",[28,1181,1182],{"id":1182},"创建任务并关联间歇定时列表属性",[11,1184,1185,1186,1190],{},"与 ",[900,1187,1189],{"href":917,"rel":1188},[904],"定时区间"," 属性一样，间歇定时列表也需要分别创建开启和关闭两个任务。",[11,1192,1193],{},[14,1194],{"alt":1195,"src":1196},"articles/2024/20260516174003_e0e34334bfebad904330679072500299.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260516174003_e0e34334bfebad904330679072500299.png",[11,1198,1199,1200,1203],{},"首先创建开启曝气设备的任务，用于向设备下发开启曝气设备的属性消息，使用属性下发任务类型。在本示例中，我们使用普通的 RS485 继电器通过 DTU 接入ThingsCloud ，开启曝气设备只需要下发设备属性 ",[1154,1201,1202],{},"relay1","，编写简单的属性下发云函数，如下图：",[11,1205,1206],{},[14,1207],{"alt":1208,"src":1209},"articles/2024/20260516174019_f5c79746d233ade258eeee58fba8d458.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260516174019_f5c79746d233ade258eeee58fba8d458.png",[11,1211,1212,1213,1216,1217,1219,1220,1143],{},"然后在任务的定时设置中，选择每日定时，在时间设置方式中，选择",[36,1214,1215],{},"读取设备定时器属性","，关联前边创建的 ",[1154,1218,1156],{},"，选择",[36,1221,1222],{},"开始时间",[11,1224,1225],{},[14,1226],{"alt":1227,"src":1228},"articles/2024/20260516174131_7a710ebd58b10ebeb6685266ccb71940.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260516174131_7a710ebd58b10ebeb6685266ccb71940.png",[11,1230,1231,1232,1219,1234,1143],{},"同样的方式，再创建一个关闭曝气设备的任务，在任务定时设置中关联 ",[1154,1233,1156],{},[36,1235,1236],{},"结束时间",[11,1238,1239],{},[14,1240],{"alt":1241,"src":1242},"articles/2024/20260516174229_849ad34aab20f68477e442dba8f8d542.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260516174229_849ad34aab20f68477e442dba8f8d542.png",[11,1244,1245],{},"创建好两个任务后，系统会根据间歇定时列表中每组生效条目的起始区间、间隔和单次运行时长，自动计算所有周期的起始时间点和结束时间点，分别触发开启和关闭任务。",[28,1247,1248],{"id":1248},"为设备面板添加间歇定时列表组件",[11,1250,1251,1252,1257],{},"接下来，我们将在 ThingsX App 的",[900,1253,1256],{"href":1254,"rel":1255},"https://www.thingscloud.xyz/docs/guide/device-type/app-panel-editor.html",[904],"设备面板","中添加间歇定时列表组件，让您可以在 App 中集中管理多组间歇定时设置。",[11,1259,1260,1261,1264],{},"进入设备类型的 ThingsX App 设备面板编辑器，在左侧的日期时间控制组件分类中，找到",[36,1262,1263],{},"间歇定时列表组件","，添加到设备面板中。",[11,1266,1267,1268,1270],{},"然后在右侧的组件设置中，为该组件选择之前创建的 ",[1154,1269,1156],{}," 间歇定时列表属性，如下图：",[11,1272,1273],{},[14,1274],{"alt":1275,"src":1276},"articles/2024/20260516174537_08f21afb100a1e2aa67e06e8074cfaea.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260516174537_08f21afb100a1e2aa67e06e8074cfaea.png",[11,1278,1279],{},"在右侧的样式编辑中，可以设置图标、颜色以及各种样式。",[11,1281,1282],{},"保存设备面板后，您在 ThingsX App 上再次进入设备面板时，就可以使用该组件了。",[28,1284,1286],{"id":1285},"使用-thingsx-app-设置多组间歇定时","使用 ThingsX App 设置多组间歇定时",[11,1288,1289,1293],{},[900,1290,209],{"href":1291,"rel":1292},"https://www.thingscloud.xyz/docs/guide/customer-app/common-app.html",[904]," 支持 iOS/Android/微信小程序等多移动平台。间歇定时列表组件为您提供了更灵活的操作方式，可新增一组间歇定时，可点击已有条目进行编辑，可禁用或删除已有的间歇定时。",[11,1295,1296],{},"以污水处理系统的间歇曝气控制为例，您可以为它设置不同日期的循环运行策略，如下图：",[14,1298],{"src":1299,"style":1300},"https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260516175017_13c2f0545579bb15dbefabdf8db38524.png","width: 300px;",[11,1302,1303],{},"这里我们设置了两组间歇定时：",[44,1305,1306,1312],{},[47,1307,1308,1311],{},[36,1309,1310],{},"工作日","：8:00 ~ 18:00，每隔 40 分钟曝气 10 分钟",[47,1313,1314,1317],{},[36,1315,1316],{},"周末","：9:00 ~ 17:00，每隔 30 分钟曝气 8 分钟",[11,1319,1320],{},"您可以随时启用或禁用某组间歇定时，也可以继续添加更多条目来满足不同处理工艺或不同水质的曝气需求。",[11,1322,1323,1324,1327,1328,1331],{},"如果需要为其他处理池设置独立的间歇定时策略，可以同理添加多个间歇定时列表属性，例如 ",[1154,1325,1326],{},"timer_interval_list_pool2","、",[1154,1329,1330],{},"timer_interval_list_pool3"," 等，在 App 面板中预留多个间歇定时列表组件即可。",[28,1333,1334],{"id":1334},"支持全球时区",[11,1336,1337],{},"间歇定时列表组件支持全球时区，默认自动跟随用户手机系统的时区设置，自动计算定时任务的触发时间，确保无论用户身处哪个时区，都能按本地时间准确执行定时任务。",[11,1339,1340],{},"您也可以在组件设置中自定义时区，覆盖默认的手机系统时区设置，满足跨时区使用的需求。例如，设备部署在海外农场，但您在中国大陆使用 App，可以将组件时区设置为设备所在时区，这样定时任务就会按照设备本地时间来执行。",[28,1342,1343],{"id":1343},"总结",[11,1345,1346,1347,1350],{},"如果您的设备需要支持周期性循环运行的定时策略，那么每日间歇定时和每日间歇定时列表是理想的选择。相比定时器和定时区间，间歇定时的核心优势在于",[36,1348,1349],{},"一次配置，周期执行","：",[85,1352,1353,1364],{},[88,1354,1355],{},[91,1356,1357,1359,1362],{},[94,1358,1071],{},[94,1360,1361],{},"定时器 / 定时区间",[94,1363,1077],{},[104,1365,1366,1377,1387],{},[91,1367,1368,1371,1374],{},[109,1369,1370],{},"执行次数",[109,1372,1373],{},"在指定时间点执行一次",[109,1375,1376],{},"在指定区间内周期性多次执行",[91,1378,1379,1381,1384],{},[109,1380,1084],{},[109,1382,1383],{},"每个执行点需独立配置",[109,1385,1386],{},"配置区间、间隔和单次时长即可",[91,1388,1389,1392,1395],{},[109,1390,1391],{},"适用场景",[109,1393,1394],{},"单次触发、定时开关",[109,1396,1397],{},"周期性循环运行、间歇控制",[11,1399,1400],{},"通过将任务事先创建好并关联设备的间歇定时列表属性，再使用 App 设备面板中对应的列表组件，用户只需要在一个入口中即可完成所有间歇定时的管理。这大大简化了平台的配置和用户的操作，实现更个性化、更灵活的设备管理体验。",[11,1402,1403],{},"您学会了吗？快来试试吧！",[11,1405,1406,1407,39],{},"物联网设备接入 ThingsCloud ，请参考 ",[900,1408,1411],{"href":1409,"rel":1410},"https://www.thingscloud.xyz/docs/guide/connect-device/",[904],"设备接入指南",{"title":935,"searchDepth":936,"depth":936,"links":1413},[1414,1415,1416,1417,1418,1419,1420,1421,1422],{"id":1003,"depth":936,"text":1003},{"id":1015,"depth":936,"text":1015},{"id":1059,"depth":936,"text":1059},{"id":1136,"depth":936,"text":1136},{"id":1182,"depth":936,"text":1182},{"id":1248,"depth":936,"text":1248},{"id":1285,"depth":936,"text":1286},{"id":1334,"depth":936,"text":1334},{"id":1343,"depth":936,"text":1343},["Date","2026-05-13T00:00:00.000Z"],"通过全新的间歇定时组件，用户可以在 ThingsX App 中为设备设置周期循环运行的定时策略，满足更精细的自动化控制需求。",{},"/blog/feature-task-daily-timer-interval-attribute",{"title":926,"description":1424},"blog/feature-task-daily-timer-interval-attribute",[976,1430],"quickstart","oMFSX64lVMwq8fJAZpIesqTSVwQJJxOBccSfBCFywok",{"id":1433,"title":919,"automation":6,"body":1434,"buy":6,"category":6,"categorySlug":6,"createdAt":1781,"description":1782,"deviceRefs":6,"difficulty":6,"estimatedTime":6,"extension":969,"headpic":1441,"image":6,"industry":6,"industrySlug":6,"keywords":6,"links":6,"meta":1783,"model":6,"name":6,"navigation":971,"path":1784,"protocol":6,"scenario":6,"scenarioSlug":6,"seo":1785,"stem":1786,"tagSlugs":1787,"tags":6,"vendor":6,"website":6,"__hash__":1788},"content/blog/feature-task-daily-timer-list-attribute.md",{"type":8,"value":1435,"toc":1773},[1436,1442,1452,1455,1481,1484,1496,1499,1502,1505,1510,1516,1523,1529,1537,1540,1543,1546,1549,1555,1558,1566,1572,1579,1585,1591,1594,1600,1603,1609,1616,1622,1628,1634,1636,1642,1645,1649,1655,1658,1661,1664,1667,1677,1679,1682,1685,1688,1690,1693,1763,1766,1768],[11,1437,1438],{},[14,1439],{"alt":1440,"src":1441},"articles/2024/20260505221613_a789e3915046c3f65e125d78938d14f3.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260505221613_a789e3915046c3f65e125d78938d14f3.png",[11,1443,1444,1445,996,1448,1451],{},"在前两篇博客 ",[900,1446,905],{"href":902,"rel":1447},[904],[900,1449,912],{"href":910,"rel":1450},[904]," 中，我们介绍了如何通过每日定时器和每日定时区间属性，让用户在 ThingsX App 中为设备设置独立的定时任务和定时开关。",[11,1453,1454],{},"然而，当设备需要更复杂的定时策略时，例如：",[44,1456,1457,1463,1469,1475],{},[47,1458,1459,1462],{},[36,1460,1461],{},"智能插座","：用户根据每日用电需求，随时添加或删除定时开关组——有时只需要早晚各一组，有时则需要早中晚多达四组甚至更多，数量完全由用户自主决定。",[47,1464,1465,1468],{},[36,1466,1467],{},"智慧养殖","：饲料投喂设备一天需要多次投料，如 7:00、12:00、16:00 各一次，且随着养殖周期变化，用户可能随时增减投喂频次和时段。",[47,1470,1471,1474],{},[36,1472,1473],{},"智能窗帘","：工作日和周末需要不同的开合时段，工作日 8:00 开、18:00 关，周末 9:00 开、17:00 关——不同家庭还可能额外增加午休遮光时段，组数因人而异。",[47,1476,1477,1480],{},[36,1478,1479],{},"商业照明","：不同门店、不同季节或不同促销活动的营业照明需求差异很大，有的门店只需两组时段，有的则需要五组以上，无法预先固定数量。",[11,1482,1483],{},"如果沿用之前的方案，每增加一组定时就要创建一个独立的属性，并在 App 面板上占用一个组件位置。更重要的是，由于用户实际需要的定时组数无法预先确定，平台端只能要么提前配置大量冗余属性以备不时之需。",[11,1485,1486,1487,165,1489,1491,1492,1495],{},"为此，ThingsCloud 全新推出了",[36,1488,205],{},[36,1490,369],{},"两种属性类型。配合 ThingsX App 中全新的列表组件，用户可以在一个组件入口中集中管理多组定时设置。它们的最大优势在于：",[36,1493,1494],{},"仅需一个属性、一个组件，即可实现多组定时的灵活配置","，大幅简化平台端的配置流程，提升终端用户的操作体验。",[11,1497,1498],{},"本篇博客将以继电器开关控制为例，介绍如何快速完成平台端配置，让用户通过 ThingsX App 灵活设置多组定时区间任务。",[11,1500,1501],{},"任何接入 ThingsCloud 的开关设备都可以使用本例中的方法，这里我们以一台 RS485 16 路继电器为例。",[28,1503,1504],{"id":1504},"添加每日定时区间列表属性",[11,1506,1139,1507,1143],{},[36,1508,1509],{},"DailyTimerRangeList（每日定时区间列表）",[11,1511,1512],{},[14,1513],{"alt":1514,"src":1515},"articles/2024/20260505210717_a9084913fd22f4d18bb3af417729866e.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260505210717_a9084913fd22f4d18bb3af417729866e.png",[11,1517,1518,1519,1522],{},"我们添加一个定时区间列表属性 ",[1154,1520,1521],{},"relay1_timer_range_list","，用于管理继电器 #1 的多组定时开关区间。用户只需要在这个列表中添加、编辑或删除定时区间条目，设置每条目的启用状态、开始时间、结束时间和重复方式即可。",[11,1524,1525],{},[14,1526],{"alt":1527,"src":1528},"articles/2024/20260505210854_064c8fbc327595b215974923d6737621.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260505210854_064c8fbc327595b215974923d6737621.png",[11,1530,1531,1532,1172,1535,1176],{},"这里我们在创建定时区间列表属性时，",[900,1533,1171],{"href":1169,"rel":1534},[904],[36,1536,1175],{},[11,1538,1539],{},"一个每日定时区间列表属性，可以容纳多组定时区间设置，每组区间包含独立的开始时间和结束时间，用户后续在 App 中可以自由添加、编辑或删除其中的条目，所有区间共用统一的时区设置。",[28,1541,1542],{"id":1542},"创建任务并关联定时区间列表属性",[11,1544,1545],{},"与单一定时区间一样，定时区间列表也需要分别创建开启和关闭两个任务。",[11,1547,1548],{},"首先创建开启继电器的任务，用于向设备下发开启电源的属性消息，如下图：",[11,1550,1551],{},[14,1552],{"alt":1553,"src":1554},"articles/2024/20260505211016_9ac3b23bfdadd1c26792649406aff7c2.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260505211016_9ac3b23bfdadd1c26792649406aff7c2.png",[11,1556,1557],{},"使用属性下发任务类型，开启继电器 #1 只需要下发对应的开关属性。",[11,1559,1212,1560,1216,1562,1219,1564,1143],{},[36,1561,1215],{},[1154,1563,1521],{},[36,1565,1222],{},[11,1567,1568],{},[14,1569],{"alt":1570,"src":1571},"articles/2024/20260505211250_ae87200683908baae14d07a320a52ca6.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260505211250_ae87200683908baae14d07a320a52ca6.png",[11,1573,1574,1575,1219,1577,1143],{},"同样的方式，再创建一个关闭继电器 #1 的任务，在任务定时设置中关联 ",[1154,1576,1521],{},[36,1578,1236],{},[11,1580,1581],{},[14,1582],{"alt":1583,"src":1584},"articles/2024/20260505211347_aae0b15f991bbdce5d2f44ad65ca3680.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260505211347_aae0b15f991bbdce5d2f44ad65ca3680.png",[11,1586,1587],{},[14,1588],{"alt":1589,"src":1590},"articles/2024/20260505211425_cefe0ddd7a0453ab5ff2ea668859ab75.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260505211425_cefe0ddd7a0453ab5ff2ea668859ab75.png",[11,1592,1593],{},"创建好两个任务后，系统会根据定时区间列表中每组生效区间的开始时间和结束时间，分别触发开启和关闭任务。",[11,1595,1596],{},[14,1597],{"alt":1598,"src":1599},"articles/2024/20260505211635_02e2a76e77785e6b1e3bf024f9693e91.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260505211635_02e2a76e77785e6b1e3bf024f9693e91.png",[28,1601,1602],{"id":1602},"为设备面板添加定时区间列表组件",[11,1604,1251,1605,1608],{},[900,1606,1256],{"href":1254,"rel":1607},[904],"中添加定时区间列表组件，让用户可以在 App 中集中管理多组定时区间设置。",[11,1610,1611,1612,1615],{},"进入设备类型的 ThingsX App 设备面板编辑器，在左侧的日期时间组件分类中，找到",[36,1613,1614],{},"定时区间列表组件","，添加到设备面板中，如下图：",[11,1617,1618],{},[14,1619],{"alt":1620,"src":1621},"articles/2024/20260505212954_4f8cdf1cedc1c48f384deecf8219e277.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260505212954_4f8cdf1cedc1c48f384deecf8219e277.png",[11,1623,1624,1625,1627],{},"在右侧的组件设置中，为该组件选择之前创建的 ",[1154,1626,1521],{}," 定时区间列表属性，如下图：",[11,1629,1630],{},[14,1631],{"alt":1632,"src":1633},"articles/2024/20260505213021_f049c5cd9088110474ac60a88b5564ba.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260505213021_f049c5cd9088110474ac60a88b5564ba.png",[11,1635,1279],{},[11,1637,1638],{},[14,1639],{"alt":1640,"src":1641},"articles/2024/20260505213335_c60c199b542ec92c97ba1be5f529f0de.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260505213335_c60c199b542ec92c97ba1be5f529f0de.png",[11,1643,1644],{},"保存设备面板后，用户在 ThingsX App 上再次进入设备面板时，就可以使用该组件了。",[28,1646,1648],{"id":1647},"使用-thingsx-app-设置多组定时区间","使用 ThingsX App 设置多组定时区间",[11,1650,1651,1654],{},[900,1652,209],{"href":1291,"rel":1653},[904]," 支持 iOS/Android/微信小程序等多移动平台。定时区间列表组件为用户提供了更灵活的操作方式，可新增一组定时区间，可点击已有条目进行编辑，可禁用或删除已有的定时区间。",[14,1656],{"src":1657,"style":1300},"https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260505213543_e6d641c551ab476ae26a616f81378d37.png",[11,1659,1660],{},"以继电器 #1 的定时控制为例，用户可以为它设置不同日期的开启和关闭时段，如下图：",[14,1662],{"src":1663,"style":1300},"https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260505213613_0275e9c6db5c41b63f87c1d93e2aaf07.png",[11,1665,1666],{},"这里我们设置了两组定时区间：工作日 8:00 开启、18:00 关闭，周末 9:00 开启、17:00 关闭。用户可以随时启用或禁用某组区间，也可以继续添加更多条目来满足更复杂的日程安排。",[11,1668,1669,1670,1327,1673,1676],{},"如果需要为其他继电器通道设置独立的定时区间，可以同理添加多个定时区间列表属性，例如 ",[1154,1671,1672],{},"relay2_timer_range_list",[1154,1674,1675],{},"relay3_timer_range_list"," 等，在 App 面板中预留多个定时区间列表组件即可。",[28,1678,1334],{"id":1334},[11,1680,1681],{},"定时器列表组件和定时区间列表组件支持全球时区，默认自动跟随用户手机系统的时区设置，自动计算定时任务的触发时间，确保无论用户身处哪个时区，都能按本地时间准确执行定时任务。",[11,1683,1684],{},"用户也可以在组件设置中自定义时区，覆盖默认的手机系统时区设置，满足跨时区使用的需求。例如，设备部署在美国东部，但用户在中国大陆使用 App，可以将组件时区设置为美国东部时区，这样定时任务就会按照美国东部时间来执行。",[14,1686],{"src":1687,"style":1300},"https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260505213846_49e7dfb398030bac04f6632cbcb7437c.png",[28,1689,1343],{"id":1343},[11,1691,1692],{},"如果您的设备需要支持用户自主设置多组定时任务，那么每日定时器列表和每日定时区间列表相比单一定时器和单一定时区间，会是更灵活的选择：",[85,1694,1695,1707],{},[88,1696,1697],{},[91,1698,1699,1701,1704],{},[94,1700,1071],{},[94,1702,1703],{},"单一定时器 / 单一定时区间",[94,1705,1706],{},"定时器列表 / 定时区间列表",[104,1708,1709,1720,1731,1742,1753],{},[91,1710,1711,1714,1717],{},[109,1712,1713],{},"属性数量",[109,1715,1716],{},"每组定时需一个独立属性",[109,1718,1719],{},"一个属性即可管理多组",[91,1721,1722,1725,1728],{},[109,1723,1724],{},"App 组件数量",[109,1726,1727],{},"每组定时占用一个独立组件",[109,1729,1730],{},"一个组件即可管理多组",[91,1732,1733,1736,1739],{},[109,1734,1735],{},"用户操作",[109,1737,1738],{},"分散在多个组件中设置",[109,1740,1741],{},"在同一列表中集中管理",[91,1743,1744,1747,1750],{},[109,1745,1746],{},"数量灵活性",[109,1748,1749],{},"数量固定，需预先配置",[109,1751,1752],{},"数量由用户动态决定",[91,1754,1755,1757,1760],{},[109,1756,1391],{},[109,1758,1759],{},"定时组数固定、可预先规划的场景",[109,1761,1762],{},"定时组数不确定、需用户动态调整的场景",[11,1764,1765],{},"通过将任务事先创建好并关联到设备的定时器列表或定时区间列表属性，再使用 App 设备面板中对应的列表组件，用户只需要在一个入口中即可完成所有定时管理。这大大简化了平台的配置和用户的操作，实现更个性化、更灵活的设备管理体验。",[11,1767,1403],{},[11,1769,1406,1770,39],{},[900,1771,1411],{"href":1409,"rel":1772},[904],{"title":935,"searchDepth":936,"depth":936,"links":1774},[1775,1776,1777,1778,1779,1780],{"id":1504,"depth":936,"text":1504},{"id":1542,"depth":936,"text":1542},{"id":1602,"depth":936,"text":1602},{"id":1647,"depth":936,"text":1648},{"id":1334,"depth":936,"text":1334},{"id":1343,"depth":936,"text":1343},["Date","2026-05-05T00:00:00.000Z"],"通过全新的定时器列表和定时区间列表组件，用户可以在一个组件中灵活管理多组定时设置，满足更复杂的设备定时控制需求。",{},"/blog/feature-task-daily-timer-list-attribute",{"title":919,"description":1782},"blog/feature-task-daily-timer-list-attribute",[976,1430],"H9PJIh8Mkk7oYASvBIDWL07ZXMx0iHr-yBGr5HbcAcQ",{"id":1790,"title":1791,"automation":6,"body":1792,"buy":6,"category":6,"categorySlug":6,"createdAt":2058,"description":2059,"deviceRefs":6,"difficulty":6,"estimatedTime":6,"extension":969,"headpic":1799,"image":6,"industry":6,"industrySlug":6,"keywords":6,"links":6,"meta":2060,"model":6,"name":6,"navigation":971,"path":2061,"protocol":6,"scenario":6,"scenarioSlug":6,"seo":2062,"stem":2063,"tagSlugs":2064,"tags":6,"vendor":6,"website":6,"__hash__":2066},"content/blog/feature-device-image-upload-released.md","ThingsCloud 全新图片上传服务，不止读数据，还能看画面",{"type":8,"value":1793,"toc":2040},[1794,1800,1806,1820,1822,1826,1829,1833,1836,1840,1843,1847,1850,1854,1857,1861,1864,1868,1871,1873,1877,1880,1887,1896,1899,1902,1928,1938,1940,1944,1947,1950,1953,1959,1962,1965,1971,1975,1978,1984,1987,1990,1992,1996,1999,2019,2022,2029,2031],[11,1795,1796],{},[14,1797],{"alt":1798,"src":1799},"articles/2024/20260427110942_eec365ae7b89c49bc9cbbfeeec12d889.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260427110942_eec365ae7b89c49bc9cbbfeeec12d889.png",[11,1801,1802,1803],{},"在传统的物联网系统中，设备与云端的交互大多停留在数字和状态层面 —— 温度、湿度、开关量、电流电压……这些数据虽然精准，但面对某些场景时，管理者依然会产生一个朴素的念头：",[36,1804,1805],{},"\"如果我能直接看到现场画面，该有多好？\"",[11,1807,1808,1809,1812,1813,1816,1817,39],{},"今天，ThingsCloud 正式推出 ",[36,1810,1811],{},"设备图片上传服务","。无论是摄像头抓拍的报警现场，还是虫情测报灯拍摄的害虫照片，设备只需通过简单的 HTTP 请求，就能将图片直接上传到云端，并自动关联到设备属性中。从此，物联网不再只是 ",[36,1814,1815],{},"\"读数\"","，而是真正 ",[36,1818,1819],{},"\"看得见\"",[25,1821],{},[28,1823,1825],{"id":1824},"这些场景正在因图片而变得更智能","这些场景，正在因\"图片\"而变得更智能 📸",[11,1827,1828],{},"图片上传看似简单，却能解决大量行业场景中的核心痛点：",[193,1830,1832],{"id":1831},"农业虫情监测","🌾 农业虫情监测",[11,1834,1835],{},"虫情测报灯自动诱捕害虫并拍照，设备将照片上传至云平台，结合 AI 识别实现虫害统计和预警，让农田管理从\"靠经验\"走向\"看照片\"。",[193,1837,1839],{"id":1838},"安防联动预警","🚨 安防联动预警",[11,1841,1842],{},"门磁传感器、红外人体感应器触发报警后，联动摄像头抓拍现场照片并上传，管理人员无需到场即可远程确认警情，大幅提升响应效率。",[193,1844,1846],{"id":1845},"消防热成像辅助","🔥 消防热成像辅助",[11,1848,1849],{},"热成像相机检测到温度异常或明火时，自动拍摄可见光照片上传，为消防预警和事后溯源提供直观的影像依据。",[193,1851,1853],{"id":1852},"工业质检追溯","🏭 工业质检追溯",[11,1855,1856],{},"产线视觉检测设备发现产品缺陷时，将异常品照片上传，质量管理人员可随时远程复核，形成完整的质量追溯链条。",[193,1858,1860],{"id":1859},"️-设备远程巡检","🖥️ 设备远程巡检",[11,1862,1863],{},"带有屏幕的工控设备或仪表，定期截屏上传，运维人员坐在办公室就能查看现场界面运行状态，减少不必要的现场出勤。",[193,1865,1867],{"id":1866},"ai-识别结果留档","🤖 AI 识别结果留档",[11,1869,1870],{},"边缘计算设备完成图像识别后，将标记了识别结果的照片上传，用于留档或人工二次确认，确保关键决策有据可查。",[25,1872],{},[28,1874,1876],{"id":1875},"实现方式比你想象的更简单","实现方式比你想象的更简单 ⚡",[11,1878,1879],{},"ThingsCloud 的图片上传服务基于标准 HTTP 协议，对硬件没有特殊要求。无论是通信模组、嵌入式开发板，还是边缘计算设备，只要支持 TCP/IP，就能轻松接入。",[11,1881,1882,1883,1886],{},"设备端只需将图片以",[36,1884,1885],{},"原始二进制数据","的形式，通过 HTTP POST 发送到指定接入点即可：",[1888,1889,1894],"pre",{"className":1890,"code":1892,"language":1893},[1891],"language-text","POST https://\u003Cendpoint>/device/v1/\u003CAccessToken>/\u003Cidentifier>/image\n","text",[1154,1895,1892],{"__ignoreMap":935},[11,1897,1898],{},"平台会自动将图片存储到项目集成的 OSS 对象存储中，并将图片 URL 更新到相关设备属性。整个过程无需您操心存储、CDN 或链接管理。",[11,1900,1901],{},"设备端的接入方式也非常灵活：",[44,1903,1904,1910,1916,1922],{},[47,1905,1906,1909],{},[36,1907,1908],{},"自行构造 HTTP 请求","：适用于具备网络协议栈能力的设备。",[47,1911,1912,1915],{},[36,1913,1914],{},"AT 指令模组","：常见的 2G/3G/4G/NB-IoT 通信模组通常支持 HTTP AT 指令，主控通过串口即可发送图片。",[47,1917,1918,1921],{},[36,1919,1920],{},"开放模组开发","：ESP32、合宙 Air 系列（LuatOS）、移远 QuecPython 等支持脚本开发的模组，可直接调用 HTTP 客户端库实现上传。",[47,1923,1924,1927],{},[36,1925,1926],{},"边缘计算设备","：树莓派、Jetson Nano 等可使用 Python、Node.js 编写上传脚本，灵活处理图片数据。",[19,1929,1930],{},[11,1931,1932,1933,39],{},"详细的接入协议和示例代码，请参阅 ",[900,1934,1937],{"href":1935,"rel":1936},"https://www.thingscloud.xyz/docs/guide/connect-device/image-upload.html",[904],"设备图片上传文档",[25,1939],{},[28,1941,1943],{"id":1942},"上传之后图片在哪里看","上传之后，图片在哪里看？👀",[11,1945,1946],{},"图片上传成功后，会自动成为设备的一个属性值（图片 URL 格式）。您可以在多个场景下直接查看：",[193,1948,1949],{"id":1949},"控制台设备详情页",[11,1951,1952],{},"在 ThingsCloud 控制台中，图片属性支持点击直接查看，无需拼接任何链接。",[11,1954,1955],{},[14,1956],{"alt":1957,"src":1958},"articles/2024/20260426233508_321c1bae780372f1d5efa2de167c7c20.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260426233508_321c1bae780372f1d5efa2de167c7c20.png",[193,1960,1961],{"id":1961},"可视化看板",[11,1963,1964],{},"看板中的图片组件支持绑定设备属性，用户在监控大屏上就能直接查看设备上传的最新照片，实现真正的\"一屏观全局\"。",[11,1966,1967],{},[14,1968],{"alt":1969,"src":1970},"articles/2024/20260426233629_cabc75618c2b5ec071d229d7535e1fe8.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260426233629_cabc75618c2b5ec071d229d7535e1fe8.png",[193,1972,1974],{"id":1973},"用户-app-面板","用户 App 面板",[11,1976,1977],{},"ThingsX 设备面板中可以添加图片组件，绑定设备属性后即可展示设备上传的图片，为终端用户提供直观的设备影像信息。",[11,1979,1980],{},[14,1981],{"alt":1982,"src":1983},"articles/2024/20260426233934_fa29cd620e92e10ae587eb69be2a9d0b.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260426233934_fa29cd620e92e10ae587eb69be2a9d0b.png",[193,1985,1986],{"id":1986},"第三方业务系统",[11,1988,1989],{},"您还可以通过 ThingsCloud 项目 HTTP API，在自有业务系统中读取设备图片 URL，实现更深度的业务集成。",[25,1991],{},[28,1993,1995],{"id":1994},"即刻体验","即刻体验 🚀",[11,1997,1998],{},"ThingsCloud 设备图片上传服务为企业版及以上版本提供支持。如果您希望在项目中启用该能力，只需完成以下两步：",[2000,2001,2002,2009],"ol",{},[47,2003,2004,2005,2008],{},"在 ",[36,2006,2007],{},"项目设置 > 第三方集成"," 中，完成阿里云 OSS 对象存储的配置。",[47,2010,2011,2012,2015,2016,39],{},"在设备类型的物模型中，定义一个",[36,2013,2014],{},"文本类型","的属性，并将其数据格式设为",[36,2017,2018],{},"图片 URL",[11,2020,2021],{},"之后，设备就可以开始上传图片了。",[11,2023,2024,2025,2028],{},"从数字到画面，从感知到见证。ThingsCloud 设备图片上传服务，让物联网的远程监测真正迈入 ",[36,2026,2027],{},"\"眼见为实\""," 的时代。",[25,2030],{},[19,2032,2033],{},[11,2034,2035,2036,39],{},"详细的 API 规范、完整示例代码和错误码说明，请查阅 ",[900,2037,2039],{"href":1935,"rel":2038},[904],"设备图片上传开发文档",{"title":935,"searchDepth":936,"depth":936,"links":2041},[2042,2050,2051,2057],{"id":1824,"depth":936,"text":1825,"children":2043},[2044,2045,2046,2047,2048,2049],{"id":1831,"depth":943,"text":1832},{"id":1838,"depth":943,"text":1839},{"id":1845,"depth":943,"text":1846},{"id":1852,"depth":943,"text":1853},{"id":1859,"depth":943,"text":1860},{"id":1866,"depth":943,"text":1867},{"id":1875,"depth":936,"text":1876},{"id":1942,"depth":936,"text":1943,"children":2052},[2053,2054,2055,2056],{"id":1949,"depth":943,"text":1949},{"id":1961,"depth":943,"text":1961},{"id":1973,"depth":943,"text":1974},{"id":1986,"depth":943,"text":1986},{"id":1994,"depth":936,"text":1995},["Date","2026-04-26T00:00:00.000Z"],"ThingsCloud 正式推出设备图片上传服务，广泛应用于农业虫情监测、安防预警、工业质检等场景。",{},"/blog/feature-device-image-upload-released",{"title":1791,"description":2059},"blog/feature-device-image-upload-released",[976,2065],"device-connect","IkQTLAeQ5KVvabE69iiW3ZyU9RLscuaE1tpunOtcqPA",{"id":2068,"title":2069,"automation":6,"body":2070,"buy":6,"category":6,"categorySlug":6,"createdAt":2879,"description":2880,"deviceRefs":6,"difficulty":6,"estimatedTime":6,"extension":969,"headpic":2077,"image":6,"industry":6,"industrySlug":6,"keywords":6,"links":6,"meta":2881,"model":6,"name":6,"navigation":971,"path":2882,"protocol":6,"scenario":6,"scenarioSlug":6,"seo":2883,"stem":2884,"tagSlugs":2885,"tags":6,"vendor":6,"website":6,"__hash__":2887},"content/blog/how-to-create-devices-automation.md","如何创建你的设备自动化？ThingsCloud 零代码自动化指南",{"type":8,"value":2071,"toc":2857},[2072,2078,2081,2084,2088,2102,2105,2165,2168,2188,2192,2196,2206,2211,2215,2222,2227,2232,2361,2366,2380,2384,2391,2396,2401,2468,2472,2475,2480,2485,2570,2574,2581,2586,2591,2611,2615,2618,2624,2628,2633,2647,2652,2660,2664,2668,2679,2683,2691,2694,2697,2701,2704,2718,2722,2725,2739,2745,2749,2752,2763,2768,2771,2797,2799,2802,2816,2825,2827],[11,2073,2074],{},[14,2075],{"alt":2076,"src":2077},"articles/2024/20260327100605_3a27d6723b4b0b5440dd46c7cb53950f.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260327100605_3a27d6723b4b0b5440dd46c7cb53950f.png",[11,2079,2080],{},"ThingsCloud 自动化功能让物联网系统从\"被动感知\"走向\"主动闭环\"。在告警规则能够及时通知异常的基础上，自动化进一步实现了设备的自主决策和执行——无需人工干预，系统就能根据预设条件自动完成一系列操作。",[11,2082,2083],{},"对于各行业用户而言，这意味着项目落地门槛的大幅降低和运营模式的根本性变革。无需编写代码，业务人员通过可视化配置就能在数分钟内完成复杂的控制逻辑部署。无论是农业大棚的精准灌溉、工业产线的联动保护，还是楼宇设备的节能管控，自动化都能让设备 7×24 小时自主运转，将管理人员从繁琐的重复操作中解放出来，实现真正的无人值守和业务自治。",[28,2085,2087],{"id":2086},"自动化能做什么","自动化能做什么？",[11,2089,2090,2091,39],{},"一句话：",[36,2092,2093,2094,2098,2099],{},"当 ",[2095,2096,2097],"span",{},"某条件"," 满足时，自动执行 ",[2095,2100,2101],{},"某些动作",[11,2103,2104],{},"举几个实际例子：",[85,2106,2107,2119],{},[88,2108,2109],{},[91,2110,2111,2113,2116],{},[94,2112,423],{},[94,2114,2115],{},"触发条件",[94,2117,2118],{},"执行动作",[104,2120,2121,2132,2143,2154],{},[91,2122,2123,2126,2129],{},[109,2124,2125],{},"🌱 智慧农业",[109,2127,2128],{},"土壤湿度 \u003C 30%",[109,2130,2131],{},"开启水泵灌溉，10 分钟后关闭",[91,2133,2134,2137,2140],{},[109,2135,2136],{},"🏭 工业监控",[109,2138,2139],{},"设备温度 > 80℃",[109,2141,2142],{},"开启风机散热，发送告警通知",[91,2144,2145,2148,2151],{},[109,2146,2147],{},"🏠 智能家居",[109,2149,2150],{},"检测到人体移动",[109,2152,2153],{},"自动开灯，5 分钟后关灯",[91,2155,2156,2159,2162],{},[109,2157,2158],{},"🔔 安全监控",[109,2160,2161],{},"门磁被打开",[109,2163,2164],{},"立即推送 APP 通知",[28,2166,2167],{"id":2167},"自动化的工作原理",[44,2169,2170,2176,2182],{},[47,2171,2172,2175],{},[36,2173,2174],{},"触发器","：什么时候启动（如温度超标、定时、手动点击）",[47,2177,2178,2181],{},[36,2179,2180],{},"条件","：额外判断（如只在工作时间执行）",[47,2183,2184,2187],{},[36,2185,2186],{},"动作","：最终执行的操作（如开灯、发通知、延时）",[28,2189,2191],{"id":2190},"如何创建自动化","如何创建自动化？",[193,2193,2195],{"id":2194},"第一步进入创建页面","第一步：进入创建页面",[11,2197,2198,2199,2202,2203,39],{},"点击控制台左侧",[36,2200,2201],{},"自动化","菜单，然后点击右上角",[36,2204,2205],{},"创建自动化",[11,2207,2208],{},[14,2209],{"alt":935,"src":2210},"https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260313144344_fbc3c806a58f379f7c734b520a0ca833.png",[193,2212,2214],{"id":2213},"第二步配置触发器","第二步：配置触发器",[11,2216,2217,2218,2221],{},"触发器是自动化的\"导火索\"。点击",[36,2219,2220],{},"添加触发器","，选择触发类型：",[11,2223,2224],{},[14,2225],{"alt":935,"src":2226},"https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260313144615_047fe74e57597e8478cc7d543f57395a.png",[11,2228,2229],{},[36,2230,2231],{},"所有触发器类型：",[85,2233,2234,2247],{},[88,2235,2236],{},[91,2237,2238,2241,2244],{},[94,2239,2240],{},"类型",[94,2242,2243],{},"用途",[94,2245,2246],{},"示例",[104,2248,2249,2263,2277,2291,2305,2319,2333,2347],{},[91,2250,2251,2257,2260],{},[109,2252,2253,2254],{},"📊 ",[36,2255,2256],{},"设备属性变化",[109,2258,2259],{},"传感器数据变化",[109,2261,2262],{},"温度 > 30℃ 时触发",[91,2264,2265,2271,2274],{},[109,2266,2267,2268],{},"📢 ",[36,2269,2270],{},"设备事件",[109,2272,2273],{},"设备上报特定事件",[109,2275,2276],{},"门被打开、按钮被按下",[91,2278,2279,2285,2288],{},[109,2280,2281,2282],{},"⏰ ",[36,2283,2284],{},"定时触发",[109,2286,2287],{},"按固定时间执行",[109,2289,2290],{},"每天 8:00、18:00 执行",[91,2292,2293,2299,2302],{},[109,2294,2295,2296],{},"📅 ",[36,2297,2298],{},"绝对时间",[109,2300,2301],{},"指定日期时间执行",[109,2303,2304],{},"2026-06-01 09:00 执行一次",[91,2306,2307,2313,2316],{},[109,2308,2309,2310],{},"🔄 ",[36,2311,2312],{},"间隔触发",[109,2314,2315],{},"每隔固定时间执行",[109,2317,2318],{},"每 5 分钟采集一次数据",[91,2320,2321,2327,2330],{},[109,2322,2323,2324],{},"🌅 ",[36,2325,2326],{},"日出日落",[109,2328,2329],{},"根据当地日出日落",[109,2331,2332],{},"日落时自动开灯",[91,2334,2335,2341,2344],{},[109,2336,2337,2338],{},"🔔 ",[36,2339,2340],{},"告警状态变化",[109,2342,2343],{},"告警规则状态变化",[109,2345,2346],{},"告警产生或恢复时触发",[91,2348,2349,2355,2358],{},[109,2350,2351,2352],{},"👆 ",[36,2353,2354],{},"手动触发",[109,2356,2357],{},"人工点击执行",[109,2359,2360],{},"一键开启所有设备",[11,2362,2363],{},[36,2364,2365],{},"配置示例：温度超标检测",[44,2367,2368,2371,2374,2377],{},[47,2369,2370],{},"选择设备：温湿度传感器",[47,2372,2373],{},"选择属性：温度",[47,2375,2376],{},"操作符：大于(>)",[47,2378,2379],{},"阈值：30",[193,2381,2383],{"id":2382},"第三步配置条件可选","第三步：配置条件（可选）",[11,2385,2386,2387,2390],{},"条件用于进一步筛选，",[36,2388,2389],{},"所有条件都满足","才会执行动作。",[11,2392,2393],{},[14,2394],{"alt":935,"src":2395},"https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260313144641_2ac8feb0e8e0eb2f42e2aa43a333b957.png",[11,2397,2398],{},[36,2399,2400],{},"所有条件类型：",[85,2402,2403,2413],{},[88,2404,2405],{},[91,2406,2407,2409,2411],{},[94,2408,2240],{},[94,2410,2243],{},[94,2412,2246],{},[104,2414,2415,2429,2442,2455],{},[91,2416,2417,2423,2426],{},[109,2418,2419,2420],{},"🕐 ",[36,2421,2422],{},"时间范围",[109,2424,2425],{},"只在指定时间段内执行",[109,2427,2428],{},"只在工作时间 09:00-18:00 执行",[91,2430,2431,2436,2439],{},[109,2432,2323,2433],{},[36,2434,2435],{},"日出日落范围",[109,2437,2438],{},"根据日出日落判断",[109,2440,2441],{},"只在夜间执行",[91,2443,2444,2449,2452],{},[109,2445,2253,2446],{},[36,2447,2448],{},"设备属性",[109,2450,2451],{},"检查设备属性值",[109,2453,2454],{},"检查设备是否在线",[91,2456,2457,2462,2465],{},[109,2458,2337,2459],{},[36,2460,2461],{},"告警规则状态",[109,2463,2464],{},"检查告警当前状态",[109,2466,2467],{},"某告警未解除时才执行",[193,2469,2471],{"id":2470},"第四步配置动作","第四步：配置动作",[11,2473,2474],{},"动作是最终要执行的操作，多个动作按顺序执行。",[11,2476,2477],{},[14,2478],{"alt":935,"src":2479},"https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260313144703_f1263419e503bcce0d948a73fe134c71.png",[11,2481,2482],{},[36,2483,2484],{},"所有动作类型：",[85,2486,2487,2498],{},[88,2488,2489],{},[91,2490,2491,2493,2496],{},[94,2492,2240],{},[94,2494,2495],{},"说明",[94,2497,2246],{},[104,2499,2500,2514,2528,2542,2556],{},[91,2501,2502,2508,2511],{},[109,2503,2504,2505],{},"📤 ",[36,2506,2507],{},"下发属性到设备",[109,2509,2510],{},"向设备下发控制命令",[109,2512,2513],{},"打开开关、设置温度",[91,2515,2516,2522,2525],{},[109,2517,2518,2519],{},"☁️ ",[36,2520,2521],{},"更新云端属性",[109,2523,2524],{},"修改平台属性值（不下发设备）",[109,2526,2527],{},"更新统计值、标记状态",[91,2529,2530,2536,2539],{},[109,2531,2532,2533],{},"📋 ",[36,2534,2535],{},"执行任务",[109,2537,2538],{},"让设备执行预定义任务",[109,2540,2541],{},"重启设备、查询状态",[91,2543,2544,2550,2553],{},[109,2545,2546,2547],{},"🎬 ",[36,2548,2549],{},"执行场景",[109,2551,2552],{},"触发另一个场景的执行",[109,2554,2555],{},"执行\"下班模式\"",[91,2557,2558,2564,2567],{},[109,2559,2560,2561],{},"⏱️ ",[36,2562,2563],{},"延迟",[109,2565,2566],{},"等待一段时间再执行下一步",[109,2568,2569],{},"延时 10 分钟后关灯",[193,2571,2573],{"id":2572},"第五步填写基础信息","第五步：填写基础信息",[11,2575,2576,2577,2580],{},"点击",[36,2578,2579],{},"下一步","，填写名称、描述，以及其它设置。",[11,2582,2583],{},[14,2584],{"alt":935,"src":2585},"https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260313144852_f19caaf1bd63a33d622a84c8e7b6d3ad.png",[11,2587,2588],{},[36,2589,2590],{},"其它设置说明：",[44,2592,2593,2599,2605],{},[47,2594,2595,2598],{},[36,2596,2597],{},"自动化时区","：默认跟随项目时区，跨国项目可单独设置",[47,2600,2601,2604],{},[36,2602,2603],{},"并发策略","：正在执行时又有新触发，是放弃还是终止前次",[47,2606,2607,2610],{},[36,2608,2609],{},"失败策略","：某个动作失败时，继续执行还是停止",[28,2612,2614],{"id":2613},"实战案例大棚温控自动化","实战案例：大棚温控自动化",[11,2616,2617],{},"下面我们配置一个实际的温室大棚温度控制自动化：",[11,2619,2620,2623],{},[36,2621,2622],{},"需求","：当温度超过 35℃ 时，自动开启风机；温度降到 28℃ 以下时，自动关闭风机。",[193,2625,2627],{"id":2626},"创建高温开风机自动化","创建\"高温开风机\"自动化",[11,2629,2630],{},[36,2631,2632],{},"触发器配置：",[44,2634,2635,2638,2641,2644],{},[47,2636,2637],{},"类型：设备属性变化",[47,2639,2640],{},"设备：温湿度传感器",[47,2642,2643],{},"属性：温度",[47,2645,2646],{},"条件：大于 35℃",[11,2648,2649],{},[36,2650,2651],{},"动作配置：",[2000,2653,2654,2657],{},[47,2655,2656],{},"下发属性 → 风机设备 → 开关 = ON",[47,2658,2659],{},"更新云端属性 → 标记状态为\"散热中\"",[193,2661,2663],{"id":2662},"创建低温关风机自动化","创建\"低温关风机\"自动化",[11,2665,2666],{},[36,2667,2632],{},[44,2669,2670,2672,2674,2676],{},[47,2671,2637],{},[47,2673,2640],{},[47,2675,2643],{},[47,2677,2678],{},"条件：小于 28℃",[11,2680,2681],{},[36,2682,2651],{},[2000,2684,2685,2688],{},[47,2686,2687],{},"下发属性 → 风机设备 → 开关 = OFF",[47,2689,2690],{},"更新云端属性 → 标记状态为\"待机\"",[11,2692,2693],{},"这样，系统就能自动维持大棚温度在 28℃~35℃ 的舒适区间，无需人工干预。",[28,2695,2696],{"id":2696},"更多实用场景",[193,2698,2700],{"id":2699},"工业设备保护","🏭 工业设备保护",[11,2702,2703],{},"当设备温度超过安全阈值：",[2000,2705,2706,2709,2712,2715],{},[47,2707,2708],{},"立即开启散热风扇",[47,2710,2711],{},"延时 30 秒",[47,2713,2714],{},"如温度仍超标，自动降速运行",[47,2716,2717],{},"如达到极限值，执行停机保护",[193,2719,2721],{"id":2720},"智能灌溉","🚰 智能灌溉",[11,2723,2724],{},"当土壤湿度低于 30%：",[2000,2726,2727,2730,2733,2736],{},[47,2728,2729],{},"开启水泵",[47,2731,2732],{},"延时 10 分钟",[47,2734,2735],{},"关闭水泵",[47,2737,2738],{},"更新灌溉次数统计",[11,2740,2741,2744],{},[36,2742,2743],{},"并发策略建议","：选择\"放弃本次\"，避免正在灌溉时重复触发。",[193,2746,2748],{"id":2747},"会议室节能","🏢 会议室节能",[11,2750,2751],{},"当人体传感器 10 分钟未检测到移动：",[2000,2753,2754,2757,2760],{},[47,2755,2756],{},"延时 10 分钟（等待期）",[47,2758,2759],{},"关闭空调",[47,2761,2762],{},"关闭照明",[11,2764,2765,2767],{},[36,2766,2743],{},"：选择\"终止前次\"，有人返回时重新计时。",[28,2769,2770],{"id":2770},"使用技巧",[2000,2772,2773,2779,2785,2791],{},[47,2774,2775,2778],{},[36,2776,2777],{},"先测试后启用","：创建后保持\"停用\"状态，测试无误再启用",[47,2780,2781,2784],{},[36,2782,2783],{},"命名要清晰","：如\"大棚温度>35℃开风机\"，避免\"自动化1\"这种模糊名称",[47,2786,2787,2790],{},[36,2788,2789],{},"善用标签","：用\"农业\"、\"告警\"等标签分类管理",[47,2792,2793,2796],{},[36,2794,2795],{},"查看日志","：执行详情页可查看每次触发的完整记录",[28,2798,1343],{"id":1343},[11,2800,2801],{},"ThingsCloud 自动化功能让企业无需编写代码，就能构建 7×24 小时无人值守的智能管理系统：",[44,2803,2804,2807,2810,2813],{},[47,2805,2806],{},"✅ 零代码可视化配置",[47,2808,2809],{},"✅ 灵活的触发器、条件、动作组合",[47,2811,2812],{},"✅ 详细的执行日志和统计",[47,2814,2815],{},"✅ 支持延时、场景联动等复杂逻辑",[11,2817,2818,2819,2824],{},"立即登录 ",[900,2820,2823],{"href":2821,"rel":2822},"https://console.thingscloud.xyz/",[904],"ThingsCloud 控制台","，创建你的第一个自动化规则！",[25,2826],{},[19,2828,2829,2834],{},[11,2830,2831],{},[36,2832,2833],{},"了解更多",[44,2835,2836,2843,2850],{},[47,2837,2838],{},[900,2839,2842],{"href":2840,"rel":2841},"https://www.thingscloud.xyz/docs/guide/automations/overview.html",[904],"自动化与场景功能综述",[47,2844,2845],{},[900,2846,2849],{"href":2847,"rel":2848},"https://www.thingscloud.xyz/docs/guide/automations/create-automation.html",[904],"自动化配置指南",[47,2851,2852],{},[900,2853,2856],{"href":2854,"rel":2855},"https://www.thingscloud.xyz/docs/guide/automations/automations-examples.html",[904],"行业自动化应用案例",{"title":935,"searchDepth":936,"depth":936,"links":2858},[2859,2860,2861,2868,2872,2877,2878],{"id":2086,"depth":936,"text":2087},{"id":2167,"depth":936,"text":2167},{"id":2190,"depth":936,"text":2191,"children":2862},[2863,2864,2865,2866,2867],{"id":2194,"depth":943,"text":2195},{"id":2213,"depth":943,"text":2214},{"id":2382,"depth":943,"text":2383},{"id":2470,"depth":943,"text":2471},{"id":2572,"depth":943,"text":2573},{"id":2613,"depth":936,"text":2614,"children":2869},[2870,2871],{"id":2626,"depth":943,"text":2627},{"id":2662,"depth":943,"text":2663},{"id":2696,"depth":936,"text":2696,"children":2873},[2874,2875,2876],{"id":2699,"depth":943,"text":2700},{"id":2720,"depth":943,"text":2721},{"id":2747,"depth":943,"text":2748},{"id":2770,"depth":936,"text":2770},{"id":1343,"depth":936,"text":1343},["Date","2026-03-25T00:00:00.000Z"],"从零开始学习 ThingsCloud 设备自动化功能。无需编写代码，轻松实现 7×24 小时业务无人值守。",{},"/blog/how-to-create-devices-automation",{"title":2069,"description":2880},"blog/how-to-create-devices-automation",[976,2886],"automations","bMZjmLXgbHd7MUDPte19HGHD6bDFd5Ng62SsExHT6QY",{"id":2889,"title":2890,"automation":6,"body":2891,"buy":6,"category":6,"categorySlug":6,"createdAt":3491,"description":3492,"deviceRefs":6,"difficulty":6,"estimatedTime":6,"extension":969,"headpic":3493,"image":6,"industry":6,"industrySlug":6,"keywords":6,"links":6,"meta":3494,"model":6,"name":6,"navigation":971,"path":3495,"protocol":6,"scenario":6,"scenarioSlug":6,"seo":3496,"stem":3497,"tagSlugs":3498,"tags":6,"vendor":6,"website":6,"__hash__":3499},"content/blog/scada-vs-thingscloud-positioning-differences-value.md","工业现场有 SCADA 就够了？这 7 个场景告诉你为什么错了",{"type":8,"value":2892,"toc":3475},[2893,2908,2912,2921,2928,2934,2954,2960,2962,2966,2977,3073,3076,3083,3085,3089,3100,3104,3107,3112,3119,3123,3126,3131,3138,3142,3145,3150,3157,3161,3164,3169,3176,3180,3183,3188,3194,3198,3201,3206,3213,3247,3255,3259,3262,3267,3274,3314,3326,3328,3332,3338,3358,3364,3366,3370,3379,3387,3390,3407,3417,3419,3423,3460,3462],[11,2894,2895,2896,2899,2900,2903,2904,2907],{},"在工业自动化与物联网融合的今天，",[36,2897,2898],{},"SCADA"," 与 ",[36,2901,2902],{},"物联网云平台"," 是企业数字化转型中高频出现的两个核心系统。很多正在使用传统 SCADA 的客户会问：两者是什么关系？各自侧重什么？现有 SCADA 接入物联网云平台，能带来哪些实实在在的价值？本文结合 ",[36,2905,2906],{},"ThingsCloud 物联网平台"," 的实践，为大家清晰解读。",[28,2909,2911],{"id":2910},"一先搞清楚scada-是什么核心定位在哪","一、先搞清楚：SCADA 是什么，核心定位在哪 🔧",[11,2913,2914,2916,2917,2920],{},[36,2915,2898],{},"（Supervisory Control And Data Acquisition），即 ",[36,2918,2919],{},"数据采集与监视控制系统","，是工业现场的 \"本地中控大脑\"。",[11,2922,2923,2924,2927],{},"它部署在厂区/场站本地，直接对接 ",[36,2925,2926],{},"PLC、传感器、仪表、变频器、RTU"," 等现场设备，核心做三件事：",[11,2929,2930],{},[14,2931],{"alt":2932,"src":2933},"articles/2024/20260322215449_a581675124e5e985ec1eb46f31bc87d3.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260322215449_a581675124e5e985ec1eb46f31bc87d3.png",[44,2935,2936,2942,2948],{},[47,2937,2938,2941],{},[36,2939,2940],{},"实时采集","：温度、压力、流量、液位、电流、开关状态等工艺数据；",[47,2943,2944,2947],{},[36,2945,2946],{},"本地监控","：组态画面、实时报警、趋势曲线、本地操作控制；",[47,2949,2950,2953],{},[36,2951,2952],{},"现场闭环","：控制产线启停、阀门调节、传送带运行、设备联锁保护，保障生产安全稳定。",[11,2955,2956,2957,39],{},"简单说：",[36,2958,2959],{},"SCADA 扎根现场，管单一场站/产线的实时控制与本地监视，优先保证本地可靠运行",[25,2961],{},[28,2963,2965],{"id":2964},"二scada-vs-thingscloud-物联网云平台核心区别一目了然","二、SCADA vs ThingsCloud 物联网云平台：核心区别一目了然 📊",[11,2967,2968,2969,2972,2973,2976],{},"两者都做数据采集与设备监控，但 ",[36,2970,2971],{},"部署范围、管理半径、能力侧重"," 完全不同，是 ",[36,2974,2975],{},"互补而非替代"," 关系。",[85,2978,2979,2993],{},[88,2980,2981],{},[91,2982,2983,2987,2990],{},[94,2984,2986],{"align":2985},"left","对比维度",[94,2988,2989],{"align":2985},"传统 SCADA 系统",[94,2991,2992],{"align":2985},"ThingsCloud 物联网云平台",[104,2994,2995,3008,3021,3034,3047,3060],{},[91,2996,2997,3002,3005],{},[109,2998,2999],{"align":2985},[36,3000,3001],{},"部署方式",[109,3003,3004],{"align":2985},"本地工控机/服务器，局域网运行",[109,3006,3007],{"align":2985},"云端全托管，跨网全域访问",[91,3009,3010,3015,3018],{},[109,3011,3012],{"align":2985},[36,3013,3014],{},"管理范围",[109,3016,3017],{"align":2985},"单厂区、单产线、本地闭环",[109,3019,3020],{"align":2985},"多站点、多厂区、全国/全球统一管理",[91,3022,3023,3028,3031],{},[109,3024,3025],{"align":2985},[36,3026,3027],{},"核心侧重",[109,3029,3030],{"align":2985},"现场实时控制、本地安全稳定",[109,3032,3033],{"align":2985},"集中监控、数据汇聚、智能分析、远程运维",[91,3035,3036,3041,3044],{},[109,3037,3038],{"align":2985},[36,3039,3040],{},"数据能力",[109,3042,3043],{"align":2985},"本地存储，基础报表与追溯",[109,3045,3046],{"align":2985},"云端时序数据、AI 分析、预测性维护、数据打通",[91,3048,3049,3054,3057],{},[109,3050,3051],{"align":2985},[36,3052,3053],{},"访问方式",[109,3055,3056],{"align":2985},"控制室本地电脑，受限访问",[109,3058,3059],{"align":2985},"手机/PC/平板，随时随地 Web/App 访问",[91,3061,3062,3067,3070],{},[109,3063,3064],{"align":2985},[36,3065,3066],{},"扩展成本",[109,3068,3069],{"align":2985},"硬件扩容、定制开发，成本高周期长",[109,3071,3072],{"align":2985},"弹性扩容，零代码/低代码快速配置",[11,3074,3075],{},"一句话总结：",[19,3077,3078],{},[11,3079,3080],{},[36,3081,3082],{},"SCADA 是现场 \"执行者\"，管稳生产；ThingsCloud 是云端 \"指挥中心\"，管活全局。",[25,3084],{},[28,3086,3088],{"id":3087},"三现有-scada-用户上云能获得什么核心价值️","三、现有 SCADA 用户，上云能获得什么核心价值？☁️",[11,3090,3091,3092,3095,3096,3099],{},"企业 ",[36,3093,3094],{},"不需要替换"," 现有 SCADA，而是通过 ",[36,3097,3098],{},"边缘网关 + 云平台","，让本地 SCADA 数据安全上云，快速升级数字化能力。",[193,3101,3103],{"id":3102},"_1-打破地域限制实现全域远程监控","1. 打破地域限制，实现全域远程监控 🌍",[11,3105,3106],{},"传统 SCADA 只能在控制室看，管理人员、运维人员必须到现场。",[11,3108,3109],{},[14,3110],{"alt":935,"src":3111},"https://img-1300291923.cos.accelerate.myqcloud.com/articles/2023/20231215180034_e0b0d9d827e49cbf743a394653b10422.png",[11,3113,3114,3115,3118],{},"接入 ThingsCloud 后，",[36,3116,3117],{},"手机、电脑随时随地查看实时数据、工艺画面、设备状态","，跨厂区、跨城市统一监管，真正实现 \"现场有人值守，云端全域掌控\"。",[193,3120,3122],{"id":3121},"_2-打通数据孤岛集团化统一管理","2. 打通数据孤岛，集团化统一管理 🔗",[11,3124,3125],{},"多工厂、多场站的 SCADA 数据相互孤立，无法汇总对比。",[11,3127,3128],{},[14,3129],{"alt":935,"src":3130},"https://img-1300291923.cos.accelerate.myqcloud.com/articles/2023/20231217104940_2b7bf9b9b83206af1903550eaa554d7d.png",[11,3132,3133,3134,3137],{},"ThingsCloud 支持",[36,3135,3136],{},"海量 SCADA 系统统一接入、数据标准化汇聚","，集团层面可实时查看各站点产能、能耗、设备效率，数据一盘棋，决策更精准。",[193,3139,3141],{"id":3140},"_3-升级数据能力从-看数据-到-用数据","3. 升级数据能力，从 \"看数据\" 到 \"用数据\" 📈",[11,3143,3144],{},"传统 SCADA 以本地存储和基础报表为主，难以做深度分析。",[11,3146,3147],{},[14,3148],{"alt":935,"src":3149},"https://img-1300291923.cos.accelerate.myqcloud.com/articles/2023/20231215195216_87078c67b3a1a1559bcbaec844572190.png",[11,3151,3152,3153,3156],{},"平台提供",[36,3154,3155],{},"云端时序数据库、历史曲线、智能告警、能耗分析、预测性维护","，让历史数据转化为优化依据，提前预判故障、降低停机损失。",[193,3158,3160],{"id":3159},"_4-降低运维成本提升管理效率","4. 降低运维成本，提升管理效率 💰",[11,3162,3163],{},"本地 SCADA 维护依赖专人驻场，硬件故障、系统升级繁琐。",[11,3165,3166],{},[14,3167],{"alt":935,"src":3168},"https://img-1300291923.cos.accelerate.myqcloud.com/articles/2023/20231216203333_13ab90579ae16302f4394b3e06841b69.png",[11,3170,3171,3172,3175],{},"ThingsCloud 提供",[36,3173,3174],{},"远程配置、OTA 升级、告警推送、工单联动","，减少现场出差频次，简化运维流程，中小场景运维成本可显著降低。",[193,3177,3179],{"id":3178},"_5-开放集成打通-ot-与-it","5. 开放集成，打通 OT 与 IT 🔌",[11,3181,3182],{},"传统 SCADA 对接 ERP、MES 等信息化系统难度大、成本高。",[11,3184,3185],{},[14,3186],{"alt":935,"src":3187},"https://img-1300291923.cos.accelerate.myqcloud.com/articles/2023/20231216215444_8ccf55679270c97a2f8bcecd4677e93a.png",[11,3189,3152,3190,3193],{},[36,3191,3192],{},"开放 API、标准协议适配","，轻松实现设备数据与业务系统互通，推动 OT 与 IT 深度融合，支撑企业全流程数字化。",[193,3195,3197],{"id":3196},"_6-零代码生成移动端应用提升管理效率","6. 零代码生成移动端应用，提升管理效率 📱",[11,3199,3200],{},"传统 SCADA 只能在控制室通过固定工位查看，管理人员必须到现场或通过 VPN 访问内网才能了解设备状态。",[11,3202,3203],{},[14,3204],{"alt":935,"src":3205},"https://img-1300291923.cos.accelerate.myqcloud.com/articles/2023/20231215220714_95a783cf17d854bf06d8efd0c41a7e2b.png",[11,3207,3208,3209,3212],{},"ThingsCloud 提供 ",[36,3210,3211],{},"零代码 App 生成能力","，让 SCADA 数据直达移动端：",[44,3214,3215,3225,3231,3241],{},[47,3216,3217,3220,3221,3224],{},[36,3218,3219],{},"多端覆盖","：无需编写代码，即可生成 ",[36,3222,3223],{},"iOS、Android、微信小程序、Web App"," 等多端应用",[47,3226,3227,3230],{},[36,3228,3229],{},"设备面板自定义","：通过可视化组件拖拽，快速构建设备详情页，实时数据、历史曲线、控制按钮一目了然",[47,3232,3233,3236,3237,3240],{},[36,3234,3235],{},"移动告警触达","：设备异常时，告警信息通过 ",[36,3238,3239],{},"微信公众号、短信、App 推送"," 直达责任人手机，实现随时随地响应",[47,3242,3243,3246],{},[36,3244,3245],{},"扫码即控","：用户通过手机扫描二维码即可绑定设备，无需复杂的账号配置流程",[19,3248,3249],{},[11,3250,3251,3252,39],{},"管理人员无论身处何地，都能通过手机实时掌握产线运行状态，",[36,3253,3254],{},"管理半径从 \"控制室\" 扩展到 \"全球任意角落\"",[193,3256,3258],{"id":3257},"_7-云端自动化编排实现跨设备智能联动","7. 云端自动化编排，实现跨设备智能联动 ⚡",[11,3260,3261],{},"传统 SCADA 实现设备联动控制依赖底层 PLC 编程，逻辑硬编码、调试周期长，且难以跨产线、跨厂区协同。",[11,3263,3264],{},[14,3265],{"alt":935,"src":3266},"https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260318215636_14fd4460c40b3f0345c3636e75c523fa.png",[11,3268,3269,3270,3273],{},"ThingsCloud 的 ",[36,3271,3272],{},"云侧自动化规则引擎","，让业务逻辑与底层硬件解耦：",[44,3275,3276,3286,3292,3302,3308],{},[47,3277,3278,3281,3282,3285],{},[36,3279,3280],{},"零代码逻辑编排","：通过可视化界面配置 ",[36,3283,3284],{},"触发器-条件-动作"," 规则，无需编写 PLC 程序或脚本代码",[47,3287,3288,3291],{},[36,3289,3290],{},"跨设备集群联动","：支持跨产线、跨厂区的异构设备协同，例如 \"A 厂区温度超标自动触发 B 厂区风机联动\"",[47,3293,3294,3297,3298,3301],{},[36,3295,3296],{},"云端实时生效","：规则配置完成后即时生效，",[36,3299,3300],{},"无需停机部署、无需硬件烧录","，大幅降低调试成本",[47,3303,3304,3307],{},[36,3305,3306],{},"秒级响应","：支持秒级本地或云端联动，满足实时性要求高的工业场景",[47,3309,3310,3313],{},[36,3311,3312],{},"复杂场景编排","：内置延时、条件分支、场景模板等能力，轻松实现 \"温度超限 → 开启风机 → 延时 5 分钟 → 检查温度 → 决定是否关闭\" 等复杂闭环逻辑",[19,3315,3316],{},[11,3317,3318,3319,3322,3323,39],{},"自动化逻辑从 \"硬件层\" 上移至 \"云端\"，让工程师",[36,3320,3321],{},"专注于业务策略而非底层通信协议","，缩短从构思到落地的周期，实现真正的 ",[36,3324,3325],{},"业务自治",[25,3327],{},[28,3329,3331],{"id":3330},"四最佳实践scada-thingscloud稳现场-强云端","四、最佳实践：SCADA + ThingsCloud，稳现场 + 强云端 🤝",[11,3333,3334,3335,1350],{},"对于工业企业，最优方案不是替换，而是 ",[36,3336,3337],{},"协同",[2000,3339,3340,3346,3352],{},[47,3341,3342,3345],{},[36,3343,3344],{},"现场层","：保留现有 SCADA，继续负责本地实时控制、联锁保护，保障生产稳定；",[47,3347,3348,3351],{},[36,3349,3350],{},"边缘层","：通过边缘网关采集 SCADA/PLC 数据，断网续传、本地缓存，安全上云；",[47,3353,3354,3357],{},[36,3355,3356],{},"云端层","：ThingsCloud 负责集中监控、数据分析、远程运维、智能决策。",[11,3359,3360,3363],{},[36,3361,3362],{},"现场稳生产，云端提效率","，兼顾安全性与灵活性，是工业数字化转型的成熟路径。",[25,3365],{},[28,3367,3369],{"id":3368},"五结语","五、结语 🌟",[11,3371,3372,3374,3375,3378],{},[36,3373,2898],{}," 是工业自动化的基石，负责 ",[36,3376,3377],{},"把现场管好","；",[11,3380,3381,3383,3384,39],{},[36,3382,2992],{}," 是数字化升级的引擎，负责 ",[36,3385,3386],{},"把全局用活",[11,3388,3389],{},"如果您正在使用传统 SCADA，希望：",[44,3391,3392,3395,3398,3401,3404],{},[47,3393,3394],{},"🌍 突破地域限制",[47,3396,3397],{},"🏭 实现多站点统一管理",[47,3399,3400],{},"📊 挖掘数据价值",[47,3402,3403],{},"📱 获得移动端管理能力",[47,3405,3406],{},"⚡ 实现跨设备智能联动",[11,3408,3409,3410,3412,3413,3416],{},"欢迎对接 ",[36,3411,2906],{},"，我们以 ",[36,3414,3415],{},"极简接入、稳定可靠、开放灵活"," 的能力，助力企业轻松实现 SCADA 上云，迈向更高效、智能的工业数字化新阶段。",[25,3418],{},[28,3420,3422],{"id":3421},"立即体验","立即体验 🚀",[44,3424,3425,3431,3437,3444,3452],{},[47,3426,3427,3430],{},[900,3428,2823],{"href":2821,"rel":3429},[904]," —— 免费注册，快速开始",[47,3432,3433,3436],{},[900,3434,1411],{"href":1409,"rel":3435},[904]," —— 了解如何将 SCADA 数据上云",[47,3438,3439,3443],{},[900,3440,1961],{"href":3441,"rel":3442},"https://www.thingscloud.xyz/features/devices-visualization/",[904]," —— 探索数据可视化能力",[47,3445,3446,3451],{},[900,3447,3450],{"href":3448,"rel":3449},"https://www.thingscloud.xyz/features/automations/",[904],"设备自动化"," —— 让物联网真正运转起来",[47,3453,3454,3459],{},[900,3455,3458],{"href":3456,"rel":3457},"https://www.thingscloud.xyz/docs/guide/api/project-api.html",[904],"开放 API 文档"," —— 实现与业务系统深度集成",[25,3461],{},[19,3463,3464],{},[11,3465,3466],{},[36,3467,3468,3469,3474],{},"访问 ",[900,3470,3473],{"href":3471,"rel":3472},"https://www.thingscloud.xyz",[904],"ThingsCloud 官网","，开启您的工业数字化升级之旅。",{"title":935,"searchDepth":936,"depth":936,"links":3476},[3477,3478,3479,3488,3489,3490],{"id":2910,"depth":936,"text":2911},{"id":2964,"depth":936,"text":2965},{"id":3087,"depth":936,"text":3088,"children":3480},[3481,3482,3483,3484,3485,3486,3487],{"id":3102,"depth":943,"text":3103},{"id":3121,"depth":943,"text":3122},{"id":3140,"depth":943,"text":3141},{"id":3159,"depth":943,"text":3160},{"id":3178,"depth":943,"text":3179},{"id":3196,"depth":943,"text":3197},{"id":3257,"depth":943,"text":3258},{"id":3330,"depth":936,"text":3331},{"id":3368,"depth":936,"text":3369},{"id":3421,"depth":936,"text":3422},["Date","2026-03-19T00:00:00.000Z"],"SCADA 只能管现场，云平台才能管全局。7 个真实场景，带你看清 SCADA 上云的核心价值与最佳实践。","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260322214951_400ceef17afa392b8e368be8503f5915.png",{},"/blog/scada-vs-thingscloud-positioning-differences-value",{"title":2890,"description":3492},"blog/scada-vs-thingscloud-positioning-differences-value",[977,976],"j33wwoBAkAbDiKo7EI9dPouipoEMM1Qk1-Jd9EBxXgM",{"id":3501,"title":3502,"automation":6,"body":3503,"buy":6,"category":6,"categorySlug":6,"createdAt":4194,"description":4195,"deviceRefs":6,"difficulty":6,"estimatedTime":6,"extension":969,"headpic":3510,"image":6,"industry":6,"industrySlug":6,"keywords":6,"links":6,"meta":4196,"model":6,"name":6,"navigation":971,"path":4197,"protocol":6,"scenario":6,"scenarioSlug":6,"seo":4198,"stem":4199,"tagSlugs":4200,"tags":6,"vendor":6,"website":6,"__hash__":4201},"content/blog/smart-aquaculture-automation.md","养殖不用熬夜巡塘，设备自动护池，再也不怕泛塘、死鱼、闷棚",{"type":8,"value":3504,"toc":4170},[3505,3511,3514,3519,3529,3539,3542,3553,3555,3559,3562,3618,3621,3626,3629,3634,3640,3645,3648,3653,3656,3663,3669,3671,3675,3682,3685,3754,3757,3789,3791,3795,3799,3805,3810,3845,3847,3851,3856,3860,3883,3885,3889,3894,3898,3920,3922,3926,3929,3984,3987,4013,4015,4019,4022,4091,4093,4097,4100,4120,4122,4126,4147,4149],[11,3506,3507],{},[14,3508],{"alt":3509,"src":3510},"articles/2024/20260317112428_1f8897c51eedf3dfc48015757345b04c.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260317112428_1f8897c51eedf3dfc48015757345b04c.png",[11,3512,3513],{},"在现代水产养殖中，环境指标的剧烈波动是导致货损的主要原因：",[19,3515,3516],{},[11,3517,3518],{},"溶氧量在凌晨时段骤降导致鱼群浮头；\n突发停电导致增氧设备停止运行，未能及时发现；\n夏季持续高温导致水温超限，引发病害或死亡。",[11,3520,3521,3522,3525,3526,39],{},"任何一次环境异常，都可能造成 ",[36,3523,3524],{},"整季收成的损失","，甚至导致 ",[36,3527,3528],{},"前期投入的资源付诸东流",[11,3530,3531,3532,3535,3536,39],{},"传统的养殖模式高度依赖 ",[36,3533,3534],{},"人工值守与经验判断"," —— 管理人员需要定期巡塘、手动测量溶氧及水质指标。然而，由于生理限制和管理间隙，",[36,3537,3538],{},"环境风险往往发生在监测盲区内",[11,3540,3541],{},"ThingsCloud 自动化方案通过技术手段解决了这一难题。",[11,3543,3544,3545,3548,3549,3552],{},"通过 ",[36,3546,3547],{},"溶氧低自动联动增氧、氨氮高自动换水、温度异常自动调节","，系统实现了 ",[36,3550,3551],{},"24 小时持续监控与自动响应","，将养殖管理从“经验驱动”升级为“数据驱动”。",[25,3554],{},[28,3556,3558],{"id":3557},"一传统养殖的管理挑战环境复杂与人工局限","一、传统养殖的管理挑战：环境复杂与人工局限 😫",[193,3560,3561],{"id":3561},"夜间环境风险分析",[85,3563,3564,3577],{},[88,3565,3566],{},[91,3567,3568,3571,3574],{},[94,3569,3570],{},"时间",[94,3572,3573],{},"环境风险",[94,3575,3576],{},"潜在后果",[104,3578,3579,3592,3605],{},[91,3580,3581,3586,3589],{},[109,3582,3583],{},[36,3584,3585],{},"凌晨 2-4 点",[109,3587,3588],{},"水体溶氧降至最低点",[109,3590,3591],{},"缺氧浮头、大规模死亡",[91,3593,3594,3599,3602],{},[109,3595,3596],{},[36,3597,3598],{},"夏季高温期",[109,3600,3601],{},"高温低压导致溶氧效率降低",[109,3603,3604],{},"闷棚、鱼类窒息",[91,3606,3607,3612,3615],{},[109,3608,3609],{},[36,3610,3611],{},"恶劣天气",[109,3613,3614],{},"水质突变，氨氮/亚硝酸盐指标升高",[109,3616,3617],{},"中毒、病害爆发",[193,3619,3620],{"id":3620},"人工管理的局限性",[11,3622,3623],{},[36,3624,3625],{},"🌙 局限一：监测频率不足",[11,3627,3628],{},"人工巡塘无法覆盖全天候的所有时间段，尤其在深夜和极端天气下，监测盲区极大。",[11,3630,3631],{},[36,3632,3633],{},"⏱️ 局限二：响应延迟",[11,3635,3636,3637,39],{},"从发现环境异常到人工采取措施（如开启泵机、换水），存在明显的反应滞后。在缺氧等极端情况下，",[36,3638,3639],{},"响应速度直接决定了成活率",[11,3641,3642],{},[36,3643,3644],{},"👀 局限三：多塘管理难度大",[11,3646,3647],{},"当养殖规模扩大、池塘分布较广时，单人管理多个池塘的效率会大幅下降，难以保证每个池塘都能得到及时关注。",[11,3649,3650],{},[36,3651,3652],{},"😰 局限四：缺乏数据沉淀",[11,3654,3655],{},"依靠经验判断缺乏准确性，且无法形成长期的环境数据记录，难以优化后续的养殖策略。",[19,3657,3658],{},[11,3659,3660],{},[36,3661,3662],{},"传统养殖依赖人力，智慧养殖依靠自动化数据闭环。",[11,3664,3665,3666,39],{},"ThingsCloud 自动化旨在通过技术手段消除 ",[36,3667,3668],{},"管理不确定性",[25,3670],{},[28,3672,3674],{"id":3673},"二24-小时自动值守方案数据监测与自动控制","二、24 小时自动值守方案：数据监测与自动控制 🤖",[11,3676,3677,3678,3681],{},"ThingsCloud 自动化方案通过部署工业级传感器与智能控制器，构建了从 ",[36,3679,3680],{},"数据采集到逻辑执行"," 的闭环体系。",[193,3683,3684],{"id":3684},"关键监测指标",[85,3686,3687,3700],{},[88,3688,3689],{},[91,3690,3691,3694,3697],{},[94,3692,3693],{},"指标",[94,3695,3696],{},"硬件设备",[94,3698,3699],{},"核心功能",[104,3701,3702,3715,3728,3741],{},[91,3703,3704,3709,3712],{},[109,3705,3706],{},[36,3707,3708],{},"溶解氧",[109,3710,3711],{},"溶氧传感器",[109,3713,3714],{},"实时监测水体含氧量，预防窒息风险",[91,3716,3717,3722,3725],{},[109,3718,3719],{},[36,3720,3721],{},"水温",[109,3723,3724],{},"温度传感器",[109,3726,3727],{},"监控水温趋势，防止应激反应",[91,3729,3730,3735,3738],{},[109,3731,3732],{},[36,3733,3734],{},"pH 值",[109,3736,3737],{},"pH 传感器",[109,3739,3740],{},"实时监测酸碱度，维持平衡环境",[91,3742,3743,3748,3751],{},[109,3744,3745],{},[36,3746,3747],{},"水质指标",[109,3749,3750],{},"复合水质传感器",[109,3752,3753],{},"检测氨氮、亚硝酸盐，预防中毒",[193,3755,3756],{"id":3756},"自动化执行逻辑",[2000,3758,3759,3769,3783],{},[47,3760,3761,3764,3765,3768],{},[36,3762,3763],{},"溶氧保护机制","：当水体溶氧低于 ",[36,3766,3767],{},"5mg/L"," 时，系统秒级识别异常并自动启动增氧机；待溶氧恢复至安全阈值后，设备自动停机。",[47,3770,3771,3774,3775,3778,3779,3782],{},[36,3772,3773],{},"温度调节机制","：当水温超过 ",[36,3776,3777],{},"32℃","（高温预警）或低于 ",[36,3780,3781],{},"10℃","（低温预警）时，系统自动联动降温或加热设备，确保环境稳定。",[47,3784,3785,3788],{},[36,3786,3787],{},"水质干预机制","：当氨氮或有害物质浓度超过安全上限时，系统自动启动换水泵进行水体置换，并同步向管理人员推送高优先级告警。",[25,3790],{},[28,3792,3794],{"id":3793},"三核心应用场景预防性管理与风险对冲-️","三、核心应用场景：预防性管理与风险对冲 🛡️",[193,3796,3798],{"id":3797},"场景一低溶氧自动增氧","场景一：低溶氧自动增氧 🌙",[11,3800,3801,3804],{},[36,3802,3803],{},"风险现状：","\n凌晨时段溶氧量自然下降，若人工发现不及时，鱼群在极短时间内便会受损。",[11,3806,3807],{},[36,3808,3809],{},"ThingsCloud 自动化方案：",[44,3811,3812,3822,3832,3838],{},[47,3813,3814,3815,3818,3819,3821],{},"🚨 ",[36,3816,3817],{},"阈值预警","：溶氧降至 ",[36,3820,3767],{}," 时，发送系统通知。",[47,3823,3824,3825,3818,3828,3831],{},"⚡ ",[36,3826,3827],{},"自动执行",[36,3829,3830],{},"4mg/L"," 时，自动开启增氧机组。",[47,3833,2337,3834,3837],{},[36,3835,3836],{},"紧急通知","：若指标持续恶化，系统通过电话/短信推送紧急告警。",[47,3839,3840,3841,3844],{},"✅ ",[36,3842,3843],{},"自动恢复","：溶氧达标后，系统自动停机，节约能耗。",[25,3846],{},[193,3848,3850],{"id":3849},"场景二极端气温自动调控-️","场景二：极端气温自动调控 🌡️",[11,3852,3853,3855],{},[36,3854,3803],{},"\n夏季高温导致水温持续上升，超出鱼类耐受极限，引发大面积货损。",[11,3857,3858],{},[36,3859,3809],{},[44,3861,3862,3869,3876],{},[47,3863,3864,3865,3868],{},"🌡️ ",[36,3866,3867],{},"分级控制","：达到预设温度时，依次开启遮阳系统、循环泵。",[47,3870,3871,3872,3875],{},"❄️ ",[36,3873,3874],{},"联动降温","：触发高危温度时，启动紧急换水或大功率制冷辅助。",[47,3877,3878,3879,3882],{},"📱 ",[36,3880,3881],{},"状态追踪","：管理人员可随时通过手机查看当前调控进度。",[25,3884],{},[193,3886,3888],{"id":3887},"场景三水质超标自动处置","场景三：水质超标自动处置 💧",[11,3890,3891,3893],{},[36,3892,3803],{},"\n饲料残留导致氨氮超标，若处理不及时会诱发爆发性病害。",[11,3895,3896],{},[36,3897,3809],{},[44,3899,3900,3907,3913],{},[47,3901,3902,3903,3906],{},"☠️ ",[36,3904,3905],{},"实时检测","：传感器 24 小时在线监测水质。",[47,3908,2309,3909,3912],{},[36,3910,3911],{},"自动净化","：指标异常时自动开启爆气及排灌系统。",[47,3914,3915,3916,3919],{},"📝 ",[36,3917,3918],{},"日志记录","：系统自动记录事件起因及处理结果，供管理层复盘。",[25,3921],{},[28,3923,3925],{"id":3924},"四部署与配置流程","四、部署与配置流程 🚀",[193,3927,3928],{"id":3928},"硬件选型建议",[85,3930,3931,3943],{},[88,3932,3933],{},[91,3934,3935,3938,3940],{},[94,3936,3937],{},"设备类别",[94,3939,3699],{},[94,3941,3942],{},"部署建议",[104,3944,3945,3958,3971],{},[91,3946,3947,3952,3955],{},[109,3948,3949],{},[36,3950,3951],{},"智能采集终端",[109,3953,3954],{},"接入各类传感器数据",[109,3956,3957],{},"靠近监控区域的防护箱内",[91,3959,3960,3965,3968],{},[109,3961,3962],{},[36,3963,3964],{},"传感器组",[109,3966,3967],{},"采集溶氧、温度、pH 等数据",[109,3969,3970],{},"池塘代表性采样点水下部署",[91,3972,3973,3978,3981],{},[109,3974,3975],{},[36,3976,3977],{},"控制器/继电器",[109,3979,3980],{},"控制泵机、电机开关",[109,3982,3983],{},"接入现有配电柜",[193,3985,3986],{"id":3986},"快速配置步骤",[2000,3988,3989,3995,4007],{},[47,3990,3991,3994],{},[36,3992,3993],{},"设备接入","：将各传感器及控制器接入 ThingsCloud 平台，实现数据上云。",[47,3996,3997,4000,4001,2899,4004,39],{},[36,3998,3999],{},"逻辑配置","：基于 ThingsCloud 自动化引擎，设定 ",[36,4002,4003],{},"触发器（如溶氧 \u003C 5）",[36,4005,4006],{},"执行动作（如开启增氧机）",[47,4008,4009,4012],{},[36,4010,4011],{},"系统上线","：开启规则，系统进入 24 小时全自动化监控模式。",[25,4014],{},[28,4016,4018],{"id":4017},"五方案应用价值分析","五、方案应用价值分析 😴",[193,4020,4021],{"id":4021},"某水产养殖基地应用对比",[85,4023,4024,4037],{},[88,4025,4026],{},[91,4027,4028,4031,4034],{},[94,4029,4030],{},"核心指标",[94,4032,4033],{},"部署自动化方案前",[94,4035,4036],{},"部署自动化方案后",[104,4038,4039,4052,4065,4078],{},[91,4040,4041,4044,4047],{},[109,4042,4043],{},"异常响应时间",[109,4045,4046],{},"15 - 30 分钟（人工）",[109,4048,4049],{},[36,4050,4051],{},"\u003C 3 秒（系统）",[91,4053,4054,4057,4060],{},[109,4055,4056],{},"货损风险率",[109,4058,4059],{},"较高，受人为因素影响大",[109,4061,4062],{},[36,4063,4064],{},"极低，具备冗余保护机制",[91,4066,4067,4070,4073],{},[109,4068,4069],{},"人力投入",[109,4071,4072],{},"需专人夜间巡检",[109,4074,4075],{},[36,4076,4077],{},"远程监控，异常响应",[91,4079,4080,4083,4086],{},[109,4081,4082],{},"运行能耗",[109,4084,4085],{},"手动开关，运行时间过长",[109,4087,4088],{},[36,4089,4090],{},"根据指标精准控制，节能 20%",[25,4092],{},[28,4094,4096],{"id":4095},"六结语迈向无人值守的智慧养殖","六、结语：迈向无人值守的智慧养殖 🌟",[11,4098,4099],{},"ThingsCloud 自动化方案帮助养殖企业实现了：",[44,4101,4102,4108,4114],{},[47,4103,3840,4104,4107],{},[36,4105,4106],{},"精细化环境控制"," —— 确保各项环境指标处于最优范围。",[47,4109,3840,4110,4113],{},[36,4111,4112],{},"风险秒级响应"," —— 将意外损失降至最低水平。",[47,4115,3840,4116,4119],{},[36,4117,4118],{},"降本增效"," —— 减少人工成本与能源浪费，保障收成稳定性。",[25,4121],{},[28,4123,4125],{"id":4124},"进一步了解方案","进一步了解方案 🚀",[44,4127,4128,4134,4140],{},[47,4129,4130],{},[900,4131,4133],{"href":2840,"rel":4132},[904],"了解 ThingsCloud 自动化功能",[47,4135,4136],{},[900,4137,4139],{"href":2854,"rel":4138},[904],"查看自动化应用示例",[47,4141,4142],{},[900,4143,4146],{"href":4144,"rel":4145},"https://www.thingscloud.xyz/docs/contact.html",[904],"联系我们获取专属方案",[25,4148],{},[19,4150,4151,4156,4161],{},[11,4152,4153],{},[36,4154,4155],{},"通过技术手段构建安全防线。",[11,4157,4158],{},[36,4159,4160],{},"ThingsCloud 自动化，为每一口塘提供稳定保障。",[11,4162,4163],{},[36,4164,3468,4165,4169],{},[900,4166,3473],{"href":4167,"rel":4168},"https://www.thingscloud.xyz/docs/",[904],"，开启智慧养殖转型之旅！",{"title":935,"searchDepth":936,"depth":936,"links":4171},[4172,4176,4180,4185,4189,4192,4193],{"id":3557,"depth":936,"text":3558,"children":4173},[4174,4175],{"id":3561,"depth":943,"text":3561},{"id":3620,"depth":943,"text":3620},{"id":3673,"depth":936,"text":3674,"children":4177},[4178,4179],{"id":3684,"depth":943,"text":3684},{"id":3756,"depth":943,"text":3756},{"id":3793,"depth":936,"text":3794,"children":4181},[4182,4183,4184],{"id":3797,"depth":943,"text":3798},{"id":3849,"depth":943,"text":3850},{"id":3887,"depth":943,"text":3888},{"id":3924,"depth":936,"text":3925,"children":4186},[4187,4188],{"id":3928,"depth":943,"text":3928},{"id":3986,"depth":943,"text":3986},{"id":4017,"depth":936,"text":4018,"children":4190},[4191],{"id":4021,"depth":943,"text":4021},{"id":4095,"depth":936,"text":4096},{"id":4124,"depth":936,"text":4125},["Date","2026-03-10T00:00:00.000Z"],"养殖不再靠天吃饭。智慧养殖方案实时监控水质，溶氧不足自动增氧，全天候守护鱼塘，告别熬夜巡塘，再不怕死鱼泛塘。",{},"/blog/smart-aquaculture-automation",{"title":3502,"description":4195},"blog/smart-aquaculture-automation",[977,2886],"nvrKtTi7-6FOsM2nmy6Nq2RoCAM25o18lOt-j2IwUO8",{"id":4203,"title":4204,"automation":6,"body":4205,"buy":6,"category":6,"categorySlug":6,"createdAt":4805,"description":4806,"deviceRefs":6,"difficulty":6,"estimatedTime":6,"extension":969,"headpic":4212,"image":6,"industry":6,"industrySlug":6,"keywords":6,"links":6,"meta":4807,"model":6,"name":6,"navigation":971,"path":4808,"protocol":6,"scenario":6,"scenarioSlug":6,"seo":4809,"stem":4810,"tagSlugs":4811,"tags":6,"vendor":6,"website":6,"__hash__":4812},"content/blog/smart-cold-chain-automation.md","冷链不用人整夜盯仓，温湿度一超标自动调节，从源头杜绝货损",{"type":8,"value":4206,"toc":4782},[4207,4213,4216,4221,4227,4234,4241,4251,4253,4257,4260,4329,4332,4337,4340,4345,4351,4356,4359,4364,4367,4374,4376,4380,4383,4386,4455,4458,4488,4490,4494,4498,4503,4507,4531,4533,4537,4542,4546,4561,4563,4567,4572,4576,4597,4599,4603,4606,4629,4631,4635,4638,4705,4707,4711,4714,4734,4736,4740,4760,4762],[11,4208,4209],{},[14,4210],{"alt":4211,"src":4212},"articles/2024/20260315190953_6e534c5b2149cb9ef8fe4cc6b96e34d4.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260315190953_6e534c5b2149cb9ef8fe4cc6b96e34d4.png",[11,4214,4215],{},"在冷链仓储行业，环境参数的波动直接关系到货物的品质安全：",[19,4217,4218],{},[11,4219,4220],{},"制冷机组发生故障导致温度漂移，生鲜产品变质；\n库门未严密关闭导致冷气外泄，增加能耗并影响药品效价；\n环境湿度过高引发干货霉变，造成不可逆的货损。",[11,4222,4223,4224,39],{},"冷链管理的核心挑战在于：",[36,4225,4226],{},"温湿度偏离阈值的时间越长，货损风险呈指数级增长",[11,4228,4229,4230,4233],{},"传统的管理模式依赖 ",[36,4231,4232],{},"人工巡检与手动记录"," —— 管理人员需定时抄表并监控设备状态。但在夜间或多库并发异常时，人工响应的滞后性往往成为风险爆发的诱因。",[11,4235,4236,4237,4240],{},"ThingsCloud 自动化方案通过 ",[36,4238,4239],{},"实时环境感知与预设逻辑执行","，实现了冷链管理的智能化升级。",[11,4242,3544,4243,4246,4247,4250],{},[36,4244,4245],{},"温度漂移自动补偿、湿度超标自动除湿、系统故障自动告警","，系统构建了 ",[36,4248,4249],{},"7×24 小时的自动化安全防线","，从源头杜绝货损风险。",[25,4252],{},[28,4254,4256],{"id":4255},"一冷链管理的痛点环境敏感度与人工监测局限-️","一、冷链管理的痛点：环境敏感度与人工监测局限 🌡️",[193,4258,4259],{"id":4259},"环境敏感货物分类及风险",[85,4261,4262,4275],{},[88,4263,4264],{},[91,4265,4266,4269,4272],{},[94,4267,4268],{},"货物类别",[94,4270,4271],{},"存储温度要求",[94,4273,4274],{},"异常风险后果",[104,4276,4277,4290,4303,4316],{},[91,4278,4279,4284,4287],{},[109,4280,4281],{},[36,4282,4283],{},"生物医药/疫苗",[109,4285,4286],{},"2-8℃",[109,4288,4289],{},"效价失效，面临合规风险与巨额损失",[91,4291,4292,4297,4300],{},[109,4293,4294],{},[36,4295,4296],{},"冷冻食品/海鲜",[109,4298,4299],{},"≤ -18℃",[109,4301,4302],{},"解冻引发微生物超标，食品安全风险",[91,4304,4305,4310,4313],{},[109,4306,4307],{},[36,4308,4309],{},"生鲜果蔬",[109,4311,4312],{},"0-4℃",[109,4314,4315],{},"加速腐烂，货架期显著缩短",[91,4317,4318,4323,4326],{},[109,4319,4320],{},[36,4321,4322],{},"仓储干货",[109,4324,4325],{},"常温 / 湿度 \u003C 60%",[109,4327,4328],{},"受潮发霉，品质受损",[193,4330,4331],{"id":4331},"传统管理的局限性",[11,4333,4334],{},[36,4335,4336],{},"🌙 局限一：监控间隙风险",[11,4338,4339],{},"人工巡检存在物理间隔（如每 2 小时一次）。在两次巡检之间，若发生制冷机组跳闸，温度可能已超出安全范围。",[11,4341,4342],{},[36,4343,4344],{},"⏱️ 局限二：应急处置滞后",[11,4346,4347,4348,39],{},"从发现温度异常到人工到场排查、启动备用机组，通常需要 30 分钟以上的处理周期。对于高敏感货物，",[36,4349,4350],{},"这一延迟往往是致命的",[11,4352,4353],{},[36,4354,4355],{},"👀 局限三：管理覆盖度不足",[11,4357,4358],{},"多温区、多库点分布时，单凭人力难以实现全方位的精细化监控，极易出现管理盲点。",[11,4360,4361],{},[36,4362,4363],{},"🌡️ 局限四：缺乏异常追溯",[11,4365,4366],{},"人工记录易出现误差或遗漏，在发生货损时，难以通过历史数据进行精准的责任判定与流程优化。",[19,4368,4369],{},[11,4370,4371],{},[36,4372,4373],{},"传统仓储依赖人工盯防，智慧冷链依靠自动化闭环管控。",[25,4375],{},[28,4377,4379],{"id":4378},"二24-小时自动化值守方案核心技术支撑","二、24 小时自动化值守方案：核心技术支撑 🤖",[11,4381,4382],{},"ThingsCloud 自动化方案通过工业级物联网终端，将冷库环境参数与制冷设备深度整合。",[193,4384,4385],{"id":4385},"关键监控指标",[85,4387,4388,4401],{},[88,4389,4390],{},[91,4391,4392,4395,4398],{},[94,4393,4394],{},"监测维度",[94,4396,4397],{},"硬件配置",[94,4399,4400],{},"应用价值",[104,4402,4403,4416,4429,4442],{},[91,4404,4405,4410,4413],{},[109,4406,4407],{},[36,4408,4409],{},"环境温湿度",[109,4411,4412],{},"高精度传感器",[109,4414,4415],{},"实时获取环境参数，精确度达 ±0.1℃",[91,4417,4418,4423,4426],{},[109,4419,4420],{},[36,4421,4422],{},"出入口状态",[109,4424,4425],{},"无线门磁",[109,4427,4428],{},"监控库门开合时间，防止冷气流失",[91,4430,4431,4436,4439],{},[109,4432,4433],{},[36,4434,4435],{},"用电/动力状态",[109,4437,4438],{},"电流传感器",[109,4440,4441],{},"实时监测压缩机运行负荷及市电状态",[91,4443,4444,4449,4452],{},[109,4445,4446],{},[36,4447,4448],{},"设备运行反馈",[109,4450,4451],{},"智能控制器",[109,4453,4454],{},"接收云端指令，实现设备的远程启停与调控",[193,4456,4457],{"id":4457},"自动化执行机制说明",[2000,4459,4460,4466,4476,4482],{},[47,4461,4462,4465],{},[36,4463,4464],{},"温度补偿逻辑","：当监测点温度超过设定上限（如 -17℃）时，系统秒级触发制冷增强指令；待温度回落至安全区间后，自动调整至低功耗运行模式。",[47,4467,4468,4471,4472,4475],{},[36,4469,4470],{},"湿度精准干预","：当湿度超过 ",[36,4473,4474],{},"65% RH"," 时，自动开启除湿系统或换气扇；指标达标后自动停机。",[47,4477,4478,4481],{},[36,4479,4480],{},"出入口安全保护","：若库门开启时长超过预设时间（如 60 秒），系统自动触发声光告警并推送通知给值班人员，同时临时提高制冷功率以对冲冷量损耗。",[47,4483,4484,4487],{},[36,4485,4486],{},"冗余切换机制","：监测到主压缩机电流异常或故障时，系统自动启动备用机组，确保温控不间断。",[25,4489],{},[28,4491,4493],{"id":4492},"三核心应用场景全生命周期货损预防-️","三、核心应用场景：全生命周期货损预防 🛡️",[193,4495,4497],{"id":4496},"场景一温度漂移自动对冲-️","场景一：温度漂移自动对冲 ❄️",[11,4499,4500,4502],{},[36,4501,3803],{},"\n凌晨机组异常导致库温升高，若在 1 小时内未处理，冷冻产品将面临解冻风险。",[11,4504,4505],{},[36,4506,3809],{},[44,4508,4509,4519,4525],{},[47,4510,3864,4511,4514,4515,4518],{},[36,4512,4513],{},"预警触发","：温度偏离预设值 ",[36,4516,4517],{},"0.5℃"," 时，启动预警流程。",[47,4520,2309,4521,4524],{},[36,4522,4523],{},"自动联动","：自动检测从机状态并按需启动，实现冷量补给。",[47,4526,3878,4527,4530],{},[36,4528,4529],{},"多通道告警","：通过 APP、短信、语音电话同步通知管理团队。",[25,4532],{},[193,4534,4536],{"id":4535},"场景二环境湿度智能管控","场景二：环境湿度智能管控 💧",[11,4538,4539,4541],{},[36,4540,3803],{},"\n雨季湿度飙升导致外包装受潮及产品霉变。",[11,4543,4544],{},[36,4545,3809],{},[44,4547,4548,4555],{},[47,4549,4550,4551,4554],{},"💧 ",[36,4552,4553],{},"闭环控制","：湿度传感器实时回传数据，自动调配除湿机组运行。",[47,4556,3915,4557,4560],{},[36,4558,4559],{},"合规报表","：自动生成温湿度历史曲线，满足行业监管追溯要求。",[25,4562],{},[193,4564,4566],{"id":4565},"场景三设备故障自动切换与防护-️","场景三：设备故障自动切换与防护 ⚠️",[11,4568,4569,4571],{},[36,4570,3803],{},"\n关键温控设备在无人值守时段发生故障，缺乏自动切换能力。",[11,4573,4574],{},[36,4575,3809],{},[44,4577,4578,4585,4591],{},[47,4579,4580,4581,4584],{},"⚠️ ",[36,4582,4583],{},"异常识别","：通过电流及状态监测，秒级定位设备故障。",[47,4586,2309,4587,4590],{},[36,4588,4589],{},"无缝切换","：执行预设自动化脚本，自动激活备用制冷链路。",[47,4592,3840,4593,4596],{},[36,4594,4595],{},"风险降级","：通过自动化干预，将潜在的灾难性货损降级为可控的设备维护任务。",[25,4598],{},[28,4600,4602],{"id":4601},"四部署与实施建议","四、部署与实施建议 🚀",[193,4604,4605],{"id":4605},"实施流程",[2000,4607,4608,4614,4623],{},[47,4609,4610,4613],{},[36,4611,4612],{},"终端部署","：在冷库关键位置（中心区、死角、回风口）部署温湿度采集点。",[47,4615,4616,4619,4620,39],{},[36,4617,4618],{},"逻辑建模","：在 ThingsCloud 平台根据货物特性配置 ",[36,4621,4622],{},"自动化规则（Trigger-Condition-Action）",[47,4624,4625,4628],{},[36,4626,4627],{},"策略验证","：通过模拟异常触发，验证联动逻辑的准确性与响应时效。",[25,4630],{},[28,4632,4634],{"id":4633},"五应用价值与效益分析","五、应用价值与效益分析 📊",[193,4636,4637],{"id":4637},"典型案例数据对比",[85,4639,4640,4652],{},[88,4641,4642],{},[91,4643,4644,4646,4649],{},[94,4645,4030],{},[94,4647,4648],{},"传统人工模式",[94,4650,4651],{},"ThingsCloud 自动化模式",[104,4653,4654,4666,4679,4692],{},[91,4655,4656,4659,4662],{},[109,4657,4658],{},"环境响应时间",[109,4660,4661],{},"30 分钟 - 2 小时",[109,4663,4664],{},[36,4665,3306],{},[91,4667,4668,4671,4674],{},[109,4669,4670],{},"异常发现率",[109,4672,4673],{},"依赖巡检频率，存在滞后",[109,4675,4676],{},[36,4677,4678],{},"100% 实时捕获",[91,4680,4681,4684,4687],{},[109,4682,4683],{},"货损发生率",[109,4685,4686],{},"受设备故障与人为疏忽驱动",[109,4688,4689],{},[36,4690,4691],{},"通过冗余控制大幅降低",[91,4693,4694,4697,4700],{},[109,4695,4696],{},"管理成本",[109,4698,4699],{},"需多班次人员持续驻守",[109,4701,4702],{},[36,4703,4704],{},"集约化远程管理，降本 50% 以上",[25,4706],{},[28,4708,4710],{"id":4709},"六结语智慧冷链的可持续发展","六、结语：智慧冷链的可持续发展 🌟",[11,4712,4713],{},"ThingsCloud 自动化方案为冷链企业提供了：",[44,4715,4716,4722,4728],{},[47,4717,3840,4718,4721],{},[36,4719,4720],{},"精细化温控能力"," —— 提升货物存储质量与市场竞争力。",[47,4723,3840,4724,4727],{},[36,4725,4726],{},"风险主动干预"," —— 从被动“救火”转变为主动“防火”。",[47,4729,3840,4730,4733],{},[36,4731,4732],{},"合规数字化"," —— 完整的监测日志为行业监管提供支撑。",[25,4735],{},[28,4737,4739],{"id":4738},"进一步探索","进一步探索 🚀",[44,4741,4742,4748,4754],{},[47,4743,4744],{},[900,4745,4747],{"href":2840,"rel":4746},[904],"了解 ThingsCloud 自动化核心技术",[47,4749,4750],{},[900,4751,4753],{"href":2854,"rel":4752},[904],"查看冷链行业应用案例",[47,4755,4756],{},[900,4757,4759],{"href":4144,"rel":4758},[904],"联系我们定制专属方案",[25,4761],{},[19,4763,4764,4769,4774],{},[11,4765,4766],{},[36,4767,4768],{},"通过数据闭环保障每一份货物的安全。",[11,4770,4771],{},[36,4772,4773],{},"ThingsCloud 自动化，构建透明、可靠、高效的智慧冷链。",[11,4775,4776],{},[36,4777,3468,4778,4781],{},[900,4779,3473],{"href":4167,"rel":4780},[904],"，开启冷链数字化管理新篇章！",{"title":935,"searchDepth":936,"depth":936,"links":4783},[4784,4788,4792,4797,4800,4803,4804],{"id":4255,"depth":936,"text":4256,"children":4785},[4786,4787],{"id":4259,"depth":943,"text":4259},{"id":4331,"depth":943,"text":4331},{"id":4378,"depth":936,"text":4379,"children":4789},[4790,4791],{"id":4385,"depth":943,"text":4385},{"id":4457,"depth":943,"text":4457},{"id":4492,"depth":936,"text":4493,"children":4793},[4794,4795,4796],{"id":4496,"depth":943,"text":4497},{"id":4535,"depth":943,"text":4536},{"id":4565,"depth":943,"text":4566},{"id":4601,"depth":936,"text":4602,"children":4798},[4799],{"id":4605,"depth":943,"text":4605},{"id":4633,"depth":936,"text":4634,"children":4801},[4802],{"id":4637,"depth":943,"text":4637},{"id":4709,"depth":936,"text":4710},{"id":4738,"depth":936,"text":4739},["Date","2026-03-02T00:00:00.000Z"],"告别彻夜盯仓！智慧冷链方案实现温湿度超标自动调节与断电告警，24小时无人值守，从源头杜绝货损风险，省心更省钱。",{},"/blog/smart-cold-chain-automation",{"title":4204,"description":4806},"blog/smart-cold-chain-automation",[977,2886],"wBwfed3MuukGgzoUH6oB988CWkKCa4FGu0Ty8TNQ8nI",{"id":4814,"title":4815,"automation":6,"body":4816,"buy":6,"category":6,"categorySlug":6,"createdAt":5241,"description":5242,"deviceRefs":6,"difficulty":6,"estimatedTime":6,"extension":969,"headpic":4823,"image":6,"industry":6,"industrySlug":6,"keywords":6,"links":6,"meta":5243,"model":6,"name":6,"navigation":971,"path":5244,"protocol":6,"scenario":6,"scenarioSlug":6,"seo":5245,"stem":5246,"tagSlugs":5247,"tags":6,"vendor":6,"website":6,"__hash__":5248},"content/blog/visualization-automation-upgrade.md","数据可视化是基础，智能联动是升级：让你的物联网从 \"看得见\" 走向 \"管得好\"",{"type":8,"value":4817,"toc":5226},[4818,4824,4831,4834,4837,4844,4854,4861,4863,4867,4873,4876,4902,4913,4919,4921,4925,4932,4938,4941,5021,5026,5028,5032,5039,5043,5050,5054,5061,5065,5072,5074,5078,5081,5085,5092,5097,5111,5115,5121,5126,5151,5153,5157,5163,5169,5176,5178,5182,5209,5211],[11,4819,4820],{},[14,4821],{"alt":4822,"src":4823},"articles/2024/20260315190523_d4db2396c320c79ee859115f8c1c8da8.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260315190523_d4db2396c320c79ee859115f8c1c8da8.png",[11,4825,4826,4827,4830],{},"在物联网系统的构建过程中，",[36,4828,4829],{},"设备联网与数据可视化"," 是实现数字化管理的首要环节。",[11,4832,4833],{},"通过实时查看设备状态、监测传感器数据以及追溯历史曲线，企业能够实现管理过程的透明化与线上化，从而显著提升决策效率。",[11,4835,4836],{},"在 ThingsCloud 的产品哲学中：",[19,4838,4839],{},[11,4840,4841],{},[36,4842,4843],{},"数据可视化是物联网的基石，而自动化管理则是其价值的升华。",[11,4845,4846,4847,4850,4851,39],{},"随着 ThingsCloud ",[36,4848,4849],{},"自动化与场景功能"," 的深度集成，我们旨在可视化能力的基础上，为用户提供更高维度的管理手段 —— ",[36,4852,4853],{},"通过预设逻辑实现设备间的智能协同，减少对人工干预的依赖",[11,4855,4856,4857,4860],{},"可视化与自动化互为补充，共同构成了 ",[36,4858,4859],{},"完整、可靠、可落地"," 的物联网闭环管理体系。",[25,4862],{},[28,4864,4866],{"id":4865},"一数据可视化实现管理透明化的物理基础","一、数据可视化：实现管理透明化的物理基础 📊",[11,4868,4869,4870,39],{},"数据可视化解决了物联网系统中最核心的问题：",[36,4871,4872],{},"状态感知",[11,4874,4875],{},"其核心价值体现在：",[44,4877,4878,4884,4890,4896],{},[47,4879,3840,4880,4883],{},[36,4881,4882],{},"实时状态监控","：消除物理空间障碍，实现对分布设备的集中化查看。",[47,4885,3840,4886,4889],{},[36,4887,4888],{},"管理透明度","：将离散的现场数据转化为直观的图表，提升组织沟通效率。",[47,4891,3840,4892,4895],{},[36,4893,4894],{},"决策依据","：通过历史趋势与报表分析，为运营策略的优化提供客观数据支撑。",[47,4897,3840,4898,4901],{},[36,4899,4900],{},"远程运维","：降低现场巡检频次，实现故障的远程初步诊断。",[11,4903,4904,4905,4908,4909,4912],{},"作为 ThingsCloud 平台的基础能力，无论是在 ",[36,4906,4907],{},"标准版"," 还是 ",[36,4910,4911],{},"企业版"," 中，用户均可获得高性能、高可靠的可视化交互体验。",[11,4914,4915,4916,39],{},"然而，单纯的“感知”仅能解决发现问题的问题，要实现管理效率的质变，还需引入 ",[36,4917,4918],{},"主动执行能力",[25,4920],{},[28,4922,4924],{"id":4923},"二自动化从感知到干预的智能跨越","二、自动化：从“感知”到“干预”的智能跨越 🤖",[11,4926,4927,4928,4931],{},"如果说数据可视化专注于 ",[36,4929,4930],{},"“信息呈现”","，",[11,4933,4934,4935,39],{},"那么自动化则侧重于 ",[36,4936,4937],{},"“策略执行”",[11,4939,4940],{},"自动化并非替代可视化，而是在感知数据的基础上，赋予系统逻辑判断与主动反馈的能力：",[85,4942,4943,4956],{},[88,4944,4945],{},[91,4946,4947,4950,4953],{},[94,4948,4949],{},"业务维度",[94,4951,4952],{},"数据可视化（被动感知）",[94,4954,4955],{},"自动化管理（主动执行）",[104,4957,4958,4974,4989,5005],{},[91,4959,4960,4965,4968],{},[109,4961,4962],{},[36,4963,4964],{},"环境调控",[109,4966,4967],{},"监测到环境温度超限",[109,4969,4970,4973],{},[36,4971,4972],{},"自动触发"," 散热或制冷设备",[91,4975,4976,4981,4984],{},[109,4977,4978],{},[36,4979,4980],{},"设备安全",[109,4982,4983],{},"识别到电压波动异常",[109,4985,4986,4988],{},[36,4987,4523],{}," 断电保护或负载切换",[91,4990,4991,4996,4999],{},[109,4992,4993],{},[36,4994,4995],{},"资源调度",[109,4997,4998],{},"查看储罐液位不足",[109,5000,5001,5004],{},[36,5002,5003],{},"自动启动"," 输送泵进行补料",[91,5006,5007,5012,5015],{},[109,5008,5009],{},[36,5010,5011],{},"能效优化",[109,5013,5014],{},"监测到非工作时段能耗过高",[109,5016,5017,5020],{},[36,5018,5019],{},"自动调整"," 照明与暖通运行策略",[11,5022,5023],{},[36,5024,5025],{},"核心逻辑：可视化实现“信息对齐”，自动化实现“闭环管理”。",[25,5027],{},[28,5029,5031],{"id":5030},"三协同效应可视化与自动化的深度融合场景","三、协同效应：可视化与自动化的深度融合场景 🚀",[11,5033,5034,5035,5038],{},"在 ThingsCloud 架构中，",[36,5036,5037],{},"自动化逻辑与可视化看板"," 深度协同，为不同行业提供了高效的解决方案：",[193,5040,5042],{"id":5041},"_1-环境自适应调控-️","1. 环境自适应调控 🌡️",[11,5044,5045,5046,5049],{},"系统通过可视化看板展示现场的温湿度、光照、气体浓度等实时数据；同时，",[36,5047,5048],{},"自动化引擎"," 根据预设的逻辑曲线，在指标偏离最优区间时自动调控执行器，确保环境指标的持续稳定性，无需人工守候。",[193,5051,5053],{"id":5052},"_2-预测性安全防护-️","2. 预测性安全防护 🛡️",[11,5055,5056,5057,5060],{},"看板实时刷新关键设备的振动、温度、电流等运行特征。当自动化引擎捕捉到异常先兆（如瞬间电流激增或温度持续攀升）时，会立即执行 ",[36,5058,5059],{},"降级策略或停机保护","，在故障扩大前完成干预。",[193,5062,5064],{"id":5063},"_3-多端业务协同流程-️","3. 多端业务协同流程 ⚙️",[11,5066,5067,5068,5071],{},"在复杂的生产线或大型园区管理中，可视化看板作为管理指挥中心展示全局状态，而 ",[36,5069,5070],{},"自动化场景"," 则负责在不同设备、不同协议之间建立逻辑联系，实现跨系统的流程联动。",[25,5073],{},[28,5075,5077],{"id":5076},"四版本选型建议按需构建物联网能力","四、版本选型建议：按需构建物联网能力 🎯",[11,5079,5080],{},"ThingsCloud 提供了差异化的版本支持，以匹配不同阶段的业务需求：",[193,5082,5084],{"id":5083},"标准版聚焦感知与交互","标准版：聚焦感知与交互",[11,5086,5087,5088,5091],{},"适用于需要 ",[36,5089,5090],{},"快速实现设备联网、移动端查看、数据看板展示"," 的基础应用场景。",[11,5093,5094],{},[36,5095,5096],{},"核心能力：",[44,5098,5099,5102,5105,5108],{},[47,5100,5101],{},"多协议设备接入（MQTT / TCP / Modbus / HTTP）",[47,5103,5104],{},"高实时性的数据监控与历史曲线追溯",[47,5106,5107],{},"零代码构建可视化看板与 APP 端",[47,5109,5110],{},"告警规则定义与多渠道通知推送",[193,5112,5114],{"id":5113},"企业版聚焦协同与效率","企业版：聚焦协同与效率",[11,5116,5087,5117,5120],{},[36,5118,5119],{},"无人值守、复杂逻辑联动、跨系统调度"," 的深度应用场景。",[11,5122,5123],{},[36,5124,5125],{},"在标准版基础上新增：",[44,5127,5128,5133,5139,5145],{},[47,5129,5130,5132],{},[36,5131,5048],{},"：支持 Trigger-Condition-Action 模式，实现秒级本地或云端联动。",[47,5134,5135,5138],{},[36,5136,5137],{},"场景编排功能","：支持对多台设备进行批量、顺序或并行控制。",[47,5140,5141,5144],{},[36,5142,5143],{},"全量执行日志","：详细记录每一次逻辑触发与执行结果，确保过程可审计。",[47,5146,5147,5150],{},[36,5148,5149],{},"效率统计分析","：提供触发频率与执行成功率的深度分析报表。",[25,5152],{},[28,5154,5156],{"id":5155},"五总结构建具备思考能力的物联网系统","五、总结：构建具备“思考能力”的物联网系统 🌱",[11,5158,5159,5162],{},[36,5160,5161],{},"数据可视化"," 是物联网的基石，确保系统具备基本的数字化能力。",[11,5164,5165,5168],{},[36,5166,5167],{},"智能自动化"," 是物联网的升级，通过逻辑驱动实现降本增效与智能化运营。",[11,5170,5171,5172,5175],{},"ThingsCloud 致力于从底层接入到上层应用，为用户提供一条 ",[36,5173,5174],{},"从“接入”到“感知”再到“自动控制”"," 的平滑演进路径。",[25,5177],{},[28,5179,5181],{"id":5180},"资源导航","资源导航 📚",[44,5183,5184,5190,5195,5202],{},[47,5185,5186],{},[900,5187,5189],{"href":2840,"rel":5188},[904],"什么是自动化与场景？",[47,5191,5192],{},[900,5193,2190],{"href":2847,"rel":5194},[904],[47,5196,5197],{},[900,5198,5201],{"href":5199,"rel":5200},"https://www.thingscloud.xyz/docs/guide/automations/create-scene.html",[904],"如何配置业务场景",[47,5203,5204],{},[900,5205,5208],{"href":5206,"rel":5207},"https://www.thingscloud.xyz/docs/pricing.html",[904],"查阅 ThingsCloud 版本功能对比",[25,5210],{},[19,5212,5213,5218],{},[11,5214,5215],{},[36,5216,5217],{},"可视化与自动化双轮驱动，让物联网资产创造更大价值。",[11,5219,5220],{},[36,5221,3468,5222,5225],{},[900,5223,3473],{"href":4167,"rel":5224},[904],"，开启您的智能化转型。",{"title":935,"searchDepth":936,"depth":936,"links":5227},[5228,5229,5230,5235,5239,5240],{"id":4865,"depth":936,"text":4866},{"id":4923,"depth":936,"text":4924},{"id":5030,"depth":936,"text":5031,"children":5231},[5232,5233,5234],{"id":5041,"depth":943,"text":5042},{"id":5052,"depth":943,"text":5053},{"id":5063,"depth":943,"text":5064},{"id":5076,"depth":936,"text":5077,"children":5236},[5237,5238],{"id":5083,"depth":943,"text":5084},{"id":5113,"depth":943,"text":5114},{"id":5155,"depth":936,"text":5156},{"id":5180,"depth":936,"text":5181},["Date","2026-02-13T00:00:00.000Z"],"物联网不仅要“看得见”，更要“管得好”。全新自动化功能助您实现从被动监控到主动管理的跨越，让设备管理更智能。",{},"/blog/visualization-automation-upgrade",{"title":4815,"description":5242},"blog/visualization-automation-upgrade",[976,2886],"8A7Ephsm9NmoX7sp3DycbqQBH5qY5dYhdk0KrzsLFPs",{"id":5250,"title":5251,"automation":6,"body":5252,"buy":6,"category":6,"categorySlug":6,"createdAt":5783,"description":5784,"deviceRefs":6,"difficulty":6,"estimatedTime":6,"extension":969,"headpic":5259,"image":6,"industry":6,"industrySlug":6,"keywords":6,"links":6,"meta":5785,"model":6,"name":6,"navigation":971,"path":5786,"protocol":6,"scenario":6,"scenarioSlug":6,"seo":5787,"stem":5788,"tagSlugs":5789,"tags":6,"vendor":6,"website":6,"__hash__":5790},"content/blog/zero-code-automation-easy-setup.md","零代码物联网自动化配置指南：通过可视化闭环逻辑提升业务自治效率",{"type":8,"value":5253,"toc":5768},[5254,5260,5267,5273,5288,5290,5294,5297,5308,5319,5333,5335,5339,5349,5353,5356,5382,5388,5392,5395,5415,5425,5429,5432,5458,5464,5475,5477,5481,5488,5566,5580,5582,5586,5589,5593,5599,5614,5618,5628,5652,5659,5661,5665,5668,5682,5692,5703,5709,5711,5721,5728,5730,5732,5755,5757],[11,5255,5256],{},[14,5257],{"alt":5258,"src":5259},"articles/2024/20260315190252_4e279b6a5b2dd484c031d49e45eef97d.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260315190252_4e279b6a5b2dd484c031d49e45eef97d.png",[11,5261,5262,5263,5266],{},"在 ThingsCloud 持续迭代的过程中，我们始终致力于 ",[36,5264,5265],{},"提升物联网系统的构建效率与运行稳定性"," 。",[11,5268,5269,5270,5272],{},"从设备快速接入、可视化监控到应用交付，我们不断降低物联网系统的工程化门槛，使企业能够通过标准化工具快速构建 ",[36,5271,3325],{}," 的物联网环境。",[11,5274,5275,5276,5279,5280,5283,5284,5287],{},"随着 ",[36,5277,5278],{},"自动化与场景编排功能"," 的正式上线，ThingsCloud 实现了配置流程的高度解耦 —— 通过 ",[36,5281,5282],{},"全程零代码、可视化配置"," ，用户可快速完成设备逻辑的编排与下发。该功能并非简单的工具堆叠，而是在稳定的底层架构之上，为用户提供了更高维度的 ",[36,5285,5286],{},"业务编排与逻辑闭环"," 能力。",[25,5289],{},[28,5291,5293],{"id":5292},"一解构技术壁垒实现业务逻辑与底层代码的解耦","一、解构技术壁垒：实现业务逻辑与底层代码的解耦 🚧",[11,5295,5296],{},"在传统模式下，实现设备自动化联动通常面临以下挑战：",[44,5298,5299,5302,5305],{},[47,5300,5301],{},"❌ 依赖专业工程师编写底层逻辑代码",[47,5303,5304],{},"❌ 需处理异构设备间复杂的通信协议",[47,5306,5307],{},"❌ 业务逻辑硬编码，缺乏灵活性",[11,5309,5310,5311,5314,5315,5318],{},"这种模式不仅 ",[36,5312,5313],{},"开发周期长、实施成本高"," ，且后期 ",[36,5316,5317],{},"维护复杂度极高"," 。当业务场景发生变动时，系统调整往往牵一发而动全身。",[11,5320,5321,5322,5325,5326,5329,5330,5266],{},"ThingsCloud 认为， ",[36,5323,5324],{},"智能化不应受限于技术实现的复杂度"," ，而应回归业务本质。通过将复杂的底层逻辑封装为标准化的配置组件，管理人员与运维人员可以根据实际业务需求，直接定义 ",[36,5327,5328],{},"逻辑闭环"," 规则，从而大幅提升 ",[36,5331,5332],{},"配置效率",[25,5334],{},[28,5336,5338],{"id":5337},"二标准化配置流程三步构建业务逻辑闭环-️","二、标准化配置流程：三步构建业务逻辑闭环 ⚙️",[11,5340,5341,5342,5345,5346,5266],{},"ThingsCloud 自动化功能遵循 ",[36,5343,5344],{},"“极简编排、直观可视、系统稳定”"," 的设计原则。用户无需具备编程背景，通过可视化界面即可完成复杂的 ",[36,5347,5348],{},"逻辑编排",[193,5350,5352],{"id":5351},"第一步定义触发机制","第一步：定义触发机制 🎯",[11,5354,5355],{},"支持多种事件驱动模式：",[44,5357,5358,5364,5370,5376],{},[47,5359,2253,5360,5363],{},[36,5361,5362],{},"设备数据阈值触发"," （如温度超限、压力异常）",[47,5365,2337,5366,5369],{},[36,5367,5368],{},"设备状态事件触发"," （如上线/离线、心跳异常）",[47,5371,2281,5372,5375],{},[36,5373,5374],{},"确定性计划任务"," （如定时巡检、周期性控制）",[47,5377,4580,5378,5381],{},[36,5379,5380],{},"系统告警状态联动"," （如告警产生即时响应）",[11,5383,5384,5385,5266],{},"通过简单的配置操作即可完成规则定义，确保触发逻辑的 ",[36,5386,5387],{},"精准性",[193,5389,5391],{"id":5390},"第二步配置逻辑判断条件-️","第二步：配置逻辑判断条件 🎛️",[11,5393,5394],{},"灵活嵌入业务限制条件，确保执行逻辑的严密性：",[44,5396,5397,5403,5409],{},[47,5398,2419,5399,5402],{},[36,5400,5401],{},"时间窗口策略"," （如仅在工作时段生效）",[47,5404,2253,5405,5408],{},[36,5406,5407],{},"多维状态校验"," （如设备处于特定运行模式）",[47,5410,2323,5411,5414],{},[36,5412,5413],{},"环境因素关联"," （如基于日照时间的动态调整）",[11,5416,5417,5418,5421,5422,5266],{},"支持 ",[36,5419,5420],{},"多条件复合逻辑"," ，确保自动化执行精准适配实际生产场景，提升系统的 ",[36,5423,5424],{},"抗干扰能力与运行稳定性",[193,5426,5428],{"id":5427},"第三步编排执行动作序列","第三步：编排执行动作序列 ⚡",[11,5430,5431],{},"支持原子化动作的组合编排：",[44,5433,5434,5440,5446,5452],{},[47,5435,2504,5436,5439],{},[36,5437,5438],{},"单一控制指令下发"," （如远程开启/关闭设备）",[47,5441,5442,5443,5445],{},"🔗 ",[36,5444,3290],{}," （如同组设备协同运行）",[47,5447,2560,5448,5451],{},[36,5449,5450],{},"时序化动作流 + 延迟补偿"," （支持按序执行与延时逻辑）",[47,5453,2546,5454,5457],{},[36,5455,5456],{},"预设场景一键调用"," （实现复杂业务模版的快速复用）",[11,5459,5460,5461,5463],{},"通过灵活的动作编排，系统可实现 ",[36,5462,3306],{}," 的业务自动化。",[19,5465,5466],{},[11,5467,5468,5469,5472,5473,5266],{},"💡 ",[36,5470,5471],{},"标准化配置流程确保了业务逻辑的高效沉淀与复用"," ，使用户能够在极短的时间内完成生产级自动化规则的构建，实现真正的 ",[36,5474,3325],{},[25,5476],{},[28,5478,5480],{"id":5479},"三可视化编排兼顾配置效率与逻辑深度","三、可视化编排：兼顾配置效率与逻辑深度 💪",[11,5482,5483,5484,5487],{},"低代码/零代码并不意味着功能缺失。ThingsCloud 的自动化与场景编排功能在简化操作的同时，保持了强大的 ",[36,5485,5486],{},"底层逻辑支撑"," 能力：",[85,5489,5490,5500],{},[88,5491,5492],{},[91,5493,5494,5497],{},[94,5495,5496],{},"能力维度",[94,5498,5499],{},"技术核心",[104,5501,5502,5515,5528,5540,5553],{},[91,5503,5504,5509],{},[109,5505,5506],{},[36,5507,5508],{},"跨域协同",[109,5510,5511,5512],{},"支持异构设备、多产品线、多空间的 ",[36,5513,5514],{},"深度联动",[91,5516,5517,5522],{},[109,5518,5519],{},[36,5520,5521],{},"严密逻辑",[109,5523,5524,5525],{},"支持布尔逻辑与复杂条件嵌套，满足 ",[36,5526,5527],{},"精细化业务规则",[91,5529,5530,5535],{},[109,5531,5532],{},[36,5533,5534],{},"时序编排",[109,5536,5537,5538],{},"内置动作延迟与执行顺序控制，实现 ",[36,5539,5328],{},[91,5541,5542,5547],{},[109,5543,5544],{},[36,5545,5546],{},"可观测性",[109,5548,5549,5550],{},"提供详尽的执行日志记录与链路追踪，确保 ",[36,5551,5552],{},"调试与溯源效率",[91,5554,5555,5560],{},[109,5556,5557],{},[36,5558,5559],{},"系统兼容",[109,5561,5562,5563],{},"与现有数字孪生看板、实时监控体系 ",[36,5564,5565],{},"无缝解耦并集成",[11,5567,5568,5569,5572,5573,5576,5577,5266],{},"无论是简单的单体控制逻辑，还是复杂的 ",[36,5570,5571],{},"无人值守、分级保护流程"," ，均可通过 ",[36,5574,5575],{},"零代码方式实现高效交付"," ，平衡了 ",[36,5578,5579],{},"部署速度与系统鲁棒性",[25,5581],{},[28,5583,5585],{"id":5584},"四阶梯化赋能从基础监控到业务自治","四、阶梯化赋能：从基础监控到业务自治 🤝",[11,5587,5588],{},"ThingsCloud 提供灵活的功能组合，支持企业根据业务成熟度平滑演进。",[193,5590,5592],{"id":5591},"标准版构建管理基础","标准版：构建管理基础",[11,5594,5595,5596,5598],{},"对于 ",[36,5597,4907],{}," 用户：",[44,5600,5601,5604,5607],{},[47,5602,5603],{},"实现设备全生命周期管理与远程监控",[47,5605,5606],{},"构建数据可视化体系与应用分发",[47,5608,5609,5610,5613],{},"满足 ",[36,5611,5612],{},"高可靠性的基础监控需求"," ，是物联网系统构建的稳健起点。",[193,5615,5617],{"id":5616},"企业版实现智能治理","企业版：实现智能治理",[11,5619,5620,5621,5624,5625,5627],{},"对于追求 ",[36,5622,5623],{},"降本增效与业务自治"," 的用户， ",[36,5626,4911],{}," 在此基础上进一步增强：",[44,5629,5630,5636,5641,5646],{},[47,5631,5632,5633],{},"🤖 ",[36,5634,5635],{},"复杂自动化规则引擎",[47,5637,2546,5638],{},[36,5639,5640],{},"多场景协同编排",[47,5642,2253,5643],{},[36,5644,5645],{},"全链路执行日志分析",[47,5647,5648,5649],{},"📈 ",[36,5650,5651],{},"多维业务统计报表",[11,5653,5654,5655,5658],{},"助力企业在实现“数据在线”后，进一步构建 ",[36,5656,5657],{},"“逻辑在线”与“自动执行”"," 的智能体系。",[25,5660],{},[28,5662,5664],{"id":5663},"五回归业务本质驱动逻辑闭环","五、回归业务本质，驱动逻辑闭环 🌟",[11,5666,5667],{},"物联网的价值在于服务业务。ThingsCloud 始终认为：",[19,5669,5670],{},[11,5671,5672,5675,5676,5675,5679,5266],{},[36,5673,5674],{},"优秀的平台应将复杂的技术实现隐藏在标准化的体验之下"," ，\n",[36,5677,5678],{},"让用户专注于业务逻辑的构建",[36,5680,5681],{},"而非受困于底层代码的堆砌",[11,5683,5684,5685,5688,5689,5691],{},"零代码自动化的核心价值在于，它使企业能够以 ",[36,5686,5687],{},"最低的边际成本"," 实现 ",[36,5690,3325],{}," ：",[44,5693,5694,5697,5700],{},[47,5695,5696],{},"❌ 摆脱对特定代码开发的强依赖",[47,5698,5699],{},"❌ 降低系统的二次开发与维护成本",[47,5701,5702],{},"❌ 缩短业务逻辑从构思到落地的周期",[11,5704,5705,5706,5708],{},"通过构建 ",[36,5707,5328],{}," ，企业可确保设备管理更稳定、运营效率更高。",[25,5710],{},[19,5712,5713],{},[11,5714,5715,5718],{},[36,5716,5717],{},"看得见是基础，自动管是核心；",[36,5719,5720],{},"低门槛是路径，闭环治理是价值。",[11,5722,5723,5724,5727],{},"ThingsCloud 零代码智能自动化，助力企业构建 ",[36,5725,5726],{},"高可用、自动化、业务自治"," 的物联网系统。",[25,5729],{},[28,5731,3422],{"id":3421},[44,5733,5734,5741,5748],{},[47,5735,5736,5740],{},[900,5737,5739],{"href":2847,"rel":5738},[904],"创建第一个自动化规则"," —— 标准化快速上手",[47,5742,5743,5747],{},[900,5744,5746],{"href":5199,"rel":5745},[904],"配置设备联动场景"," —— 实现一键逻辑编排",[47,5749,5750,5754],{},[900,5751,5753],{"href":2854,"rel":5752},[904],"自动化实战案例"," —— 深入了解行业应用",[25,5756],{},[19,5758,5759],{},[11,5760,5761],{},[36,5762,3468,5763,5767],{},[900,5764,5766],{"href":4167,"rel":5765},[904],"ThingsCloud 文档中心","，开启业务自治新纪元。",{"title":935,"searchDepth":936,"depth":936,"links":5769},[5770,5771,5776,5777,5781,5782],{"id":5292,"depth":936,"text":5293},{"id":5337,"depth":936,"text":5338,"children":5772},[5773,5774,5775],{"id":5351,"depth":943,"text":5352},{"id":5390,"depth":943,"text":5391},{"id":5427,"depth":943,"text":5428},{"id":5479,"depth":936,"text":5480},{"id":5584,"depth":936,"text":5585,"children":5778},[5779,5780],{"id":5591,"depth":943,"text":5592},{"id":5616,"depth":943,"text":5617},{"id":5663,"depth":936,"text":5664},{"id":3421,"depth":936,"text":3422},["Date","2026-02-05T00:00:00.000Z"],"不懂代码也能玩转自动化！零代码可视化配置，助您快速搭建设备闭环逻辑。让业务自治更高效，系统运行更稳健。",{},"/blog/zero-code-automation-easy-setup",{"title":5251,"description":5784},"blog/zero-code-automation-easy-setup",[976,2886],"k9Y7qSvL7-xGPf7vrBxqB6yjtICA0-nbw4huO_999UI",{"id":5792,"title":5793,"automation":6,"body":5794,"buy":6,"category":6,"categorySlug":6,"createdAt":6250,"description":6251,"deviceRefs":6,"difficulty":6,"estimatedTime":6,"extension":969,"headpic":5801,"image":6,"industry":6,"industrySlug":6,"keywords":6,"links":6,"meta":6252,"model":6,"name":6,"navigation":971,"path":6253,"protocol":6,"scenario":6,"scenarioSlug":6,"seo":6254,"stem":6255,"tagSlugs":6256,"tags":6,"vendor":6,"website":6,"__hash__":6257},"content/blog/automation-scene-feature-released.md","ThingsCloud 自动化与场景功能发布：让设备逻辑闭环，实现无人值守",{"type":8,"value":5795,"toc":6232},[5796,5802,5808,5821,5825,5828,5832,5835,5839,5846,5850,5856,5860,5863,5870,5874,5883,5886,5912,5926,5930,5936,5940,5954,5958,5961,5977,5983,5987,6007,6011,6081,6085,6099,6127,6134,6138,6148,6154,6165,6174,6176,6179,6214,6216],[11,5797,5798],{},[14,5799],{"alt":5800,"src":5801},"articles/2024/20260315194000_eedd53c4282594b264e3adb61a23d3b7.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260315194000_eedd53c4282594b264e3adb61a23d3b7.png",[11,5803,5804,5805,5807],{},"在物联网应用日益普及的背景下，实现设备接入与数据可视化已成为行业基础。然而，由于缺乏有效的 ",[36,5806,5328],{}," ，许多系统在实际运行中仍高度依赖人工干预：人工监测告警、手动切换开关、人工处理异常。",[11,5809,5810,5811,5814,5815,5817,5818,5820],{},"这种模式不仅增加了运营成本，更限制了物联网系统在复杂环境下的响应速度。 ThingsCloud 认为，成熟的物联网架构应具备 ",[36,5812,5813],{},"“设备感知、自动决策、闭环执行”"," 的能力。为此，我们正式推出 ",[36,5816,5278],{}," ，旨在赋能企业构建 ",[36,5819,3325],{}," 的无人值守智能管理体系。",[28,5822,5824],{"id":5823},"一人工干预模式的瓶颈成本与稳定性的双重考验","一、人工干预模式的瓶颈：成本与稳定性的双重考验 💔",[11,5826,5827],{},"在工业制造、智慧农业、机房运维等关键场景中，传统的“人工盯盘”模式正面临严峻挑战：",[193,5829,5831],{"id":5830},"_1-运营成本持续攀升","1. 运营成本持续攀升",[11,5833,5834],{},"专人值守带来的高额人力开支与管理复杂性，已成为制约中小企业实现数字化转型的核心瓶颈。",[193,5836,5838],{"id":5837},"_2-异常响应延迟","2. 异常响应延迟",[11,5840,5841,5842,5845],{},"人类感知的局限性导致在面对温度突变、压力异常、漏水断电等突发状况时，响应速度难以满足 ",[36,5843,5844],{},"系统稳定性"," 要求，往往错过最佳处置窗口。",[193,5847,5849],{"id":5848},"_3-系统鲁棒性不足","3. 系统鲁棒性不足",[11,5851,5852,5853,5266],{},"关键设备的非预设状态可能导致严重的生产损失。过度依赖人工干预，意味着系统缺乏一套 ",[36,5854,5855],{},"标准化、可预测的应急逻辑闭环",[193,5857,5859],{"id":5858},"_4-流程缺乏一致性","4. 流程缺乏一致性",[11,5861,5862],{},"人工操作存在随机性，难以形成稳定、可追溯且标准化的业务执行闭环，导致管理效能难以持续优化。",[19,5864,5865],{},[11,5866,5867],{},[36,5868,5869],{},"如果物联网系统仅停留在数据呈现阶段，其本质仍是辅助监控工具，而非真正的智能管理闭环。",[28,5871,5873],{"id":5872},"二从人工干预到业务自治自动化引擎","二、从“人工干预”到“业务自治”：自动化引擎 🚀",[11,5875,5876,5877,5879,5880],{},"ThingsCloud ",[36,5878,5048],{}," 的设计核心在于： ",[36,5881,5882],{},"将重复性逻辑转化为确定性的机器执行流，实现系统级的逻辑闭环。",[11,5884,5885],{},"通过零代码可视化配置，用户可使物联网系统具备以下能力：",[44,5887,5888,5894,5900,5906],{},[47,5889,3840,5890,5893],{},[36,5891,5892],{},"自主感知"," 环境与状态变化",[47,5895,3840,5896,5899],{},[36,5897,5898],{},"自动校验"," 业务逻辑执行条件",[47,5901,3840,5902,5905],{},[36,5903,5904],{},"闭环执行"," 预设动作序列",[47,5907,3840,5908,5911],{},[36,5909,5910],{},"全量记录"," 执行状态与通知追踪",[11,5913,5914,5915,5918,5919,5922,5923,5266],{},"基于 ",[36,5916,5917],{},"“预设逻辑，确定性执行”"," 的原则，系统可在无人干预的情况下实现 ",[36,5920,5921],{},"7×24 小时稳定运行"," ，显著提升 ",[36,5924,5925],{},"配置效率与运行稳定性",[28,5927,5929],{"id":5928},"三典型业务自治场景分析-️","三、典型业务自治场景分析 ⚙️",[11,5931,5932,5933,5935],{},"通过以下垂直行业的应用逻辑，可以直观理解 ",[36,5934,5328],{}," 的核心价值。",[193,5937,5939],{"id":5938},"场景-1精准灌溉业务闭环","场景 1：精准灌溉业务闭环 🌱",[11,5941,5942,5943,5946,5947,5950,5951,5266],{},"基于土壤湿度传感器数据，当湿度跌至预设阈值时， ",[36,5944,5945],{},"自动化引擎自动驱动灌溉泵开启"," ；当达到饱和阈值或执行时长达标后， ",[36,5948,5949],{},"自动执行关闭逻辑"," 。该流程实现了从感知到执行的 ",[36,5952,5953],{},"无人值守自治",[193,5955,5957],{"id":5956},"场景-2工业设备保护逻辑","场景 2：工业设备保护逻辑 🔥",[11,5959,5960],{},"当监测到设备运行温度超过安全阈值，系统即刻进入保护闭环：",[2000,5962,5963,5968,5971],{},[47,5964,3824,5965],{},[36,5966,5967],{},"触发级联散热逻辑",[47,5969,5970],{},"⚡ 降级运行策略自动下发",[47,5972,5973,5974],{},"⚡ 达到极限值时 ",[36,5975,5976],{},"自动执行停机保护",[11,5978,5979,5980,5982],{},"全流程 ",[36,5981,3306],{}," ，确保设备处于安全运行区间。",[193,5984,5986],{"id":5985},"场景-3关键基础设施环境治理","场景 3：关键基础设施环境治理 🏢",[44,5988,5989,5995,6001],{},[47,5990,5991,5992],{},"环境指标异常 → ",[36,5993,5994],{},"联动空调/新风系统自动调节",[47,5996,5997,5998],{},"漏水/烟雾感应 → ",[36,5999,6000],{},"自动切断阀门并触发紧急响应逻辑",[47,6002,6003,6004],{},"电力故障 → ",[36,6005,6006],{},"自动切换备用电源并完成状态同步",[28,6008,6010],{"id":6009},"四自动化编排的核心价值分析","四、自动化编排的核心价值分析 💎",[85,6012,6013,6023],{},[88,6014,6015],{},[91,6016,6017,6020],{},[94,6018,6019],{},"核心维度",[94,6021,6022],{},"业务收益",[104,6024,6025,6035,6045,6058,6068],{},[91,6026,6027,6032],{},[109,6028,6029],{},[36,6030,6031],{},"🎯 降本增效",[109,6033,6034],{},"大幅降低人工巡检与值守成本，实现资源的最优配置",[91,6036,6037,6042],{},[109,6038,6039],{},[36,6040,6041],{},"⚡ 逻辑闭环响应",[109,6043,6044],{},"消除人工干预延迟，确保异常处置的实时性与准确性",[91,6046,6047,6052],{},[109,6048,6049],{},[36,6050,6051],{},"🌙 高可用运行",[109,6053,6054,6055],{},"保证系统在非工作时段及极端环境下的 ",[36,6056,6057],{},"持续稳定性",[91,6059,6060,6065],{},[109,6061,6062],{},[36,6063,6064],{},"📊 执行可溯源",[109,6066,6067],{},"提供详尽的流水化日志，实现自动化逻辑执行的闭环审计",[91,6069,6070,6075],{},[109,6071,6072],{},[36,6073,6074],{},"🔧 交付效率",[109,6076,6077,6078],{},"业务人员可通过零代码方式快速部署复杂的 ",[36,6079,6080],{},"自治规则",[28,6082,6084],{"id":6083},"五场景编排多设备协同的标准化入口","五、场景编排：多设备协同的标准化入口 🤝",[11,6086,6087,6088,6091,6092,6095,6096,5691],{},"除 ",[36,6089,6090],{},"自动化触发"," 逻辑外，ThingsCloud 同时提供 ",[36,6093,6094],{},"场景编排"," 能力。场景是一组原子化动作的集合，旨在实现 ",[36,6097,6098],{},"多设备协同的标准化控制",[44,6100,6101,6108,6115,6121],{},[47,6102,6103,6104,6107],{},"🏭 ",[36,6105,6106],{},"产线快速启动"," ：按工艺顺序一键调起全线设备",[47,6109,6110,6111,6114],{},"🛑 ",[36,6112,6113],{},"应急安全停机"," ：根据预设的安全序列执行设备下线",[47,6116,5468,6117,6120],{},[36,6118,6119],{},"能效管理模式"," ：一键切换系统至低功耗运行状态",[47,6122,3814,6123,6126],{},[36,6124,6125],{},"安全模式联动"," ：一键开启安防布防并同步环境状态",[11,6128,6129,6130,6133],{},"场景与自动化可深度融合：场景可作为自动化的 ",[36,6131,6132],{},"动作目标"," ，实现多维度的逻辑嵌套与闭环。",[28,6135,6137],{"id":6136},"六构建智能物联网的逻辑大脑","六、构建智能物联网的逻辑大脑 🎉",[11,6139,6140,6141,6144,6145,5266],{},"过去，ThingsCloud 协助用户完成了从设备接入到数据可视化的基础建设。现在，随着 ",[36,6142,6143],{},"自动化与场景编排"," 功能的发布，我们将进一步赋能用户构建系统的 ",[36,6146,6147],{},"“逻辑大脑”",[1888,6149,6152],{"className":6150,"code":6151,"language":1893},[1891],"设备接入 → 数据可视化 → 逻辑闭环 → 业务自治\n",[1154,6153,6151],{"__ignoreMap":935},[11,6155,6156,6157,6160,6161,6164],{},"这标志着系统从 ",[36,6158,6159],{},"单纯的监控工具"," 向 ",[36,6162,6163],{},"高可用的智能治理平台"," 的演进。通过将逻辑深度嵌入业务流程，我们帮助企业实现真正的降本增效。",[11,6166,6167,6168,6170,6171,5266],{},"欢迎体验 ThingsCloud ",[36,6169,6143],{}," 功能，开启物联网系统的 ",[36,6172,6173],{},"业务自治新时代",[25,6175],{},[28,6177,6178],{"id":2833},"了解更多 📚",[44,6180,6181,6187,6193,6200,6206],{},[47,6182,6183,6186],{},[900,6184,2842],{"href":2840,"rel":6185},[904]," —— 核心概念与应用场景分析",[47,6188,6189,6192],{},[900,6190,2849],{"href":2847,"rel":6191},[904]," —— 快速上手流程",[47,6194,6195,6199],{},[900,6196,6198],{"href":5199,"rel":6197},[904],"场景编排配置指南"," —— 多设备协同配置",[47,6201,6202,6205],{},[900,6203,2856],{"href":2854,"rel":6204},[904]," —— 深入了解实战应用",[47,6207,6208,6213],{},[900,6209,6212],{"href":6210,"rel":6211},"https://www.thingscloud.xyz/docs/guide/automations/scenes-examples.html",[904],"典型场景编排示例"," —— 标准化控制模板",[25,6215],{},[19,6217,6218,6226],{},[11,6219,6220],{},[36,6221,3468,6222,6225],{},[900,6223,2823],{"href":2821,"rel":6224},[904]," 体验全新的逻辑闭环治理能力。",[11,6227,6228,6229,5266],{},"更多技术支持请参考 ",[900,6230,5766],{"href":4167,"rel":6231},[904],{"title":935,"searchDepth":936,"depth":936,"links":6233},[6234,6240,6241,6246,6247,6248,6249],{"id":5823,"depth":936,"text":5824,"children":6235},[6236,6237,6238,6239],{"id":5830,"depth":943,"text":5831},{"id":5837,"depth":943,"text":5838},{"id":5848,"depth":943,"text":5849},{"id":5858,"depth":943,"text":5859},{"id":5872,"depth":936,"text":5873},{"id":5928,"depth":936,"text":5929,"children":6242},[6243,6244,6245],{"id":5938,"depth":943,"text":5939},{"id":5956,"depth":943,"text":5957},{"id":5985,"depth":943,"text":5986},{"id":6009,"depth":936,"text":6010},{"id":6083,"depth":936,"text":6084},{"id":6136,"depth":936,"text":6137},{"id":2833,"depth":936,"text":6178},["Date","2026-01-26T00:00:00.000Z"],"自动化与场景功能重磅发布！通过预设逻辑实现设备业务自治，大幅降低人工成本，助您构建稳如磐石的无人值守智能管理体系。",{},"/blog/automation-scene-feature-released",{"title":5793,"description":6251},"blog/automation-scene-feature-released",[976,2886],"rHlzt9gEO7_2d8ZkXPCRNZlWfVLEJYRQAaFjLqLj4Dk",{"id":6259,"title":6260,"automation":6,"body":6261,"buy":6,"category":6,"categorySlug":6,"createdAt":6928,"description":6929,"deviceRefs":6,"difficulty":6,"estimatedTime":6,"extension":969,"headpic":6268,"image":6,"industry":6,"industrySlug":6,"keywords":6,"links":6,"meta":6930,"model":6,"name":6,"navigation":971,"path":6931,"protocol":6,"scenario":6,"scenarioSlug":6,"seo":6932,"stem":6933,"tagSlugs":6934,"tags":6,"vendor":6,"website":6,"__hash__":6935},"content/blog/scene-feature-smart-control.md","一键执行场景：轻松实现多设备、多步骤、组合式控制",{"type":8,"value":6262,"toc":6912},[6263,6269,6276,6283,6309,6311,6315,6318,6339,6342,6351,6361,6371,6378,6411,6413,6417,6426,6436,6440,6494,6501,6512,6518,6529,6536,6538,6542,6549,6552,6556,6569,6573,6583,6587,6598,6602,6611,6615,6625,6645,6647,6651,6668,6674,6684,6702,6709,6723,6734,6742,6744,6748,6770,6781,6812,6819,6843,6859,6861,6868,6874,6876,6878,6900,6902],[11,6264,6265],{},[14,6266],{"alt":6267,"src":6268},"articles/2024/20260315193658_af44d17227c26784f1d6acd90de6777f.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260315193658_af44d17227c26784f1d6acd90de6777f.png",[11,6270,6271,6272,6275],{},"在 ThingsCloud 平台持续进化的过程中，我们始终围绕着用户最真实的使用场景，不断打磨",[36,6273,6274],{},"更简单、更高效、更智能","的功能体验。",[11,6277,6278,6279,6282],{},"从设备快速接入、数据可视化监控，到一键生成专属物联网 APP，再到全新上线的",[36,6280,6281],{},"零代码自动化能力","，我们一步步夯实基础，也一步步为用户打开物联网的更多可能。",[11,6284,6285,6286,6289,6290,6292,6293,6296,6297,6300,6301,6304,6305,6308],{},"如今，随着",[36,6287,6288],{},"场景功能","正式与",[36,6291,2201],{},"协同上线，我们希望为每一位用户带来",[36,6294,6295],{},"更直观、更便捷、更具质感","的管理体验 —— 用",[36,6298,6299],{},"一键场景","，整合复杂操作，简化流程控制，让物联网从 ",[36,6302,6303],{},"\"看得清、自动管\"","，升级为 ",[36,6306,6307],{},"\"一键控、全局协\"","，让设备管理更轻松、更高效、更智能。",[25,6310],{},[28,6312,6314],{"id":6313},"一场景化操作是物联网智能体验的重要升级","一、场景化操作，是物联网智能体验的重要升级 🚀",[11,6316,6317],{},"在日常设备管理中，我们常常会遇到这样的情况：",[44,6319,6320,6326,6333],{},[47,6321,6103,6322,6325],{},[36,6323,6324],{},"启动一条产线","，需要依次开启多台设备",[47,6327,6328,6329,6332],{},"💼 ",[36,6330,6331],{},"下班或离开现场","，需要逐一关闭灯光、空调、风机",[47,6334,3814,6335,6338],{},[36,6336,6337],{},"进入应急状态","，需要快速调整一系列设备参数",[11,6340,6341],{},"操作繁琐、步骤多、耗时长，还容易因为遗漏或误操作带来风险。",[11,6343,6344,6345,1327,6348,6350],{},"过去，我们的",[36,6346,6347],{},"远程控制",[36,6349,1961],{},"已经很好地解决了远程查看、远程操作的基础需求，让管理摆脱空间限制。",[11,6352,6353,6354,6356,6357,6360],{},"而",[36,6355,6288],{},"的到来，则是在成熟的能力之上，进一步解决",[36,6358,6359],{},"流程化、一键化、标准化","的高阶需求。",[11,6362,6363,6364,6367,6368,39],{},"它不是替代原有控制方式，也不是弱化基础功能，而是让",[36,6365,6366],{},"常用操作、组合操作、模式化操作","，变得更",[36,6369,6370],{},"快捷、更统一、更可靠",[11,6372,6373,6374,6377],{},"无论是日常运维、模式切换、节能管理，还是应急启动、产线启停，都可以提前编排成专属场景，在需要的时候",[36,6375,6376],{},"轻轻一点","，即可自动执行整套流程。",[19,6379,6380,6385],{},[11,6381,6382],{},[36,6383,6384],{},"简单来说：",[44,6386,6387,6393,6399,6405],{},[47,6388,6389,6390],{},"可视化让管理",[36,6391,6392],{},"更清晰",[47,6394,6395,6396],{},"场景功能让管理",[36,6397,6398],{},"更轻松",[47,6400,6401,6402],{},"自动化让设备",[36,6403,6404],{},"更智能",[47,6406,6407,6408],{},"场景功能让操作",[36,6409,6410],{},"更简单",[25,6412],{},[28,6414,6416],{"id":6415},"二什么是场景功能一键触发整套流程自动执行","二、什么是场景功能？一键触发，整套流程自动执行 🎯",[11,6418,5876,6419,6421,6422,6425],{},[36,6420,6288],{},"，是为",[36,6423,6424],{},"高频、多步骤、组合式操作","量身打造的智能模式功能。",[11,6427,6428,6429,6432,6433,39],{},"你可以把它理解为物联网系统里的 ",[36,6430,6431],{},"\"一键模式\"","，就像我们熟悉的居家场景、办公场景、睡眠场景一样，在物联网设备管理中，同样可以拥有",[36,6434,6435],{},"属于业务的专属场景",[193,6437,6439],{"id":6438},"它的核心价值非常清晰","它的核心价值非常清晰：",[85,6441,6442,6452],{},[88,6443,6444],{},[91,6445,6446,6449],{},[94,6447,6448],{},"核心价值",[94,6450,6451],{},"具体说明",[104,6453,6454,6464,6474,6484],{},[91,6455,6456,6461],{},[109,6457,6458],{},[36,6459,6460],{},"打包复杂操作",[109,6462,6463],{},"把复杂的多设备操作，打包成一个按钮",[91,6465,6466,6471],{},[109,6467,6468],{},[36,6469,6470],{},"自动化流程",[109,6472,6473],{},"把人工依次执行的流程，变成自动化顺序执行",[91,6475,6476,6481],{},[109,6477,6478],{},[36,6479,6480],{},"标准化控制",[109,6482,6483],{},"把容易出错的手动控制，变成标准化、可复用的场景",[91,6485,6486,6491],{},[109,6487,6488],{},[36,6489,6490],{},"灵活编排",[109,6492,6493],{},"支持延迟执行、顺序控制、多设备协同，逻辑清晰，运行稳定",[11,6495,6496,6497,6500],{},"在配置上，场景功能延续了 ThingsCloud 一贯的 ",[36,6498,6499],{},"零代码、可视化、易上手"," 风格：",[44,6502,6503,6506,6509],{},[47,6504,6505],{},"❌ 无需开发",[47,6507,6508],{},"❌ 无需代码",[47,6510,6511],{},"❌ 无需专业技术",[11,6513,6514,6515,39],{},"业务人员与运维人员都能",[36,6516,6517],{},"轻松创建、随时修改",[11,6519,6520,6521,6524,6525,6528],{},"创建完成后，你可以在",[36,6522,6523],{},"平台网页端、手机 APP、大屏看板","上随时调用，",[36,6526,6527],{},"一键触发，全程自动执行","，真正实现：",[19,6530,6531],{},[11,6532,6533],{},[36,6534,6535],{},"复杂流程简单化，简单操作标准化。",[25,6537],{},[28,6539,6541],{"id":6540},"三这些高频场景让设备管理效率大幅提升","三、这些高频场景，让设备管理效率大幅提升 ⚡",[11,6543,6544,6545,6548],{},"场景功能可以灵活适配",[36,6546,6547],{},"各行各业的业务需求","，快速落地大量实用的智能模式。",[11,6550,6551],{},"以下是最常见的应用场景：",[193,6553,6555],{"id":6554},"_1-生产场景一键启动-停止产线","1. 生产场景：一键启动 / 停止产线 🏭",[11,6557,6558,6559,6562,6563,6565,6566,39],{},"提前编排好产线设备启动流程，上班时",[36,6560,6561],{},"一键触发","，系统按顺序开启设备、启动泵阀、运行辅助设施；下班时",[36,6564,6561],{},"，系统依次关闭设备、停止运行，",[36,6567,6568],{},"安全又高效",[193,6570,6572],{"id":6571},"_2-节能场景一键进入节能模式","2. 节能场景：一键进入节能模式 💡",[11,6574,6575,6576,6579,6580,39],{},"离开办公室、仓库、车间后，",[36,6577,6578],{},"一键触发节能场景","，自动关闭照明、空调、风机、非必要负载，在不影响安全的前提下",[36,6581,6582],{},"最大化降低能耗",[193,6584,6586],{"id":6585},"_3-安防场景一键布防-撤防","3. 安防场景：一键布防 / 撤防 🔒",[11,6588,6589,6590,6593,6594,6597],{},"适用于园区、机房、仓库等区域，",[36,6591,6592],{},"一键开启","安防监控、声光报警、门禁锁定、区域监测；工作开始后",[36,6595,6596],{},"一键撤防","，恢复正常使用状态。",[193,6599,6601],{"id":6600},"_4-应急场景一键应急处理","4. 应急场景：一键应急处理 🚨",[11,6603,6604,6605,6607,6608,39],{},"针对漏水、超温、断电、设备故障等突发情况，预设应急处理流程，",[36,6606,6561],{},"即可执行关阀、停机、启动备用设备、通知管理员等整套动作，",[36,6609,6610],{},"快速降低风险",[193,6612,6614],{"id":6613},"_5-农业-养殖场景一键管理环境","5. 农业 / 养殖场景：一键管理环境 🌱",[11,6616,6617,6618,6621,6622,39],{},"灌溉、通风、降温、增氧等组合操作打包成场景，根据天气、时段、作物需求",[36,6619,6620],{},"一键执行","，让种植养殖管理",[36,6623,6624],{},"更轻松、更规范",[19,6626,6627],{},[11,6628,6629,6630,6633,6634,6633,6637,6640,6641,6644],{},"场景功能让每一次操作都更有",[36,6631,6632],{},"秩序","、更有",[36,6635,6636],{},"效率",[36,6638,6639],{},"质感","，也让物联网系统的",[36,6642,6643],{},"专业度与体验感","同步提升。",[25,6646],{},[28,6648,6650],{"id":6649},"四场景-自动化双剑合璧智能体验再升级-️","四、场景 + 自动化：双剑合璧，智能体验再升级 ⚔️",[11,6652,6653,6654,6656,6657,6659,6660,6663,6664,6667],{},"在 ThingsCloud ",[36,6655,4911],{},"中，",[36,6658,6288],{},"与",[36,6661,6662],{},"自动化功能","完美配合，形成 ",[36,6665,6666],{},"自动触发 + 一键执行"," 的完整智能体系：",[1888,6669,6672],{"className":6670,"code":6671,"language":1893},[1891],"┌─────────────────┐      ┌─────────────────┐\n│   自动化        │  +   │      场景       │\n│  （自动触发）    │      │   （一键执行）   │\n├─────────────────┤      ├─────────────────┤\n│ 条件满足时自动  │      │ 需要时一键执行  │\n│ 执行，实现无人  │      │ 实现便捷操控    │\n│ 值守            │      │                 │\n└─────────────────┘      └─────────────────┘\n          ↓                      ↓\n          └──────────┬───────────┘\n                     ↓\n            自动化可调用场景\n            场景可整合多设备\n",[1154,6673,6671],{"__ignoreMap":935},[11,6675,6676,6677,6680,6681,1350],{},"两者可以",[36,6678,6679],{},"独立使用","，也可以",[36,6682,6683],{},"互相联动",[44,6685,6686,6694],{},[47,6687,5632,6688,6690,6691],{},[36,6689,2201],{},"里可以直接",[36,6692,6693],{},"调用场景",[47,6695,2546,6696,6698,6699],{},[36,6697,423],{},"里也可以",[36,6700,6701],{},"整合多个设备动作",[11,6703,6704,6705,6708],{},"满足从",[36,6706,6707],{},"简单到复杂","的全场景需求。",[11,6710,6711,6712,6714,6715,6718,6719,6722],{},"而对于使用",[36,6713,4907],{},"的用户，现有的",[36,6716,6717],{},"设备接入、远程控制、数据可视化、APP 生成","等核心能力依然",[36,6720,6721],{},"稳定、高效、好用","，完全可以满足日常基础管理需求。",[11,6724,6725,6726,6729,6730,6733],{},"场景与自动化，是为有",[36,6727,6728],{},"更高阶需求","的用户提供的",[36,6731,6732],{},"升级选择","，而非替代原有价值。",[19,6735,6736],{},[11,6737,6738,6739],{},"我们始终坚持：",[36,6740,6741],{},"适合用户的功能，才是最好的功能；循序渐进的升级，才是最安心的升级。",[25,6743],{},[28,6745,6747],{"id":6746},"五更简单的操作更强大的体验thingscloud-持续为你创造价值","五、更简单的操作，更强大的体验，ThingsCloud 持续为你创造价值 🌟",[11,6749,6750,6751,6754,6755,6758,6759,6754,6762,6765,6766,6769],{},"从",[36,6752,6753],{},"设备连接","，到",[36,6756,6757],{},"可视化监控","，从",[36,6760,6761],{},"零代码自动化",[36,6763,6764],{},"一键智能场景","，ThingsCloud 一直在用",[36,6767,6768],{},"更简单、更易用、更贴近业务","的方式，让物联网真正走进每一个行业、每一家企业、每一位用户。",[11,6771,6772,6773,6776,6777,6780],{},"场景功能的上线，不仅是",[36,6774,6775],{},"一次功能的升级","，更是",[36,6778,6779],{},"一次体验的进化"," ——",[44,6782,6783,6793,6801,6806],{},[47,6784,6785,6786,6789,6790],{},"让",[36,6787,6788],{},"复杂","变",[36,6791,6792],{},"简单",[47,6794,6785,6795,6789,6798],{},[36,6796,6797],{},"繁琐",[36,6799,6800],{},"便捷",[47,6802,6803,6804],{},"让管理更有",[36,6805,6639],{},[47,6807,6808,6809],{},"让智能更有",[36,6810,6811],{},"温度",[11,6813,6814,6815,6818],{},"未来，我们将继续以",[36,6816,6817],{},"用户需求为中心","，不断优化产品体验：",[44,6820,6821,6827,6832,6837],{},[47,6822,6823,6824],{},"让连接",[36,6825,6826],{},"更稳定",[47,6828,6829,6830],{},"让可视化",[36,6831,6392],{},[47,6833,6834,6835],{},"让自动化",[36,6836,6404],{},[47,6838,6839,6840],{},"让场景化",[36,6841,6842],{},"更实用",[11,6844,6845,6846,6849,6850,6758,6853,6849,6856,39],{},"与所有用户一起，从",[36,6847,6848],{},"物联网基础","走向",[36,6851,6852],{},"物联网智能",[36,6854,6855],{},"高效管理",[36,6857,6858],{},"无人值守",[25,6860],{},[19,6862,6863],{},[11,6864,6865],{},[36,6866,6867],{},"一键场景，一键智能，一键掌控全局。",[11,6869,6870,6871,39],{},"ThingsCloud 让你的物联网管理，",[36,6872,6873],{},"更简单、更高效、更强大",[25,6875],{},[28,6877,3422],{"id":3421},[44,6879,6880,6887,6894],{},[47,6881,6882,6886],{},[900,6883,6885],{"href":5199,"rel":6884},[904],"创建你的第一个场景"," —— 3 分钟快速上手",[47,6888,6889,6893],{},[900,6890,6892],{"href":6210,"rel":6891},[904],"场景示例"," —— 学习产线启停、节能模式等实战案例",[47,6895,6896,6899],{},[900,6897,5189],{"href":2840,"rel":6898},[904]," —— 了解核心概念",[25,6901],{},[19,6903,6904],{},[11,6905,6906],{},[36,6907,3468,6908,6911],{},[900,6909,3473],{"href":3471,"rel":6910},[904],"，开启一键智能场景之旅！",{"title":935,"searchDepth":936,"depth":936,"links":6913},[6914,6915,6918,6925,6926,6927],{"id":6313,"depth":936,"text":6314},{"id":6415,"depth":936,"text":6416,"children":6916},[6917],{"id":6438,"depth":943,"text":6439},{"id":6540,"depth":936,"text":6541,"children":6919},[6920,6921,6922,6923,6924],{"id":6554,"depth":943,"text":6555},{"id":6571,"depth":943,"text":6572},{"id":6585,"depth":943,"text":6586},{"id":6600,"depth":943,"text":6601},{"id":6613,"depth":943,"text":6614},{"id":6649,"depth":936,"text":6650},{"id":6746,"depth":936,"text":6747},{"id":3421,"depth":936,"text":3422},["Date","2026-01-17T00:00:00.000Z"],"复杂操作一键搞定！场景功能将多设备联动打包成简单模式，配合自动化实现全局协作，让您的管理体验更直观、更具质感。",{},"/blog/scene-feature-smart-control",{"title":6260,"description":6929},"blog/scene-feature-smart-control",[976,2886],"ZB0Z6Lt27EKKyfzbgM-F_5AGRgBZ9L6ENvrIA7NCES0",{"id":6937,"title":6938,"automation":6,"body":6939,"buy":6,"category":6,"categorySlug":6,"createdAt":8190,"description":8191,"deviceRefs":6,"difficulty":6,"estimatedTime":6,"extension":969,"headpic":6946,"image":6,"industry":6,"industrySlug":6,"keywords":6,"links":6,"meta":8192,"model":6,"name":6,"navigation":971,"path":8193,"protocol":6,"scenario":6,"scenarioSlug":6,"seo":8194,"stem":8195,"tagSlugs":8196,"tags":6,"vendor":6,"website":6,"__hash__":8199},"content/blog/how-to-build-perfect-iot-alarm-notification.md","如何用 ThingsCloud 打造全方位多层次的设备告警通知体系",{"type":8,"value":6940,"toc":8153},[6941,6947,6950,6953,6956,6960,6968,6971,6974,6987,6990,6996,6999,7002,7016,7021,7024,7027,7030,7033,7036,7039,7065,7068,7072,7080,7083,7086,7112,7115,7119,7122,7125,7139,7142,7145,7148,7151,7171,7176,7179,7182,7186,7189,7193,7201,7251,7254,7258,7267,7290,7293,7298,7301,7304,7324,7327,7332,7336,7345,7348,7359,7362,7366,7369,7372,7375,7389,7392,7395,7398,7412,7415,7418,7425,7429,7440,7443,7454,7457,7462,7466,7469,7472,7481,7501,7506,7509,7512,7517,7520,7523,7528,7531,7534,7566,7569,7578,7582,7585,7589,7595,7600,7604,7700,7704,7727,7731,7751,7755,7758,7760,7764,7769,7773,7776,7872,7875,7900,7903,7923,7926,7929,7931,7935,7940,7944,7947,8040,8043,8066,8069,8095,8098,8101,8103,8107,8110,8113,8139,8142],[11,6942,6943],{},[14,6944],{"alt":6945,"src":6946},"articles/2024/20260122120832_e50ee2a9439abac39ad2e9b16538027c.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260122120832_e50ee2a9439abac39ad2e9b16538027c.png",[11,6948,6949],{},"在物联网项目的实际应用中，设备告警通知是保障设备稳定运行的核心环节。一个优秀的告警通知体系，不仅要在设备出现异常时及时通知相关人员，更要能够智能判断、精准推送，避免告警风暴对管理者造成骚扰。",[11,6951,6952],{},"ThingsCloud 经过多年在各行业的实践积累，打造了一套全方位、多层次的设备告警通知体系。这套体系从触发机制、状态管理、通知方式、分级控制等多个维度，为不同规模、不同行业的物联网项目提供了灵活而强大的告警通知能力。",[11,6954,6955],{},"本文将带您深入了解 ThingsCloud 的告警通知体系，帮助您构建完善的设备告警通知系统。",[28,6957,6959],{"id":6958},"第一层智能触发机制","第一层：智能触发机制",[11,6961,6962,6967],{},[900,6963,6966],{"href":6964,"rel":6965},"https://www.thingscloud.xyz/docs/guide/alarm/alarm-rule.html",[904],"告警规则","的触发是整个告警通知体系的起点。ThingsCloud 提供了丰富的触发类型和触发条件，让告警规则能够精准捕捉设备异常。",[193,6969,6970],{"id":6970},"灵活的触发类型",[11,6972,6973],{},"ThingsCloud 支持两种触发类型：",[44,6975,6976,6981],{},[47,6977,6978,6980],{},[36,6979,2256],{},"：当设备属性值发生变化时触发告警检查，包括属性上报、属性下发、云端属性更新。",[47,6982,6983,6986],{},[36,6984,6985],{},"设备不活跃","：当设备属性未更新超过设置时间后触发告警检查，用于实现设备离线告警。",[11,6988,6989],{},"这两种触发类型覆盖了绝大多数物联网应用场景，无论是温湿度传感器数据异常、设备故障，还是设备意外离线，都能及时检测到。",[11,6991,6992],{},[14,6993],{"alt":6994,"src":6995},"articles/2024/20260122120952_2c8c95e56e3090a598509b493465951e.png","https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260122120952_2c8c95e56e3090a598509b493465951e.png",[193,6997,6998],{"id":6998},"强大的触发条件",[11,7000,7001],{},"在触发条件方面，ThingsCloud 支持设置多个属性条件，并可以灵活组合：",[44,7003,7004,7010],{},[47,7005,7006,7009],{},[36,7007,7008],{},"AND 逻辑","：多个条件同时成立才触发告警。例如：温度大于 50℃ 且 湿度大于 80% 时触发。",[47,7011,7012,7015],{},[36,7013,7014],{},"OR 逻辑","：多个条件只要有一个成立即触发告警。例如：温度大于 50℃ 或 湿度大于 90% 时触发。",[11,7017,7018],{},[14,7019],{"alt":935,"src":7020},"https://img-1300291923.cos.accelerate.myqcloud.com/articles/2023/20240119223501_acbd261fec1e40f788d38eddfd4d2714.png",[193,7022,7023],{"id":7023},"动态阈值功能",[11,7025,7026],{},"在实际应用中，不同设备往往需要不同的告警阈值。ThingsCloud 提供了动态阈值功能，可以让每个设备自动使用不同的告警阈值。",[11,7028,7029],{},"例如，1000 个温湿度传感器分布在不同的安装位置，每个位置的告警阈值各不相同。使用动态阈值后，无需为每个设备创建独立的告警规则，只需在设备属性中保存阈值，告警规则会自动读取每个设备的阈值进行判断。",[11,7031,7032],{},"更进一步，您还可以让用户通过 App 面板中的数值控制组件，随时修改自己设备的告警阈值，实现真正的个性化告警管理。",[193,7034,7035],{"id":7035},"高级防抖动机制",[11,7037,7038],{},"设备数据往往存在波动，如果频繁在临界值附近变化，会导致大量无效的告警触发和恢复。ThingsCloud 提供了三种防抖动机制：",[2000,7040,7041,7047,7053],{},[47,7042,7043,7046],{},[36,7044,7045],{},"重复次数","：设置条件连续触发的次数，达到次数后才进入告警状态。",[47,7048,7049,7052],{},[36,7050,7051],{},"持续时间","：设置条件持续满足的时间长度，达到时间后才进入告警状态。",[47,7054,7055,7058,7059,7064],{},[36,7056,7057],{},"动态生成条件属性","：使用",[900,7060,7063],{"href":7061,"rel":7062},"https://www.thingscloud.xyz/docs/guide/rules/attrs-rpt-preproc.html",[904],"属性上报预处理规则","，通过代码精确定义告警触发和恢复的边界值，实现完美的防抖动效果。",[11,7066,7067],{},"例如，您可以设置温度大于 20℃ 时触发告警，但温度小于 15℃ 时才恢复告警，这样 15-20℃ 之间的波动就不会导致告警状态抖动。",[28,7069,7071],{"id":7070},"第二层精细化状态管理","第二层：精细化状态管理",[11,7073,7074,7079],{},[900,7075,7078],{"href":7076,"rel":7077},"https://www.thingscloud.xyz/docs/guide/alarm/alarm-state.html",[904],"告警状态","管理是告警通知体系的核心，ThingsCloud 提供了完善的告警状态机制，确保告警通知的准确性和及时性。",[193,7081,7082],{"id":7082},"四种告警状态",[11,7084,7085],{},"ThingsCloud 定义了四种告警状态：",[44,7087,7088,7094,7100,7106],{},[47,7089,7090,7093],{},[36,7091,7092],{},"正常（Ok）","：最近一次设备属性上报未触发告警规则",[47,7095,7096,7099],{},[36,7097,7098],{},"告警（Alerting）","：告警规则已被触发且达到设置的重复次数和持续时间",[47,7101,7102,7105],{},[36,7103,7104],{},"待定（Pending）","：告警规则已触发但未达到设置的重复次数和持续时间",[47,7107,7108,7111],{},[36,7109,7110],{},"未知（Unknown）","：告警规则暂时无明确的告警状态",[11,7113,7114],{},"这种状态机制避免了瞬时数据异常导致的误报，只有当告警条件持续满足时才会真正进入告警状态。",[11,7116,7117],{},[14,7118],{"alt":935,"src":3168},[193,7120,7121],{"id":7121},"设备级告警状态",[11,7123,7124],{},"设备下可能有多个告警规则，设备的告警状态取所有告警规则中最严重的那个状态。分为：",[44,7126,7127,7130,7133,7136],{},[47,7128,7129],{},"无告警",[47,7131,7132],{},"普通告警",[47,7134,7135],{},"重要告警",[47,7137,7138],{},"紧急告警",[11,7140,7141],{},"这样管理人员可以在设备列表中快速识别哪些设备需要优先处理。",[193,7143,7144],{"id":7144},"有效时段管理",[11,7146,7147],{},"在实际应用中，有些告警规则只需要在特定时段生效。ThingsCloud 提供了有效时段功能，可以设置告警规则在一天中的任意时段生效。",[11,7149,7150],{},"例如：",[44,7152,7153,7159,7165],{},[47,7154,7155,7158],{},[36,7156,7157],{},"农业大棚","：白天时段（08:00-19:00）光照强度低于阈值时触发告警",[47,7160,7161,7164],{},[36,7162,7163],{},"园区路灯","：夜晚时段（19:00-次日06:00）某路继电器未闭合时触发告警",[47,7166,7167,7170],{},[36,7168,7169],{},"办公楼宇","：非工作时段监测到异常用电指标时触发告警",[11,7172,7173],{},[14,7174],{"alt":935,"src":7175},"https://img-1300291923.cos.accelerate.myqcloud.com/articles/2023/20230713114117_1496fbcecff6a0199f5c2500f21e13e1.png",[11,7177,7178],{},"您甚至可以对同一个设备属性，在不同时段设置不同的告警规则，实现精细化的时间管理。",[11,7180,7181],{},"此外，还可以开启\"无效时段允许告警恢复\"选项，在有效时段外仍允许告警恢复正常。",[28,7183,7185],{"id":7184},"第三层多元化通知方式","第三层：多元化通知方式",[11,7187,7188],{},"当告警触发后，如何及时通知到相关人员？ThingsCloud 提供了丰富的通知方式，覆盖了不同的使用场景和通知对象。",[193,7190,7192],{"id":7191},"通知组面向项目成员","通知组（面向项目成员）",[11,7194,7195,7200],{},[900,7196,7199],{"href":7197,"rel":7198},"https://www.thingscloud.xyz/docs/guide/alarm/notification.html",[904],"告警通知组","用于为项目成员发送告警通知，支持以下通知方式：",[44,7202,7203,7209,7215,7221,7227,7233,7239,7245],{},[47,7204,7205,7208],{},[36,7206,7207],{},"邮件通知","：发送到项目成员的注册邮箱",[47,7210,7211,7214],{},[36,7212,7213],{},"短信通知","：发送到项目成员认证的手机号码",[47,7216,7217,7220],{},[36,7218,7219],{},"电话通知","：自动拨打电话通知项目成员（需购买电话配额）",[47,7222,7223,7226],{},[36,7224,7225],{},"微信公众号通知","：推送到项目成员绑定的微信公众号",[47,7228,7229,7232],{},[36,7230,7231],{},"企业微信群机器人","：推送到企业微信群",[47,7234,7235,7238],{},[36,7236,7237],{},"钉钉群机器人","：推送到钉钉群",[47,7240,7241,7244],{},[36,7242,7243],{},"飞书群机器人","：推送到飞书群",[47,7246,7247,7250],{},[36,7248,7249],{},"Webhook","：推送到第三方系统 URL",[11,7252,7253],{},"一个告警规则可以关联多个通知组，一个通知组也可以关联到多个告警规则，灵活复用。",[193,7255,7257],{"id":7256},"用户通知面向设备所属用户","用户通知（面向设备所属用户）",[11,7259,7260,7261,7266],{},"除了项目成员，您还可以为设备所属的用户发送",[900,7262,7265],{"href":7263,"rel":7264},"https://www.thingscloud.xyz/docs/guide/alarm/customer-alarm-notify.html",[904],"用户告警通知","。支持以下方式：",[44,7268,7269,7274,7279,7284],{},[47,7270,7271,7273],{},[36,7272,7225],{},"：用户在微信中收到公众号推送的告警消息，可直接点击跳转到设备详情页",[47,7275,7276,7278],{},[36,7277,7213],{},"：发送到用户账号中的手机号码",[47,7280,7281,7283],{},[36,7282,7219],{},"：自动拨打电话通知用户",[47,7285,7286,7289],{},[36,7287,7288],{},"App 通知","：推送到 ThingsX App",[11,7291,7292],{},"如果设备归属于多个用户，平台会为所有用户同时发送告警通知。",[11,7294,7295],{},[14,7296],{"alt":935,"src":7297},"https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260120214654_563789066f958eff738d4793378977e9.png",[193,7299,7300],{"id":7300},"用户个性化通知设置",[11,7302,7303],{},"ThingsCloud 允许为每个用户设置个性化的通知参数：",[44,7305,7306,7312,7318],{},[47,7307,7308,7311],{},[36,7309,7310],{},"开启/关闭通知方式","：用户可以选择接收哪些类型的通知",[47,7313,7314,7317],{},[36,7315,7316],{},"每日通知上限","：为防止频繁告警骚扰用户，可设置每日最大通知次数",[47,7319,7320,7323],{},[36,7321,7322],{},"免打扰时段","：设置多个时间段，在这些时段内不向用户发送告警通知",[11,7325,7326],{},"例如，用户可以设置夜间 22:00-08:00 为免打扰时段，避免夜间非紧急告警影响休息。",[11,7328,7329],{},[14,7330],{"alt":935,"src":7331},"https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260120214136_3d041e77a72a2162354460228179f9af.png",[193,7333,7335],{"id":7334},"webhook-扩展能力","Webhook 扩展能力",[11,7337,7338,7339,7344],{},"如果内置的通知方式无法满足需求，您可以使用 ",[900,7340,7343],{"href":7341,"rel":7342},"https://www.thingscloud.xyz/docs/guide/alarm/alarm-notify-webhook.html",[904],"Webhook 通知","功能，将告警信息推送到任意第三方系统 URL。",[11,7346,7347],{},"Webhook 支持：",[44,7349,7350,7353,7356],{},[47,7351,7352],{},"自定义请求格式（JSON 或表单格式）",[47,7354,7355],{},"自定义 HTTP 请求头",[47,7357,7358],{},"在请求头和请求体中使用动态参数",[11,7360,7361],{},"通过 Webhook，您可以对接几乎任何通知渠道，如自建的消息系统、第三方告警平台等。",[28,7363,7365],{"id":7364},"第四层分级管理与配额控制","第四层：分级管理与配额控制",[11,7367,7368],{},"告警通知不仅要\"发得出\"，还要\"发得对\"、\"发得值\"。ThingsCloud 提供了完善的分级管理和配额控制机制。",[193,7370,7371],{"id":7371},"告警级别",[11,7373,7374],{},"ThingsCloud 支持三种告警级别：",[44,7376,7377,7381,7385],{},[47,7378,7379],{},[36,7380,7132],{},[47,7382,7383],{},[36,7384,7135],{},[47,7386,7387],{},[36,7388,7138],{},[11,7390,7391],{},"告警级别会显示在告警历史和告警通知中，例如邮件通知的标题中会包含告警级别。这样接收者可以快速判断告警的重要程度，决定处理优先级。",[193,7393,7394],{"id":7394},"通知次数上限",[11,7396,7397],{},"为避免设备频繁触发和恢复告警产生大量重复通知，ThingsCloud 提供了两种通知次数上限：",[44,7399,7400,7406],{},[47,7401,7402,7405],{},[36,7403,7404],{},"每日通知次数上限","：设置该告警规则每日的总通知次数上限",[47,7407,7408,7411],{},[36,7409,7410],{},"单个设备每日通知次数上限","：设置对单个设备每日的通知次数上限",[11,7413,7414],{},"当达到上限后，当日将不再发送通知，避免对用户造成骚扰，也避免浪费通知配额。",[193,7416,7417],{"id":7417},"配额管理",[11,7419,7420,7421,1350],{},"邮件、短信、电话通知需要消耗相应的通知配额。ThingsCloud 提供了两级",[900,7422,7417],{"href":7423,"rel":7424},"https://www.thingscloud.xyz/docs/guide/alarm/alarm-notify-quota.html",[904],[7426,7427,7428],"h4",{"id":7428},"项目级配额",[44,7430,7431,7434,7437],{},[47,7432,7433],{},"项目拥有统一的邮件、短信、电话配额池",[47,7435,7436],{},"在项目概要中可以查看剩余配额",[47,7438,7439],{},"需购买配额包才能使用",[7426,7441,7442],{"id":7442},"用户级配额",[44,7444,7445,7448,7451],{},[47,7446,7447],{},"可以为每个用户分配独立的短信和电话配额",[47,7449,7450],{},"支持增加或减少配额，并记录变更历史",[47,7452,7453],{},"用户可以在自己的账户设置中查看配额余额和消耗历史",[11,7455,7456],{},"这种配额机制既保证了通知功能的可用性，又避免了配额浪费，适合 SaaS 模式的运营。",[11,7458,7459],{},[14,7460],{"alt":935,"src":7461},"https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260120214429_9324f3d88f8ea172d8b8b4907eb6e1e8.png",[28,7463,7465],{"id":7464},"第五层全面监控与生态集成","第五层：全面监控与生态集成",[11,7467,7468],{},"完善的告警通知体系不仅要能发送通知，还要能够监控通知效果，并支持与第三方系统的集成。",[193,7470,7471],{"id":7471},"告警历史与通知记录",[11,7473,7474,7475,7480],{},"ThingsCloud 记录了所有的",[900,7476,7479],{"href":7477,"rel":7478},"https://www.thingscloud.xyz/docs/guide/alarm/alarm-message.html",[904],"告警消息","和通知发送记录：",[44,7482,7483,7489,7495],{},[47,7484,7485,7488],{},[36,7486,7487],{},"告警消息历史","：可在项目概要、设备详情、告警规则三个维度查看告警历史",[47,7490,7491,7494],{},[36,7492,7493],{},"告警通知记录","：每条告警消息都会显示是否发送了通知，以及通知方式",[47,7496,7497,7500],{},[36,7498,7499],{},"发送失败追踪","：如果通知发送失败，可以查看失败原因，便于排查问题",[11,7502,7503],{},[14,7504],{"alt":935,"src":7505},"https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260120215737_419be6ad4038efbb6276756580380f38.png",[193,7507,7508],{"id":7508},"告警统计",[11,7510,7511],{},"在项目概要和设备概要中，提供了告警历史统计图表，帮助您直观分析不同时段的告警频次，发现告警规律，优化告警规则。",[11,7513,7514],{},[14,7515],{"alt":935,"src":7516},"https://img-1300291923.cos.ap-beijing.myqcloud.com/articles/2024/20260120214044_70169d4508aaa3ba067a7f8a6bf5b34b.png",[193,7518,7519],{"id":7519},"控制台实时提示",[11,7521,7522],{},"当设备触发告警或恢复正常时，控制台右上角会有通知提示，点击可快速到达设备页面。还支持告警音效，帮助您第一时间发现异常。",[11,7524,7525],{},[14,7526],{"alt":935,"src":7527},"https://img-1300291923.cos.accelerate.myqcloud.com/articles/2023/20230327210611_623ef40c9016417ed51d9c6d4417783a.png",[193,7529,7530],{"id":7530},"生态集成能力",[11,7532,7533],{},"ThingsCloud 提供了多种集成方式，支持在您的业务系统中实现更丰富的告警逻辑：",[44,7535,7536,7546,7556],{},[47,7537,7538,7545],{},[36,7539,7540],{},[900,7541,7544],{"href":7542,"rel":7543},"https://www.thingscloud.xyz/docs/guide/api/project-mqtt-subscribe.html",[904],"MQTT 应用端订阅","：订阅设备实时消息，包括设备告警状态更新，在应用端实现个性化告警逻辑",[47,7547,7548,7555],{},[36,7549,7550],{},[900,7551,7554],{"href":7552,"rel":7553},"https://www.thingscloud.xyz/docs/guide/rules/attrs-rpt.html",[904],"消息规则引擎","：基于数据流转（MQTT/Webhook），获得设备实时消息，实现应用端的告警处理",[47,7557,7558,7565],{},[36,7559,7560],{},[900,7561,7564],{"href":7562,"rel":7563},"https://www.thingscloud.xyz/docs/guide/api/http-api-reference.html",[904],"HTTP API","：通过项目 API 获得聚合数据，实现应用端的告警逻辑",[193,7567,7568],{"id":7568},"集成第三方通知通道",[11,7570,7571,7572,7577],{},"企业版用户可以集成第三方短信和",[900,7573,7576],{"href":7574,"rel":7575},"https://www.thingscloud.xyz/docs/guide/alarm/alarm-notify-voice.html",[904],"语音通知服务","（如阿里云），不消耗平台通知配额，具有更高的灵活性和定制能力。",[28,7579,7581],{"id":7580},"最佳实践三个典型场景的告警通知方案","最佳实践：三个典型场景的告警通知方案",[11,7583,7584],{},"为了帮助您更好地理解如何在实际项目中应用 ThingsCloud 的告警通知体系，下面我们分享三个典型场景的实战案例。",[193,7586,7588],{"id":7587},"场景一农业大棚的智能告警管理","场景一：农业大棚的智能告警管理",[11,7590,7591,7594],{},[36,7592,7593],{},"项目背景","：某农业合作社管理着 50 个智慧大棚，种植反季节蔬菜，需要监控温度、湿度、光照、土壤湿度等关键指标。",[11,7596,7597,1350],{},[36,7598,7599],{},"告警通知方案",[7426,7601,7603],{"id":7602},"_1-告警规则设计","1. 告警规则设计",[85,7605,7606,7622],{},[88,7607,7608],{},[91,7609,7610,7612,7614,7617,7619],{},[94,7611,6966],{},[94,7613,2115],{},[94,7615,7616],{},"有效时段",[94,7618,7371],{},[94,7620,7621],{},"通知方式",[104,7623,7624,7640,7656,7671,7685],{},[91,7625,7626,7629,7632,7635,7637],{},[109,7627,7628],{},"温度过高告警",[109,7630,7631],{},"温度 > 35℃",[109,7633,7634],{},"08:00-19:00",[109,7636,7135],{},[109,7638,7639],{},"微信公众号 + 短信",[91,7641,7642,7645,7648,7651,7653],{},[109,7643,7644],{},"温度过低告警",[109,7646,7647],{},"温度 \u003C 5℃",[109,7649,7650],{},"全天",[109,7652,7138],{},[109,7654,7655],{},"电话 + 微信 + 短信",[91,7657,7658,7661,7664,7666,7668],{},[109,7659,7660],{},"湿度异常告警",[109,7662,7663],{},"湿度 > 90% 或 \u003C 40%",[109,7665,7634],{},[109,7667,7132],{},[109,7669,7670],{},"微信公众号",[91,7672,7673,7676,7679,7681,7683],{},[109,7674,7675],{},"光照不足告警",[109,7677,7678],{},"光照 \u003C 2000Lux",[109,7680,7634],{},[109,7682,7132],{},[109,7684,7670],{},[91,7686,7687,7690,7693,7695,7697],{},[109,7688,7689],{},"设备离线告警",[109,7691,7692],{},"设备不活跃 > 30分钟",[109,7694,7650],{},[109,7696,7135],{},[109,7698,7699],{},"微信 + 短信",[7426,7701,7703],{"id":7702},"_2-高级功能应用","2. 高级功能应用",[44,7705,7706,7712,7717,7722],{},[47,7707,7708,7711],{},[36,7709,7710],{},"动态阈值","：不同作物品种设置不同的温度和湿度阈值，管理员可通过 App 随时调整",[47,7713,7714,7716],{},[36,7715,7045],{},"：温度告警设置 3 次重复触发，避免瞬时数据波动导致误报",[47,7718,7719,7721],{},[36,7720,7394],{},"：每日通知上限 20 次，避免告警风暴骚扰",[47,7723,7724,7726],{},[36,7725,7322],{},"：夜间 22:00-06:00 仅紧急告警发送通知",[7426,7728,7730],{"id":7729},"_3-通知对象设置","3. 通知对象设置",[44,7732,7733,7739,7745],{},[47,7734,7735,7738],{},[36,7736,7737],{},"项目成员","（农业技术员）：接收所有告警通知，通过微信公众号和短信",[47,7740,7741,7744],{},[36,7742,7743],{},"农户","（设备所属用户）：仅接收温度和湿度的紧急告警，通过微信公众号和电话",[47,7746,7747,7750],{},[36,7748,7749],{},"钉钉群","：技术支持群接收所有告警，便于团队协作",[7426,7752,7754],{"id":7753},"_4-实施效果","4. 实施效果",[11,7756,7757],{},"通过分时段、分级别的告警通知策略，农户能够在第一时间获知大棚异常情况，及时采取通风、加热、补光等措施，有效减少了作物损失。技术员也可以通过告警历史分析，优化大棚环境控制策略。",[25,7759],{},[193,7761,7763],{"id":7762},"场景二自来水厂-plc-设备远程监测","场景二：自来水厂 PLC 设备远程监测",[11,7765,7766,7768],{},[36,7767,7593],{},"：某水务公司管理着 10 个水厂，每个水厂有 20-30 台 PLC 设备，需要监控水压、流量、水质、设备状态等关键指标，确保供水安全。",[11,7770,7771,1350],{},[36,7772,7599],{},[7426,7774,7603],{"id":7775},"_1-告警规则设计-1",[85,7777,7778,7793],{},[88,7779,7780],{},[91,7781,7782,7784,7786,7789,7791],{},[94,7783,6966],{},[94,7785,2115],{},[94,7787,7788],{},"重复次数/持续时间",[94,7790,7371],{},[94,7792,7621],{},[104,7794,7795,7811,7826,7842,7858],{},[91,7796,7797,7800,7803,7806,7808],{},[109,7798,7799],{},"出水压力异常",[109,7801,7802],{},"压力 \u003C 0.3MPa 持续 5分钟",[109,7804,7805],{},"持续时间 5分钟",[109,7807,7138],{},[109,7809,7810],{},"电话 + 钉钉群 + 短信",[91,7812,7813,7816,7819,7822,7824],{},[109,7814,7815],{},"进水流量骤降",[109,7817,7818],{},"流量下降 > 50%",[109,7820,7821],{},"重复次数 2次",[109,7823,7138],{},[109,7825,7810],{},[91,7827,7828,7831,7834,7837,7839],{},[109,7829,7830],{},"浊度超标",[109,7832,7833],{},"浊度 > 1.0 NTU",[109,7835,7836],{},"重复次数 3次",[109,7838,7135],{},[109,7840,7841],{},"钉钉群 + 邮件",[91,7843,7844,7847,7850,7853,7855],{},[109,7845,7846],{},"PLC 离线告警",[109,7848,7849],{},"设备不活跃 > 5分钟",[109,7851,7852],{},"无",[109,7854,7135],{},[109,7856,7857],{},"钉钉群 + 短信",[91,7859,7860,7863,7866,7868,7870],{},[109,7861,7862],{},"水池液位告警",[109,7864,7865],{},"液位 > 90% 或 \u003C 20%",[109,7867,7821],{},[109,7869,7132],{},[109,7871,7749],{},[7426,7873,7703],{"id":7874},"_2-高级功能应用-1",[44,7876,7877,7883,7888,7894],{},[47,7878,7879,7882],{},[36,7880,7881],{},"多条件组合","：使用 AND 逻辑，当\"压力低\"且\"流量下降\"同时触发时升级为紧急告警",[47,7884,7885,7887],{},[36,7886,7051],{},"：压力异常需持续 5 分钟才触发，避免水泵启停过程中的瞬时波动",[47,7889,7890,7893],{},[36,7891,7892],{},"告警级别管理","：根据影响范围和紧急程度区分普通、重要、紧急三级",[47,7895,7896,7899],{},[36,7897,7898],{},"Webhook 集成","：将告警信息推送到企业的 SCADA 系统，实现自动派单",[7426,7901,7730],{"id":7902},"_3-通知对象设置-1",[44,7904,7905,7911,7917],{},[47,7906,7907,7910],{},[36,7908,7909],{},"运维团队","（钉钉群）：接收所有告警，支持 @成员实现紧急通知",[47,7912,7913,7916],{},[36,7914,7915],{},"值班工程师","（项目成员）：接收紧急和重要告警，通过电话和短信",[47,7918,7919,7922],{},[36,7920,7921],{},"部门领导","（邮件）：仅接收紧急告警的每日汇总报告",[7426,7924,7754],{"id":7925},"_4-实施效果-1",[11,7927,7928],{},"通过多层次的告警通知体系，水务公司实现了 24 小时无人值守监控。紧急告警通过电话直接通知值班工程师，确保 5 分钟内响应；一般告警通过钉钉群通知团队，便于合理安排维修计划。告警历史数据还帮助公司优化了设备维护策略，降低了故障率。",[25,7930],{},[193,7932,7934],{"id":7933},"场景三康养机构的老人睡眠监测","场景三：康养机构的老人睡眠监测",[11,7936,7937,7939],{},[36,7938,7593],{},"：某高端康养机构为每个房间配备了智能床垫，监测老人的心率、呼吸率、体动、在离床状态等，夜间需要关注老人的睡眠质量和安全状况。",[11,7941,7942,1350],{},[36,7943,7599],{},[7426,7945,7603],{"id":7946},"_1-告警规则设计-2",[85,7948,7949,7963],{},[88,7950,7951],{},[91,7952,7953,7955,7957,7959,7961],{},[94,7954,6966],{},[94,7956,2115],{},[94,7958,7616],{},[94,7960,7371],{},[94,7962,7621],{},[104,7964,7965,7981,7996,8010,8025],{},[91,7966,7967,7970,7973,7976,7978],{},[109,7968,7969],{},"夜间长时间离床",[109,7971,7972],{},"离床状态 > 30分钟",[109,7974,7975],{},"22:00-06:00",[109,7977,7135],{},[109,7979,7980],{},"值班室 App + 护工站屏幕",[91,7982,7983,7986,7989,7991,7993],{},[109,7984,7985],{},"心率异常",[109,7987,7988],{},"心率 \u003C 50 或 > 120",[109,7990,7650],{},[109,7992,7138],{},[109,7994,7995],{},"电话 + App + 微信(家属)",[91,7997,7998,8001,8004,8006,8008],{},[109,7999,8000],{},"呼吸异常",[109,8002,8003],{},"呼吸率 \u003C 10 或 > 25",[109,8005,7650],{},[109,8007,7138],{},[109,8009,7995],{},[91,8011,8012,8015,8018,8020,8022],{},[109,8013,8014],{},"体动异常（夜间）",[109,8016,8017],{},"体动为 0 持续 2小时",[109,8019,7975],{},[109,8021,7135],{},[109,8023,8024],{},"App + 护工站屏幕",[91,8026,8027,8030,8033,8035,8037],{},[109,8028,8029],{},"设备离线",[109,8031,8032],{},"智能床垫不活跃 > 1小时",[109,8034,7650],{},[109,8036,7132],{},[109,8038,8039],{},"App",[7426,8041,7703],{"id":8042},"_2-高级功能应用-2",[44,8044,8045,8050,8056,8061],{},[47,8046,8047,8049],{},[36,8048,7616],{},"：夜间长时间离床告警仅在 22:00-06:00 生效，避免白天误报",[47,8051,8052,8055],{},[36,8053,8054],{},"用户配额管理","：每个老人的家属账户分配 10 条短信/月配额，超出后仅接收微信公众号通知",[47,8057,8058,8060],{},[36,8059,7322],{},"：体动异常告警在 23:00-06:00 不向家属发送，仅通知值班人员",[47,8062,8063,8065],{},[36,8064,7316],{},"：心率异常告警每日上限 5 次，避免老人病情波动时频繁骚扰家属",[7426,8067,7730],{"id":8068},"_3-通知对象设置-2",[44,8070,8071,8077,8083,8089],{},[47,8072,8073,8076],{},[36,8074,8075],{},"值班护士","（App 通知）：接收所有告警，App 推送确保及时响应",[47,8078,8079,8082],{},[36,8080,8081],{},"护工站","（看板组件）：在大屏幕显示所有告警历史，便于全局监控",[47,8084,8085,8088],{},[36,8086,8087],{},"老人家属","（微信公众号 + 短信）：仅接收紧急告警（心率、呼吸异常），通过微信公众号查看详情可直接跳转到老人健康数据页面",[47,8090,8091,8094],{},[36,8092,8093],{},"院长","（告警统计报告）：每周一通过邮件接收上周告警统计",[7426,8096,7754],{"id":8097},"_4-实施效果-2",[11,8099,8100],{},"通过精细化、个性化的告警通知方案，康养机构实现了对老人夜间安全的全方位保障。紧急情况能够第一时间通知值班护士和家属，普通异常则通过看板和大屏幕提醒护工关注。用户配额管理和免打扰设置既保证了重要告警的及时送达，又避免了对家属的过度打扰，提升了服务质量。",[25,8102],{},[28,8104,8106],{"id":8105},"结语构建适合您的告警通知体系","结语：构建适合您的告警通知体系",[11,8108,8109],{},"ThingsCloud 的告警通知体系是一个多层次、全方位的完整解决方案。从触发机制到状态管理，从通知方式到配额控制，从监控统计到生态集成，每个层次都提供了丰富的功能选项。",[11,8111,8112],{},"通过本文的介绍和三个典型案例的分析，您可以根据项目的具体需求，灵活组合这些功能：",[44,8114,8115,8121,8127,8133],{},[47,8116,8117,8120],{},[36,8118,8119],{},"小型项目","：使用基本的告警规则 + 邮件/短信通知即可满足需求",[47,8122,8123,8126],{},[36,8124,8125],{},"中型项目","：增加告警级别、有效时段、通知次数上限等管理功能",[47,8128,8129,8132],{},[36,8130,8131],{},"大型项目","：充分利用动态阈值、用户通知、Webhook、配额管理等高级功能",[47,8134,8135,8138],{},[36,8136,8137],{},"SaaS 项目","：结合用户通知、用户配额、免打扰时段等，实现多租户管理",[11,8140,8141],{},"无论您的项目规模如何，ThingsCloud 都能为您提供合适的告警通知方案，帮助您构建可靠的物联网设备管理体系。",[11,8143,8144,8145,996,8148,39],{},"如果您正在将物联网设备接入 ThingsCloud，请参考 ",[900,8146,1411],{"href":1409,"rel":8147},[904],[900,8149,8152],{"href":8150,"rel":8151},"https://www.thingscloud.xyz/docs/tutorials/",[904],"教程",{"title":935,"searchDepth":936,"depth":936,"links":8154},[8155,8161,8166,8172,8177,8184,8189],{"id":6958,"depth":936,"text":6959,"children":8156},[8157,8158,8159,8160],{"id":6970,"depth":943,"text":6970},{"id":6998,"depth":943,"text":6998},{"id":7023,"depth":943,"text":7023},{"id":7035,"depth":943,"text":7035},{"id":7070,"depth":936,"text":7071,"children":8162},[8163,8164,8165],{"id":7082,"depth":943,"text":7082},{"id":7121,"depth":943,"text":7121},{"id":7144,"depth":943,"text":7144},{"id":7184,"depth":936,"text":7185,"children":8167},[8168,8169,8170,8171],{"id":7191,"depth":943,"text":7192},{"id":7256,"depth":943,"text":7257},{"id":7300,"depth":943,"text":7300},{"id":7334,"depth":943,"text":7335},{"id":7364,"depth":936,"text":7365,"children":8173},[8174,8175,8176],{"id":7371,"depth":943,"text":7371},{"id":7394,"depth":943,"text":7394},{"id":7417,"depth":943,"text":7417},{"id":7464,"depth":936,"text":7465,"children":8178},[8179,8180,8181,8182,8183],{"id":7471,"depth":943,"text":7471},{"id":7508,"depth":943,"text":7508},{"id":7519,"depth":943,"text":7519},{"id":7530,"depth":943,"text":7530},{"id":7568,"depth":943,"text":7568},{"id":7580,"depth":936,"text":7581,"children":8185},[8186,8187,8188],{"id":7587,"depth":943,"text":7588},{"id":7762,"depth":943,"text":7763},{"id":7933,"depth":943,"text":7934},{"id":8105,"depth":936,"text":8106},["Date","2026-01-05T00:00:00.000Z"],"深入解析ThingsCloud告警通知体系，从智能触发、状态管理、多元化通知到分级控制，帮助您构建完善的物联网设备告警通知系统。",{},"/blog/how-to-build-perfect-iot-alarm-notification",{"title":6938,"description":8191},"blog/how-to-build-perfect-iot-alarm-notification",[8197,976,8198],"alarm-alerts","best-practices","77bSb8183UloBy0_SS35j1Pes3pN0SZ6SHtpEZy5sJk",1778939677336]