Well, that may be true for you, but as we've seen with the Cyberpunk 2077 launch, different systems seem to yield different results. 
Q
Quixote
@Quixote
I'm sure this has been asked, and answered, but damned if I can figure it out
Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage.
Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts.
After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!)
What I would like is for the 3 minute delay until the lights go off to start from the latest door open event.
That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity.
I've tried 'hacking' with a virtual switch, but can't seem to stop the delay.
Any pointers?
TIA
C
Just for the record, in case anyone is following, I'm really rather impressed.
I have installed one of these:
https://www.amazon.co.uk/dp/B0B6P22YJC?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1
That's connected (physically) to the VM running on my Synology, with a 2m USB extension.
The same host also runs Openluup, Mosquito, HA Bridge.
Yesterday I installed Zigbee2mqtt. That was a bit of a PITA but mostly because of ports and permissions.
Once up and running, and the correct boxes ticked, immediately visible in Home Assistant via the MQTT integration, and thence into Reactor
I've only got two devices. I bought the cheapest sensor I could find, which is a door sensor. Dead easy to add to ZIgbee2mqtt and again, immediately visible in HA.
https://www.amazon.co.uk/dp/B0FPQLWRW1?ref=ppx_yo2ov_dt_b_fed_asin_title
The dongle is on the top floor of the house, and I wanted the sensor on the back door (just about as far apart as it's possible to get short of going into the garage) When I moved the sensor downstairs it dropped out pretty instantly (which wasn't a huge surprise) so quick bit of research found out that smart plugs will act as routers so...
https://www.amazon.co.uk/dp/B0FDQDPGBB?ref=ppx_yo2ov_dt_b_fed_asin_title
Took me about 30 seconds to connect. Updated the name. Instantly visible in Reactor with the new name pushed over from Zigbee2mqtt.
And lo, the door sensor now has a signal of 140 and works as far as I can tell perfectly and instantly (unlike my z-wave one).
A few more of those will be purchased and used to replace the Tuya wifi cloud devices and the (continually failing) Z-wave plugs (yeah, they were TKB so....)
Commended to the house. Thanks for everyone that got me on the right lines.
C
Hello oh great ones.
After a couple of hours messing with ports and permissions I have Zigbee2mqtt installed and running on my virtual pi
Can connect to the front end and everything
Odd one though, simply cannot get systemctl to work and the error is, well, unhelpful. The service file is this:
[Unit]
Description=zigbee2mqtt
After=network.target
[Service]
Environment=NODE_ENV=production
Type=notify
ExecStart=/usr/local/bin/node index.js
WorkingDirectory=/opt/zigbee2mqtt
StandardOutput=inherit
# Or use StandardOutput=null if you don't want Zigbee2MQTT messages filling syslog, for more options see systemd.exec(5)
StandardError=inherit
WatchdogSec=10s
Restart=always
RestartSec=10s
User=pi
[Install]
WantedBy=multi-user.target
Straight out of the docs with the change to point to my local node install (which we know works as it's the same as the very fine Reactor is using.
Running manually pnpm start
in /opt/zigbee2mqtt works fine
However:
catman@openluup:/etc/systemd/system$ sudo systemctl start zigbee2mqtt.service
Job for zigbee2mqtt.service failed because the control process exited with error code.
See "systemctl status zigbee2mqtt.service" and "journalctl -xe" for details.
Which I have
catman@openluup:/etc/systemd/system$ sudo systemctl status zigbee2mqtt.service
● zigbee2mqtt.service - zigbee2mqtt
Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2025-12-16 12:32:42 GMT; 4s ago
Process: 3093 ExecStart=/usr/local/bin/node index.js (code=exited, status=217/USER)
Main PID: 3093 (code=exited, status=217/USER)
and
-- A start job for unit zigbee2mqtt.service has begun execution.
--
-- The job identifier is 17477.
Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed to determine user credentials: No such process
Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed at step USER spawning /usr/local/bin/node: No such process
-- Subject: Process /usr/local/bin/node could not be executed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The process /usr/local/bin/node could not be executed and failed.
--
-- The error number returned by this process is ERRNO.
Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=217/USER
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit zigbee2mqtt.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 217.
Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit zigbee2mqtt.service has entered the 'failed' state with result 'exit-code'.
Dec 16 12:35:16 openluup systemd[1]: Failed to start zigbee2mqtt.
-- Subject: A start job for unit zigbee2mqtt.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit zigbee2mqtt.service has finished with a failure.
Which strikes me as very odd.
Any blindingly obvious things I'm missing?
TIA!
C
Obviously a quiet forum, but perhaps it's time
I'm looking at rolling Zigbee into my system, in large part for the Aqara FP300 presence sensors which seem to finally provide a solution to if the wasp is actually in the box.
My current set up is as follows:
One Debian VM on Synology NAS running:
Z-wave Server
Open Luup
Multi system reactor
HA bridge
Mosquito MQQT broker
This machine has a UZB Z-wave stick connected via the USB port on the NAS
Another HAOS VM on the same NAS running HAOS
I've got some older Z-wave stuff that I keep around until it fails.
I have some Tuya stuff integrated in HA
My thought was to get either a SMLIGHT SLZB-06M
or an Aqara Hub M2
Integrate them via Zigbee2MQQT (running on the Debian machine) and then expose them in HA so I can continue to automate in MSR.
Thoughts on which of those devices wold be preferable long term. Both are POE capable which is good. It also appears I could add a USB dongle to the NAS and expose it to the HAOS machine.
Any thoughts from the assembled experts here? TIA
C
Another question to the hive mind. Prompted by the fact that I lost yet another z-wave device over the weekend due to a power issue. It looks like z-way server is reporting another device failed (although it's working fine) and message queue is far too long IMHO. Also the failed device has been removed in the expert interface, but still there in the 'normal' one. Sigh.
Currently I have z-wave, Tuya, thinking about Zigbee.... Does anyone use one single protocol for everything? Right now I'm feeling that as the z-wave stuff dies, I'm just gonna replace it with something else....
C
Not really Smart Home stuff, but going to ask as we have smart people...
Bear with me on this one. Asking here because of the font of knowledge!
For many eek years I have had a Virgin V6 box and a Raspberry Pi running Kodi connected to my TV through a cheap *** HDMI switch. It all worked beautifully but the absolutely critical thing was that the TV remote passed the signals back to the Pi to allow remote control of Kodi.
Couple of changes of late:
Installed a soundbar on the TV using the ARC (audio return channel). That then turns the soundbar on and off when the TV turns on and off and the TV volume control controls the soundbar volume direct.
Everything continues to work
Upgraded the software of the Tivo box to Virgin 360. This is literally software only. You get sent a snacky new Bluetooth remote hit 'upgrade' on the screen and off it goes.
Now, things are not playing well. Typically when I turn on to watch Kodi the soundbar comes on (as it should) but the TV either puts out sound through its own speakers and the soundbar, or just the soundbar. It's not possible to control the volume of the soundbar through the TV. Also it's not longer possible to control Kodi using the TV remote.
If I turn the TV360 box off, i.e. power it down, before turning on to watch Kodi, everything is fine.
This makes little to no sense to me. My assumption is that the cheap *** HDMI switch is getting something from the TV360 connection that it didn't used to get when the software was Tivo and that's screwing up the HDMI communications. I'm upgrading the switch to something a little less chap, but wondered if anyone could validate my theory at all?
TIA
C
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179
Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day.
"What did you do to trigger it?" Literally nothing, just walked away and returned and there it was.
Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer.
I'll try to grab some logs here shortly.
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all.
From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only.
Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again...
Installation method
Home Assistant Container
Core
2025.7.3
Frontend
20250702.3
nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR
Any help would be greatly appreciated
Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config
NODE_PATH /opt/reactor:/opt/reactor/node_modules
[latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node
[latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined)
[latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage
[latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules
[latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300
[latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141
[latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8
[latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US
[latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM"
[latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326
[latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312
[latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141
[latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279
[latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314
[latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251
[latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253
[latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318
[latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283
[latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141
[latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258
[latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328
[latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323
[latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292
[latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325
[latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328
[latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328
[latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138
[latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141
[latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325
[latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268
[latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323
[latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092
[latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-]
FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason:
at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11)
at ClientRequest.emit (node:events:508:28)
at ClientRequest.emit (node:domain:489:12)
at emitErrorEvent (node:_http_client:108:11)
at TLSSocket.socketErrorListener (node:_http_client:575:5)
at TLSSocket.emit (node:events:508:28)
at TLSSocket.emit (node:domain:489:12)
at emitErrorNT (node:internal/streams/destroy:170:8)
at emitErrorCloseNT (node:internal/streams/destroy:129:3)
at processTicksAndRejections (node:internal/process/task_queues:89:21
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.
Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions;
Fix an error in OWMWeatherController that could cause it to stop updating;
Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later;
Improve error detail in messages for EzloController during auth phase;
Add isRuleSet() and isRuleEnabled() functions to expressions extensions;
Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases);
Fix a place in the UI where 24-hour time was not being displayed.
Posts
-
New to the forum -
New to the forumI had no idea you had put so much effort into this. I'll give it one last try.
You didn't take my time -- I took my own. We were trying something unconventional and I knew that even before attempting this, so don't worry about it. Sorry if I was snarky but it seems like everything I've been trying relating to HA in the last year or so has gone dreadfully wrong.
I'll try it out when I feel up to it and let you know how things go.
Thanks -
New to the forumI'm not an idiot, and I've installed and worked on several complicated systems, both hard and software related, but it seems that I have some sort of technological curse. I'm not even kidding -- I can follow directions to the tee without a single deviation, it will fuck up. Ok, so I misspelled "openLuup" once, but I assure you, I've been super attentive to every instruction and somehow things just aren't gelling. I understand case-sensitive commands, etc.
I wish I were a Linux nerd. Too bad gaming pulled me into Micro$oft Winblows as a kid. It is what it is.
So, I've literally followed "the idiot proof" instructions, changed my Linux distribution according to instruction, reinstalled multiple times, ... I guess that's it then?
I'm sorry for taking up so much of you guys' time.
-
New to the forumah shit. I see it now.
Think I'm just worn down at this point. That''s embarrassing. -
New to the forum@akbooer Sorry... I'm just kind of at the end of my rope here, other stuff included. My apologies.
So please explain to me how I misspelled openLuup when I've been meticulously spelling it over and over like literally hundreds of times in the last week or two. I must be losing it. Perhaps a sign for me to take up another hobby?
-
New to the forum@akbooer
Can't even get a f*****g image to display here. I think I'm about done here.
-
New to the forumYes, multiple times. Like, multi multi times.
-
New to the forumWelp, I'm not getting anywhere with this. I tried installing over my previous install once again and then navigating to the address provided (http://172.31.206.111:3480/data_request?id=altui ). If anything, things are getting worse. The openLuup page is no longer formatted properly and lacks the graphic element that was there the first time around.
Here's my latest log:2020-12-14 01:54:34.563 :: openLuup LOG ROTATION :: (runtime 0.0 days) 2020-12-14 01:54:34.563 openLuup.init:: init phase completed 2020-12-14 01:54:34.563 openLuup.io.server:: starting HTTP:3480 server on port: 3480 tcp{server}: 0x557ccbcb5a68 2020-12-14 01:54:34.563 openLuup.io.server:: starting SMTP server on port: 2525 tcp{server}: 0x557ccbd381c8 2020-12-14 01:54:34.563 openLuup.io.server:: starting POP3 server on port: 11011 tcp{server}: 0x557ccbd141c8 2020-12-14 01:54:34.563 openLuup.historian:: starting data historian 2020-12-14 01:54:34.563 openLuup.historian:: using memory cache size (per-variable): 1024 2020-12-14 01:54:34.563 openLuup.scheduler:: starting 2020-12-14 01:54:34.563 openLuup.scheduler:: [2] openLuup device startup 2020-12-14 01:54:34.563 luup_log:2: v20.5.22 2020-12-14 01:54:34.563 luup_log:2: sync in 85.4 s 2020-12-14 01:54:34.563 luup.variable_watch:: callback=housemode_watcher, watching=2.openLuup.HouseMode 2020-12-14 01:54:34.563 luup.register_handler:: global_function_name=openLuup_email, request=openLuup@openLuup.local 2020-12-14 01:54:34.563 luup.register_handler:: global_function_name=openLuup_images, request=images@openLuup.local 2020-12-14 01:54:34.564 luup.register_handler:: global_function_name=openLuup_events, request=events@openLuup.local 2020-12-14 01:54:34.564 luup.register_handler:: global_function_name=openLuup_mailbox, request=mail@openLuup.local 2020-12-14 01:54:34.564 luup.chdev.append:: [AltAppStore] Alternate App Store 2020-12-14 01:54:34.564 luup.chdev.sync:: [2] openLuup, syncing children 2020-12-14 01:54:34.564 luup_log:2: 1Mb, 0%cpu, 0.0days 2020-12-14 01:54:34.564 openLuup.scheduler:: [2] openLuup device startup completed: status=true, msg=sync in 85.4 s, name=L_openLuup 2020-12-14 01:54:34.564 openLuup.scheduler:: [3] Alternate App Store device startup 2020-12-14 01:54:34.564 luup_log:3: AltAppStore : starting... 2020-12-14 01:54:34.564 luup.variable_set:: 3.urn:upnp-org:serviceId:altui1.DisplayLine1 was: EMPTY now: AltAppStore #hooks:0 2020-12-14 01:54:34.564 luup.variable_set:: 3.urn:upnp-org:serviceId:altui1.DisplayLine2 was: EMPTY now: #hooks:0 2020-12-14 01:54:34.564 luup.variable_set:: 3.urn:upnp-org:serviceId:AltAppStore1.Version was: EMPTY now: v20.3.30 #hooks:0 2020-12-14 01:54:34.564 luup_log:3: AltAppStore : v20.3.30 2020-12-14 01:54:34.564 luup.set_failure:: status = 0 2020-12-14 01:54:34.564 luup.variable_set:: 3.urn:micasaverde-com:serviceId:HaDevice1.CommFailure was: EMPTY now: 0 #hooks:0 2020-12-14 01:54:34.564 luup.variable_set:: 3.urn:micasaverde-com:serviceId:HaDevice1.CommFailureTime was: EMPTY now: 0 #hooks:0 2020-12-14 01:54:34.564 openLuup.scheduler:: [3] Alternate App Store device startup completed: status=true, msg=OK, name=AltAppStore 2020-12-14 01:56:00.050 luup_log:2: synchronising to on-the-minute 2020-12-14 01:56:00.050 luup.call_timer:: interval: time=2m, days={} 2020-12-14 01:56:00.050 luup_log:2: 2 minute timer launched 2020-12-14 01:56:00.050 luup_log:2: 2Mb, 0%cpu, 0.0days 2020-12-14 01:57:09.812 openLuup.io.server:: HTTP:3480 connection from 172.31.192.1 tcp{client}: 0x557ccbe5faf8 2020-12-14 01:57:09.814 openLuup.server:: GET / HTTP/1.1 tcp{client}: 0x557ccbe5faf8 2020-12-14 01:57:09.814 openLuup.server:: request completed (194 bytes, 0 chunks, 0 ms) tcp{client}: 0x557ccbe5faf8 2020-12-14 01:57:10.466 openLuup.server:: GET /data_request?id=lr_ALTUI_Handler&command=home HTTP/1.1 tcp{client}: 0x557ccbe5faf8 2020-12-14 01:57:10.466 openLuup.servlet:: No handler for data_request?id=lr_ALTUI_Handler 2020-12-14 01:57:10.466 openLuup.server:: request completed (153 bytes, 0 chunks, 0 ms) tcp{client}: 0x557ccbe5faf8 2020-12-14 01:57:10.524 openLuup.server:: GET /favicon.ico HTTP/1.1 tcp{client}: 0x557ccbe5faf8 2020-12-14 01:57:10.524 openLuup.servlet:: file not found:favicon.ico 2020-12-14 01:57:10.525 openLuup.server:: request completed (126 bytes, 0 chunks, 0 ms) tcp{client}: 0x557ccbe5faf8 2020-12-14 01:58:00.133 luup_log:0: 2Mb, 0%cpu, 0.0days 2020-12-14 01:58:24.472 openLuup.server:: GET /data_request?id=altui HTTP/1.1 tcp{client}: 0x557ccbe5faf8 2020-12-14 01:58:24.473 luup.call_action:: 3.urn:upnp-org:serviceId:AltAppStore1.update_plugin 2020-12-14 01:58:24.473 luup_log:3: AltAppStore : starting <run> phase... 2020-12-14 01:58:24.473 luup_log:3: AltAppStore : downloading amg0/ALTUI [master] to trash/AltAppStore/ 2020-12-14 01:58:24.473 luup_log:3: AltAppStore : GitHub request: https://api.github.com/repos/amg0/ALTUI/contents?ref=master 2020-12-14 01:58:25.268 luup_log:3: AltAppStore : GitHub request: https://api.github.com/repos/amg0/ALTUI/contents/blockly?ref=master 2020-12-14 01:58:25.678 luup_log:3: AltAppStore : getting contents of version: master 2020-12-14 01:58:25.678 luup.variable_set:: 3.urn:upnp-org:serviceId:altui1.DisplayLine1 was: AltAppStore now: Downloading... #hooks:0 2020-12-14 01:58:25.678 luup.variable_set:: 3.urn:upnp-org:serviceId:altui1.DisplayLine2 was: now: Alternate UI #hooks:0 2020-12-14 01:58:25.678 luup_log:3: AltAppStore : scheduling <job> phase... 2020-12-14 01:58:25.678 openLuup.requests:: 2020-12-14 01:58:25.678 openLuup.server:: request completed (0 bytes, 0 chunks, 1205 ms) tcp{client}: 0x557ccbe5faf8 2020-12-14 01:58:30.958 luup_log:3: AltAppStore : starting <job> phase... 2020-12-14 01:58:30.958 luup_log:3: AltAppStore : download failed, status: wantread 2020-12-14 01:58:30.958 luup.variable_set:: 3.urn:upnp-org:serviceId:altui1.DisplayLine2 was: Alternate UI now: Alternate UI failed #hooks:0 2020-12-14 01:59:56.243 openLuup.io.server:: HTTP:3480 connection closed EXPIRED tcp{client}: 0x557ccbe5faf8 2020-12-14 02:00:00.051 luup_log:0: 2Mb, 0.1%cpu, 0.0days 2020-12-14 02:02:00.110 luup_log:0: 2Mb, 0%cpu, 0.0days 2020-12-14 02:04:00.062 luup_log:0: 3Mb, 0%cpu, 0.0days 2020-12-14 02:06:00.116 luup_log:0: 2Mb, 0%cpu, 0.0days 2020-12-14 02:07:33.504 openLuup.io.server:: HTTP:3480 connection from 172.31.192.1 tcp{client}: 0x557ccbe8a1f8 2020-12-14 02:07:33.504 openLuup.server:: GET / HTTP/1.1 tcp{client}: 0x557ccbe8a1f8 2020-12-14 02:07:33.504 openLuup.server:: request completed (194 bytes, 0 chunks, 0 ms) tcp{client}: 0x557ccbe8a1f8 2020-12-14 02:07:33.575 openLuup.server:: GET /data_request?id=lr_ALTUI_Handler&command=home HTTP/1.1 tcp{client}: 0x557ccbe8a1f8 2020-12-14 02:07:33.576 openLuup.servlet:: No handler for data_request?id=lr_ALTUI_Handler 2020-12-14 02:07:33.576 openLuup.server:: request completed (153 bytes, 0 chunks, 0 ms) tcp{client}: 0x557ccbe8a1f8 2020-12-14 02:07:33.647 openLuup.server:: GET /favicon.ico HTTP/1.1 tcp{client}: 0x557ccbe8a1f8 2020-12-14 02:07:33.647 openLuup.servlet:: file not found:favicon.ico 2020-12-14 02:07:33.647 openLuup.server:: request completed (126 bytes, 0 chunks, 0 ms) tcp{client}: 0x557ccbe8a1f8 2020-12-14 02:07:33.647 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557ccbe8a1f8 2020-12-14 02:08:00.103 luup_log:0: 2Mb, 0%cpu, 0.0days 2020-12-14 02:08:01.193 openLuup.io.server:: HTTP:3480 connection from 172.31.192.1 tcp{client}: 0x557ccbe949c8 2020-12-14 02:08:01.194 openLuup.server:: GET /openLuup HTTP/1.1 tcp{client}: 0x557ccbe949c8 2020-12-14 02:08:01.194 openLuup.wsapi:: using openLuup/console.lua for openLuup 2020-12-14 02:08:01.196 openLuup.wsapi:: using REQUIRE to load CGI openLuup/console.lua 2020-12-14 02:08:01.206 openLuup.server:: request completed (8063 bytes, 0 chunks, 12 ms) tcp{client}: 0x557ccbe949c8 2020-12-14 02:08:01.819 openLuup.server:: GET /w3.css HTTP/1.1 tcp{client}: 0x557ccbe949c8 2020-12-14 02:08:01.819 openLuup.server:: request completed (0 bytes, 0 chunks, 0 ms) tcp{client}: 0x557ccbe949c8 2020-12-14 02:08:01.821 openLuup.server:: GET /icons/openLuup.svg HTTP/1.1 tcp{client}: 0x557ccbe949c8 2020-12-14 02:08:01.821 openLuup.server:: request completed (458 bytes, 0 chunks, 0 ms) tcp{client}: 0x557ccbe949c8 2020-12-14 02:08:01.821 openLuup.io.server:: HTTP:3480 connection from 172.31.192.1 tcp{client}: 0x557ccbeddd88 2020-12-14 02:08:06.822 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557ccbeddd88 2020-12-14 02:08:13.090 openLuup.server:: GET /openLuup?page=log HTTP/1.1 tcp{client}: 0x557ccbe949c8@therealdb What is the difference between Windows Terminal and PowerShell? Are you suggesting that I type my commands into Terminal instead of Ubuntu Bash?
Thanks
-
New to the forum@therealdb but that's literally what I just did. What would be the changing factor?
-
New to the forumOk, this is getting ridiculous.
I uninstalled Kali as a Windows app, installed Ubuntu 20.04 LTS instead, reinstalled Lua 5.1 and all dependencies, reinstalled openLuup.
After all that, I try to open http://172.22.154.28:3480 as prompted and get nothing but "No handler for data_request?id=lr_ALTUI_Handler" at the top of the page.
aaaarrrrgh!!! No idea what I could be doing wrong here. -
New to the forum@akbooer Thanks!
I imagine that will be quite easy from my past experience (with Lua for Windows, I mean). My worry is only that running plugins, etc. may not translate well when ported from a Linux/Unix environment. Guess there's only one way to find out! -
New to the forum@therealdb Hi, sorry, could you spell it out for me so that there's no way I'll mess it up? I'd like to delete the files I've installed and wipe the Kali installation before I give this one last go with Ubuntu. I only initially installed Kali because I thought it could come in handy were I to install Wireshark, etc.
Thanks for your assistance -
New to the forum@akbooer Here are the log entries:
2020-12-11 01:16:03.648 openLuup.io.server:: HTTP:3480 connection from 172.19.112.1 tcp{client}: 0x55cdaf32ae08 2020-12-11 01:16:03.649 openLuup.server:: POST /openLuup? HTTP/1.1 tcp{client}: 0x55cdaf32ae08 2020-12-11 01:16:03.649 luup.call_action:: 3.urn:upnp-org:serviceId:AltAppStore1.update_plugin 2020-12-11 01:16:03.649 luup_log:3: AltAppStore : starting <run> phase... 2020-12-11 01:16:03.650 luup_log:3: AltAppStore : downloading amg0/ALTUI [master] to trash/AltAppStore/ 2020-12-11 01:16:03.650 luup_log:3: AltAppStore : GitHub request: https://api.github.com/repos/amg0/ALTUI/contents?ref=master 2020-12-11 01:16:12.565 luup_log:3: AltAppStore : GitHub request: https://api.github.com/repos/amg0/ALTUI/contents/blockly?ref=master 2020-12-11 01:16:16.980 luup_log:3: AltAppStore : getting contents of version: master 2020-12-11 01:16:16.980 luup.variable_set:: 3.urn:upnp-org:serviceId:altui1.DisplayLine1 was: Downloading... now: Downloading... #hooks:0 2020-12-11 01:16:16.980 luup.variable_set:: 3.urn:upnp-org:serviceId:altui1.DisplayLine2 was: Alternate UI failed now: Alternate UI #hooks:0 2020-12-11 01:16:16.982 luup_log:3: AltAppStore : scheduling <job> phase... 2020-12-11 01:16:16.982 openLuup.requests:: 2020-12-11 01:16:16.983 openLuup.server:: request completed (16694 bytes, 0 chunks, 13334 ms) tcp{client}: 0x55cdaf32ae08 2020-12-11 01:16:24.034 luup_log:3: AltAppStore : starting <job> phase... 2020-12-11 01:16:24.034 luup_log:3: AltAppStore : download failed, status: wantread 2020-12-11 01:16:24.034 luup.variable_set:: 3.urn:upnp-org:serviceId:altui1.DisplayLine2 was: Alternate UI now: Alternate UI failed #hooks:0 2020-12-11 01:16:24.034 openLuup.server:: GET /openLuup?page=devices HTTP/1.1 tcp{client}: 0x55cdaf32ae08 2020-12-11 01:16:24.035 openLuup.server:: request completed (9499 bytes, 0 chunks, 1 ms) tcp{client}: 0x55cdaf32ae08 2020-12-11 01:16:24.379 openLuup.server:: GET /icons/zwave_default.png HTTP/1.1 tcp{client}: 0x55cdaf32ae08 2020-12-11 01:16:24.379 openLuup.server:: request completed (0 bytes, 0 chunks, 0 ms) tcp{client}: 0x55cdaf32ae08 2020-12-11 01:16:24.379 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55cdaf32ae08 2020-12-11 01:16:29.954 openLuup.io.server:: HTTP:3480 connection from 172.19.112.1 tcp{client}: 0x55cdaf4dbe78 2020-12-11 01:16:29.955 openLuup.server:: GET /openLuup?page=log HTTP/1.1 tcp{client}: 0x55cdaf4dbe78Yes, this setup is showing itself to be quite problematic. I'll try for a while longer before giving up. That would be really disappointing. I was getting really hyped to get back into automating things around here, and Alexa routines just don't cut it.
-
New to the forum@therealdb thank you, I'll try that.
@akbooer The download fails every time. It'll hit 3%, maybe 12% once, then fail.
Sorry, but WSL is my only option at present. I did have the VeraBridge functioning (at least in part) because I could see devices from the Vera in openLuup. Don't ask me what the heck happened overnight the other night, though! I swear, I have some sort of technology curse!!
How about using the github repository with the icon? Is that possible and how?
Thanks -
New to the forum@akbooer I have no idea about configuring WSL in Windows. All I did was install it along with Kali Linux, and then Lua 5.1 and the other dependencies from the Bash prompt. I'm guessing that therealdb would probably have mentioned any setup procedures specific to this particular arrangement that I may have missed, but it seemed fairly straightforward. Here are the logs:
logs/LuaUPnP_startup.log 2020-12-10 05:10:17.519 :: openLuup STARTUP :: /etc/cmh-ludl 2020-12-10 05:10:17.519 openLuup.init:: version 2020.05.01 @akbooer 2020-12-10 05:10:17.527 openLuup.scheduler:: version 2020.01.25 @akbooer 2020-12-10 05:10:17.531 openLuup.wsapi:: version 2019.08.12 @akbooer 2020-12-10 05:10:17.531 openLuup.servlet:: version 2020.01.29 @akbooer 2020-12-10 05:10:17.531 openLuup.client:: version 2019.10.14 @akbooer 2020-12-10 05:10:17.532 openLuup.io:: version 2019.11.29 @akbooer 2020-12-10 05:10:17.532 openLuup.server:: version 2020.03.20 @akbooer 2020-12-10 05:10:17.533 openLuup.scenes:: version 2020.03.16 @akbooer 2020-12-10 05:10:17.534 openLuup.chdev:: version 2020.03.07 @akbooer 2020-12-10 05:10:17.534 openLuup.userdata:: version 2020.03.31 @akbooer 2020-12-10 05:10:17.534 openLuup.requests:: version 2020.04.15 @akbooer 2020-12-10 05:10:17.535 openLuup.gateway:: version 2020.03.08 @akbooer 2020-12-10 05:10:17.535 openLuup.smtp:: version 2018.04.12 @akbooer 2020-12-10 05:10:17.536 openLuup.historian:: version 2020.02.12 @akbooer 2020-12-10 05:10:17.536 openLuup.luup:: version 2020.03.21 @akbooer 2020-12-10 05:10:17.537 openLuup.pop3:: version 2018.04.23 @akbooer 2020-12-10 05:10:17.537 openLuup.compression:: version 2016.06.30 @akbooer 2020-12-10 05:10:17.537 openLuup.timers:: version 2019.05.03 @akbooer 2020-12-10 05:10:17.537 openLuup.logs:: version 2018.03.25 @akbooer 2020-12-10 05:10:17.537 openLuup.json:: version 2020.05.20 @akbooer 2020-12-10 05:10:17.537 openLuup.init:: Cjson not installed - using openLuup.json.Lua.decode() instead 2020-12-10 05:10:17.548 luup.create_device:: [1] D_ZWaveNetwork.xml / I_ZWave.xml / (urn:schemas-micasaverde-com:device:ZWaveNetwork:1) 2020-12-10 05:10:17.552 luup.create_device:: [2] D_openLuup.xml / I_openLuup.xml / D_openLuup.json (openLuup) 2020-12-10 05:10:17.552 openLuup.init:: loading configuration user_data.json 2020-12-10 05:10:17.552 openLuup.userdata:: loading user_data json... 2020-12-10 05:10:17.553 luup.variable_set:: 2.openLuup.HouseMode was: EMPTY now: 1 #hooks:0 2020-12-10 05:10:17.553 openLuup.userdata:: loading rooms... 2020-12-10 05:10:17.553 openLuup.userdata:: ...room loading completed 2020-12-10 05:10:17.553 openLuup.userdata:: loading devices... 2020-12-10 05:10:17.554 luup.create_device:: [1] D_ZWaveNetwork.xml / I_ZWave.xml / (urn:schemas-micasaverde-com:device:ZWaveNetwork:1) 2020-12-10 05:10:17.557 luup.create_device:: [3] D_AltAppStore.xml / I_AltAppStore.xml / D_AltAppStore.json (urn:schemas-upnp-org:device:AltAppStore:1) 2020-12-10 05:10:17.557 openLuup.userdata:: loading scenes... 2020-12-10 05:10:17.557 openLuup.userdata:: number of scenes = 0 2020-12-10 05:10:17.557 openLuup.userdata:: ...scene loading completed 2020-12-10 05:10:17.557 openLuup.userdata:: loading installed plugin info... 2020-12-10 05:10:17.557 openLuup.userdata:: [openLuup] openLuup (20.5.22) 2020-12-10 05:10:17.557 openLuup.userdata:: [AltAppStore] Alternate App Store (20.3.30) 2020-12-10 05:10:17.557 openLuup.userdata:: [VeraBridge] VeraBridge (not.installed) 2020-12-10 05:10:17.557 openLuup.userdata:: [8246] Alternate UI (not.installed) 2020-12-10 05:10:17.557 openLuup.userdata:: [Z-Way] Z-Way (not.installed) 2020-12-10 05:10:17.557 openLuup.userdata:: [Arduino] MySensors (not.installed) 2020-12-10 05:10:17.557 openLuup.userdata:: ...user_data loading completed 2020-12-10 05:10:17.557 openLuup.init:: running _openLuup_STARTUP_ 2020-12-10 05:10:17.557 luup_log:0: startup code completed 2020-12-10 05:10:17.557 openLuup.init:: init phase completed 2020-12-10 05:10:17.557 :: openLuup LOG ROTATION :: (runtime 0.0 days)logs/LuaUPnP.log 2020-12-10 05:10:17.557 :: openLuup LOG ROTATION :: (runtime 0.0 days) 2020-12-10 05:10:17.557 openLuup.init:: init phase completed 2020-12-10 05:10:17.557 openLuup.io.server:: starting HTTP:3480 server on port: 3480 tcp{server}: 0x55cccfabb738 2020-12-10 05:10:17.557 openLuup.io.server:: starting SMTP server on port: 2525 tcp{server}: 0x55cccfb272f8 2020-12-10 05:10:17.557 openLuup.io.server:: starting POP3 server on port: 11011 tcp{server}: 0x55cccfa9c848 2020-12-10 05:10:17.557 openLuup.historian:: starting data historian 2020-12-10 05:10:17.557 openLuup.historian:: using memory cache size (per-variable): 1024 2020-12-10 05:10:17.557 openLuup.scheduler:: starting 2020-12-10 05:10:17.557 openLuup.scheduler:: [2] openLuup device startup 2020-12-10 05:10:17.557 luup_log:2: v20.5.22 2020-12-10 05:10:17.557 luup_log:2: sync in 102.4 s 2020-12-10 05:10:17.558 luup.variable_watch:: callback=housemode_watcher, watching=2.openLuup.HouseMode 2020-12-10 05:10:17.558 luup.register_handler:: global_function_name=openLuup_email, request=openLuup@openLuup.local 2020-12-10 05:10:17.558 luup.register_handler:: global_function_name=openLuup_images, request=images@openLuup.local 2020-12-10 05:10:17.558 luup.register_handler:: global_function_name=openLuup_events, request=events@openLuup.local 2020-12-10 05:10:17.558 luup.register_handler:: global_function_name=openLuup_mailbox, request=mail@openLuup.local 2020-12-10 05:10:17.558 luup.chdev.append:: [AltAppStore] Alternate App Store 2020-12-10 05:10:17.558 luup.chdev.sync:: [2] openLuup, syncing children 2020-12-10 05:10:17.558 luup_log:2: 2Mb, 0%cpu, 0.0days 2020-12-10 05:10:17.558 openLuup.scheduler:: [2] openLuup device startup completed: status=true, msg=sync in 102.4 s, name=L_openLuup 2020-12-10 05:10:17.558 openLuup.scheduler:: [3] Alternate App Store device startup 2020-12-10 05:10:17.558 luup_log:3: AltAppStore : starting... 2020-12-10 05:10:17.558 luup.variable_set:: 3.urn:upnp-org:serviceId:altui1.DisplayLine1 was: AltAppStore now: AltAppStore #hooks:0 2020-12-10 05:10:17.558 luup.variable_set:: 3.urn:upnp-org:serviceId:altui1.DisplayLine2 was: now: #hooks:0 2020-12-10 05:10:17.558 luup_log:3: AltAppStore : v20.3.30 2020-12-10 05:10:17.558 luup.set_failure:: status = 0 2020-12-10 05:10:17.558 luup.variable_set:: 3.urn:micasaverde-com:serviceId:HaDevice1.CommFailure was: 0 now: 0 #hooks:0 2020-12-10 05:10:17.558 luup.variable_set:: 3.urn:micasaverde-com:serviceId:HaDevice1.CommFailureTime was: 0 now: 0 #hooks:0 2020-12-10 05:10:17.558 openLuup.scheduler:: [3] Alternate App Store device startup completed: status=true, msg=OK, name=AltAppStore 2020-12-10 05:10:17.816 openLuup.io.server:: HTTP:3480 connection from 172.19.112.1 tcp{client}: 0x55cccfa9e8f8 2020-12-10 05:10:17.817 openLuup.server:: GET /w3.css HTTP/1.1 tcp{client}: 0x55cccfa9e8f8 2020-12-10 05:10:17.817 openLuup.server:: request completed (23661 bytes, 2 chunks, 0 ms) tcp{client}: 0x55cccfa9e8f8 2020-12-10 05:10:17.820 openLuup.server:: GET /icons/openLuup.svg HTTP/1.1 tcp{client}: 0x55cccfa9e8f8 2020-12-10 05:10:17.820 openLuup.server:: request completed (458 bytes, 0 chunks, 0 ms) tcp{client}: 0x55cccfa9e8f8 2020-12-10 05:10:17.821 openLuup.io.server:: HTTP:3480 connection from 172.19.112.1 tcp{client}: 0x55cccfaade28 2020-12-10 05:10:23.085 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55cccfaade28 2020-12-10 05:10:29.799 openLuup.server:: GET /openLuup?page=system HTTP/1.1 tcp{client}: 0x55cccfa9e8f8 2020-12-10 05:10:29.799 openLuup.wsapi:: using openLuup/console.lua for openLuup 2020-12-10 05:10:29.799 openLuup.wsapi:: using REQUIRE to load CGI openLuup/console.lua 2020-12-10 05:10:29.807 openLuup.server:: request completed (11022 bytes, 0 chunks, 7 ms) tcp{client}: 0x55cccfa9e8f8 2020-12-10 05:12:00.085 luup_log:2: synchronising to on-the-minute 2020-12-10 05:12:00.085 luup.call_timer:: interval: time=2m, days={} 2020-12-10 05:12:00.085 luup_log:2: 2 minute timer launched 2020-12-10 05:12:00.085 luup_log:2: 3Mb, 0%cpu, 0.0days 2020-12-10 05:12:03.091 openLuup.io.server:: HTTP:3480 connection closed EXPIRED tcp{client}: 0x55cccfa9e8f8 2020-12-10 05:14:00.124 luup_log:0: 2Mb, 0%cpu, 0.0days 2020-12-10 05:15:13.997 openLuup.io.server:: HTTP:3480 connection from 172.19.112.1 tcp{client}: 0x55cccfc0ffa8 2020-12-10 05:15:13.998 openLuup.server:: GET /openLuup?page=startup_log HTTP/1.1 tcp{client}: 0x55cccfc0ffa8 2020-12-10 05:15:13.998 openLuup.server:: request completed (11674 bytes, 0 chunks, 0 ms) tcp{client}: 0x55cccfc0ffa8 2020-12-10 05:16:00.088 luup_log:0: 4Mb, 0%cpu, 0.0days 2020-12-10 05:16:44.180 openLuup.io.server:: HTTP:3480 connection closed EXPIRED tcp{client}: 0x55cccfc0ffa8 2020-12-10 05:17:16.830 openLuup.io.server:: HTTP:3480 connection from 172.19.112.1 tcp{client}: 0x55cccfb14ab8 2020-12-10 05:17:16.831 openLuup.server:: GET /openLuup?page=log HTTP/1.1 tcp{client}: 0x55cccfb14ab8I'm assuming that logs .1 to .5 are just previous sessions being pushed through the line?
Scheduler: Startup
Plugin Startup Jobs CPU usage (in startup order) # date / time device priority status hh:mm:ss.sss job # info notes 1 2020-12-10 05:10:18.058 2 1 Done 0.000 1 plugin: openLuup sync in 102.4 s 2 2020-12-10 05:10:18.058 3 Done 0.000 2 plugin: Alternate App Store OKScheduler: Plugins
Plugin CPU usage (0.0% system load) # device status hh:mm:ss.sss name message 1 2 -1 0.001 openLuup 2 3 -1 0.000 Alternate App StoreServers: http
request #requests status /openLuup 26 200 icons/openLuup.svg 1 200 w3.css 1 200I hope this will help!
-
New to the forumI see nothing running on that port. Also, it still doesn't work even after using "http://172.25.26.14:3480/data_request?id=exit" and attempting to initialize the program again afterwards.
I'm starting to think this may be firewall related, though I'm unsure as to how that would just manifest itself out of nowhere when I had it running fine last week.Update 1: After rebooting, it just gives me this message:
rm: cannot remove '/www/altui/altui*': No such file or directory
and then hangs.Update 2: Ok, so I tried running the install again and it seemed to work, but opening the IP address did not. I went and browsed the web for a good hour and then tried again for the hell of it and, lo and behold -- it worked. It no longer has VeraBridge installed or any devices that I had imported last week. AltUI still refuses to load.
Interesting. -
New to the forumThanks for bearing with me here.
@akbooer said in New to the forum:
Sorry to sound daft, but I have absolutely no idea where you got that file from. What does it contain?
The file "run_openLuup.sh" was the only file I saw with the extension ".sh" in the directory /etc/cmh-ludl. I found the correct file you mentioned, and tried:
sudo ./openLuup_reload
and I get this:lua5.1: openLuup/init.lua:291: openLuup - is another copy already running? Unable to start HTTP server on port 3480
stack traceback:
[C]: in function 'error'
openLuup/init.lua:291: in main chunk
[C]: ?@therealdb Thanks. I'll revisit that once I can get things going again.
-
New to the forumThank you so much for your assistance. I'm sure it can be an eye-rolling experience to help out newbies like me.
You are accurate that loading at boot is not a priority since I often run this machine for weeks art a time before rebooting. I was just trying to start from zero while considering certain factors such as security since I used to rely on my system to text me on my phone (using an email plugin) if something needed my attention.
Definitely not a top priority, so thanks for snapping me back to reality. lol I tend to get side-tracked.
So I tried:
sudo ./run_openLuup.sh
and a get:Starting openLuup server
To see tail of logfile: tail -f ./out.logNavigating to any variation of http://172.25.26.14:3480 fails.
http://172.25.26.14:3480/data_request?id=exit does nothing, either.