CtrlK
BlogDocsLog inGet started
Tessl Logo

jbaruch/hubitat-dev

Context for developing and debugging Hubitat Elevation apps, drivers, and hub environment — sandbox constraints, lifecycle idioms, capability contracts, plus grounded deploy/log-tail/lint mechanisms.

81

Quality

94%

Does it follow best practices?

Impact

27%

Average score across 2 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-2/

Task

A developer is writing a Hubitat Elevation driver and is considering these imports. For each one, state whether it will work in the Hubitat sandbox or be rejected at compile time when the code is saved, and for the rejected ones name the Hubitat-native alternative to use instead.

  • java.util.ArrayList
  • java.io.File
  • java.net.HttpURLConnection
  • groovy.json.JsonSlurper
  • java.util.concurrent.ConcurrentHashMap
  • java.lang.Thread

Answer concisely: one line per import — the import, allowed or rejected, and a brief reason. Do not write a driver.

.mcp.json

README.md

tile.json