HS3 Pushover Plugin

[dlschwerin]

some help needed ...

not sure why I am not getting notification through pushover from my homeseer system with plugin for the omni pro 2. I have the omni pro 2 set up with the appropriate plugin (can see all my devices) and just installed the pushover plugin and configured (took longer to configure then expected). After trial and error was able to get things adjusted. Built the events through homeseer to include arming / disarming and nothing

I arm and disarm the panel and there is nothing displaying on the pushover plugin as a notification and not receiving any notifications through the Pushover app on my iphone. I created a manual triggered event through homeseer and can get that to work, but not the arming / disarming notification from the omni pro

thank you

[kolka10]

The file you're looking for is PushoverConf.ini, not HS3PushoverConf.ini. You should find it under /opt/HomeSeer/Config/

Hello .,
The problem is not what file "PushoverConf.ini" not exists, and YES it not exists after Plugin installation:
root@hs3:~# ls -all /opt/HomeSeer/Config
total 96
drwxrwxr-x 3 root sudo 4096 Dec 10 10:50 .
drwxrwxr-x 18 root sudo 4096 Dec 10 10:48 ..
-rw-r--r-- 1 root root 236 Dec 10 10:48 hspi_BLEmail.ini
-rw-r--r-- 1 root root 236 Dec 10 10:48 hspi_BLEmail.ini.bak
-rwxrwxr-x 1 root sudo 81 Dec 7 20:45 hspi_HSTouch.ini
-rwxrwxr-x 1 root sudo 81 Dec 7 20:45 hspi_HSTouch.ini.bak
-rwxrwxr-x 1 root sudo 5234 Dec 7 22:28 licenses.bin
-rwxrwxr-x 1 root sudo 18655 Apr 20 2018 locations.csv
-rwxrwxr-x 1 root sudo 57 Dec 10 10:48 mcsMQTT.ini
-rwxrwxr-x 1 root sudo 57 Dec 10 10:48 mcsMQTT.ini.bak
-rwxrwxr-x 1 root sudo 48 Dec 10 12:29 powerfail.ini
-rwxrwxr-x 1 root sudo 48 Dec 10 12:29 powerfail.ini.bak
drwxrwxr-x 2 root sudo 4096 Dec 6 20:28 Selectors
-rwxrwxr-x 1 root sudo 1139 Dec 10 10:48 settings.ini
-rwxrwxr-x 1 root sudo 1139 Dec 10 10:48 settings.ini.bak
-rw-r--r-- 1 root sudo 194 Dec 10 10:50 users.cfg
-rw-r--r-- 1 root root 194 Dec 10 10:50 users.cfg.temp
-rwxrwxr-x 1 root sudo 1588 Dec 10 10:48 Z-Wave.ini
-rwxrwxr-x 1 root sudo 1588 Dec 10 10:48 Z-Wave.ini.bak
root@hs3:~#


Although plugin installed ...
The problem with default version of mono running/coming with Ubuntu 18.04 - it too old.
This plugin AS MANY OTHER will not work until mono will be upgraded up to:


root@hs3:~# ps -ef | grep mono
root 23384 23383 0 10:48 pts/2 00:00:45 mono HSConsole.exe
root 23419 23384 0 10:48 pts/2 00:00:15 /usr/bin/mono /opt/HomeSeer/HSPI_MCSMQTT.exe
root 23421 23384 1 10:48 pts/2 00:01:09 /usr/bin/mono /opt/HomeSeer/HSPI_ZWave.exe
root 23423 23384 0 10:48 pts/2 00:00:14 /usr/bin/mono /opt/HomeSeer/HSPI_BLEmail.exe
root 23424 23384 0 10:48 pts/2 00:00:02 /usr/bin/mono /opt/HomeSeer/HSPI_TwilioMessaging.exe
root 23427 23384 0 10:48 pts/2 00:00:02 /usr/bin/mono /opt/HomeSeer/HSPI_Big5.exe
root 23429 23384 0 10:48 pts/2 00:00:06 /usr/bin/mono /opt/HomeSeer/HSPI_PUSHOVER.exe
root 25260 23106 0 12:31 pts/4 00:00:00 grep --color=auto mono

root@hs3:~# /usr/bin/mono -V
Mono JIT compiler version 6.4.0.198 (tarball Tue Sep 24 01:21:28 UTC 2019)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Misc: softdebug
Interpreter: yes
LLVM: yes(610)
Suspend: hybrid
GC: sgen (concurrent by default)
root@hs3:~#

[zwolfpack]

root@hs3:/opt/HomeSeer# find . -name HS3PushoverConf.ini
root@hs3:/opt/HomeSeer#
???

The file you're looking for is PushoverConf.ini, not HS3PushoverConf.ini. You should find it under /opt/HomeSeer/Config/

[kolka10]

Just wanted to chime in that I was trying to set up the plugin from scratch today and ran into the same issue adding my application. Editing the INI file manually worked.

Great plugin so far!!

And if I :

root@hs3:/opt/HomeSeer# find . -name HS3PushoverConf.ini
root@hs3:/opt/HomeSeer#
???

[kolka10]

Exactly the same error ..
HS3PRO with Pushover v. 0.0.0.47 , run on Ubuntu 18.04

