Loosely Coupled
At Seed we are promoting a rather radical departure from the currently established smart home topologies. Almost everybody else have been promoting two fundamental angles of approach:
#2 is more tricky. You press a switch. The light turns on. Is the switch sending a command to the lamp? In most systems it is. Be it a source-based routed (Z-Wave) or destination-based routed (ZigBee, Thread) network, the switch formats a command and based on the pre-configured relationship sends the command to the lamp. Which is OK for the switch example. But take the motion sensor. It should activate the lamp, but only when it is dark. The ambient light sensor is a separate unit. How does the motion sensor coordinate the actions with the ambient light sensor to turn on the lamp? It is difficult.
So why don't we reverse the relationships? Instead of the switch addressing the lamp, it should just broadcast the state change "I see motion". The ambient light sensor would report "It is dark". The lamp would listen to the selected messages figuring out: "it is dark, there is motion detected, I should turn on". This publish - subscribe information flow model fundamentally changes how the devices are configured and how the information is being exchanged. Neither the switch nor the light sensor know the recipients of their messages. They just broadcast. The actor devices listen to the subscribed broadcasts and act.
We strongly believe this broadcaster - subscriber model is the right one for smart home. So it is not just the Bluetooth radio that makes us different. It is the approach to the information exchange model, which we believe, is the winning one.
- A smartphone is used to control the devices
- A routed mesh network is needed to deliver the commands to the devices
- A smartphone is used to configure the smart home network
(it can also be used as a controller but when outside, to control remotely) - There are no control commands being sent to the devices
#2 is more tricky. You press a switch. The light turns on. Is the switch sending a command to the lamp? In most systems it is. Be it a source-based routed (Z-Wave) or destination-based routed (ZigBee, Thread) network, the switch formats a command and based on the pre-configured relationship sends the command to the lamp. Which is OK for the switch example. But take the motion sensor. It should activate the lamp, but only when it is dark. The ambient light sensor is a separate unit. How does the motion sensor coordinate the actions with the ambient light sensor to turn on the lamp? It is difficult.
So why don't we reverse the relationships? Instead of the switch addressing the lamp, it should just broadcast the state change "I see motion". The ambient light sensor would report "It is dark". The lamp would listen to the selected messages figuring out: "it is dark, there is motion detected, I should turn on". This publish - subscribe information flow model fundamentally changes how the devices are configured and how the information is being exchanged. Neither the switch nor the light sensor know the recipients of their messages. They just broadcast. The actor devices listen to the subscribed broadcasts and act.
We strongly believe this broadcaster - subscriber model is the right one for smart home. So it is not just the Bluetooth radio that makes us different. It is the approach to the information exchange model, which we believe, is the winning one.
Comments
Post a Comment