Pushing Images with Pushover 3.0

Feature Requests
81

I just installed v.91 - for some reason this custom component is no longer overriding the default pushover component. I’ve been running the custom component for almost a year without issue - I had to change the folder structure several releases ago to custom_components/pushover/notify.py and all was working great until now.

Anyone else having this issue? Is there a way to force HA to pickup the custom pushover component?

EDIT

Was able to get this working again in v.91 - not sure if this issue popped up for anyone else in .91 but here’s what I did to fix it:

1.) Modified the custom component directory name /custom_components/pushover/ to /custom_components/pushover_file

2.) added Domain = ‘pushover_file’ after the _Logger line in the notify.py file

3.) Modified my configuration.yaml to reference platform: pushover_file vs platform: pushover

2 Likes
82

I was able to get it working following your instructions, but did not have to do step 2. Basically just renamed folder and updated config.yaml

83

I’m unsure how to follow these instructions… with this pushover_file mention and "notify.py (which one is that?)
This is my actual setup:
in “/custom_components/notify”, I have this:
“pushover.py”
And since latest update, it’s not working (since it uses the same name as built in one I presume)
I think I need to create the structure /custom_components/pushover/notify.py but so not sure how to do this and what to modify… (plus I think I need to rename to something else but unsure where to fix everywhere it could refer to it)…

84

But I did not have to do step 2. Bottom line, the folder name can no longer be the same name as a existing component.

85

in this procedure, what is “pushover_file” a folder or the pushover "notify.py file?

edit: ok, I got it…
/custom_components/pushover_custom/notify.py
Edit the platform in notify.yaml to “pushover_custom” instead of “pushover” (based on my choice of folder name)

1 Like
86

You can also create a group of devices in pushover with its own key and use that to notify multiple users/devices as one operation.

1 Like
87

didn’t know that, thanks!

88

Amazing that pushover is 2.0 in hass…why not just get this stuff in the default?

89

It would be very nice to have this feature (and the new animated gifs) into the default pushover component of HASS!

1 Like
90

Local as well.

91

I tried this for the first time today. For a new user it took some time of trial and error with all variants above.

This is how I made it work:

  1. Download pushover.py
  2. Save it as /custom_components/pushover_file/notify.py
  3. Add line: Domain = 'pushover_file' after the _Logger line in notify.py
  4. Add
    whitelist_external_dirs
    - /tmp to configuration.yaml
  5. Reboot
  6. Automation:
  - service: camera.snapshot
    data:
      entity_id: camera.cam01
      filename: '/tmp/snapshot_camera01.jpg'

and

- service: notify.pushover_file
    data_template:
      message: 'Alert - {{now().strftime("%Y-%m-%d %H:%M")}}'
    data:
      title: Alarm
      data:
        file:
          path: /tmp/snapshot_camera01.jpg
        priority: 1
  1. Profit.

Thanks to everyone that contributed in the thread!

4 Likes
93

Hi guys,
has anyone updated to 0.92 and can they confirm everything with the component is working?

94

Not for me. I’ve updated from 0.87 to 0.92, and this is the only thing that doesn’t seem to be working.
I’ve tried various different things from this thread. I’m getting this error:

attachment: invalid message parameter

And I’m seeing this in the startup. Not sure if it’s the issue:

[homeassistant.util.package] Attempting install of python-pushover==0.3

95

Works for me still…

96

Can you share your custom component and config please?

97

It the one from here with folder structure mentioned there:

98

Yeah, that’s what I used. I missed a step though, the manifest.json still had “python-pushover==0.3” in for the requirements :frowning:
Updated to 0.4 and it’s sorted now :smiley:

1 Like
101

I’m on 0.92 and I’m also getting the attachment: invalid message parameter
And the error is coming from the custom_component.

102

@orson1282 Have you updated the manifest.json to have python-pushover 0.4 in the requirement? When I copied the original over from the HA install it was forcing 0.3 to be installed. Changing that fixed it for me. What version of python-pushover do you have?

1 Like
103

Is anyone running .92.1 ? I finally got around to trying to fix this after it broke with .91 a few days ago and I’m getting the following errors in my logs whenever an automation runs that calls the pushover custom component:

2019-04-27 07:35:37 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was     never retrieved
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/helpers/script.py", line 131, in async_run
    await self._handle_action(action, variables, context)
  File "/usr/src/app/homeassistant/helpers/script.py", line 210, in _handle_action
    action, variables, context)
  File "/usr/src/app/homeassistant/helpers/script.py", line 299, in _async_call_service
    context=context
  File "/usr/src/app/homeassistant/helpers/service.py", line 89, in async_call_from_config
    domain, service_name, service_data, blocking=blocking, context=context)
  File "/usr/src/app/homeassistant/core.py", line 1115, in async_call
    raise ServiceNotFound(domain, service) from None
homeassistant.exceptions.ServiceNotFound: (ServiceNotFound(...), 'Service notify.pushover_file not found')

OK Fixed this - needed to create a manifest.json file in the pushover custom component directory:

{
  "domain": "pushover_file",
  "name": "pushover_file",
  "documentation": "https://home-assistant.io/components/notify.pushover/",
  "dependencies": [],
  "codeowners": [],
  "requirements": ["python-pushover==0.4"]
}
3 Likes