1583103 - Toggles on webpage are not recognized eg refreshed. (websocket error)

Status: UNCONFIRMED

(Core :: Networking: WebSockets, defect, P3)

Description

[PA3FAT]

Attachment: Domoticz dashboard.PNG

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

Tried same URL in Edge and Internet Explorer and works.. It works in Firefox mobile version on my iPhone 6s.
Tried it on my daughteres laptop running Firefox, it also doesn't work.

Actual results:

The toggle on the webpage does not refresh the screen. Data and webpage remains the same.
This has 'always' worked but in very recent version of FF this stopped.
I am running FF V69.0.1 currently.

Expected results:

Domoticz is a home automation system. So when i toggle e.g. a lamp in the house it should go from off to on. The systems itself works so the lights will turn on but the webpage is not reflecting this.

As i am using this webpage on a locally running hardware will supply the url to support when requested.

Comment 1

[PA3FAT]

Tested using Chrome. Works.

Comment 2

[PA3FAT]

Any update?
Willing to supply my private url to the system. Can't post it public.

Comment 3

[PA3FAT]

In debug mode FF 69.0.1 is throwing "Websocket error". Can't find more details in developer mode........lack of knowledge......

Comment 4

[PA3FAT]

FF beta 70.0b9 has same issue. Need help to get it resolved. FF (Windows) seems only platform with issue.

Comment 5

[Fredrik]

I experience the exact same thing. Please let me know if I can contribute with any information

Comment 6

[gloupgloup]

Internet Explorer works.

Comment 7

[gloupgloup]

Microsoft EDGE works perfectly

Comment 8

[PA3FAT]

seems related to the issue: absense of certificate on host server (Domoticz).

https://www.domoticz.com/forum/viewtopic.php?f=6&t=29414

Comment 9

[PA3FAT]

70.0b10 still has issue.

Comment 10

[gloupgloup]

Firefox Nightly 71.0a1 still has issue

Comment 11

[Raluca Popovici, Desktop QA]

Hi,
I can't manage to reproduce this issue on my machine Win 10 with Firefox Release 69 and Nightly 71. From comment 3 I understand that could be a WebSocket issue so I will set Core::Networking:WebSockets component. If this is not the right component please feel free to change it.

Comment 12

[PA3FAT]

@Raluca,

Can give you url to my server. So you can test. Let me know via private message.

Comment 13

[philippe.drouet7]

Hi,
problem is still present on the last version of Firefox v69.0.3

Comment 14

[philippe.drouet7]

(In reply to PA3FAT from comment #8)

seems related to the issue: absense of certificate on host server (Domoticz).

https://www.domoticz.com/forum/viewtopic.php?f=6&t=29414

I don't think so because I have certificates on 3 Raspberry Pi 3 B+ and a computer running Windows Server 2016 and all have a valid certificate generated by LetsEncrypt that is well recognized by Firefox (green lock).
All these computers used as servers for Domoticz have this problem with Firefox. All the other browsers I have tested are working correctly (Chrome, Opera, Edge). Even Chromium works under Raspbian.

Comment 15

[philippe.drouet7]

In the console the problem seems related to the angular-websocket.js file (angular-websocket.js:127:14)
Evry 4 or 5 second the console add a line with this error (translated from French) :
Firefox cannot establish a connection with the server at ws://xxx.xxx.xxx.xxx:8080/json. angular-websocket.js:127:14
The line 1278 in the file :
else if (cfg.protocols) {me.$$ws = new WebSocket(cfg.url, cfg.protocols);
}

Comment 16

[PA3FAT]

FF 70.0 still has the issue.

Comment 17

[gloupgloup]

LG WebOS works fine!

Comment 18

[philippe.drouet7]

(In reply to gloupgloup from comment #17)

LG WebOS works fine!

Hi,
it seems that only Firefox don't works :(

Comment 19

[philippe.drouet7]

Problem is still present after the last version 4.11375 on Raspberry Pi
It's starting to take a while, no one to fix this bug ?

Comment 20

[PA3FAT]

V11.386 and later the issue in Domotic

Call can be closed.

Comment 21

[PA3FAT]

V11.386 and later the issue in Domotic is solved.