-
Notifications
You must be signed in to change notification settings - Fork 42
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
Make MQTT optional #32
Comments
Thanks for the feedback, will add it |
* Removed hard-dependency on MQTT, if MQTT integration was not set, binary sensors will not be created - Issue #32 * Username and password are now optional, if not set, will not create profile's switches * Added validation for host, port and SSL state in configuration, if URL is not accessible, will throw an error * Validate administrator username and password, in case entered wrong credentials, will throw an error * Fix issue #28 - entities not available after restart * Fix issue #27 - when changing switch it doesn't work smoothly and after restart * Resources (strings) fixed
@fotiDim, please let me know how it works for you |
@elad-bar thanks for the new release. My Hass.io: add-on 'Mosquitto broker' log below is configured and it's working though. Don't see any sensors from BlueIris even though i configured exactly as mentioned in readme. 1583123026: New connection from 10.0.0.75 on port 1883. |
Please go to the to the entities tab (Configuration -> Entities), if you will see those entities with error status, remove the integration and re-add it, it supposed to clean them |
@elad-bar Don't see any invalid Blue Iris related entries under Entities Tab ( Configuration -> Entities ). I did get all the motion, connectivity and cams entries and i have a Cycling Cam on lovelace and works good. I think my problem is - don't see any Blue Iris entities under ... Configuration --> Integrations --> MQTT Mosquito Broker ; this part should be Blue Iris responsibility to push the mqtt data which has watchdog and motion alerts entries right ? i followed the instructions as in readme. I can see the BlueIris client connected to Mqtt broker too in logs and there are motion alerts reported from my cams normally. Just don't see them in MQTT. thanks. |
@elad-bar I do actually see the motion sensors showing Detected from after update from last evening. So, guess i'm good :) Thanks for the great work. Still don't know why i dont see any mqtt data from blue iris though. |
@webwhiz, the components are not being created by MQTT integration, BlueIris integration creates them, that's the reason why you see them in BlueIris, that's by design. MQTT integration is mandatory in case you would like to get notifications from the BlueIris as Binary Sensors mostly because the component is relaying on the connection to avoid creating multiple connection and load the CPU |
can we close that issue? |
I do have a question here I see sensors in my BlueIris Integration related to connectivity and motion. I have never fully configured the mqtt thing as it was tedious to go through every camera and setup mqtt broadcast. Are those sensors (Connected and Motion) fake as in they never change because I didn't setup mqtt in BlueIris? |
If you didn't configure it, you will not get event for them and therefore will not be usable, Anyway, you don't need to go camera by camera to set it up, you can point to one camera to do all the configuration - in each of the camera go to:
|
Very cool component! Thanks for your work. 👏
As a suggestionI wanted to use the component without MQTT just not to have to reconfigure each camera individually in HA. Perhaps MQTT can be optional in that case.
As a side note, if the MQTT add-on is not installed then the configuration popup just never appears. If MQTT is mandatory it should fail more gracefully. Even after enabling it I had to restart HA for the configuration popup to work.
The text was updated successfully, but these errors were encountered: