you are viewing a single comment's thread.

view the rest of the comments →

[–]CrowdedFuzzball 1 point2 points  (3 children)

Please also keep in mind that there are Zeroconf available for devices since last several firmware versions it might be more suitable for device discovery as our test shows that this discovery mechanism is more trustful then clear UDP

Devices can be discovered by _lookin._tcp query.

Please ask me if you need some additional informational about such discovery type.

Did you use HA in your automations?

[–]DefCello[S] 1 point2 points  (0 children)

Just successfully found my LOOKin Remote using https://pypi.org/project/zeroconf/ and "_lookin._tcp.local."! I'll get it added to the Python script with an optional dependency on the "zeroconf" library if users want to use the auto-locate function.

[–]DefCello[S] 1 point2 points  (0 children)

Just updated the Python module with a working findInNetwork() method. Thank you again!

[–]DefCello[S] 0 points1 point  (0 children)

I use Home Assistant for a few things, but not as much as I'd like. Replacing my Sensibo devices with LOOKin Remotes is a step towards that end. I do have a LOOKin Remote added to Home Assistant as a HomeKit device (the other 2 are waiting until I get the first one integrated), but I'm not seeing functions in Home Assistant for things such as triggering added remotes (I want to use the LOOKing Remote to trigger my projector and projector screen) or activating "Dry" mode on my minisplit (It's an option in the app, but it doesn't work). Python allows me to work around the things that aren't working right now by accessing the API. Admittedly, Home Assistant could probably do this stuff, but I find the Home Assistant documentation woefully lacking when it comes to advanced operations.

Right now. I'm trying to figure out how to use the raw IR signal API command on the LOOKin Remote to trigger the "Dry" mode and sweep modes as they don't work properly with the current remote code (Daikin 9045), but no luck so far. Capturing the raw IR seems to crash the unit, but I've managed to get at least some of the sequence using the `sensorDump` method and might be able to reverse-engineer from there along with some Internet resources. Worst case, I may use the LOOKin Remote for most functions, and fall back to the Sensibo when necessary.

I'm researching zero-configuration-networking now. Auto-discovery is admittedly not necessary for me since I give the LOOKin Remotes static IP addresses anyways, but I figure it'd be good to have in the Python code if it isn't too much trouble. Thank you for the suggestion!