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
megashub
Question -- is there any way to manually re-add a device to Tim's Broadlink Control dockerized API service? I have it running on my NAS and all was working fine, but then I replaced my home network with better gear, and added a properly isolated IoT network with WAN only access, with my LAN devices able to see devices on the IoT network. Works great. My NAS is on my main LAN network, and the Broadlink RM4 mini is on the IoT network. I manually joined the RM4 mini to the IoT network, but now, the Broadlink Control service on the NAS can't discover the RM4... so /command json commands fail out with 'null' results.
TechnoTim
This is a tough one since you want these broadcasted packets to traverse vlans / networks. I think it might be possible with mDNS. I would look into that for your firewall.
megashub
yeah that's what I was afraid of... mDNS is a little brute force on Ubiquiti's Dream Machine Pro, I'm afraid. Could the container service be made to work strictly via static IP vs. requiring broadcast packet discovery? or are the commands sent to the RM4 via broadcast?
TechnoTim
possibly but I think you need to discover the device at least once to do some sort of handshake, I can't remember the details.
megashub
hmm that makes sense.. it creates a json file per discovered MAC... so I was hoping I could just edit the IP in the existing file and it would pick it up.. but that hasn't worked.
TechnoTim
I think I understand why, but I would have to rework some stuff to make it work. If you open an issue on github I can try to take look sometime! That would be super helpful, that way someone else could possibly provide a fix too
The text was updated successfully, but these errors were encountered:
megashub
Question -- is there any way to manually re-add a device to Tim's Broadlink Control dockerized API service? I have it running on my NAS and all was working fine, but then I replaced my home network with better gear, and added a properly isolated IoT network with WAN only access, with my LAN devices able to see devices on the IoT network. Works great. My NAS is on my main LAN network, and the Broadlink RM4 mini is on the IoT network. I manually joined the RM4 mini to the IoT network, but now, the Broadlink Control service on the NAS can't discover the RM4... so /command json commands fail out with 'null' results.
TechnoTim
This is a tough one since you want these broadcasted packets to traverse vlans / networks. I think it might be possible with mDNS. I would look into that for your firewall.
megashub
yeah that's what I was afraid of... mDNS is a little brute force on Ubiquiti's Dream Machine Pro, I'm afraid. Could the container service be made to work strictly via static IP vs. requiring broadcast packet discovery? or are the commands sent to the RM4 via broadcast?
TechnoTim
possibly but I think you need to discover the device at least once to do some sort of handshake, I can't remember the details.
megashub
hmm that makes sense.. it creates a json file per discovered MAC... so I was hoping I could just edit the IP in the existing file and it would pick it up.. but that hasn't worked.
TechnoTim
I think I understand why, but I would have to rework some stuff to make it work. If you open an issue on github I can try to take look sometime! That would be super helpful, that way someone else could possibly provide a fix too
The text was updated successfully, but these errors were encountered: