npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

loewe.js

v1.0.3

Published

unofficial loewe tv typescript / javascript api wrapper

Readme

Loewe.js API wrapper

Hey, this is a simple wrapper for the Loewe SOAP API. It's not complete, but it's enough for my needs. Feel free to contribute.

Please note, that the code is mostly auto-generated by wsdl-tsclient, but modified by hand to make it work better using the Loewe SOAP API, as it often handles a bit difficult!

Disclaimer

I am already coding for about 4 years, but this is my first published library / SDK - so feel free to contribute and improve it - also concerning readability and code quality in libraries, as I am not that experienced in Module / SDK development :)

Usage

Installation

npm install loewe-js

In order to use the library, you first have to download the WSDL file from your TV. It is located here: http://:905/lowew_tablet_0001?wsdl Alternatively, you can use the WSDL file from this repository, but it might be outdated. (loewe didn't change it since 2018, so feel free :)

Quick dive into the Loewe API

The Loewe API is no API, you love to use - but I want to make you have a best experience using it! (at least as far as it's possible ;)

This ist the API Flow:

  1. Send a login request: Call RequestAuth with the needed parameters (see tabcompletion or typing files), but put ? as the ClientId
  2. Receive the new ClientId. Note, that the AccessStatus value currently is Pending.
  3. Wait some seconds and call RequestAuth again with the same parameters, but now with the ClientId you received in step 2.
  4. Receive the Response containing the same information except, the AccessStatus value is now Accepted.

You can now use the ClientId and fcid for further requests. It's not clear how long the ClientId is valid. I experienced a lifetime of the time while the TV isn't restarted (standby ok, but no deep-sleep), but docs are saying "until the TV needs resources and cancels the ClientId".

Hints on the Credentials: The fcid is like a username. The ClientId is like a token. DeviceType can be selected freely. DeviceName can be selected freely. DeviceUUID should be a MAC-Address like string RequesterName can be selected freely.

Example

import { createClientAsync } from 'loewe-js';
const authData = {
    fcid: "fcid",
    DeviceType: "deviceType",
    DeviceName: "deviceName",
    DeviceUUID: "deviceUUID",
    RequesterName: "requesterName",
    ClientId: "?"
}

createClientAsync("path/to/wsdl.wsdl", {
    endpoint: "http://<ip-of-tv>:905/loewe_tablet_0001"
})
.then(c => {
    c.RequestAccess(authData)
        .then(authResponse => {
            const clientId = authResponse[0].ClientId;
            // send further requests with the clientId
        })
})

The response data is serialized to JSON, so you can use it directly. It's located inside the first array element.

FAQ

How do I implement an array of e.g. RCKeys?

I just had the same problem ;) I haven't known much about SOAP myself, so I found out, there's an easy way. Look at the demo.ts file in this packages directory. Important are:

  1. the namespaceArrayElements: false option in the createClientAsync call
  2. the InputEventSequence with its Array of XML nodes containing the attributes defining the RCKey

looks a bit difficult or annoying - but works completely fine with the built-in serializer!

Contribution

Feel free to contribute to this project. Just fork it and create a pull request. Any Bugfixes or new features are welcome.