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
Looking at using Home Assistant for the first time, either on a Home Assistant Green, their own hardware or buying a cheap second hand mini PC.
Sounds like Home Assistant OS is linux based using Docker for HA etc.
Would I also be able to install things like MSR as well on their OS ? On the same box?
Thanks.
The last of four boards I'm trying in this batch is the Orange Pi 4 LTS. I purchased a 3GB RAM + 16GB eMMC model from Amazon for $83, making it the most costly of the four boards tried, but still well under my US$100 limit.
This board is powered by a Rockchip RK3399-T processor, ARM-compatible with dual Cortex-A72 cores and quad Cortex-A53 cores at 1.6Ghz (1.8Ghz for the 4GB model); compare this to the RPi 3B+ with four Cortex-A53 and the RPi 4B with four Cortex-A72, this board is a hybrid that I would expect to stand in the performance middle between the two RPi models. It's available in 3GB and 4GB DDR4 RAM configurations, with and without 16GB eMMC storage. It has a MicroSDHC slot, gigabit Ethernet, WiFi and BT, two USB 2.0 type A ports, one USB 3.0 type C port, a mini PCIe ribbon-cable connector (requires add-on board for standard connector), two each RPi-compatible camera and LCD ports, HDMI type A, and can be powered (5VDC/3A) via USB-C or DC type C (3.8mm OD/1.1mm ID) jack (center-positive), an odd and perhaps unwelcome departure from the more common type A (5.5mm/2.1mm). A serial port for console/debug can be connected by using a (not included) USB-TTL adapter (3.3V) via pin headers like the Orange Pi Zero 2. The included dual-band antenna connects via U.FL connector to the board, so it's easy substituting for another if you prefer. The manufacturer recommends use of a heat sink (which was included in the box). A metal cooling case is also offered by the manufacturer (a bundle with the metal case and a power supply is sold on Amazon for $90 as of this writing).
The Orange Pi 4 LTS is somewhat longer than the RPi 4B, and although the boards are the same width, the mounting hole placement is different both in length and (oddly) width. Between this and the differences in connector locations, neither board is a drop-in replacecment for the other and their respective cases are not interchangeable. The 26-pin header is a subset of the RPi 4B's 40-pin header, so some HATs for the RPi may work (although the mounting hole differences will make securing them "interesting"), and some HATs will surely not.
Models with eMMC storage have an OS installed and boot immediately with SSH daemon running and ready for login. Mine was running Debian Bullseye, which would probably be fine for most users. It had clearly been on there a while, because it needed a lot of updates, but it's a current distro, so you're running out of the box with something that will last.
A different OS can be installed by downloading an image (once again I chose Ubuntu Jammy) and writing it to a MicroSD card, then booting the system from the SD card. You can either leave the system in that state (running the OS from the SD card), or copy the OS from the SD card to the eMMC. The latter is done by a script; documentation for the process is best described in the downloadable PDF User Manual. This took about 10 minutes and went smoothly, and I was able to boot the system without the SD card after the process completed.
I have lingering questions around the value of the eMMC storage. It's definitely faster than using MicroSD or USB-based storage (I got 311MB/s average on a 4GB write, compared to MicroSD performance around 15MB/s), but it would take a long-term test of this product to determine if the on-board eMMC option has the stamina to take the write counts typical of Linux systems, and if its wear-leveling and error correction are sufficient to assure a long, error-free life. Given the high premium apparently being paid for including eMMC on the board, it should be fast and durable, but only time and experience (perhaps painful) would tell the latter. A careful configuration with other Flash-friendly filesystems could be used to reduce wear, but this is an advanced configuration/cookbook topic and beyond the scope of this writing. This question is also not unique to eMMC — MicroSD cards are also known to fail with high write cycles, so the use of a "high endurance" product is recommended for any and all systems using MicroSD as primary storage. The board has Mini PCIe capability, and that may be a storage alternative, but read on...
Also bear in mind that the eMMC storage is fixed-size forever; it cannot be expanded, and 16GB can run out pretty quickly these days. Users of MicroSD cards for primary storage can upgrade to bigger cards, but when users of eMMC primary storage outgrow it, the only choice is to add a MicroSD card or other "external" storage to the system, move part of the filesystem to it, and then manage both storage devices and deal with the limitations and risks of both.
As I mentioned with the Orange Pi Zero 2, if you are going to use this board as a home automation controller/gateway or similar role, it should (IMO) have a battery-backed real time clock (RTC), and Orange Pi offers an add-on module that connects directly to the 26-pin header on the board. An available expansion board provides a standard Mini PCIe interface and SIM card slot (hmm...), but it connects to the main board via a short ribbon cable, and its mounting holes have no complement on the main board, so it seems like it would be a fragile dangly thing that's a nuisance to deal with.
I want to like this board more, and it's very capable, but I'm concerned about value. The limited options for eMMC (16GB or none), the question mark of the eMMC's longevity vs cost, the strange DC power connector choice, the lack of 40-pin GPIO on a full-size (plus) board, the inconsistent hole placement, and the fragile Mini PCIe arrangement, are all "cons" that devalue this board in my view. The price point is clearly driven by the additional capabilities of the board (camera support, ports, six core CPU, extra RAM, on-board eMMC storage), but unfortunately, a great many of these features may not be useful for home automation, and therefore potentially a waste of money.
In terms of overall value, I still believe the Libre "Le Potato" seems a better choice to me, and the Orange Pi Zero 2 (very) a close second, but I'll admit I'm focused on a particular application and your needs may be better suited to what this board offers than mine.
Passmark Results:
OrangePi 4 LTS
Cortex-A72 (aarch64)
6 cores @ 1200 MHz | 2.9 GiB RAM
Number of Processes: 6 | Test Iterations: 1 | Test Duration: Medium
--------------------------------------------------------------------------
CPU Mark: 583
Integer Math 12037 Million Operations/s
Floating Point Math 2542 Million Operations/s
Prime Numbers 4.5 Million Primes/s
Sorting 3141 Thousand Strings/s
Encryption 153 MB/s
Compression 4049 KB/s
CPU Single Threaded 154 Million Operations/s
Physics 80.5 Frames/s
Extended Instructions (NEON) 244 Million Matrices/s
Memory Mark: 498
Database Operations 551 Thousand Operations/s
Memory Read Cached 2524 MB/s
Memory Read Uncached 2602 MB/s
Memory Write 3182 MB/s
Available RAM 1947 Megabytes
Memory Latency 119 Nanoseconds
Memory Threaded 6243 MB/s
---------------
eMMC storage write 311MB/s average for 4GB; MicroSD (Samsung 32GB class 10) storage write 15MB/s.
With Raspberry Pi boards continuing to be relatively scarce, I've been trying a few alternatives to see what may be usable and good. I had previously written about the Jetson Nano 2GB, which is great, but a little pricey, so I'm trying to find sub-US$100 boards that will run Reactor.
I've got four that I'm trying now, but one in particular goes right to work in the most predictable way and seems worth a mention immediately: the Libre Computer Board AML-S905X-CC 2GB (known as "Le Potato").
The form factor is very similar to that of the Raspberry Pi 3 B+, and has comparable CPU (ARM Cortex-A53, quad 64-bit cores at 1.5+GHz -- slightly higher clock speed). It's US$35 on Amazon and LoverPi in the (recommended) 2GB configuration, and easy to get.
Startup is like RPi: download one of the available OS images (Ubuntu, Raspbian, Debian, ARMbian, etc.) from their site and write the image to a MicroSD card, insert into slot, power up, and off you go. I tried the Ubuntu 22.04 image first and it comes right up. No problem getting nodejs 18.12.1 installed and running (with Reactor).
No WiFi on board, but I don't see that as a minus for use as a controller/hub (which should be hard-wired, IMO). The 40-pin GPIO connector is compatible with typical RPi HATs (PoE, breakouts, etc.).
There is an available eMMC (solid state storage) module to use instead of MicroSD, which I would recommend for long-term use. It runs US$25 for 32GB (64GB and 128GB available). The module is scarcely larger than the chip it carries, and has the smallest board-to-board connector I've ever seen.
Next up: ESPRESSObin 2GB (spoiler: it's... technical...)
Having been messing around with some stuff I worked a way to self trigger some tests that I wanted to do on the HA <> MSR integration
This got me wondering if there's an entity that changes state / is exposed when a configured controller goes off line? I can't see one but thought it might be hidden or something?
Cheers
C
Using build 25328 and having the following users.yaml configuration:
users:
# This section defines your valid users.
admin: *******
groups:
# This section defines your user groups. Optionally, it defines application
# and API access restrictions (ACLs) for the group. Users may belong to
# more than one group. Again, no required or special groups here.
admin_group:
users:
- admin
applications: true # special form allows access to ALL applications
guests:
users: "*"
applications:
- dashboard
api_acls:
# This ACL allows users in the "admin" group to access the API
- url: "/api"
group: admin_group
allow: true
log: true
# This ACL allows anyone/thing to access the /api/v1/alive API endpoint
- url: "/api/v1/alive"
allow: true
session:
timeout: 7200 # (seconds)
rolling: true # activity extends timeout when true
# If log_acls is true, the selected ACL for every API access is logged.
log_acls: true
# If debug_acls is true, even more information about ACL selection is logged.
debug_acls: true
My goal is to allow anonymous user to dashboard, but MSR is still asking for a password when trying to access that. Nothing in the logs related to dashboard access. Probably an error in the configuration, but help needed to find that. Tried to put url: "/dashboard" under api_acls, but that was a long shot and didn't work.
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules.
I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds).
Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off?
With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches.
Thanks
Reactor (Multi-hub) latest-26011-c621bbc7
VirtualEntityController v25356
Synology Docker
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future.
In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level.
Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way.
I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption.
A few other things to know:
If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc.
Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy).
The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON.
You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach).
The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case.
This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change.
This thread is open for any questions or concerns.
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks.
Any chance of a 'bulk delete' option?
No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices
Cheers
C
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.
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
If you’re like me and still running HABridge to control your devices locally via Alexa, you might need to tweak your endpoints to call Reactor via HTTP. Here’s the best way to do it, IMO:
Insert the Reactor Canonical ID (e.g., zwavejs>71-1) into the MapID field, but make sure it’s URL-encoded like this: zwavejs%3E71-1.
Then, configure these endpoints as needed:
On: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.on
Off: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.off
Dim:
For lights: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/dimming.set?level=${intensity.decimal_percent}
For roller shutters: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/position.set?value=${intensity.decimal_percent}
Color: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/rgb_color.set_rgb?red=${color.r}&green=${color.g}&blue=${color.b}
Just replace [ReactorIP] with your actual IP address. By using these placeholders, you can standardize your endpoints across all devices, making maintenance easier.
This setup works with any device mapped under MSR, regardless of the controller (ZWaveJS, Vera, HASS, OpenSprinkler, virtual, MQTT, DynamicEntities, etc.). If you need different calls, just go to the entities, get the action and parameters, and adjust accordingly. Enjoy super fast access to your devices via Alexa!
If you're migrating from Vera, the endpoints are (URL-encoded) in a file called device.db, in JSON format, under your config. You'd write a script to align the new endpoints to the new one, if you prefer to do it automatically. YMMV.
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.