Announcement

Collapse
No announcement yet.

Missing feature on device

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

  • will40
    replied
    That was it, messages are gone with v36. Thanks Dirk!

    Leave a comment:


  • dcorsus
    replied
    Originally posted by will40 View Post
    hmmmm....wonder if this HS4 update from today has anything to do with the minute by minute logging of the RING nag message while I am on the plugins.html page?

    Click image for larger version Name:	image.png Views:	0 Size:	105.9 KB ID:	1619035
    Indeed something that came in, in latest HS4 update. Just posted v36 that removes that log statement

    Leave a comment:


  • will40
    replied
    hmmmm....wonder if this HS4 update from today has anything to do with the minute by minute logging of the RING nag message while I am on the plugins.html page?

    Click image for larger version  Name:	image.png Views:	0 Size:	105.9 KB ID:	1619035

    Leave a comment:


  • will40
    replied
    Yes quite strange. Even weirder it seems it only happens when I am focused or leave a tab open on the HS plug-ins page /plugins.html...LOL...I browse away from it and the logging stops. It does explain why I see it often.

    COME ON that can't be!....right? I've seen some strange things but this one takes the cake

    Leave a comment:


  • windracer
    replied
    Originally posted by will40 View Post
    I see this log message very often even when I make a change to any of my plugins. In fact right now it is triggering every minute. Would you know why HS would need to poll the plug in so often?
    I'm not seeing it that often, weird.

    Leave a comment:


  • will40
    replied
    Originally posted by dcorsus View Post

    You should see that at start of the PI or whenever HS polls the PI for it status. It indicates that after Aug 31st, this PI will not start up anymore, hence my plan to deliver an official (for pay) version by then ​

    I see this log message very often even when I make a change to any of my plugins. In fact right now it is triggering every minute. Would you know why HS would need to poll the plug in so often?

    I understand the reason for the messages, and I have every intention on buying this plugin when you release it, but is there a way to reduce the reminder message so it only occurs when only the RING plugin is initialized?

    Thanks

    Click image for larger version

Name:	image.png
Views:	64
Size:	380.0 KB
ID:	1619029
    HS4 Pro Edition 4.2.18.18 (Windows)

    Leave a comment:


  • windracer
    replied
    Originally posted by dcorsus View Post
    windracer Found that the battery feature for cameras (as opposed to alarm devices) is only created when the device is created, so if it wasn't there when the camera was first created and later found (due to change from powered to battery), the PI wouldn't not add the feature.
    Bingo!

    Click image for larger version

Name:	image.png
Views:	60
Size:	92.5 KB
ID:	1618899

    I'll keep an eye on performance as well with the websockets fix, thanks!

    Originally posted by dcorsus View Post
    Everything was packaged up last Thursday ...


    Good to hear and hope everything goes smoothly for you. I get to work at home (ever since the pandemic) so I know what you mean about cloud-based services.

    Leave a comment:


  • dcorsus
    replied
    Originally posted by windracer View Post
    I know you're busy moving, so this is obviously not a big deal right now.
    Everything was packaged up last Thursday, we handed over the keys to the house on Friday and now camping out in an apartment until we jump on a flight with our dog. Boat arrives with our stuff late July. Plenty of time now, just no active setup. I know a lot of people hate cloud based services, but the irony is that I can do testing and development from anywhere in the world, despite the fact that the setup is down, the ring server reports all the devices ... as down

    Leave a comment:


  • dcorsus
    replied
    windracer I just posted v.35 which fixes the issue where multiple websockets were opened, which might explain the sluggishness. Also fixed an issue where the websocket feature state wasn't updated. Found that the battery feature for cameras (as opposed to alarm devices) is only created when the device is created, so if it wasn't there when the camera was first created and later found (due to change from powered to battery), the PI wouldn't not add the feature.

    Leave a comment:


  • windracer
    replied
    Yeah after the reboot performance went back to normal (and I haven't tried a device refresh again from the PI). I'll PM you the JSON capture.

    Leave a comment:


  • dcorsus
    replied
    Originally posted by windracer View Post
    Restarted the PI, saw this in the log (after everything initialized and started up):

    Code:
    Warning OpenWebSocket for Home couldn't be opened with Url = wss://ec2-18-207-227-17.prd.rings.solutions/ws?authcode=<redacted>&ack=false
    Battery feature isn't hidden or filtered, it's just not there.

    Click image for larger version

Name:	image.png
Views:	65
Size:	42.3 KB
ID:	1618842

    Something is really killing the CPU on the RasPi right now (the HS4 GUI is extremely sluggish) so I'm going to do a clean reboot and see what happens.
    I just realized that the fix I made this morning, which was a bug introduced to support multiple locations, I think the side effect is that many websockets are being opened and maybe that is the explanation of the sluggishness. I assume after you rebooted the system, things looked better?
    If you can PM me that capture log, then I can check why no battery feature is being created. One explanation I could think off, is that problem that when a feature is being deleted when the PI is not running, the PI is not smart enough to recover from that, only a delete of the device would fix that, and a delete of a device can be done when PI is running or not. However, if the capture log does not show a battery feature, than the problem is something else.

    I do need to check my old code again, that dealt with properly dealing with deleting a feature while the PI is running, maybe that code is not doing anymore what it was supposed to do, due to more recent changes.


    Leave a comment:


  • dcorsus
    replied
    Originally posted by windracer View Post
    Still nothing after the reboot. Checking the debug JSON capture, the camera looks like the other three except it's missing the "devicebatteryhsref" in the featurereflist.

    I know you're busy moving, so this is obviously not a big deal right now.
    Can you PM me that capture file?

    Leave a comment:


  • windracer
    replied
    Still nothing after the reboot. Checking the debug JSON capture, the camera looks like the other three except it's missing the "devicebatteryhsref" in the featurereflist.

    I know you're busy moving, so this is obviously not a big deal right now.

    Leave a comment:


  • windracer
    replied
    Restarted the PI, saw this in the log (after everything initialized and started up):

    Code:
    Warning OpenWebSocket for Home couldn't be opened with Url = wss://ec2-18-207-227-17.prd.rings.solutions/ws?authcode=<redacted>&ack=false
    Battery feature isn't hidden or filtered, it's just not there.

    Click image for larger version

Name:	image.png
Views:	65
Size:	42.3 KB
ID:	1618842

    Something is really killing the CPU on the RasPi right now (the HS4 GUI is extremely sluggish) so I'm going to do a clean reboot and see what happens.

    Leave a comment:


  • dcorsus
    replied
    Originally posted by dcorsus View Post

    Appears I can reproduce this when clicking refresh devices' info. Will look at it
    Ok, just fixed it, don't think this would be the reason the battery feature is missing. Make sure it isn't hidden or filtered out somehow. If all looks ok, do restart the PI, the refresh may actually have an issue, but I would think this has no bearing on the battery feature, a restart will make sure it all gets refreshed.
    I'll hold off with posting this fix till we figure this out.

    Leave a comment:

Working...
X