Hub v2 and Stability
1.35- Platform reliability/stability
2:15- Most stability issues experience in 6-9 months - DevConn layer. This allows us to hold all the connection with all the SmartThings hubs.
3:05- Jeff explains how the Devconn layer works
4:20 - Inbound/Outbound : Outbound is where we’ve had some challenges. Vertex supports clustering of servers. One of them will be orphaned from the clusters.
5:29 - We are no longer using Vertex technology, and we’re using a more home-grown solution.
6:30 - 3 architectural changes: 1 was Vertex, 2nd is our Queueing system (not done yet), Scheduler improvements (this has been replaced, but we haven’t moved all customers to it yet.)
8:17 - Jeff talks about scheduler improvement
10:23- Q/A on Reliability/Stability
10:51 - Release cycles - Weekly updates on the platform side. and a monthly update on mobile updates.
13:07 - Jeff is talking about availability - 99.99, long term, 99.999%
16:10 - Best practices about writing SmartApps/Device
18:45- KPI’s on the SLA areas
25:00 - Question regarding transparency on ST changes.
30:24- HubV2 update
31:15 - runs linux OS, 512 mb memory, 1 core 1ghz processor/
31:40 - Jeff explains How Hub v2 processes their engine.
33:56- Device handler and how that works.
36:53 - Back up battery power
37:52 - Visibility and Control for Hub V2
40:01- Hub v2 life cycle : Where it is right now.
41:00 - Questions and Answers of Hub v2
41:43- Post Rollout of hubv2 - Jeff explains what will happen to hub v1.
44:38 - local storage on hubv2/external
47:07- Cloud to Cloud like Ecobee/Nest. Jeff explains how that works.
50:14 - plans and restoring previous states - Migration from hubv1-hubv2. Migration is not available on day 1, but 60 days of launch.
52:03- meta data tag to run locally.
58:09 - Scheduler in V2
1:02- Radio difference in hub v1 and hubv2
1:05- ~1/3 of the total ram with our software, rest is to run SmartApps and Device Types.
1:07 - Log access other than Live.
1:09 Z-Wave network scheduler for hubv2