search

Salamafet / ophom

Octoprint Philips Hue Outlet Manager
7 stars 1 forks source link

Octoprint web ui can't load if hue bridge is unreachable #14

Closed Salamafet closed 3 years ago

Salamafet commented 3 years ago

Add short timeout or modify the fetch process for not blocking

cstueckrath commented 3 years ago

same if the bridge-IP changes. A timeout wouldn't help here. Make the config reachable from the Octoprint interface so you can at least modify or retry a pairing. Any ETA on this?

Salamafet commented 3 years ago

I have not working on this issue since it was created.

I'm starting working on this right now.

cstueckrath commented 3 years ago

thank you very much! Uninstalling/reinstalling with 'pip uninstall ophom' doesn't clear the config, so I'm at a dead end right now. Could you tell me what file to edit to change the IP? I'm using octopi btw.

Salamafet commented 3 years ago

You can edit the config.yaml file of octoprint present in ~/.octoprint.

In plugin section you can find the ophom configuration:

ophom:
    auto_connect: true
    auto_off: true
    auto_off_bed_temp: '50'
    auto_off_nozzle_temp: '50'
    hue_ip: 192.168.10.102
    hue_token: ********************************
    light_id: '6'
    security_connection_lost: true

I'm actually working on a function for automatically find the bridge IP if the old one is unreachable.

cstueckrath commented 3 years ago

changed the ip to a dns name of the bridge (which is most likely Philips-hue for everyone). Now its running again. Thank you very much!

Salamafet commented 3 years ago

Good job !

changed the ip to a dns name of the bridge (which is most likely Philips-hue for everyone)

It's a good idea but I can't use this solution for Ophom in case there is various bridge or there is no DNS resolver (very uncommon).

Salamafet commented 3 years ago

Update done ! https://github.com/Salamafet/ophom/releases/tag/1.3.1