Announcement

Collapse
No announcement yet.

Base Station Cloud Status - changing every 4 hours?

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

  • dcorsus
    replied
    Originally posted by windracer View Post
    Ah, I see it now. Forgot there was a separate device.

    Click image for larger version Name:	image.png Views:	0 Size:	40.2 KB ID:	1617980

    So I can delete that old Alarm Cloud Status feature, right?​
    yes you can delete the Alarm Cloud Status feature and I think you may have manually changed the location to Z-Security so you would have to do that also for this new feature (totally optional)

    Leave a comment:


  • windracer
    replied
    Ah, I see it now. Forgot there was a separate device.

    Click image for larger version  Name:	image.png Views:	0 Size:	40.2 KB ID:	1617980

    So I can delete that old Alarm Cloud Status feature, right?​

    Leave a comment:


  • dcorsus
    replied
    Originally posted by windracer View Post
    So in my case the master device is the alarm base station right? I don't see anything that looks new:

    Click image for larger version Name:	image.png Views:	0 Size:	32.6 KB ID:	1617866

    No more events overnight, so that issue is fixed. Although now I need to actually test having the base station go offline, onto cellular, etc.
    Nope, there is a device called "Master" for location "Ring", that sort of holds features that are common to the PI function , including its network connectivity etc.

    Leave a comment:


  • windracer
    replied
    So in my case the master device is the alarm base station right? I don't see anything that looks new:

    Click image for larger version  Name:	image.png Views:	0 Size:	32.6 KB ID:	1617866

    No more events overnight, so that issue is fixed. Although now I need to actually test having the base station go offline, onto cellular, etc.

    Leave a comment:


  • dcorsus
    replied
    Originally posted by windracer View Post
    Should I see something different for this? I only have one location so not sure if I should see this new status ... don't see anything that looks new to me.
    The master device should have a new feature

    Leave a comment:


  • windracer
    replied
    After updating to .34, and with no changes to my event, the "every 4 hour" notifications seem to have stopped, thanks!

    Originally posted by dcorsus View Post
    now there will be a status feature under the master device for each location that has an active websocket.
    Should I see something different for this? I only have one location so not sure if I should see this new status ... don't see anything that looks new to me.

    Leave a comment:


  • windracer
    replied
    Originally posted by dcorsus View Post
    and yes they still seem to run PPPoLTE.
    Oh right, ppp0 would be the cellular.

    Originally posted by dcorsus View Post
    Just posted v34 which reverts some of the change I made, and now there will be a status feature under the master device for each location that has an active websocket.
    Thanks! Certainly did not expect a fix so quickly with the moving situation, so I appreciate that. I've upgraded to .34 and will see what happens.

    Leave a comment:


  • dcorsus
    replied
    Just posted v34 which reverts some of the change I made, and now there will be a status feature under the master device for each location that has an active websocket.
    The cloud status for alarm hubs now will reflect back the connectivity status.

    Leave a comment:


  • dcorsus
    replied
    Originally posted by windracer View Post
    That sounds to me like how the base station is connected: wireless, wired, or ?? (is point-to-point protocol even applicable here? weird).
    I already fixed the code to go back to what it was. As to the how it is connected, I was assuming that if you loose say ethernet or wlan connectivity, it would go to cellular (ppp) and yes they still seem to run PPPoLTE. ..... but.... you might be right, that might also not do what you were looking for.

    Sit tight, see if I can figure something out for these multiple locations and I'll release an update soon.

    Leave a comment:


  • windracer
    replied
    Originally posted by dcorsus View Post
    The Hub has a "NetworkConnection" attribute that is set to wlan0, eth0, ppp0
    Maybe that can be of use?
    That sounds to me like how the base station is connected: wireless, wired, or ?? (is point-to-point protocol even applicable here? weird).

    Leave a comment:


  • windracer
    replied
    Originally posted by dcorsus View Post
    Perhaps what you can do is to change your trigger to "when device is in state xxxx for 1 minute". This will filter out the 4 hour disconnect and the sporadic disconnections you may have due to a brief network issue.
    Good idea, I'll start with that.

    Thanks for the detailed explanation, and good luck with that move ... wow!

    Leave a comment:


  • dcorsus
    replied
    Sorry for all the posts, but I think I made a mistake, where I lumped the connection status of the alarm hub (online offline, cell-backup) together with the state of the websocket. Going to have to fix that, sorry

    Leave a comment:


  • dcorsus
    replied
    The Hub has a "NetworkConnection" attribute that is set to wlan0, eth0, ppp0
    Maybe that can be of use?

    Leave a comment:


  • dcorsus
    replied
    On a different note, it is not because the PI loses connectivity with the Ring servers that your alarm hub hasn't lost its connectivity with its ring server. This is an alarm between the HS PC (PI) and the Ring Server. You probably want to monitor the wifi state which I noticed I don't have for the hub itself.

    As I write this, a crew of movers, pretty much packed up the whole house and I'll be without my setup for the next 6~8 weeks or so, as we are moving internationally.
    Maybe I can start writing the functions, but testing it will not be for weeks unless you want to be a guinea pig to test.

    Leave a comment:


  • dcorsus
    replied
    The ring servers disconnect every 4 hours, so that's what you see. The PI automatically tries to re-connect and it has a bit of a gradual back-off function if it doesn't succeed to reconnect immediately. That function was always there but I'm suspect that updating the state of that feature wasn't done right.

    The latest version adds support for multiple locations, and depending on what kind of devices you have in those different locations, you can have more than one websocket connection active. This connection is typically associated with "an asset" and in your case it would be your base station (note if you have more assets in the same location, you still only have a single websocket connection). While introducing this new support, I fixed the alarming.

    Perhaps what you can do is to change your trigger to "when device is in state xxxx for 1 minute". This will filter out the 4 hour disconnect and the sporadic disconnections you may have due to a brief network issue.

    Thoughts?

    ps the "alarm cloud feature" (don't have right syntax in front of me) on the MASTER device is deprecated, as stated you can have multiple webconnections so representing it with one feature on the master devices was wrong and I believe this was the feature that would be updated each time you lost connectivity.

    Leave a comment:

Working...
X