Announcement

Collapse
No announcement yet.

HS3 Pushover Plugin

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • noopara
    replied
    Why Pushover?

    I try and keep my HS3 implementation simple with the minimum of moving parts. I've never used Pushover or anything like it. I understand that it doesn't use email or text messages. Why would someone use it instead of text messages with HS3?

    I have been using text messages from my HS3 system for years because it requires little bandwidth and will work in a lot of places where there is no data connection. I have often found that text messages will come through even in areas where you can't make a phone call.

    Leave a comment:


  • mrhappy
    replied
    Originally posted by 3IMOH View Post
    Thanks for the lightning fast response! I have updated the plugin and the link works great now as a message URL.
    Not entirely sure where and when I implemented it to start with so I'll just release the version with the latest amendment, if it does not work for anyone with this change let me know and I'll go back to putting some thought into it.

    Leave a comment:


  • 3IMOH
    replied
    Thanks for the lightning fast response! I have updated the plugin and the link works great now as a message URL.

    Leave a comment:


  • mrhappy
    replied
    Originally posted by 3IMOH View Post
    I am trying to use the message URL functionality in the plugin to send HS /json control URL's. It seems that pushover URL encodes the URL which HS does not seem to like. I can just put a link in the message body and that seems to work ok but it would be nice to be able to have a link with a title. Has anyone run into this or have a workaround?

    URL in message body works fine:
    http://homeseer:8000/JSON?request=runevent&id=5

    HS result:
    { "Response":"ok" }

    trying to use this as a "Message URL", it gets converted to:

    http://homeseer:8000/JSON?request%3drunevent%26id%3d5

    which results in:
    { "Response":"Error, bad request" }
    I'm my own worst enemy at times and this is something that has bitten me, clearly at some point I have decided to encode these URL strings anyway so it is not Pushover that are encoding them it is me. I can only imagine that was on user request as I don't use them myself but as I'm lousy at commenting the code I don't know where and why I've done it!!

    I've changed the encoding from HttpUtility.UrlEncode to HttpUtility.UrlPathEncode which seems to at least solve it for HS URL's. I'll have to do a bit more investigation as to why I did it and whether it breaks anything else but you are welcome to download the version here and try it yourself - http://s652164905.websitehome.co.uk/...r_0_0_0_34.zip

    Be aware that I have no control over the handling of these URL's inside Pushover as for me the web browser loads up which obviously gets filled with the JSON reply which looks a little ugly.

    Leave a comment:


  • 3IMOH
    replied
    Using Message URL for HS JSON requests

    I am trying to use the message URL functionality in the plugin to send HS /json control URL's. It seems that pushover URL encodes the URL which HS does not seem to like. I can just put a link in the message body and that seems to work ok but it would be nice to be able to have a link with a title. Has anyone run into this or have a workaround?

    URL in message body works fine:
    http://homeseer:8000/JSON?request=runevent&id=5

    HS result:
    { "Response":"ok" }

    trying to use this as a "Message URL", it gets converted to:

    http://homeseer:8000/JSON?request%3drunevent%26id%3d5

    which results in:
    { "Response":"Error, bad request" }
    Last edited by 3IMOH; July 3, 2017, 05:01 PM. Reason: adding title

    Leave a comment:

Working...
X