Closed rezzalex closed 5 years ago
Pushed a fix to make your error go away (1.9.8) but it won't fix the actual problem.
The "Voice Device/Group:" parameter you set in the Hardware tab needs to be the device name you gave your chromecast during setup, not the device name in Domoticz. This is known as the 'friendly name' by google.
To see it, search in the log for "Discovery message seen from", you have debug set to 'Tout' so any discovered device will be logged including the friendly name.
Thanks for your quick answer,
after modyfing the correct "Voice Device/Group", here is my logs after switching my device on with an associated voice notification.
Thanks
On Wed, 13 Mar 2019 at 11:24, dnpwwo notifications@github.com wrote:
Pushed a fix to make your error go away (1.9.8) but it won't fix the actual problem.
The "Voice Device/Group:" parameter you set in the Hardware tab needs to be the device name you gave your chromecast during setup, not the device name in Domoticz. This is known as the 'friendly name' by google.
To see it, search in the log for "Discovery message seen from", you have debug set to 'Tout' so any discovered device will be logged including the friendly name.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dnpwwo/Domoticz-Google-Plugin/issues/4#issuecomment-472364207, or mute the thread https://github.com/notifications/unsubscribe-auth/Ahgjt91kvKG62uV_nc5l9Jh0OWFyUm0Bks5vWNHRgaJpZM4bssKy .
@rezzalex ,
Didi Messages/Message.mp3 get created under you plugin directory?
Hello.
No "message" directory and no mp3 file... What do you suggest ?
Regards
Le dim. 17 mars 2019 à 10:54, dnpwwo notifications@github.com a écrit :
@rezzalex https://github.com/rezzalex ,
Didi Messages/Message.mp3 get created under you plugin directory?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dnpwwo/Domoticz-Google-Plugin/issues/4#issuecomment-473650250, or mute the thread https://github.com/notifications/unsubscribe-auth/Ahgjt7PUAxD-ja2YRcczMnBKevptL63Uks5vXhDmgaJpZM4bssKy .
I am experiencing the same and no message.mp3 file
Okay, if there is no message file then the Google device can't 'speak' it.
2 things to check/try:
Good morning, I have created the dir "Messages": the notification added to switch/device works, but I have no idea how to get it working from a script. the line: commandArray['Office speaker'] = "SendNotification 'Hello'" doesn't do anything (not even the Chromecast Beep) I have 5 Mini's and would like to activate them individually via scripting because the messages are always different.
I also noticed that when something is casting to a Mini (LMS in my case) and a notification from a switch is activated the actual casting is suppressed then a double beep... and nothing no message and no returning of LMS
Hello. After creating the " message" folder, my logs indicate: Error: (GoogleCast) handleMessage: 'NoneType' object has no attribute 'volume_level'
When trying to activate the switch that send the notification.
Regards
Le lun. 18 mars 2019 à 08:57, DutchHans notifications@github.com a écrit :
Good morning, I have created the dir "Messages": the notification added to switch/device works, but I have no idea how to get it working from a script. the line: commandArray['Office speaker'] = "SendNotification 'Hello'" doesn't do anything (not even the Chromecast Beep) I have 5 Mini's and would like to activate them individually via scripting because the messages are always different.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dnpwwo/Domoticz-Google-Plugin/issues/4#issuecomment-473805916, or mute the thread https://github.com/notifications/unsubscribe-auth/Ahgjt71RRacP9mMtCDBETwlhqf4KsvNUks5vX0bogaJpZM4bssKy .
Sounds like I need to add the Messages directory into this repo to ensure it is present.
@rezzalex, what type of device are you trying to notify? I don't get this for a Home Mini which has been my test device so far.
@DutchHans, can you turn the plugin's debugging on and post the output?
Hello.
I am using a Google home mini. The MP3 file is correctly created and tested sucessfully outside this plugin.
Le mar. 19 mars 2019 à 04:42, dnpwwo notifications@github.com a écrit :
Sounds like I need to add the Messages directory into this repo to ensure it is present.
@rezzalex https://github.com/rezzalex, what type of device are you trying to notify? I don't get this for a Home Mini which has been my test device so far.
@DutchHans https://github.com/DutchHans, can you turn the plugin's debugging on and post the output?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dnpwwo/Domoticz-Google-Plugin/issues/4#issuecomment-474186915, or mute the thread https://github.com/notifications/unsubscribe-auth/Ahgjt5_9_YbYHWESrSLGQTtu71UMThyRks5vYFytgaJpZM4bssKy .
Hi, glad to help where I can...the debugging info you asked for:
2019-03-19 09:07:10.365 (Google Devices) [Google Devices - Office speaker Status] Update 5(5):'NDR N-Joy Morningshow Adult Hits'(NDR N-Joy Morningshow Adult Hits): 0(1) 2019-03-19 09:07:10.365 (Google Devices - Office speaker Status) Updating device from 5:'NDR N-Joy Morningshow Adult Hits' to have values 5:'NDR N-Joy Morningshow Adult Hits'. 2019-03-19 09:07:10.370 (Google Devices) [Google Devices - Office speaker Volume] Update 2(2):'31'(31): 0(1) 2019-03-19 09:07:10.370 (Google Devices - Office speaker Volume) Updating device from 2:'31' to have values 2:'31'. 2019-03-19 09:07:10.376 (Google Devices) [Google Devices - Office speaker Playing] Update 0(0):'0'(0): 0(1) 2019-03-19 09:07:10.377 (Google Devices - Office speaker Playing) Updating device from 0:'0' to have values 0:'0'. 2019-03-19 09:07:10.406 (Google Devices) [Google Devices - Office speaker Volume] Update 0(2):'69'(31): 0(0) 2019-03-19 09:07:10.406 (Google Devices - Office speaker Volume) Updating device from 2:'31' to have values 0:'69'. 2019-03-19 09:07:10.452 (Google Devices) Discovery message seen from unknown device, added: 'Home group', Model: 'Google Cast Group', UUID: 'e985ae8e-d479-40e2-8953-8b842075fa67' + IP: '192.168.188.36:42999'
here is the code: commandArray = {} if devicechanged['TestSwitch'] == 'On' then print("Hello") commandArray['Office speaker'] = "SendNotification 'Hello'" end return commandArray
2019-03-19 09:08:38.898 (Dummy) Light/Switch (TestSwitch) 2019-03-19 09:08:38.887 Status: User: Admin initiated a switch command (3704/TestSwitch/On) 2019-03-19 09:08:39.808 (Google Devices) Pushing 'onHeartbeatCallback' on to queue 2019-03-19 09:08:39.836 (Google Devices) Processing 'onHeartbeatCallback' message 2019-03-19 09:08:39.836 (Google Devices) Calling message handler 'onHeartbeat'. 2019-03-19 09:08:39.160 Status: LUA: Hello
It worked !
but I have all my plugins that crashes like this :
GoogleCast hardware (20) thread seems to have ended unexpectedly
On Tue, 19 Mar 2019 at 09:10, DutchHans notifications@github.com wrote:
Hi, glad to help where I can...the debugging info you asked for:
2019-03-19 09:08:38.898 (Dummy) Light/Switch (TestSwitch) 2019-03-19 09:08:38.887 Status: User: Admin initiated a switch command (3704/TestSwitch/On) 2019-03-19 09:08:39.808 (Google Devices) Pushing 'onHeartbeatCallback' on to queue 2019-03-19 09:08:39.836 (Google Devices) Processing 'onHeartbeatCallback' message 2019-03-19 09:08:39.836 (Google Devices) Calling message handler 'onHeartbeat'. 2019-03-19 09:08:39.160 Status: LUA: Hello
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dnpwwo/Domoticz-Google-Plugin/issues/4#issuecomment-474238435, or mute the thread https://github.com/notifications/unsubscribe-auth/Ahgjt6_aBzGtHBKWJ3s0Ohn9lBavolQ7ks5vYJt2gaJpZM4bssKy .
@rezzalex,
For some reason I don't think your device has ever sent a 'status' to Domoticz which is wierd. I put in a fix that will work around the issue.
@DutchHans,
From your log, I can't see that you have a device called 'Office speaker'. Try sending the command to 'Google Devices - Office speaker Status' (you can change the name by the way, the plugin won't care)
Thank you that worked!
...but I am getting an error in the next message: 2019-03-19 13:08:01.032 Error: (Google Devices) Notification ''Good afternoon, it is now 7 minutes after 1 on Tuesday 19 March. It is 7.9 degrees outside the house, the maximum temperature will be around 11 degrees in the afternoon. The forecast for the next few days is No precipitation throughout the week, with high temperatures peaking at 19°C on Friday. Don't forget to put the Yellowbags outside! Time to work is, considering weather conditions and traffic, 25 mins. Here are a few headlines. Facebook: No Viewers Reported NZ Shooter’s Live Video. Judge orders release of Michael Cohen search warrant materials. Mike Pence will visit Nebraska today to survey flood damage. That is all for now, have a nice day and be careful!'', sent to 'Office speaker' timed out
2019-03-19 13:13:17.462 (Dummy) Light/Switch (TestSwitch) 2019-03-19 13:13:17.744 (Google Devices) Pushing 'onCommandCallback' on to queue 2019-03-19 13:13:17.790 (Google Devices) Processing 'onCommandCallback' message 2019-03-19 13:13:17.791 (Google Devices) Calling message handler 'onCommand'. 2019-03-19 13:13:17.791 (Google Devices) onCommand called for Unit 17: Parameter 'SendNotification 'Good afternoon, it is now 7 minutes after 1 on Tuesday 19 March. It is 7.9 degrees outside the house, the maximum temperature will be around 11 degrees in the afternoon. The forecast for the next few days is No precipitation throughout the week, with high temperatures peaking at 19°C on Friday. Don't forget to put the Yellowbags outside! Time to work is, considering weather conditions and traffic, 25 mins. Here are a few headlines. Facebook: No Viewers Reported NZ Shooter’s Live Video. Judge orders release of Michael Cohen search warrant materials. Mike Pence will visit Nebraska today to survey flood damage. That is all for now, have a nice day and be careful!'', sent to 'Office speaker' timed out'', Level: 0 2019-03-19 13:13:17.791 (Google Devices) UUID: 847c709a-26cb-abc8-7afd-798eaacfd7f1, sub unit: -1, Action: Sendnotification, params: 'Good afternoon, it is now 7 minutes after 1 on Tuesday 19 March. It is 7.9 degrees outside the house, the maximum temperature will be around 11 degrees in the afternoon. The forecast for the next few days is No precipitation throughout the week, with high temperatures peaking at 19°C on Friday. Don't forget to put the Yellowbags outside! Time to work is, considering weather conditions and traffic, 25 mins. Here are a few headlines. Facebook: No Viewers Reported NZ Shooter’s Live Video. Judge orders release of Michael Cohen search warrant materials. Mike Pence will visit Nebraska today to survey flood damage. That is all for now, have a nice day and be careful!'', sent to 'Office speaker' timed out' 2019-03-19 13:13:17.791 (Google Devices) handleMessage: ''Good afternoon, it is now 7 minutes after 1 on Tuesday 19 March. It is 7.9 degrees outside the house, the maximum temperature will be around 11 degrees in the afternoon. The forecast for the next few days is No precipitation throughout the week, with high temperatures peaking at 19°C on Friday. Don't forget to put the Yellowbags outside! Time to work is, considering weather conditions and traffic, 25 mins. Here are a few headlines. Facebook: No Viewers Reported NZ Shooter’s Live Video. Judge orders release of Michael Cohen search warrant materials. Mike Pence will visit Nebraska today to survey flood damage. That is all for now, have a nice day and be careful!'', sent to 'Office speaker' timed out'', sent to 'Office speaker' 2019-03-19 13:13:17.910 (Google Devices) Waiting for 'Default Media Receiver' to start 2019-03-19 13:13:17.919 (Google Devices) [Google Devices - Office speaker Volume] Update 2(2):'50'(69): 0(0) 2019-03-19 13:13:17.920 (Google Devices - Office speaker Volume) Updating device from 2:'69' to have values 2:'50'. 2019-03-19 13:13:17.928 (Google Devices) [Google Devices - Home group Volume] Update 2(2):'42'(52): 0(0) 2019-03-19 13:13:17.929 (Google Devices - Home group Volume) Updating device from 2:'52' to have values 2:'42'. 2019-03-19 13:13:17.935 (Google Devices) [Google Devices - Downstairs Volume] Update 2(2):'40'(47): 0(0) 2019-03-19 13:13:17.936 (Google Devices - Downstairs Volume) Updating device from 2:'47' to have values 2:'40'. 2019-03-19 13:13:17.457 Status: User: Admin initiated a switch command (3704/TestSwitch/On) 2019-03-19 13:13:17.718 Status: LUA: Hello 2019-03-19 13:13:18.091 (Google Devices) [Google Devices - Office speaker Volume] Update 0(2):'50'(50): 0(0) 2019-03-19 13:13:18.091 (Google Devices - Office speaker Volume) Updating device from 2:'50' to have values 0:'50'. 2019-03-19 13:13:18.193 (Google Devices) Pushing 'ProtocolDirective' on to queue 2019-03-19 13:13:18.193 (Google Devices) Pushing 'onConnectCallback' on to queue 2019-03-19 13:13:18.200 (Google Devices) Pushing 'ReadEvent' on to queue 2019-03-19 13:13:18.242 (Google Devices) Processing 'ProtocolDirective' message 2019-03-19 13:13:18.242 (Google Devices) Protocol set to: 'HTTP'. 2019-03-19 13:13:18.243 (Google Devices) Processing 'onConnectCallback' message 2019-03-19 13:13:18.243 (Google Devices) Message handler 'onConnect' not callable, ignored. 2019-03-19 13:13:18.243 (Google Devices) Processing 'ReadEvent' message 2019-03-19 13:13:18.243 (Google Devices) Received 542 bytes of data 2019-03-19 13:13:18.243 (Google Devices) 47 45 54 20 2f 6d 65 73 73 61 67 65 2e 6d 70 33 20 48 54 54 GET./message.mp3.HTT 2019-03-19 13:13:18.243 (Google Devices) 50 2f 31 2e 31 0d 0a 48 6f 73 74 3a 20 31 39 32 2e 31 36 38 P/1.1..Host:.192.168 2019-03-19 13:13:18.243 (Google Devices) 2e 31 38 38 2e 32 30 3a 38 30 30 39 0d 0a 43 6f 6e 6e 65 63 .188.20:8009..Connec 2019-03-19 13:13:18.243 (Google Devices) 74 69 6f 6e 3a 20 6b 65 65 70 2d 61 6c 69 76 65 0d 0a 41 63 tion:.keep-alive..Ac 2019-03-19 13:13:18.243 (Google Devices) 63 65 70 74 2d 45 6e 63 6f 64 69 6e 67 3a 20 69 64 65 6e 74 cept-Encoding:.ident 2019-03-19 13:13:18.243 (Google Devices) 69 74 79 3b 71 3d 31 2c 20 2a 3b 71 3d 30 0d 0a 55 73 65 72 ity;q=1,.;q=0..User 2019-03-19 13:13:18.243 (Google Devices) 2d 41 67 65 6e 74 3a 20 4d 6f 7a 69 6c 6c 61 2f 35 2e 30 20 -Agent:.Mozilla/5.0. 2019-03-19 13:13:18.243 (Google Devices) 28 58 31 31 3b 20 4c 69 6e 75 78 20 61 72 6d 76 37 6c 29 20 (X11;.Linux.armv7l). 2019-03-19 13:13:18.243 (Google Devices) 41 70 70 6c 65 57 65 62 4b 69 74 2f 35 33 37 2e 33 36 20 28 AppleWebKit/537.36.( 2019-03-19 13:13:18.243 (Google Devices) 4b 48 54 4d 4c 2c 20 6c 69 6b 65 20 47 65 63 6b 6f 29 20 43 KHTML,.like.Gecko).C 2019-03-19 13:13:18.243 (Google Devices) 68 72 6f 6d 65 2f 37 31 2e 30 2e 33 35 37 38 2e 39 39 20 53 hrome/71.0.3578.99.S 2019-03-19 13:13:18.243 (Google Devices) 61 66 61 72 69 2f 35 33 37 2e 33 36 20 43 72 4b 65 79 2f 31 afari/537.36.CrKey/1 2019-03-19 13:13:18.243 (Google Devices) 2e 33 37 2e 31 34 36 36 37 39 0d 0a 52 61 6e 67 65 3a 20 62 .37.146679..Range:.b 2019-03-19 13:13:18.244 (Google Devices) 79 74 65 73 3d 30 2d 0d 0a 63 68 72 6f 6d 65 2d 70 72 6f 78 ytes=0-..chrome-prox 2019-03-19 13:13:18.244 (Google Devices) 79 3a 20 66 72 66 72 0d 0a 41 63 63 65 70 74 3a 20 2a 2f 2a y:.frfr..Accept:./* 2019-03-19 13:13:18.244 (Google Devices) 0d 0a 41 63 63 65 70 74 2d 4c 61 6e 67 75 61 67 65 3a 20 65 ..Accept-Language:.e 2019-03-19 13:13:18.244 (Google Devices) 6e 2d 55 53 2c 65 6e 3b 71 3d 30 2e 39 0d 0a 43 41 53 54 2d n-US,en;q=0.9..CAST- 2019-03-19 13:13:18.244 (Google Devices) 44 45 56 49 43 45 2d 43 41 50 41 42 49 4c 49 54 49 45 53 3a DEVICE-CAPABILITIES: 2019-03-19 13:13:18.244 (Google Devices) 20 7b 22 61 75 64 69 6f 5f 61 73 73 69 73 74 61 6e 74 22 3a .{"audio_assistant": 2019-03-19 13:13:18.244 (Google Devices) 74 72 75 65 2c 22 62 6c 75 65 74 6f 6f 74 68 5f 73 75 70 70 true,"bluetooth_supp 2019-03-19 13:13:18.244 (Google Devices) 6f 72 74 65 64 22 3a 74 72 75 65 2c 22 64 69 73 70 6c 61 79 orted":true,"display 2019-03-19 13:13:18.244 (Google Devices) 5f 73 75 70 70 6f 72 74 65 64 22 3a 66 61 6c 73 65 2c 22 68 _supported":false,"h 2019-03-19 13:13:18.244 (Google Devices) 69 5f 72 65 73 5f 61 75 64 69 6f 5f 73 75 70 70 6f 72 74 65 i_res_audio_supporte 2019-03-19 13:13:18.244 (Google Devices) 64 22 3a 66 61 6c 73 65 2c 22 72 65 6d 6f 74 65 5f 63 6f 6e d":false,"remote_con 2019-03-19 13:13:18.244 (Google Devices) 74 72 6f 6c 5f 69 6e 70 75 74 5f 73 75 70 70 6f 72 74 65 64 trol_input_supported 2019-03-19 13:13:18.244 (Google Devices) 22 3a 66 61 6c 73 65 2c 22 74 6f 75 63 68 5f 69 6e 70 75 74 ":false,"touch_input 2019-03-19 13:13:18.244 (Google Devices) 5f 73 75 70 70 6f 72 74 65 64 22 3a 66 61 6c 73 65 7d 0d 0a _supported":false}.. 2019-03-19 13:13:18.245 (Google Devices) 0d 0a .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 2019-03-19 13:13:18.245 (Google Devices) Pushing 'onMessageCallback' on to queue 2019-03-19 13:13:18.245 (Google Devices) Processing 'onMessageCallback' message 2019-03-19 13:13:18.245 (Google Devices) Calling message handler 'onMessage'. 2019-03-19 13:13:18.245 (Google Devices) onMessage called from: 192.168.188.28:54077 2019-03-19 13:13:18.245 (Google Devices) Read 0 bytes of data into variable of type: <class 'bytes'> 2019-03-19 13:13:18.245 (Google Devices) Pushing 'WriteDirective' on to queue 2019-03-19 13:13:18.245 (Google Devices) Processing 'WriteDirective' message 2019-03-19 13:13:18.246 (Google Devices) Sending 122 bytes of data 2019-03-19 13:13:18.246 (Google Devices) 48 54 54 50 2f 31 2e 31 20 32 30 30 20 4f 4b 0d 0a 44 61 74 HTTP/1.1.200.OK..Dat 2019-03-19 13:13:18.246 (Google Devices) 65 3a 20 54 75 65 2c 20 31 39 20 4d 61 72 20 32 30 31 39 20 e:.Tue,.19.Mar.2019. 2019-03-19 13:13:18.246 (Google Devices) 31 32 3a 31 33 3a 31 38 20 47 4d 54 0d 0a 53 65 72 76 65 72 12:13:18.GMT..Server 2019-03-19 13:13:18.246 (Google Devices) 3a 20 44 6f 6d 6f 74 69 63 7a 2f 31 2e 30 0d 0a 43 6f 6e 74 :.Domoticz/1.0..Cont 2019-03-19 13:13:18.246 (Google Devices) 65 6e 74 2d 54 79 70 65 3a 20 6d 75 73 69 63 2f 6d 70 33 0d ent-Type:.music/mp3. 2019-03-19 13:13:18.246 (Google Devices) 0a 43 6f 6e 74 65 6e 74 2d 4c 65 6e 67 74 68 3a 20 30 0d 0a .Content-Length:.0.. 2019-03-19 13:13:18.246 (Google Devices) 0d 0a .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 2019-03-19 13:13:18.467 (Google Devices) Connection '192.168.188.28:54077' released by Python, reference count is 1. 2019-03-19 13:13:18.467 (Google Devices) Pushing 'DisconnectDirective' on to queue 2019-03-19 13:13:18.497 (Google Devices) Processing 'DisconnectDirective' message 2019-03-19 13:13:18.497 (Google Devices) Disconnect directive received for '192.168.188.28:54077'. 2019-03-19 13:13:18.497 (Google Devices) Handling TCP disconnect, socket (192.168.188.28:54077) is connected 2019-03-19 13:13:18.498 (Google Devices) Queued asyncronous read aborted (192.168.188.28:54077). 2019-03-19 13:13:18.498 (Google Devices) Pushing 'DisconnectedEvent' on to queue 2019-03-19 13:13:18.548 (Google Devices) Processing 'DisconnectedEvent' message 2019-03-19 13:13:18.548 (Google Devices) Disconnect event received for '192.168.188.28:54077'. 2019-03-19 13:13:18.549 (Google Devices) Pushing 'onDisconnectCallback' on to queue 2019-03-19 13:13:18.549 (Google Devices) Processing 'onDisconnectCallback' message 2019-03-19 13:13:18.549 (Google Devices) Message handler 'onDisconnect' not callable, ignored. 2019-03-19 13:13:18.549 (Google Devices) Deallocating connection object '192.168.188.28:54077' (192.168.188.28:54077). 2019-03-19 13:13:22.135 (RfxCom-1) Temp + Humidity (Temperature Livingroom) 2019-03-19 13:13:23.468 (Google Devices) Pushing 'onHeartbeatCallback' on to queue 2019-03-19 13:13:23.508 (Google Devices) Processing 'onHeartbeatCallback' message 2019-03-19 13:13:23.508 (Google Devices) Calling message handler 'onHeartbeat'. 2019-03-19 13:13:24.854 (RfxCom-1) Energy (Total Energy Consumption) 2019-03-19 13:13:25.336 (Z-wave Controller ) Thermostat ($Radiator Bedroom Setpoint) 2019-03-19 13:13:26.118 (Z-wave Controller ) Thermostat ($Radiator HWR Setpoint) 2019-03-19 13:13:27.945 (Google Devices) [Google Devices - Office speaker Volume] Update 0(0):'69'(50): 0(0) 2019-03-19 13:13:27.945 (Google Devices - Office speaker Volume) Updating device from 0:'50' to have values 0:'69'. 2019-03-19 13:13:27.969 (Google Devices) [Google Devices - Downstairs Volume] Update 2(2):'47'(40): 0(0) 2019-03-19 13:13:27.969 (Google Devices - Downstairs Volume) Updating device from 2:'40' to have values 2:'47'. 2019-03-19 13:13:27.980 (Google Devices) [Google Devices - Home group Volume] Update 2(2):'52'(42): 0(0) 2019-03-19 13:13:27.980 (Google Devices - Home group Volume) Updating device from 2:'42' to have values 2:'52'. 2019-03-19 13:13:27.991 (Google Devices) [Google Devices - Office speaker Volume] Update 2(0):'69'(69): 0(0) 2019-03-19 13:13:27.991 (Google Devices - Office speaker Volume) Updating device from 0:'69' to have values 2:'69'.
Messages longer than this: 'Good afternoon, it is now 7 minutes after 1 on Tuesday 19 March. It is' are not spoken
The interesting line is this one:
2019-03-19 13:13:18.245 (Google Devices) Read 0 bytes of data into variable of type: <class 'bytes'>
When the home device hit the plugin's web server to get the mp3 file the Python read returned nothing so nothing was sent back to the speaker (or spoken). How big is the Message.mp3 file for your full message?
The message is composed on the fly; it combines several inputs(weather, garbage, birthdays,news etc) to one "goodmorning" message. it is not always the same size. The mp3 of this one is 28.224 k
'Good afternoon, it is now 23 minutes after 2 on Tuesday 19 March. It is 8 degrees outside the house, the maximum temperature will be around 11 degrees in the afternoon. The forecast for the next few days is No precipitation throughout the week, with high temperatures peaking at 19°C on Friday. Don't forget to put the Yellowbags outside! Time to work is, considering weather conditions and traffic, 25 mins. Here are a few headlines. Devastating flooding hits already struggling Midwest farmers. Author of 'Kushner, Inc.' says Jared Kushner, Ivanka Trump on 'remarkably unstoppable' path despite continued questions about business conflicts. How Britain's parliamentary speaker just made Brexit harder. That is all for now, have a nice day and be careful!
... maybe quotes in the text may interfer as well...
They certainly wouldn't help ... I'll make a change to clean the text tonight.
The internet seems to think that the file read method I'm using will not have any issues until at least 2GB so that shouldn't be the issue.
Pushed an update where quotes are cleaned from the string but I don't think that is the problem.
I suspect the translate service only allows short messages. The one you say was successful is exactly 70 characters which makes me suspicious.
I will try it. The translate service does accept longer messages; I have this working on Chromacast via another script found here: https://www.gioexperience.com/google-home-hack-send-voice-programmaticaly-with-python/ Its not that convenient but it works. If there is anything I can do, please say so...
I've tried it but it's complete silent; only thing I hear is the Chromecast Beep
I believe the beep is normally the result of the volume change.
The code you posted is useful, I would rather not execute a curl command so I'll look into it. Sadly the first time I ran it Python blew Domoticz up and gave a 216 line stackdump :(
Update: Now generating a 1:00 mp3 (seems to cut off at that point) around 227KB which is good but Domoticz is attempting to sent the whole thing to the Google device in 1 chunk which seems to be causing issues.
Hi, I have the same problem, only volume beep.
EDIT :
hope this helps with finding the sollution
I am Identifying my individual Google- minis with Pirs. Send the message to Ipaddress of the Google Mini which is the nearest to the last activated Pir. Domoticz accepts the activation below.
os.execute('(sudo /home/pi/domoticz/scripts/python/ghome_say.py '..ReceiverIP..' "'..SpeakSentence..'"> /dev/null)&')
Maybe this helps. Cheers, Hans
I am Identifying my individual Google- minis with Pirs. Send the message to Ipaddress of the Google Mini which is the nearest to the last activated Pir. Domoticz accepts the activation below.
os.execute('(sudo /home/pi/domoticz/scripts/python/ghome_say.py '..ReceiverIP..' "'..SpeakSentence..'"> /dev/null)&')
Maybe this helps. Cheers, Hans
Thanks for th hint, The problem remains, but i found a way arround. Probably my issue is system specific, but this hint helps a lot : I can now create a mp3 file from curl in lua and then send it to indivual chromecast-IP. So this work around works
When I have the language of Domoticz set to Dutch, notifications will not be played (only the beeping of the volume adjustments). When changing to English (and restarting Dz) it works. Changing back to Dutch (restart), again breaks. Changing to French (restart) ==> works. Changing back to Dutch (No restart) ==> still works with French translations Restart ==> not working. Changing back to English (restart) ==> Working.
Seems Dutch is not working.
P.S. when selecting English, can you get the American English selected ?? sounds much better than the English English (sorry, my personal preference :-) )
When you change the Domoticz language the plugin will need to be restarted to pick it up (you can 'Update' it on the Hardware tab).
The internet seems to think that Google tts supports Dutch as of 2014, what does language string Domoticz use when the Web UI is set to Dutch?
I can't control which 'English' Domoticz chooses, the same one is sent to Google. I am originally English though and it sounds fine to me :)
When you change the Domoticz language the plugin will need to be restarted to pick it up (you can 'Update' it on the Hardware tab). OK, clear.
The internet seems to think that Google tts supports Dutch as of 2014, what does language string Domoticz use when the Web UI is set to Dutch? No idea. Will take a look at the code to see if I can find this.
I can't control which 'English' Domoticz chooses, the same one is sent to Google. I am originally English though and it sounds fine to me :) Well, my apologies if I offended you in any way ... :-)
@dnpwwo,
Did you implemented the fix you mentionned to me ? Because I have always these "thread ended unexpectedly" that might come from this plugin...
Thanks
Good Afternoon,
I have updated to the latest version but if messages are too long they won't be "spoken" ... any progress on this?
Yes. I had to update Domoticz to make the HTTP connections to support sending files in 'chunks' which I pushed 2 days ago.
Successfully played a 224 KB file last night I'm just tuning it to make it start as soon as possible.
Might push an update tonight if I get time to tweak things.
Looking forward to test it... I will let you know
Pushed version 1.14.7
Note the updated install instructions on the readme page. 'gtts' now needs to be installed
I already have... Or does it needs to be in a special place?
Getting a bunch of errors... 2019-04-07 15:00:04.431 Error: (Google Devices) 'onCommand' failed 'KeyError'. 2019-04-07 15:00:04.431 Error: (Google Devices) ----> Line 614 in '/home/pi/domoticz/plugins/Domoticz-Google-Plugin/plugin.py', function onCommand 2019-04-07 15:00:04.431 Error: (Google Devices) ----> Line 551 in '/home/pi/domoticz/plugins/Domoticz-Google-Plugin/plugin.py', function onCommand
Just needs to be installed using 'sudo'.
Did you get a message warning you "Voice notifications will not be enabled" when the plugin started?
KeyError may be because Domoticz hasn't seen the device you are trying to notify since the plugin started, was there a discovery message in the log?
They were all marked red
Do i need to uninstall?
No uninstall is required , just wait until they aren't red, then it should work.
Hmmm i deleted some of them... Will they return?
If you delete all the Domoticz devices for a piece of google hardware I believe the plugin will add them again the next time it sees it
Reinstalled the plugin completely and get the following errors:
2019-04-08 08:41:42.662 Status: (Chromecast) Entering work loop. 2019-04-08 08:41:42.664 Status: (Chromecast) Initialized version 1.14.7, author 'dnpwwo' 2019-04-08 08:41:42.794 Error: (Chromecast) discoveryCallback: 'Chromecast' object has no attribute 'start' 2019-04-08 08:41:42.868 Error: (Chromecast) discoveryCallback: 'Chromecast' object has no attribute 'start' 2019-04-08 08:41:42.933 Error: (Chromecast) discoveryCallback: 'Chromecast' object has no attribute 'start' 2019-04-08 08:41:42.998 Error: (Chromecast) discoveryCallback: 'Chromecast' object has no attribute 'start' 2019-04-08 08:41:43.068 Error: (Chromecast) discoveryCallback: 'Chromecast' object has no attribute 'start' 2019-04-08 08:41:43.133 Error: (Chromecast) discoveryCallback: 'Chromecast' object has no attribute 'start'
any suggestions?
Yes, you need to uninstall and reinstall pychromecast. When you reinstall you should get version 3.2.0 which has an improved API.
Just 'sudo pip3 uninstall pychromecast' from memory then 'sudo pip3 install pychromecast'
OK, I reinstalled pychromecast everything went well but total silence.. Dir"Messages" was not created; neither the file "Message.mp3" I created them by hand... but total silence
Have you installed gtts? If that fails to load then voice notification is disabled.
Turn the plugin's debug up to All, restart Domoticz wait for the devices to not be red then send a notification. If it doesn't work post the log.
yes I did... I hear the beep; the mp3 is now created but total silence
I'm going to need to see the FULL log
Hello,
I have installed correctly the plugin and here is my parameter Here is my plug-in Conf
Here is My notification set-up![image](https://user-images.githubusercontent.com/35136439/54265386-6c2eb000-4575-11e9-8291-c0d95f01c3db.png)
When I activate my switch, the voice message notification is not working.
Here is my logs![image](https://user-images.githubusercontent.com/35136439/54265252-2d005f00-4575-11e9-8bd3-4f46fd709794.png)
Thans for your help
RezzA