March 5, 2019 at 5:48 pm #179553
OK, understood. Will probably have to wait for the weekend to have the time to mess around with all of it this way.March 10, 2019 at 6:26 pm #180512
I edited the network name for 2.4, added only the panel and the doorbell to the 2.4 network. pushed the button, attempted to answer the call on the panel and received the same error as before. No change in behavior.
The panel is back on the 5GHz network but since the 2.4 has been renamed, I can move it back any time.March 12, 2019 at 5:06 pm #180844
Interesting, and unexpected. I think unfortunately the best course now would be to re-add the Skybell on the 2.4 network (make sure the phone is on the 2.4 network). The error is likely an artifact of the registration process through ADC/Skybell.
Can you try deleting and re-adding? Any luck?March 12, 2019 at 9:41 pm #180880
I actually couldn’t figure out how to just reauthenticate the doorbell to the new WiFi SSID, so when I did this I removed the doorbell from the account and readded as a new one so that’s already been tried (by accident).March 13, 2019 at 11:20 am #180940
Could you describe the current network setup?
Oddly the Skybell is not able to report the ISP, showing an error when attempting to determine it. I think that there is a unique feature or setting to your setup which is the ultimate monkey wrench here but it does take a little trial and error.March 13, 2019 at 3:45 pm #180995
The basic network setup is a a router/access point in one box, cable modem, three separate wireless network SSIDs (2.4 & 5 that are on the same network segment, guest network on its own subnet), 24 port gigabit switch for various stuff that’s mostly on the same network segment as the 2.4/5GHz wireless.
I have maybe 10-12 wireless clients running at any one time, some of them streaming video and the rest just standard mobile devices or PCs. I run a big SAN for storage locally.
It’s pretty standard, no VPN that’s whole house for now, so anything not running a separate VPN client is all on the open network connecting to the internet.
Internet service is gigabit fiber so no bandwidth challenges ever.March 13, 2019 at 4:16 pm #181003
According to ADC it appears that Two Factor Authentication can interfere with communication between the panel and the SkyBell.
In order to appropriately test, you will want to remove the SkyBell and factory reset the unit. You will want to also disable Two Factor Authentication. Then you will want to re-add the SkyBell and try again. Any Change?March 13, 2019 at 5:01 pm #181013
Two-factor on the ADC website you mean?March 13, 2019 at 5:03 pm #181014
Yes. The ADC 2FA settings are found on the Alarm.com website under Settings – Login Information.March 13, 2019 at 5:05 pm #181015
Yeah, gotcha, just making sure that’s what you were talking about. I can disable that now but the doorbell reset etc. isn’t going to happen until the weekend again…March 14, 2019 at 12:48 pm #245983
So just removing 2FA did the trick, no reset needed. Video to the panel was working as of last night.
Question: Does the same restriction apply to say the V722 cameras or is it just due to the path the doorbell takes through Skybell’s servers before hitting ADC? If this applies to all IP cameras, that’s kind of crappy from a security standpoint especially coming from, you know, a security company.March 14, 2019 at 12:58 pm #245988
I dont believe so no, Alarm.com indicates this is a known issue with the SkyBell only. While they indicated that a fix was in the works, there is no ETA for that fix.March 14, 2019 at 1:00 pm #245989
Thanks Tyler. Guess I’ll make a decision about what’s more important to me.
You must be logged in to reply to this topic.