Is your feature request related to a problem? Please describe.
Code in the Property descriptor calls async functions to lay the groundwork for an events/notification mechanism. This is not yet fully implemented, but is used by the web socket code. These async calls will only work when they can be run in an event loop, i.e. after the ThingServer has been started. This can lead to errors when properties are written to on a Thing that has not yet been attached to a server and started.
Describe the solution you'd like
Errors, if raised, should be helpful and make it clear that a server is required. It would be even nicer if there was a way to disable the event mechanism, so that the Thing can function without the server.
Additional context
This closely follows the discussion in #115.
Is your feature request related to a problem? Please describe.
Code in the
Propertydescriptor callsasyncfunctions to lay the groundwork for an events/notification mechanism. This is not yet fully implemented, but is used by the web socket code. Theseasynccalls will only work when they can be run in an event loop, i.e. after theThingServerhas been started. This can lead to errors when properties are written to on aThingthat has not yet been attached to a server and started.Describe the solution you'd like
Errors, if raised, should be helpful and make it clear that a server is required. It would be even nicer if there was a way to disable the event mechanism, so that the
Thingcan function without the server.Additional context
This closely follows the discussion in #115.