I had gotten tired of Alexa always responding "I can't find that device right now" after giving commands and having them work regardless. Figure I would try logging out of the skill and setting it up again. Now I can't get the skill to enable at all. Completely frustrating.
Make sure you re log backin with the skill on hubitat. That said set DHCP reservations for alexa and your echo's
I'm running pFsense and last night I played around with the settings, shutting down pfblocker and suricata just to make sure those weren't blocking any of the communication. I ended up shutting down ipv6 connectivity and clearing the states which worked. I turned on pfblocker and suricata a again and everything is still working fine, so it leads me to believe that ipv6 seems to be the issue since it's still disabled and no issues are present anymore.
So the dilema for me is where the ipv6 issue lies at. With ipv6 on, there's something blocking the response from Hubitat like Alexa responding the device isn't responding even though the commands worked.
1 Like
Well hubitat nor alexa use ipv6. What may be happening though is your pfsense make be prioritizing ipv6 traffic which may cause an issue passing packets. Honestly never been a fan of pfsense, I prefer Watchguard appliances. (Not to be confused with wireguard). Just something to look at.
I have the setting "Prefer IPv4 over IPv6" enabled so it should be prioritizing ipv4 traffic. Appreciate your feedback, I'll try the pfsense forums for some help on it, could be an issue with the latest version as I didn't have a problem beforehand.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
