Announcement

Collapse
No announcement yet.

HS3 Pushover Plugin

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

  • mrhappy
    replied
    Originally posted by teladog01 View Post
    Yep, this one seems to be working fine. And my Pushover messages that were previously flagged as over the character limit are now sent and received with no problem. Thanks, Adam!
    Great thanks - I'll get it put in the updater as soon as I can.

    Leave a comment:


  • teladog01
    replied
    Yep, this one seems to be working fine. And my Pushover messages that were previously flagged as over the character limit are now sent and received with no problem. Thanks, Adam!

    Leave a comment:


  • rprade
    replied
    Originally posted by mrhappy View Post
    Strange..how about this version?
    This one loads without issue. V 0.0.0.43


    Leave a comment:


  • mrhappy
    replied
    Strange..how about this version?
    Attached Files

    Leave a comment:


  • rprade
    replied
    Problems here as well.

    Leave a comment:


  • teladog01
    replied
    Originally posted by mrhappy View Post
    can you see if the attached is any better?
    Looks like there might be something wrong with this one. I see a message in the log that says "Finished initializing plug-in Pushover 3P", but then on the plugin management page it says "INFO: Plugin start is pending" in the Plug-in Status column, and it never goes to "OK" like it should. Then in my events where I have Pushover actions, it says "The plug-in Pushover 3P is not running or is not connected to HomeSeer."

    UPDATE:

    Tried starting the plugin with "Developer mode" checked and here's what I see:

    Click image for larger version

