You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello community / @sidoh, I am trying to set up a system where I can control Phillips Hue spike lights (lily spot) with a Milight remote control.
I have set up a milight hub on an esp8266 d1 mini for which I have created a little custom motherboard which makes connections for the RFL2401 module and a dedicated 3v3 reg for the radio.
I have tried both 1.11.2 and 1.12.0 firmware but the firmware is not the problem in this case, everything is working fine. I have set up MQTT and can see messages coming through correctly when i set up a terminal and subscribe to the topic I have set up on a mosquitto broker.
I have set up diyHue version 1966117030 on a raspberry pi 5 and linked it to the Hue Essentials app along with the legit Phillips Hue Hub. Both sets of lights (Phillips Lily spot and a test RGBCCT strip with FUT0037 3-in-1 controller) work in the hue essentials app when i group them together, although I get very little control (only on/off works in the top right corner) in the diyhue interface.
My question is, are there particular topics i need to set up for the mqtt messages to be forwarded to the Hue bridge? I just cant seem to get this to work. I have verified my device ID for the remote I was testing (FUT089) which is 0x91FE
I have tried a few different topics in the Discovery prefix in diyhue such as
milight/:device_id/:device_type/:group_id
milight/0x91FE/fut089/+
milight/state/0x91FE/fut089/2/
...and a few other variations.
What am I doing wrong here?
I would suspect I would only need to set up a "MQTT state topic pattern" so that only physical remote pressed are forwarded to the broker. But these messages must follow a particular format and (obviously) sending to the correct topic also.
I'm not super familiar with diyhue so not sure how helpful I'll be without more detail. If you tell me what you want to happen when you press a button the remote at the MQTT layer I can probably be more helpful.
Hello community / @sidoh, I am trying to set up a system where I can control Phillips Hue spike lights (lily spot) with a Milight remote control.
I have set up a milight hub on an esp8266 d1 mini for which I have created a little custom motherboard which makes connections for the RFL2401 module and a dedicated 3v3 reg for the radio.
I have tried both 1.11.2 and 1.12.0 firmware but the firmware is not the problem in this case, everything is working fine. I have set up MQTT and can see messages coming through correctly when i set up a terminal and subscribe to the topic I have set up on a mosquitto broker.
I have set up diyHue version 1966117030 on a raspberry pi 5 and linked it to the Hue Essentials app along with the legit Phillips Hue Hub. Both sets of lights (Phillips Lily spot and a test RGBCCT strip with FUT0037 3-in-1 controller) work in the hue essentials app when i group them together, although I get very little control (only on/off works in the top right corner) in the diyhue interface.
My question is, are there particular topics i need to set up for the mqtt messages to be forwarded to the Hue bridge? I just cant seem to get this to work. I have verified my device ID for the remote I was testing (FUT089) which is 0x91FE
I have tried a few different topics in the Discovery prefix in diyhue such as
...and a few other variations.
What am I doing wrong here?
I would suspect I would only need to set up a "MQTT state topic pattern" so that only physical remote pressed are forwarded to the broker. But these messages must follow a particular format and (obviously) sending to the correct topic also.
Please can someone help me out? 👍
192.168.1.230/about
192.168.1.230/settings
The text was updated successfully, but these errors were encountered: