You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been fighting with this issue for days now. As someone who owns the battery doorbell (which I assume a significant amount of people using this service fall into) not having the ability to trigger based on motion basically makes this service pointless. It is great that it exposes entities in MQTT for us to take advantage of, but without having the ability turn off the stream and wake it on motion events, the only outcomes are to either recharge the doorbell every day or nothing. From @QuantumEntangledAndy's very brief explanation, I understand that Google removed the api for push notifications, but I don't understand anything past that. Was this an API that was owned by you, or Neolink itself? Is this something that we could circumvent by spinning up an additional service to host the API? Are there any ways to intercept the notifications sent by Reolink to, for example, the mobile app? There are quite a lot of questions that have yet to be answered and are leaving us in the dark.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have been fighting with this issue for days now. As someone who owns the battery doorbell (which I assume a significant amount of people using this service fall into) not having the ability to trigger based on motion basically makes this service pointless. It is great that it exposes entities in MQTT for us to take advantage of, but without having the ability turn off the stream and wake it on motion events, the only outcomes are to either recharge the doorbell every day or nothing. From @QuantumEntangledAndy's very brief explanation, I understand that Google removed the api for push notifications, but I don't understand anything past that. Was this an API that was owned by you, or Neolink itself? Is this something that we could circumvent by spinning up an additional service to host the API? Are there any ways to intercept the notifications sent by Reolink to, for example, the mobile app? There are quite a lot of questions that have yet to be answered and are leaving us in the dark.
Beta Was this translation helpful? Give feedback.
All reactions