Major upgrade

[zoe-codez]

📬 Changes

⚠️ REQUIRES UPGRADE TO ADDON

• Improved entity syncing synapse-extension#10

Changes

• Added a bunch more debug/trace level logs
• Added native bun compatibility to project
• Locals updates now trigger synapse entity updates
• Disabled helper domains that aren't ready for general use
• Improved comms with integration (will more aggressively sync entities, see addon PR notes for more)
• Entity information more frequently written to database
• Entities like datetime/date will set a default native value of boot time if one isn't otherwise provided (this is preserved in db, not reset next boot)
• Hard to avoid circular references with reactive configs in libraries #14
• Sqlite for bun runtime #24
• Entity defaults don't transfer to home assistant #19
• Add common config for disabling entities #15

Default config updates

Previously, setting up an entity like this would cause the icon to be captured in the database, then served up as the real value until the end of time (or you reset the db)

// boot 1
const mySwitch  = synapse.switch({
  icon: "mdi:foo"
})
// ✅ boot 2, value changes
const mySwitch  = synapse.switch({
  icon: "mdi:bar"
})

When a new entity is declared, the default values are compared and the field is reset if a change in default value is detected. As long as the default value is the same, the value inside of the database continues to take priority

mySwitch.icon = "mdi:baz"; // ✅ assignment is tracked in database 

Reactive configs

Full source for example

synapse.sensor<{ locals: { targetTime: string }; state: string }>({
 // condensed notation for when the defaults will work
  icon: ({ locals }) => (locals.targetTime ? "mdi:cookie-clock" : "mdi:cookie-alert-outline"),
  locals: { targetTime: undefined },
  state: {
// expanded notation still valid
    current({ locals }) {
      const now = dayjs();
      const diff = dayjs(locals.targetTime).diff(now, "second");
      const value = Math.max(0, diff).toString();
      return `${value}s`;
    },
    schedule: CronExpression.EVERY_SECOND,
  },
});

All reactive configs receive the proxy as the 1st param. This helps to resolve circular type references (which makes typescript big mad).

Reactive bindings

The current expanded notation for reactive allows for an onUpdate list of entities to influence when the reactive functions are run. Items in the bind array in the entity reference will be merged with that list.

These apply to the condensed function notation also

synapse.sensor<{ locals: { targetTime: string }; state: string }>({
  bind: [hassEntityReference, synapseEntity],
  icon: ({ locals }) => ...
});

🗒️ Checklist

• Read the contribution guide and accept the
  code of conduct
• Readme and docs (updated or not needed)
• Tests (added, updated or not needed)