Jump to content

tmorse305

Members
  • Posts

    783
  • Joined

  • Last visited

Everything posted by tmorse305

  1. Keep an open mind, you just never know.
  2. Thanks, upgrading to the 5.4.0_3 solved the problem for me. All routines are working again including IFTTT. Thanks for your help and patience's as we all try to sort this problem out. It really looks like an Amazon problem but it has to be a mixture of both Amazon and ISY since the _3 version has fixed it for me. Now I just have to remember to disable/enable the skill each time I reboot ISY until they fix the throttling issue.
  3. Even after the upgrade it still shows 5.4.0. Can you see 5.4.0_3 in your AC?
  4. The thing is if I manually play the routine the IFTTT fires correctly
  5. I just tried your test and it still fails even after disable/enable skill.
  6. I just tried your method Delete the skill then reenable it (on phone) I didn't discover devices Tried the routine if failed. Deleted the routine re created it. Tried the routine it failed My routine involves IFTTT, do any of your routines use IFTTT?
  7. Is anyone else having trouble with routines that use a motion sensor/ISY variable? The variable is changing, and I can see the motion sensor is triggered in the Alexa app but the routine does not fire. If I manually trigger the routine it performs the trigger correctly. There was some discussion in another thread regarding the ISY upgrade to 5.4.0, @Michel Kohanim thought it was Alexa throttling but this is days later and mine still doesn't work. It looks like an Amazon problem but I'm curious if anyone else is seeing this?
  8. @JimboAutomates recently add support for Telegram which is also fast and reliable. The one advantage Telegram has over Pushover is that the messages show up in CarPlay. Pushover doesn't support CarPlay currently.
  9. There is also some configuration help built into the Node Server itself.
  10. @bpwwer, thanks for your reply. Its strange that it works for you (without the token?) Here is my configuration, does it look correct? I created a 2nd token, same result. This is a long shot but maybe related? The first time I set this up I incorrectly created a key "Station ID". When I restarted the blue message about needing the Station ID was gone so I thought I was all set. @jimboAutomates set me straight on that but could that be a left over somehow? I have deleted and re-added the NS twice so I would think that would clear everything but just thought I would throw that out there. Thanks again for your help.
  11. Thanks @bpwwer, I reinstalled Weatherflow on PG2 and it comes online with the same station ID (1866) so it seems to be something related to the PG3 version or perhaps the new token requirement. I double checked the token to make sure it is correct.
  12. Hi @bpwwer, My NS is throwing an error on startup. See the log attached. What do I need to do to fix it? Thank you WeatherFlow_2-20-2022_70419_PM.zip
  13. The tags come up initially disabled, did you enable them in the AC?
  14. Can you access ISY from the Admin console using admin/admin?
  15. Can you access ISY from the Admin console using admin/admin? This is what my configuration looks like, sounds like yours is the same. If your sure about admin/admin maybe try a reboot of the polisy box.
  16. @dbwarner5, This NS was developed by @bpwwer. @jimboAutomates just jumped in to try and help me.
  17. Try logging in as admin, pw is also admin
  18. Thanks @JimboAutomates, I removed the "Station ID" key and restarted the NS. Still not working but the error is different than previously, log attached, last restart at 19:03. @bpwwer, any advice? Thank you. WeatherFlow_2-20-2022_70419_PM.zip
  19. Hi @bpwwer, Sorry if you have watched the edits on this message. There were additional configuration instructions that came up on the NS after the station ID is entered which I didn't see initially. There still seems to be a problem, it's not happy with the Station ID. Do I have the configuration entered correctly? Thank you. Errors: 2022-02-20 16:04:23,984 Thread-1 udi_interface ERROR weatherflow:query_station: Station Query failed for Station ID: [Errno Expecting value] <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><title>GlassFish Server Open Source Edition 4.1.2 - Error report</title><style type="text/css"><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 500 - Internal Server Error</h1><hr/><p><b>type</b> Exception report</p><p><b>message</b>Internal Server Error</p><p><b>description</b>The server encountered an internal error that prevented it from fulfilling this request.</p><p><b>exception</b> <pre>javax.servlet.ServletException: java.lang.NullPointerException</pre></p><p><b>root cause</b> <pre>java.lang.NullPointerException</pre></p><p><b>note</b> <u>The full stack traces of the exception and its root causes are available in the GlassFish Server Open Source Edition 4.1.2 logs.</u></p><hr/><h3>GlassFish Server Open Source Edition 4.1.2 </h3></body></html> 2022-02-20 16:04:24,226 Thread-1 udi_interface ERROR weatherflow:query_station: Station Query failed for key: [Errno Expecting value] <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><title>GlassFish Server Open Source Edition 4.1.2 - Error report</title><style type="text/css"><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 500 - Internal Server Error</h1><hr/><p><b>type</b> Exception report</p><p><b>message</b>Internal Server Error</p><p><b>description</b>The server encountered an internal error that prevented it from fulfilling this request.</p><p><b>exception</b> <pre>javax.servlet.ServletException: java.lang.NullPointerException</pre></p><p><b>root cause</b> <pre>java.lang.NullPointerException</pre></p><p><b>note</b> <u>The full stack traces of the exception and its root causes are available in the GlassFish Server Open Source Edition 4.1.2 logs.</u></p><hr/><h3>GlassFish Server Open Source Edition 4.1.2 </h3></body></html>
  20. @JimboAutomates, thanks, there were 2 instances of Notification running. A reboot cleared that up. Thanks again for all of your support!
  21. @Jimbo, After I upgraded PG3 to 3.0.40 I'm getting an error in the log that says port 8199 is already in use. The NS is working partially, the messages are coming through but the custom sounds are not updating correctly. Restarting the NS does not solve it Thank you.
  22. @Jimbo, much better running 3.0.40! NS is up the Tag Manager appears in the AC but no tags yet. The readme refers to enabling 'Monitor Tags', where is that exactly? I've looked in the AC and the NS but I don't see it. Thank you EDIT: Disregard I found it
  23. @Jimbo, Oh, do you mean the one you highlighted and underlined???? Please tell me you just added that! BTW the "README" link takes you to the V2 README not V3. Thanks EDIT: Disregard I found it
  24. Hi @Jimbo, I just deleted the PG2 version and installed the PG3 version. I added the authorization code but it indicates that the NS is no running. Log file attached, there is an error being reported. It says KeyError is this in reference to the Auth code? I copied the one from the PG2 version. Thank you. WirelessTag_2-19-2022_74538_PM.txt
  25. You seem to be following the correct steps. Is your Java up to date? Have you tried to reboot your 994 to see if that helps? Just throwing out some other ideas.
×
×
  • Create New...