Announcement

Collapse
No announcement yet.

SpeakToFile: Not enough Storage messages

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    SpeakToFile: Not enough Storage messages

    This morning I was waiting for for wakeup chime & announcement for my childern that did not happen when I look into my HS3 Log I can see that both the scheduled event and TTS statement are sent but no sound, the execerpt below shows both a SpeakToFile error that Not enough storage is avalable to process. When I look at my Resource Manager my CPU is at ~5% and Memory is at ~14%, so... can someone explain what happen and more importantly how to resolve.

    I ended up rebooting my device to restore it back to an operation state.

    Oct-31 7:01:36 AM Sonos Error Error in DoCheckAnnouncementQueue. 180 seconds expired since the announcement started and no end was received.
    Oct-31 7:01:36 AM Error In SpeakToFile: Not enough storage is available to process this command. (Exception from HRESULT: 0x80070008)
    Oct-31 7:01:33 AM Sonos Error Error in DoCheckAnnouncementQueue. 180 seconds expired since the announcement started and no end was received.
    Oct-31 7:01:11 AM Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/Jon00UptimeHS3.vben("Main","1;DV|2;DV")
    Oct-31 7:01:11 AM Event Event Trigger "Network UpTime Monitor"
    Oct-31 7:00:59 AM Info Amazon Echo Discovery requested, version: 2
    Oct-31 7:00:51 AM Jon00_PerfMon Processing CPU usage
    Oct-31 7:00:11 AM Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/Jon00UptimeHS3.vben("Main","1;DV|2;DV")
    Oct-31 7:00:11 AM Event Event Trigger "Network UpTime Monitor"
    Oct-31 7:00:01 AM Error In SpeakToFile: Not enough storage is available to process this command. (Exception from HRESULT: 0x80070008)
    Oct-31 7:00:00 AM Z-Wave Device: Lights Amelia Amelia Light Set to 255
    Oct-31 7:00:00 AM TTS Speak: ($SONOS$Time$:*):c:\program Files (x86)\HomeSeer HS3\Media\Ship_Bell.mp3|The time is 7:00 AM
    Oct-31 7:00:00 AM Event Event Trigger "Speak Speak Hourly Chime & Time"
    Oct-31 7:00:00 AM TTS Speak: ($SONOS$Amelia$:*):c:\program Files (x86)\HomeSeer HS3\Media\Dream-sound-effect.mp3|Good morning Amelia! the time is 7:00 AM, it's time to wake up and get ready for school!
    Computer: CUK Intel NUC7i7BNH
    Op System: Windows10 Pro - Work Station
    HS Version: HS4 Pro Edition 4.2.19.0

    Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.

    #2
    Oct-31 7:01:36 AM Sonos Error Error in DoCheckAnnouncementQueue. 180 seconds expired since the announcement started and no end was received.
    Oct-31 7:01:36 AM Error In SpeakToFile: Not enough storage is available to process this command. (Exception from HRESULT: 0x80070008)
    Oct-31 7:01:33 AM Sonos Error Error in DoCheckAnnouncementQueue. 180 seconds expired since the announcement started and no end was received.


    Just guessing...

    I am not familiar with the Sonos play back wave file for speech function works or any other speech proxy utilized.

    Running Homeseer touch that includes speech a wave file is sent over to the client.

    If the Android, iOS or Windows client storage is running out of space then the file cannot be copied over or played back by said device.

    Or you are running out of disk space on the mothership maybe?

    Here my source text to speech sounds are from speaker dot exe running on Wintel clients (virtual box or Homeseer speaker running on Windows tabletop clients).
    - Pete

    Auto mator
    Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
    Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
    HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

    HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
    HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

    X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

    Comment


      #3
      Pete, thanxs for the comeback, I have two drives for the HomeSeer "Mothership" computer. My C: is a SDD (237 Gb) that has 188 Gb Free space and 49.8 Gb used the other is a Conventional Mech (931 Gb) with 931 Gb free.

      Looking again at my Resource Monitor I'm still using ~4% CPU and 15% of my Memory (16,276 MB) so I should have plenty of computer resources.

      Sonos Error Error in DoCheckAnnouncementQueue. 180 seconds expired since the announcement started and no end was received.
      The Sonos error above is a typical SONOS error that is issued if there is no end of message received. I've seen it when a SONOS speaker is locked out and not available when issuing a TTS command.

      Mike
      Computer: CUK Intel NUC7i7BNH
      Op System: Windows10 Pro - Work Station
      HS Version: HS4 Pro Edition 4.2.19.0

      Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.

      Comment


        #4
        The Sonos error above is a typical SONOS error that is issued if there is no end of message received. I've seen it when a SONOS speaker is locked out and not available when issuing a TTS command.

        So what is it that causes the Sonos speaker to get locked out and there is no end of message received?

        Could it be a wireless transport issue (well like a drop out of sorts)?

        I have seen reported 3rd party plugin issues relating to HS3 V368..

        The new HS3 V379 beta is being tested right now by many users.

        4% CPU and 15% memory is really not much utilization. Do you seen anything in the Microsoft event log that would indicate any issues?

        Here running Homeseer 3 Lite (Zee2) using 16Gb of an SD card and Homeseer 3 Pro using around 160Gb of hard drive space.

        The HS3 Lite Homeseer directory is around 250 Mb while the HS3 Pro directory is around 500 Mb in size.
        Last edited by Pete; October 31, 2017, 04:21 PM.
        - Pete

        Auto mator
        Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
        Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
        HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

        HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
        HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

        X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

        Comment


          #5
          Pete, my bad! correct terminology is "Transport is locked" as used in the SONOS Error message below. So are you suggesting that I should try the new HS3 V379 beta? If so where do I get it? Mike

          Oct-31 3:00:02 PM Sonos Error

          ERROR in PlayURI for zoneplayer = Kitchen with UPNP Error = Read only tag / Transport is locked / Access denied. URI=x-rincon:RINCON_949F3E01683401400 and isObjectID = False, MetaData=http://192.168.0.55:10210/images/Sonos/Announcement.jpgHomeSeer Announcementobject.item.audioItem.musicTrackDirk CorsusSonosControllerDirk Corsus, Error =MyUPnPService.InvokeAction for ServiceID = http://192.168.0.129:1400/xml/AVTransport1.xml while sending Action = SetAVTransportURI for URI = http://192.168.0.129:1400/MediaRende...nsport/Control and Request = 0 x-rincon:RINCON_949F3E01683401400 <DIDL-Lite xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:upnp="urn:schemas-upnp-org:metadata-1-0/upnp/" xmlns:r="urn:schemas-rinconnetworks-com:metadata-1-0/" xmlns="urn:schemas-upnp-org:metadata-1-0/DIDL-Lite/"><item id="-1" parentID="-1" restricted="true"><upnp:albumArtURI>http://192.168.0.55:10210/images/Sonos/Announcement.jpg</upnp:albumArtURI><dc:title>HomeSeer Announcement</dc:title><upnp:class>object.item.audioItem.musicTrack</upnp:class><dc:creator>Dirk Corsus</dc:creator><upnp:album>SonosController</upnp:album><r:albumArtist>Dirk Corsus</r:albumArtist></item></DIDL-Lite> UPNP Error = faultcode = s:Client, faultstring = UPnPError, detail = 501 with error = The remote server returned an error: (500) Internal Server Error.
          Computer: CUK Intel NUC7i7BNH
          Op System: Windows10 Pro - Work Station
          HS Version: HS4 Pro Edition 4.2.19.0

          Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.

          Comment


            #6
            Personally I would first check with the author of the Sonos plugin.

            You can download the beta HS3 V.379 from here:

            hxxps://homeseer.com/updates3/SetupHS3_3_0_0_379.msi

            xx=tt

            It is suggested to back up your Homeseer 3 directory before you test a beta version of Homeseer 3.

            BTW in the two threads that lead up to V379 there was a UPNP issue and Rich suggested shutting it off for testing purposes.
            Last edited by Pete; October 31, 2017, 06:16 PM.
            - Pete

            Auto mator
            Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
            Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
            HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

            HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
            HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

            X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

            Comment


              #7
              Pete, many thanxs for guidance/suggestions. I currently have a daily backup to a NAS via Blades BLBackup which works great. You indicate that I should turn off UPNP, I'm assuming your referring to SONOS or is there some other place I should be looking at? Mike

              Update: Found in setup under the "Network" Tab - "System is Discoverable Using UPNP", my system currently does not have this set.
              Last edited by MNB; November 1, 2017, 09:53 AM.
              Computer: CUK Intel NUC7i7BNH
              Op System: Windows10 Pro - Work Station
              HS Version: HS4 Pro Edition 4.2.19.0

              Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.

              Comment

              Working...
              X