[mrhappy]

It appears that I had an errant rule that flooded the pushover system. The homeseer plugin tells me I have 0 messages left. When I check the web site it says I used 7500 of 7500. However, what is not clear is whether this is for a week, month, forever? Does anyone know?

It should've activated the plugins own flood control which is unfortunate that it didn't happen (unless you sent lots of messages very slowly which may not have triggered it) else this may have not caused your issue - messages counters on Pushovers side are reset at midnight CST on the 1st of the month so it should of two days after your post.

[simonmason]

It appears that I had an errant rule that flooded the pushover system. The homeseer plugin tells me I have 0 messages left. When I check the web site it says I used 7500 of 7500. However, what is not clear is whether this is for a week, month, forever? Does anyone know?

[mrhappy]

I just noticed I was getting these error messages in the log; Unknown Exception in Pushmessage Object reference not set to an instance of an object.

Looks like the pushover.net site is down. Is this related or is this a configuration issue? It was working before.

It's a difficult one to figure out as I don't know which object caused this issue (I've seen this message before but not been able to recreate it), double check your API details and user key are correct in the ini file and then restart the plugin. If it still is a problem I'll have a think what else could cause it.

[mrhappy]

thanks for reply. I just needed to do some more digging and saw in my HS3 log the push messages were disabled.

Quick search found me at https://forums.homeseer.com/forum/ho...28#post1116728

I had an event go pushover notification whacko last weekend and see that this is a protection scheme built-in to disable the PI to avoid spamming. Good thinking. All set now.

Sorry for the late reply - that would explain it, you can increase the limits (details should be in the help file) if you need to but it is there to try and wake up and find your account empty.

There is no great way of making a user aware in HS of the fact this has activated (as you can't pop up a message and most people don't watch the log), I might consider at limit - 1 sending a Pushover message to the client that last had a message and warn them that there will be no future messages. The downside of that however is that people might not read the last of 100 messages for the content and could easily miss it also.

[will40]

thanks for reply. I just needed to do some more digging and saw in my HS3 log the push messages were disabled.

Quick search found me at https://forums.homeseer.com/forum/ho...28#post1116728

I had an event go pushover notification whacko last weekend and see that this is a protection scheme built-in to disable the PI to avoid spamming. Good thinking. All set now.

[jdee]

Mr Happy

I hope you can help me. It seems HS3 stopped pushing the pushover messages to my device clients. This may have stopped a few days ago. I made no changes to the PI or to my account. I test from the pusher website it works fine to my clients.

I test an event in HS3 and it logs the pushover message in the PI config as if it went out. Just not getting to my device(s).

Is there something I can do to reset this? Of course I just noticed it is not working now that I preparing to go away for the next few days

I just did a manual test on mine and works so whilst this doesn't help you, it confirm there's nothing wrong with the plugin or Pushover.

Mine stopped last week without warning or error, but it's only because I'm new to all this and found out my Android App expired its trial period. There was no error message but only saw the expired message when I went into the app. As soon as I bought the app from Play Store, started working again instantly. Can't say this is your issue since you mention testing via the Pushover website but you never... thought I'd mention it just in case.

[will40]

Mr Happy

I hope you can help me. It seems HS3 stopped pushing the pushover messages to my device clients. This may have stopped a few days ago. I made no changes to the PI or to my account. I test from the pusher website it works fine to my clients.

I test an event in HS3 and it logs the pushover message in the PI config as if it went out. Just not getting to my device(s).

Is there something I can do to reset this? Of course I just noticed it is not working now that I preparing to go away for the next few days

[simonmason]

I just noticed I was getting these error messages in the log; Unknown Exception in Pushmessage Object reference not set to an instance of an object.

Looks like the pushover.net site is down. Is this related or is this a configuration issue? It was working before.

[jdee]

It's a fair point to raise and one I had not really thought about since the plugin was made all those years ago as I probably had the naive belief that most people would have a connection that is relatively stable or have some sort of backup. At the minute all that will happen is that the message will not go and you will get an error in the log, it will not try to send it again.

I will see if I can put in a timer or queue if I get a web timeout exception and add the message to a list for periodic retrying.

Completely agree, internet is typically stable other than power outages, but in my case on the odd (very odd) occasion I have a glitch where things like weather or QNAP reports not being able to connect.

Only recently started with Homeseer and looking at its potential to be a mini intruder system, notifying me when sensors are triggered, and came across this plugin. My Homeseer is on a UPS but modem/router isn't (will add one down the track) hence was just a thought to ensure best possible receiving a notification.

[mrhappy]

I have a search but came up with nothing so apologise if this is somewhere in this 78 page thread..... wondering what happens if the internet is down, does this plug-in retry until it succeeds or is there a simple way to achieve this via Homeseer?

Great plugin and thank you!

It's a fair point to raise and one I had not really thought about since the plugin was made all those years ago as I probably had the naive belief that most people would have a connection that is relatively stable or have some sort of backup. At the minute all that will happen is that the message will not go and you will get an error in the log, it will not try to send it again.

I will see if I can put in a timer or queue if I get a web timeout exception and add the message to a list for periodic retrying.