Various bug reports

Configuration
91

@Tlse-vins I also have a production instance, but nothing prevents you from testing a development instance. Personally, I do it like this:
docker stop gladys

docker run -d --log-opt max-size=10m --restart=always --privileged --network=host --name gladysdev -e NODE_ENV=production -e SERVER_PORT=80 -e TZ=Europe/Paris -e SQLITE_FILE_PATH=/var/lib/gladysassistantdev/gladys-dev.db -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/gladysassistantdev:/var/lib/gladysassistantdev -v /dev:/dev -v /run/udev:/run/udev:ro gladysassistant/gladys:dev

@pierre-gilles, since my installation is fresh, I’m coming back to you for a possible bug…
So once gladys is installed, I configure the weather for example, and then I ask via the chat what the temperature is. At the moment, it does not respond, so I look at the logs, on the docker side there is nothing abnormal but on the browser side yes:

    close { target: WebSocket, isTrusted: true, wasClean: true, code: 1001, reason: "", srcElement: WebSocket, currentTarget: WebSocket, eventPhase: 2, bubbles: false, cancelable: false, … }
​
bubbles: false
​
cancelBubble: false
​
cancelable: false
​
code: 1001
​
composed: false
​
currentTarget: null
​
defaultPrevented: false
​
eventPhase: 0
​
explicitOriginalTarget: WebSocket { url: "ws://192.168.1.82/", readyState: 3, bufferedAmount: 0, … }
​
isTrusted: true
​
originalTarget: WebSocket { url: "ws://192.168.1.82/", readyState: 3, bufferedAmount: 0, … }
​
reason: ""
​
returnValue: true
​
srcElement: WebSocket { url: "ws://192.168.1.82/", readyState: 3, bufferedAmount: 0, … }
​
target: WebSocket { url: "ws://192.168.1.82/", readyState: 3, bufferedAmount: 0, … }
​
timeStamp: 266627
​
type: "close"
​
wasClean: true
​
<get isTrusted()>
​
<prototype> CloseEventPrototype { wasClean: Getter, code: Getter, reason: Getter, … }
​​
code:
​​
constructor: function ()
​​
reason:
​​
wasClean:
​​
Symbol(Symbol.toStringTag): "CloseEvent"
​​
<get code()>
​​
<get reason()>
​​
<get wasClean()>
​​
<prototype> EventPrototype { composedPath: composedPath(), stopPropagation: stopPropagation(), stopImmediatePropagation: stopImmediatePropagation(), … }
Session.js:60:6

If I refresh my page (very long to load by the way), gladys’s answer is there, often above my question, but it is there ^^. After that, no more issues, you can talk to it as much as you want, it responds immediately.
That’s it, if it can help :slight_smile: