sidoh / esp8266_milight_hub

Replacement for a Milight/LimitlessLED hub hosted on an ESP8266
MIT License
947 stars 220 forks source link

Device ID for UDP settings #694

Closed bcaro closed 3 years ago

bcaro commented 3 years ago

Hi! I'am the author of a plugin for Jeedom and I plan to replace the official discontinued ibox1/2 by this bub. In order to give advices to the users I need to know the meaning and the use of "Device ID" field in the configuration of the hub, because I do not use any ID in my plugin. Thank's for your response

Very good job, this hub is awesome to replace the stack hub.

sidoh commented 3 years ago

Hi @bcaro,

Device IDs are random 16 bit integers that are baked into every remote/wifi gateway. When you pair a bulb with a remote, it becomes associated with the remote's ID.

espMH is able to plug in whatever value you want for the device ID, which is why it's capable of controlling way more lights than the off the shelf remotes.

sidoh commented 3 years ago

In the context of your plugin:

bcaro commented 3 years ago

Thank you for the response so for "enter hub ID" I put an hex like this : 0xAABB or an integer like this 12345 And in my plugin I use this ID in position 5 and 6 of the frame : 0x80, 0x00, 0x00, 0x00, 0x11, 0xFF, 0xFF, 0xE6, 0x80, 0x00, 0x31 Thank's Bernard

sidoh commented 3 years ago

Yeah, that sounds right.

For what it's worth -- if it's possible for your plugin to use something other than the UDP protocol, I'd highly recommend it. MQTT is best, but requires your users to have an MQTT broker set up.

bcaro commented 3 years ago

OK thanks I will keep the udp protocol for users who have configured their devices et propose REST API for new users. Thank's.