function61 / hautomo Goto Github PK

This would by type-safer in cases where the adapter needs to look up config for device before acting on it. Looks awkward having to resolve device config based on the device's adapter id - in theory it could return nil but it shouldnt..

Consider using same style as here https://github.com/genuinetools/pepper

This requires:

• Code generation support
• Deserialization by InboundEventType() to actual struct

Should stop applying all policies and event subscriptions.

Only explicit on/off commands are listened to from the user.

• They could take a preinitialized Adapter instance
• They could access settings via AdapterConfig, and thus we wouldn't need additional code to map the settings to func args

https://developer.amazon.com/docs/device-apis/alexa-contactsensor.html

https://github.com/dyrkin/zigbee-steward

Not much point in it (mainly for debugging), but as long as the CLI code exists in the repo we should support it

Bluetooth is so flaky, sometimes even re-tries won't turn it on for minutes.. it sorts itself eventually

Consistency is key. Now in config adapters and sensors are unified but in code they are separate concepts..

Finally create repo for commonly used gosnippets?

https://github.com/madhead/saberlight/blob/master/protocols/Triones/protocol.md

Same style as Ubiquiti controller does