Name:	Screenshot 2018-08-16 15.25.48.png
Views:	27
Size:	23.3 KB
ID:	1241632

    Last edited by teladog01; August 16th, 2018, 03:28 PM.

    Leave a comment:


  • mrhappy
    replied
    Originally posted by teladog01 View Post
    mrhappy, apologies if you are on vacation or otherwise busy...just making sure this didn't fall through the cracks...


    I'm afraid it completely slipped my mind - I did see your post and was going to say that it should be a simple enough fix. I never considered that the replacement variables would realistically be more characters than the string itself. I've swapped things around - can you see if the attached is any better?

    Leave a comment:


  • Monk
    replied
    Originally posted by rprade View Post
    Sorry, I missed this when you posted it. If the message is 66.56, you are using the value replacement variable $$DVR:Ref:. If you want it to be 66.56 F (I don’t know how to get the degree symbol on an ipad), you should use the Status replacement variable $$DSR:Ref:. Alternately you could just put an F after the value replacement variable in the Event. If you want to drop a decimal, edit the Status Graphics of the device to only show 1 digit decimal precision. This may or may not work, depending on how the plug-in treats the device.
    Thanks as always. (Plus bring back the Riley avatar! - wife misses him?!)

    Leave a comment:


  • teladog01
    replied
    mrhappy, apologies if you are on vacation or otherwise busy...just making sure this didn't fall through the cracks...


    Originally posted by teladog01 View Post
    mrhappy,

    One of my events that sends a Pushover message is generating the following message in the HS3 log:

    Code:
    Pushover 3P -> Message Length Greater Than 512 characters
    And the message is never received on my iPhone. I assume that the message isn't sent since the plugin thinks the message is over the character limit.

    The thing is that the message is using several $$DSA replacement variables, and these variables are actually quite long since I am using the Device Address replacement, which is putting the message past the 512 character limit. After replacement, the message is well under the character limit.

    Would it be feasible for you to change the plugin to perform the character limit check *after* the variable replacement?

    Leave a comment:


  • rprade
    replied
    Originally posted by Monk View Post

    Randy - any tip on dropping a decimal? What I mean to ask is the actual device content is temperature - looks like this
    Status 66.56 = Dim
    Value 66.56 = "66.6 F"

    The resulting Pushover msg shows "66.56"

    Thanks!
    Sorry, I missed this when you posted it. If the message is 66.56, you are using the value replacement variable $$DVR:Ref:. If you want it to be 66.56 F (I don’t know how to get the degree symbol on an ipad), you should use the Status replacement variable $$DSR:Ref:. Alternately you could just put an F after the value replacement variable in the Event. If you want to drop a decimal, edit the Status Graphics of the device to only show 1 digit decimal precision. This may or may not work, depending on how the plug-in treats the device.

    Leave a comment:


  • teladog01
    replied
    mrhappy,

    One of my events that sends a Pushover message is generating the following message in the HS3 log:

    Code:
    Pushover 3P    -> Message Length Greater Than 512 characters
    And the message is never received on my iPhone. I assume that the message isn't sent since the plugin thinks the message is over the character limit.

    The thing is that the message is using several $$DSA replacement variables, and these variables are actually quite long since I am using the Device Address replacement, which is putting the message past the 512 character limit. After replacement, the message is well under the character limit.

    Would it be feasible for you to change the plugin to perform the character limit check *after* the variable replacement?

    Leave a comment:


  • mrhappy
    replied
    Originally posted by Monk View Post
    Understood - I sort of like the button rather than automatically changing.

    In any case, this plugin is awesome. Check your PayPal!
    Very kind of you thanks

    Leave a comment:


  • Monk
    replied
    Originally posted by mrhappy View Post
    Glad it is working and not a problem, I do like to sort issues out when I can. I'll do some testing but just to give some background to this the reason for the update button being there is because of the number of controls on this event being (as far as I am aware) a little more than normal plugins that might only have one/two/three boxes or controls. If I set the controls to automatically post their data back to the plugin when you select them then it will collapse the event automatically and this will become extremely annoying (as you will have to expand it every time it collapses) I guarantee as you will be halfway through creating it before it has saved itself and needs you to open it again. I don't think there is a workaround for that but don't know how other people are doing it who have a similar number of controls on their plugin triggers/actions, I felt the easiest way was to put this button on and can't say I have ever seen it do the same but if I can re-create it I will look at it a little closer.
    Understood - I sort of like the button rather than automatically changing.

    In any case, this plugin is awesome. Check your PayPal!

    Leave a comment:


  • srodgers
    replied
    Originally posted by randman View Post
    I get this same problem too, maybe 10% of the time. I use Chrome on a Mac.


    Same here. OSX Safari and Chrome both. Happened when doing successive events involving PushOver.


    Sent from my iPhone using Tapatalk

    Leave a comment:


  • mrhappy
    replied
    Originally posted by Monk View Post
    So far this is very nice - Near instant notification as opposed to my current way which is sending an email to my phone carriers text service number.

    While modifying events today I notice that maybe every third time I hit the "Update" button for an event, I get a page full of raw code. I believe it is the entire event pages raw code. Here is a snippet.


    HTML Code:
    "EventActions_249","\u003cform id=\u0027EventActForm_249_A0\u0027 name=\u0027EAF_249\u0027 method=\u0027post\u0027\u003e\r\n\r\n\u003cscript\u003e\r\n$(function() {\r\n $( \u0027#DivEvActDrag_249_A0\u0027 ).draggable({revert:\u0027invalid\u0027,stack:\u0027div\u0027});\r\n $( \u0027#DivEvActDrag_249_A0\u0027 ).droppable({hoverClass:\u0027drag-hover\u0027,accept:\u0027.DivEvActDragClass\u0027,\r\n drop: function( event, ui ) {\r\n var dropID=$(this).attr(\u0027id\u0027);\r\n var dragID=ui.draggable[0].id;\r\n var theData=\u0027action=dragdrop\u0026\u0027+dropID+\u0027=dropped\u0026\u0027+dragID+\u0027=dragged\u0027;\r\n commonAjaxPost(theData,\u0027Events\u0027);\r\n }\r\n});\r\n});\r\n\u003c/script\u003e\r\n\u003cdiv id=\u0027DivEvActDrag_249_A0\u0027 class=\u0027DivEvActDragClass\u0027\u003e\r\n\u003ctable cellspacing=\u00270\u0027 width=\u0027100%\u0027 \u003e\r\n\u003cdiv id=\u0027DivAction_249_A0\u0027 \u003e\r\n\r\n\u003ctr \u003e\u003ctd class=\u0027event_Actions_0\u0027 align=\u0027left\u0027 colspan=\u002720\u0027 \u003e\r\n\u003ctr class=\u0027event_Actions_0\u0027 \u003e\r\n\u003ctd class=\u0027event_CondThen_Width\u0027 colspan=\u00271\u0027 style=\u0027 white-space: nowrap;\u0027 \u003e\r\n\r\n\u003c!-- jqDropList ActTHENNEVER_249_A0_ID598385--\u003e\r\n\u003cscript\u003e\r\n$(function() {\r\n $(\u0027#ActTHENNEVER_249_A0_ID598385\u0027).change( function() {\r\n var value = $(this).val();\r\n value = encodeURIComponent(value);\r\n var theID;\r\n var theform =$(\u0027#\u0027+$(this)[0].form.id);\r\n var theData =
    Here is a sample event
    [ATTACH]70129[/ATTACH]

    The size of the HS event page - before this happens - is approximately 3 and 1/4 page - where I am drilled down in my event view to where the Pushover events now reside. That's probably not a lot compared to others.

    I cannot compare this to anther events when I change them, as none have an "Update" button like this one does.

    In addition - I'm using the latest version of Chrome, and I'm thru a VPN at the time of occurrence.

    When setting up the first set of events (Locally, using Chrome on same Network) I did not have this occur. Maybe about 15 events worth with no issue.

    Anyway - I'm not complaining,mind you. Just letting you know. It's a great plugin! I'm available for testing if this is something bigger than just me.

    Thanks!
    Glad it is working and not a problem, I do like to sort issues out when I can. I'll do some testing but just to give some background to this the reason for the update button being there is because of the number of controls on this event being (as far as I am aware) a little more than normal plugins that might only have one/two/three boxes or controls. If I set the controls to automatically post their data back to the plugin when you select them then it will collapse the event automatically and this will become extremely annoying (as you will have to expand it every time it collapses) I guarantee as you will be halfway through creating it before it has saved itself and needs you to open it again. I don't think there is a workaround for that but don't know how other people are doing it who have a similar number of controls on their plugin triggers/actions, I felt the easiest way was to put this button on and can't say I have ever seen it do the same but if I can re-create it I will look at it a little closer.

    Leave a comment:

Working...
X