Mecheng70

How about this? https://github.com/greghesp/assistant-relay I was going to look into running this on the RPI4 that I am running polyglot on. Currently having issues following the directions to get the google side online. May be this weekend.

Is this a typo or is there an error

Evidently I have been running my network resources without the check box "Use SNI". Once that is checked, then the pushover notifications are going through.

Just curious... is your pushover working today? The last communication from the ISY on pushover was at 0800am this morning (25Oct). Then everything has stopped. Trying to figure it out and just wondering if it was something on my side.

Figured it out... I had weewx running for my weatherflow and did not have the flag set to True for sharing. /etc/weewx/weewx.conf Updated the line under the [WeatherFlowUDP] section to be share_socket = True Thanks.

I am having issues with getting my weatherflow hub talking with the ISY with the weatherflowpoly. I have tried adding the stationID from the app and it contiues to log the following: 2019-10-25 09:10:08,744 [Controller] [INFO ] Updating Driver hub - GV4: 1572019808, uom: 57 2019-10-25 09:11:08,742 [Controller] [DEBUG] heartbeat hb=1 2019-10-25 09:11:08,743 [Controller] [DEBUG] set_hub_timestamp: 1572019868 2019-10-25 09:11:08,744 [Controller] [INFO ] Updating Driver hub - GV4: 1572019868, uom: 57 Prior to this there is an error in the log file: 2019-10-25 09:03:09,062 [Thread-1 ] [ERROR] Exception in thread Thread-1: Traceback (most recent call last): File "/usr/lib/python3.7/threading.py", line 917, in _bootstrap_inner self.run() File "/usr/lib/python3.7/threading.py", line 865, in run self._target(*self._args, **self._kwargs) File "./weatherflow.py", line 362, in udp_data s.bind(('0.0.0.0', self.udp_port)) OSError: [Errno 98] Address already in use 2019-10-25 09:03:09,063 [Thread-1 ] [WARNING] /usr/lib/python3.7/threading.py:951: ResourceWarning: unclosed <socket.socket fd=7, family=AddressFamily.AF_INET, type=SocketKind.SOCK_DGRAM, proto=0, laddr=('0.0.0.0', 0)> 2019-10-25 09:04:08,741 [Controller] [DEBUG] heartbeat hb=0 Thoughts?

No idea. Leaving that to the professionals...

Have you seen this? https://cloud.google.com/text-to-speech/ Here is the pricing... https://cloud.google.com/text-to-speech/pricing

I installed two of these this weekend. The house is a 1930s home with two ceiling fans with a neutral wire. There is only one wall switch for both the light and fan. Located the device up in the hub of the fan. So far, so good.

Did you try this one? I purchased one and can not for the life of me sync it. I have tried to reset it, remove and add it and nothing.

One new ability that Alexa has is to speak/broadcast announcements based on events. Open the Alexa app, menu button and select routines. You can add a new routine based on a variable, switch or sensor. Alexa announces when the garage door opens or closes.... have fun.

Still having issues with Alexa and Google home. The last few days it is been delayed but today it just will not work. Voice commands, web access not agave work right now. The ISY was rebooted this morning.

I have both Alexa and Google home. Just tested the dimming by saying "turn dining room lights to 80%". Can confirm that Google Home doesn't see the light as setup. Can turn it on or off just not a %. Alexa works in both scenarios. One thing I just looked at is the way the portal (or I) set them up. In both cases they are set up as lights. I switched them to switches. After pushing the commands and waiting 5 minutes. I get the same results. Seems like it is a Google thing.... Sent from my Pixel XL using Tapatalk

Did try it once and had several errors. I was working on an autovoice, text file, REST to turn lights on and off. It just wasn't working for the secure https. Did work for the http but I didn't have the patience to trouble shoot. Maybe I need to give it another shot

My biggest challenge with using rest is the SSL certificate not working correctly on the Android phones. I always get the message where I have to click continue. Frustrating.