Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Daemon fails if it cant contact http://kz0q.com/daemon-releases #152

Open
2 tasks done
martinjones12345 opened this issue May 23, 2024 · 3 comments
Open
2 tasks done
Labels
bug Something isn't working

Comments

@martinjones12345
Copy link

martinjones12345 commented May 23, 2024

Checklist:

  • I updated to the latest version available
  • I checked that my MQTT broker is otherwise working

Release with the issue:

Last working release (if known):

Hardware, Operating System, Python version:

Description of problem:
When running the daemon the daemon fails to start due to being unable to contact http://kz0q.com/daemon-releases

Commenting out this code solves the issue
"#getDaemonReleases() # and load them!"

Can this be disabled in config and/or at the very least allow the get latest releases to gracefully fail and still allow the reporter to work

Run our report script 'genBugInfo' on your failing device and include the output here:


Python errors shown in the logs (if applicable):


Additional information:

@martinjones12345 martinjones12345 added the bug Something isn't working label May 23, 2024
@martinjones12345
Copy link
Author

Sorry just found this is already reported as an issue but for other reasons. I echo the need to allow this to gracefully fail or disable it in its entirety

@kali-777
Copy link

kali-777 commented Nov 8, 2024

FYR FIX here
Just change https:// in /opt/RPi-Reporter-MQTT2HA-Daemon/ISP-RPi-mqtt-daemon.py 😎

@martinjones12345
Copy link
Author

Thank you but my issue here is not about http or https. I have a system that is behind a firewall so I prefer to run this without having to put holes in the firewall for unnecessary connections so it would be better if this failed gracefully and continued rather than killing the entire thing in this instance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants