Plugin Switchboard : Virtual Switch in VeraPlus not shown in Openluup
-
I noticed when I first starting using my new RPI4 that the SSH connection would have frequent pregnant pauses. I'd type and get no response for a few seconds, and then it would spring to life, or a rolling output would pause and then rush to catch up. Although I have good Wifi throughout my house (and well beyond), changing the connection to Ethernet was the first thing I tried and no troubles since.
Since then, I ran across an article where someone had figured out that at a specific resolution (1440p), the RF noise from the HDMI exactly stomps on WiFi channel 1 (which is what I use). Here: https://www.tomshardware.com/news/raspberry-pi-4-wi-fi-not-working
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
I noticed when I first starting using my new RPI4 that the SSH connection would have frequent pregnant pauses. I'd type and get no response for a few seconds, and then it would spring to life, or a rolling output would pause and then rush to catch up. Although I have good Wifi throughout my house (and well beyond), changing the connection to Ethernet was the first thing I tried and no troubles since.
Since then, I ran across an article where someone had figured out that at a specific resolution (1440p), the RF noise from the HDMI exactly stomps on WiFi channel 1 (which is what I use). Here: https://www.tomshardware.com/news/raspberry-pi-4-wi-fi-not-working
@toggledbits said in Plugin Switchboard : Virtual Switch in VeraPlus not shown in Openluup:
I noticed when I first starting using my new RPI4 that the SSH connection would have frequent pregnant pauses.
@toggledbits did you mean to post that reply under this topic? (Asking cuz I don't see its precedent)
-
Can’t see anything in the logs which is untoward. What may show something is a couple of the previous logs (.1, .2) after it’s failed and you’ve restarted.
-
@toggledbits said in Plugin Switchboard : Virtual Switch in VeraPlus not shown in Openluup:
I noticed when I first starting using my new RPI4 that the SSH connection would have frequent pregnant pauses.
@toggledbits did you mean to post that reply under this topic? (Asking cuz I don't see its precedent)
@librasun said in Plugin Switchboard : Virtual Switch in VeraPlus not shown in Openluup:
@toggledbits did you mean to post that reply under this topic? (Asking cuz I don't see its precedent)
Precedent was this post in topic: https://smarthome.community/post/5129
-
I changed the connection to ethernet but the problem is not resolved. It takes sometimes over 60 minutes or even more to reconnect with openluup or alui via IP; 3480. I have ordered a new micro DS card and I restore my RP4 backup. I hope the problem may be solved.
The strange thing is that node red server can be reached when openluup is not available.
-
Just out of curiosity, can you check if you are able to access the openLuup console? "http://IP:3480/openLuup"
That way you know whether it is openLuup or ALTUI which is causing the problem. ALTUI relies on a lot of stuff in the web if you don't localize the cdn and sometimes can cause some problems. I understand the need for the license check but for everything else, it seems silly to me so I have been localizing everything I could. -
This section of the latest log you sent is particularly worrying...
2021-03-08 19:10:48.819 luup.variable_set:: 28.urn:honeywell-com:serviceId:ThermostatData1.OutdoorHumidity was: now: #hooks:0 2021-03-08 19:10:48.819 luup.variable_set:: 28.urn:honeywell-com:serviceId:ThermostatData1.IndoorHumidity was: now: #hooks:0 2021-03-08 19:26:28.221 luup.variable_set:: 23.urn:joeyd-com:serviceId:HoneywellTCC1.t.6.refreshStatus was: now: #hooks:0 2021-03-08 19:26:28.222 luup.variable_set:: 23.urn:joeyd-com:serviceId:HoneywellTCC1.statusRefreshDateTime was: Mon, Mar 08, 07:10:48 PM now: Mon, Mar 08, 07:26:28 PM #hooks:0 2021-03-08 19:26:28.222 luup.variable_set:: 23.urn:joeyd-com:serviceId:HoneywellTCC1.getStatus was: Successful now: Unsuccessful. Error code: 5 #hooks:0 2021-03-08 19:26:28.222 luup.variable_set:: 23.urn:joeyd-com:serviceId:HoneywellTCC1.t.6.refreshStatus was: now: FAIL: Mon, Mar 08, 07:26 PM #hooks:0 2021-03-08 19:43:47.581 luup.variable_set:: 23.urn:joeyd-com:serviceId:HoneywellTCC1.t.7.refreshStatus was: now: #hooks:0 2021-03-08 19:43:47.582 luup.variable_set:: 23.urn:joeyd-com:serviceId:HoneywellTCC1.statusRefreshDateTime was: Mon, Mar 08, 07:26:28 PM now: Mon, Mar 08, 07:43:47 PM #Not one, but TWO, 15+ minute discontinuities, which Reactor spots has happened...
2021-03-08 19:46:05.991 luup_log:6: Reactor: ***** SYSTEM CLOCK HAS LEAPT FORWARDS! Last master tick 1615226880(2021-03-08.19:08:00), now 1615229165(2021-03-08.19:46:05)???I cannot think what might cause this, other than some event external to the system.
I do note, however, that your Honeywell devices are very, very chatty in the logs. Is that normal? Also, what might
Error code: 5mean? -
@toggledbits @akbooer
This evening I restore my backup (image) on my RP4, but the problem was not solved yet! I checked what I had edit last week. Last week I was playing a bit with switchboard. I installed this plugin on both machines (vera and openluup). On my vera I had created two virtual switches. The Switchboard plugin on both machines (Vera and Openluup) caused problem. After removing switchboard on openluup everything runs like a charm again !! -
It would be really helpful if I could get a log file from you which might highlight the problem. I've not come across this difficulty myself, nor (yet) had any other reports. Has anything else changed in your system?
Does the system remain up sufficiently long for you to get the logs and also revert? You can revert to any version manually by retrieving the files in the openLuup folder from the openLuup project in GitHub:
History for openLuup - akbooer/openLuup
a pure-Lua open-source emulation of the Vera Luup environment - History for openLuup - akbooer/openLuup
I've fallen out of the habit of tagging releases, so there's not a sufficiently recent one that you can revert to automatically.
I really would like to get to the root of this problem, though, rather than just trying to avoid it.
-
It looks like the problem has been resolved. It turned out to be the Honeywell plugin that caused problems. Honeywell's server was unreachable. Honeywell plugin on google home did not work either. Now everything works perfectly . Thanks everyone for the help
