Common TCP based protocol to automate Max2Play devices

Max2Play Home 2016 (en) Forums Max2Play Development (Ideas, Wishes) Common TCP based protocol to automate Max2Play devices

Tagged: 

This topic contains 0 replies, has 1 voice, and was last updated by  m.max2play 1 day, 10 hours ago.

Viewing 1 post (of 1 total)
  • 2. December 2016 at 6:52 #24480

    Max2Play provides plugins for audio, video, sensors and home automation.

    Instead of relying on their individual interfaces, with lack of uniformity and a standard way of communication with these disparate devices, there is a need to communicate with these using TCP based simple commands. Can Max2Play provide an aggregator TCP comms plugin which can be used to abstract away the disparate communication methods for these devices under a central standard way of communication if one uses Max2Play; this plugin should then translate the TCP comms to individual device specific comms.

    This will go a long way in making Max2Play a key piece in integration of Max2Play supported software/hardware devices into the larger home automation project. Probably Max2Play should focus on the key area of AV: Kodi for video, Squeezeserver for multi room audio, possibly TV and radio too, expanding to sensors and lights only later if needed, but allowing simple automation of Kodi and Squeezeserver/player will in itself help a lot since it is one of the most inexpensive, feature rich video and multi room music platform.

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.

Register here