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

@mschaeffler/node-red-fenecon

v0.6.2

Published

Node Red nodes to communicate with a Fenecon FEMS

Readme

@mschaeffler/node-red-fenecon

Node Red nodes to communicate with a Fenecon FEMS.

image of example flow

image of example flow

Install

$ npm install @mschaeffler/node-red-fenecon

feneconFems Node

This node contains the configuration data for the connection to the FEMS.

Parameters

|config | type | description | |:------------|:-------|:----------------------------------| |Hostname | string | hostname of the FEMS |

feneconHttpGet Node

A Node Red node to request one ore more data points from a Fenecon FEMS.

Input

|msg. | type | description | |:-------|:-------|:----------------------------------| |topic |string |data point to be requested |

Data Points

The data points of the FEMS are always named as group/name. You can get all possible data points with the request .*/.*.

Examples:

  • .*/.*
  • _meta/V.*
  • _meta/Version
  • ctrlGridOptimizedCharge0/(DelayChargeMaximumChargeLimit|_PropertyManualTargetTime)

Output

|msg. | type | description | |:------|:-------|:------------| |topic | string | same as in input.| |payload| value or object | received data points. If more than one data point is returned, it is an object with key/value pairs.|

Parameters

|config | type | description | |:-------|:------------|:----------------------------------| |Fems | feneconFems | configuration of the FEMS. | |Topic | string | the data point to request; if empty, msg.topic will be used. | |Complete| boolean | sending out the complete response data or just the value. |

feneconHttpPost node

A Node Red node to set data points at a Fenecon FEMS with the App "Schreibzugriff".

Input

|msg. | type | description | |:-------|:-------|:----------------------------------| |topic |string |data point to be written | |payload |number |value to be written |

Data Points

The data points of the FEMS are always named as group/name. You can find the writable data points at the FEMS documentation.

Examples:

  • ess0/SetActivePowerEquals
  • ess0/SetActivePowerLessOrEquals
  • ess0/SetActivePowerGreaterOrEquals

Parameters

|config | type | description | |:-------|:------------|:----------------------------------| |Fems | feneconFems | configuration of the FEMS. | |Topic | string | the data point to set; if empty, msg.topic will be used. |

feneconWebsocket node

A Node Red node to subscribe data points and configuration data at a Fenecon FEMS via the WebSocket interface similar to the web UI.

It is also possible to write config data. This can be dangerous and damage your FEMS! This is done at your own risk! Please be careful and we accept no responsibility whatsoever for a damaged FEMS!

Input

|msg. | type | description | |:-------|:-------|:----------------------------------| |topic |string |open, close or name of the config parameter to be written | |payload |number |value of the config parameter to be written |

Outputs

subscribed data

Cyclic output of the subscribed data points.

|msg. | type | description | |:------|:-------|:------------| |payload| object | received data points. It is an object with key/value pairs.|

config data

Config data of the FEMS.

|msg. | type | description | |:------|:-------|:------------| |payload| object | received config data.|

state

Actual state of the websocket connection.

|msg. | type | description | |:------|:-------|:------------| |payload| string | state of the websocket.|

Parameters

|config | type | description | |:-------|:------------|:----------------------------------| |Fems | feneconFems | configuration of the FEMS. | |Edge | string | id of the edge; normally "0". | |Inlist | array | list of subscribed data points. | |Risk | boolean | risk accepted, enables writing. | |Timeout | boolean | send "timeout" as state, if 10s no subscribed message arrives. |

Data Points

The data points of the FEMS are always named as group/name. You can find possible data points at FEMS documentation.

Example inlist:

[
    "_sum/State",
    "_sum/GridMode",
    "_sum/EssSoc",
    "_sum/ProductionActivePower",
    "_sum/EssDischargePower",
    "_sum/GridActivePower",
    "_sum/GridSellActiveEnergy",
    "_sum/GridBuyActiveEnergy",
    "_sum/ProductionActiveEnergy",
    "_sum/EssDcDischargeEnergy",
    "_sum/EssDcChargeEnergy",
    "batteryInverter0/AirTemperature",
    "batteryInverter0/RadiatorTemperature",
    "ctrlIoHeatPump0/Status",
    "charger0/ActualPower",
    "charger1/ActualPower",
    "ctrlGridOptimizedCharge0/DelayChargeState",
    "meter0/CurrentL1",
    "meter0/CurrentL2",
    "meter0/CurrentL3"
]

feneconConnMan node

A Node Red node to manage the state of a feneconWebsocket node.

Input

|msg. | type | description | |:------|:-------|:------------| |payload|string | state message from feneconWebsocket node. |

Output

|msg. | type | description | |:------|:-------|:------------| |topic |string | open command for a feneconWebsocket node. |

Parameters

|config | type | description | |:-------|:------|:----------------------------------| |cyclic |number | cyclic time of the manager in s; 15s is here the recommended value. |

Example Flow

HTTP API

WebSocket API

Author

Mathias Schäffler

License

LGPL-2.1