Announcement

Collapse
No announcement yet.

Rebuilding VR commands due to configuration change

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

    Rebuilding VR commands due to configuration change

    I searched and didn't see anything about this. Sorry if it's a dup.

    I had to move HS to another machine last week. Different IP of course. The speaker app on my main machine connects fine to the new IP. However,

    Often I get
    Rebuilding VR commands due to configuration change
    and it stops listening. Like once an hour or so. Stopping and starting Speaker fixed the problem until today.

    Now the thing won't talk to me. When I call it, the status msg changes to Listening for commands but won't say a thing.

    Everything else seems OK (although I have to re-register the world) but this bugs me. Other machines seem OK.

    Now I had a similar problem when I tried to get 5 machines talking. But right now I only have 3.

    Thanks
    John

    #2
    The rebuilding message is caused by an event changing. Do you have a lot of events changing or being changed by a plugin? Also is your speaker clients the same version as your HS version?
    -Rupp
    sigpic

    Comment


      #3
      Fwiw, I'm noticing this a lot. I've got a Speaker set up on a Windows 10 machine as an output for a HS3 install running inside a VM on a different machine. I've never really paid attention to the log in the Speaker client view.

      The odd thing is I don't even has voice recognition enabled.

      Code:
      4/11/2021 9:25:03 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:25:08 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:25:13 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:25:24 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:29:42 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:30:03 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:30:09 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:30:14 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:30:19 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:30:28 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:35:09 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:35:14 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:35:19 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:35:25 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:35:32 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:40:13 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:40:19 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:40:24 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:40:30 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:40:36 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:43:13 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:45:20 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:45:25 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:45:30 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:45:36 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:45:40 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:50:25 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:50:30 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:50:36 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:50:41 AM:Rebuilding VR commands due to configuration change
      4/11/2021 9:50:45 AM:Rebuilding VR commands due to configuration change
      I don't like to leave things spewing messages in logs because eventually something overruns and does something stupid, like run out of diskspace and cause other things to crash. So a "silent" log is a good thing.

      Can we get an option to suppress this?

      Comment


        #4
        I recall seeing these in the logs around HS2-3 times. I ignored the log entries.

        Having a look see today I do not see them in the 6 instances of Speaker.exe running on a W7 VB on Ubuntu 18.04 (HS3). Never configured base W7 VB for VR here.





        I Click image for larger version  Name:	HS3Ubuntu-W7VB-Speaker.jpg Views:	0 Size:	81.2 KB ID:	1468189
        - Pete

        Auto mator
        Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb- Mono 6.12.X - HSTouch on Intel tabletop tablets
        Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.12.X
        HS4 Pro - V4.1.11.0 - Ubuntu 20.01/VB W7e 64 bit Intel Kaby Lake CPU - 32Gb - Mono
        6.10.0.104
        HS4 Lite -

        X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Smartthings hub, Hubitat Hub, and Home Assistant

        Comment

        Working...
        X