Originally posted by 123qweasd
View Post
Announcement
Collapse
No announcement yet.
HS3 Pushover Plugin
Collapse
X
-
-
Guest repliedOriginally posted by mrhappy View Post
This is an issue which has caused an issue with other plugins of mine - it appears that the device code is dropped when you go into the device details page and then the plugin will try and create the device again (because it can't find the device in HS because the data is not there), if you edit this device again the code will go and the sorry process will continue.
I have fixed that I think now with the version on this post, sadly you will have to start again with HS devices which may cause some people to be reluctant to do this but it is there if they wish to.
just disabled the PI and copied the exe over the old one (0.0.0.54 over 0.0.0.53).
Everything else seems to work though.
Leave a comment:
-
Hello and thank you for this great plug-in. I did not see release notes, I'm curious what to expect if I update from .48 to .52?
Thanks and stay safe.
Leave a comment:
-
Originally posted by voxie View PostStrange (little) problem. Plugin version 0.0.0.52. HS3 3.0.0.548. If I modify for example the Pushover icon or the Floor parameter on a Pushover device, disable and enable the plugin new duplicate devices are created. Looks like the plugin creates new devices if something is changed on the original devices.
I have fixed that I think now with the version on this post, sadly you will have to start again with HS devices which may cause some people to be reluctant to do this but it is there if they wish to.
Attached Files
Leave a comment:
-
Strange (little) problem. Plugin version 0.0.0.52. HS3 3.0.0.548. If I modify for example the Pushover icon or the Floor parameter on a Pushover device, disable and enable the plugin new duplicate devices are created. Looks like the plugin creates new devices if something is changed on the original devices.
Leave a comment:
-
Originally posted by stefxx View PostThanks mrHappy! Latest version works just fine.
However, you are using images from the "contemporary" folder. While it does exist on my HS4 production system, (upgraded from HS3) it does not exist on a fresh HS4 installation (my dev environment). All the references images exist in the "status" folder as well, and they are exactly the same.
The simple fix would be to use the ones from the "status" folder, that should work for HS3 and HS4. As I workaround, I copied the images to the contemporary folder for now.
I know, HS4 is not supported
- Likes 1
Leave a comment:
-
Thanks mrHappy! Latest version works just fine.
However, you are using images from the "contemporary" folder. While it does exist on my HS4 production system, (upgraded from HS3) it does not exist on a fresh HS4 installation (my dev environment). All the references images exist in the "status" folder as well, and they are exactly the same.
The simple fix would be to use the ones from the "status" folder, that should work for HS3 and HS4. As I workaround, I copied the images to the contemporary folder for now.
I know, HS4 is not supported
- Likes 1
Leave a comment:
-
Originally posted by akurz View PostHi there.
Looks like with the latest version 0.0.0.52 sending messages from a script in HS3 doesn't work anymore. There's no errors or anything - just no message sent. Same script with same parameters works fine with 0.0.0.48. I've downgraded and got everything working for now, so no pressure.
Here's the relevant part of the script:
Code:Dim CO(8) as Object CO(0) = "phone1|phone2" CO(1) = "Roomba hat eine Reinigungsaufgabe in " & Total_Time & " Minuten erledigt und ist nun zurück im Dock." CO(2) = "Roomba Reinigung beendet" CO(3) = Nothing CO(4) = "Gamelan" CO(5) = Nothing CO(6) = Nothing CO(7) = "iRobot" CO(8) = Nothing hs.PluginFunction("Pushover 3P", "", "Pushscript", CO)
AlexAttached Files
Leave a comment:
-
Hi there.
Looks like with the latest version 0.0.0.52 sending messages from a script in HS3 doesn't work anymore. There's no errors or anything - just no message sent. Same script with same parameters works fine with 0.0.0.48. I've downgraded and got everything working for now, so no pressure.
Here's the relevant part of the script:
Code:Dim CO(8) as Object CO(0) = "phone1|phone2" CO(1) = "Roomba hat eine Reinigungsaufgabe in " & Total_Time & " Minuten erledigt und ist nun zurück im Dock." CO(2) = "Roomba Reinigung beendet" CO(3) = Nothing CO(4) = "Gamelan" CO(5) = Nothing CO(6) = Nothing CO(7) = "iRobot" CO(8) = Nothing hs.PluginFunction("Pushover 3P", "", "Pushscript", CO)
Alex
Leave a comment:
-
Originally posted by Ltek View PostOne small feature request if you can... it would be extremely helpful if you were able to have a tab in the PI that lists all the PO notifications used in Events (and the event they are associated to). I find that with over 350 events and growing, I often duplicate notifications and/or forget where a notification 'lives'. In the Vera system, I could see all event notifications in a table and see what-is-where.Originally posted by mrhappy View PostThis would be useful for me just as much as anyone else...sadly this is a HS limitation (and any other solution involves a huge amount of work to move the event structures outside of the HS provided solutions). If you query the events via the scripting call then all you get is the list of events and when it comes to the actions it just says that they belong to a plugin with no further information, as such I can't get a list of them easily. I contemplated making a list when an event is called and then saving that event into a list but that will be out of date should the action be changed or the action be deleted so I'd rather not have something than have something that was inaccurate.
It's also very useful for finding broken events by using 'broken' as the search term, but that's a separate topic..
Steve
Leave a comment:
-
Originally posted by mrhappy View Post
I'm with you all the way but I am afraid that this would be great to do but just too much work for me at the minute. When the plugin was written then I was new to HS3 and in hindsight I would have gone with a different route to store messages in a queue and then depending on what came back then deal with them like in your case to strip things out that caused an error or in the case of no internet connection to do periodic retries and then send the messages when it came back online...I wanted to do something quickly but in this case it was probably me not thinking for such eventualities (and indeed many of the later additions to pushover that cause these errors were simply not in the pushover functionality).
Leave a comment:
-
Originally posted by mrhappy View Post
This would be useful for me just as much as anyone else...sadly this is a HS limitation (and any other solution involves a huge amount of work to move the event structures outside of the HS provided solutions). If you query the events via the scripting call then all you get is the list of events and when it comes to the actions it just says that they belong to a plugin with no further information, as such I can't get a list of them easily. I contemplated making a list when an event is called and then saving that event into a list but that will be out of date should the action be changed or the action be deleted so I'd rather not have something than have something that was inaccurate.
Leave a comment:
Leave a comment: