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.

Sign up for GitHub

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

Jump to bottom

Not seeing location mode entity after turning on enable_mode #689

Closed
lambros414 opened this issue Jul 27, 2023 · 9 comments
Closed

Not seeing location mode entity after turning on enable_mode #689

lambros414 opened this issue Jul 27, 2023 · 9 comments
Labels
bug Some code behavior is not as expected

Comments

@lambros414
Copy link

Describe the Bug

After installing ring-matt and turning on enable_mode in its configuration, not seeing any entities regarding location or home mode with any cameras

Steps to Reproduce

I have installed ring-mqtt, and other entities are working. when I turn on enable_mode in the configuration tool, I am not seeing a location entity for any of my cameras

Expected Behavior

I would expect that you would see an entity for each camera called location mode that would allow you to pick a mode such as Home, Away, Off, etc, similar to the event_select or snapshot mode.

Log Output

When I try to include the output of ring-mqtt.log in this window, I get an error message the the comment is too long.  I have the compressed file (as in gz) but can't find a way to include in this box.  I could not find a way to upload the gz file.  Please let me know how to do so, and I will supply

Screenshots

I had turned on the enable modes option when configuring the add-on:

Screenshot 2023-07-27 at 12 41 20 PM

When going to mqtt entities and look at any of my ring cameras, the location mode isn't present:
Screenshot 2023-07-27 at 12 41 58 PM

Config File

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:


http:

# two lines below are used when using duckdns
# ssl_certificate:  /ssl/fullchain.pem
#  ssl_key: /ssl/privkey.pem
  
homeassistant:
  name: Home
  latitude: xxxxx
  longitude: xxxxx
  elevation: xxx
\
  internal_url: http://xxx

#overwrite home zone - gives ability to change radius of home zone
zone:
  - name: Home
    latitude: xxx
    longitude: xxx
    radius: 100
    icon: mdi:home

api:
alexa:
  smart_home:

ssdp:

          
python_script:

# Alarm control panel entry
alarm_control_panel:
  - platform: manual
    name: Home Alarm
    code: 'xxxx'
    code_arm_required: true
    arming_time: 30 # The time of the 'arming' state before effecting a state change
    delay_time: 30 # The time of the 'pending' state before triggering the alarm
    trigger_time: 120 # The time of the 'trigger' state in which the alarm is firing
    disarm_after_trigger: false
    disarmed:
      trigger_time: 0
    armed_home:
      arming_time: 0
      delay_time: 0

image_upload:
  
# Text to speech
tts:
  - platform: google_translate
  - platform: amazon_polly
    aws_access_key_id: xxx
    aws_secret_access_key: xxx

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

frontend:
  themes: !include_dir_merge_named themes

Install Type

Home Asssistant Add-on

Version

v5.5.1

Operating System

Home Assistant OS

Architecture

rpi-4-64

Machine Details

Raspberry PI
@lambros414 lambros414 added the bug Some code behavior is not as expected label Jul 27, 2023
@tsightler
Copy link
Owner

When going to mqtt entities and look at any of my ring cameras, the location mode isn't present:

As stated in the discussion thread, this is not where modes would appear. There will be a new device that appears as an alarm control panel where you can view and set modes.

You can either attach logs here, or you can send them to my email, same username as here at Gmail.

@lambros414
Copy link
Author

I have fount that alarm panel entity now, and when I switch it, it changes the mode in ring for me... so it works. The entity was created with a fairly odd name, and had missed it. I originally opened this up in the discussion group to see if I had done something wrong. I had searched other discussion groups, and had missed the comment about it showing up as a control panel entity. I apologize for any time spend on this, and thanks for your help

@tsightler
Copy link
Owner

Out of curiosity, can you describe what you mean by "fairly odd name"? I would expect it to be "<location_name> Mode", where <location_name> is the name of the location as configured in the Ring app.

@lambros414
Copy link
Author

lambros414 commented Jul 27, 2023 via email

@tsightler
Copy link
Owner

The switch is primarily intended as an indicator as to whether a stream is active or not. It will automatically turn on whenever any client is viewing the stream via the local RTSP server and turn off when there are no active clients.

However, there is one use case for toggling the switch manually. Since any time a user views a stream on a Ring camera it automatically creates a recording, you can use this switch to trigger a recording from an automation. For example, maybe you have a non-Ring camera or motion sensor that you want to use to trigger a recording, you can use an automation to toggle the stream on, leave it on for however many seconds, and then turn it off, and you will get a recording of that event on the Ring servers that you can download (assuming a paid Ring subscription).

Basically, if you manually toggle the stream "on" but there are no active consumers of the stream, it will manually start a local ffmpeg process to act as a client and keep the stream alive until the switch is manually toggled off or ffmpeg exits due to timeout, etc.

It can also be really useful for troubleshooting since, if a user is having a problem streaming to an external client, I can just have them toggle this switch and it will start that local ffmpeg client which still triggers the same streaming process on the backend, but doesn't require any ports or anything else to be properly configured.

The two most common issues for streaming not working are firewalls blocking dynamic UDP ports, an, probably more commonly, poor connections causing startup times to be too high. The Ring clients use WebRTC which is pretty tolerant of startup delays, but RTSP requires a stream to start within 5 seconds or it will timeout and disconnect and a lot of people with battery cameras on 2.4Ghz Wifi that isn't super strong really struggle to meet that requirement.

But streaming has become pretty relaible at this point, most issues seem to be environmental as, over the last year, ever user that had a problem and was willing to share their camera with me did work for my case, but not on their network. Various issues from replacing a network switch, to changing DNS or firewall settings eventually resolved the issue, not code changes.

@lambros414
Copy link
Author

lambros414 commented Jul 29, 2023 via email

@tsightler
Copy link
Owner

The problem with creating detailed instructions is that details have a tendency to change over time. HA constantly changes UI elements here and there so the steps have probably changed slightly. I'll you need to do is open the Info sensor and expand the attributes, they should be right there.

The RTSP URL will not point to the HA instance web UI. RTSP is it's own protocol and will point to the RTSP running in the addon/container. When using the addon it will be something like:

rtsp://03cabcc9-ring-mqtt:8554/<camera_id>_live

The still image URL, which is also important, will point to the HA web UI,.

@lambros414
Copy link
Author

lambros414 commented Jul 29, 2023 via email

@lambros414
Copy link
Author

lambros414 commented Jul 29, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Some code behavior is not as expected
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tsightler @lambros414