The sender should be collected and sent along to Mycroft via the messagebus. The sender id would need to be stored in a database which would correspond with a friendlier name (like kitchen, or Chris).
A hurdle to go through would be that the sender id (I think) automatically is generated every time the client connects. A solution would be to when connecting to a new network, send the device id that Mycroft Home gives it to the other devices, who then can store that value, and use it in the future when checking if a device has already been connected
The sender should be collected and sent along to Mycroft via the messagebus. The sender id would need to be stored in a database which would correspond with a friendlier name (like kitchen, or Chris).
A hurdle to go through would be that the sender id (I think) automatically is generated every time the client connects. A solution would be to when connecting to a new network, send the device id that Mycroft Home gives it to the other devices, who then can store that value, and use it in the future when checking if a device has already been connected