node-red-contrib-power-saver 4.2.1 → 4.2.2

package/docs/.vuepress/config.js

@@ -11,14 +11,14 @@ export default defineUserConfig({
   description: "A Node-RED node collection to save money on hourly changing power prices",
   head: [
     ["link", { rel: "shortcut icon", type: "image/x-icon", href: "euro.png" }],
-    [
-      "script",
-      {
-        async: true,
-        crossorigin: "anonymous",
-        src: "https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-9857859182772006",
-      },
-    ],
+    // [
+    //   "script",
+    //   {
+    //     async: true,
+    //     crossorigin: "anonymous",
+    //     src: "https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-9857859182772006",
+    //   },
+    // ],
   ],
   lang: "en-US",
   plugins: [

package/docs/.vuepress/public/ads.txt

@@ -1 +0,0 @@
-google.com, pub-9857859182772006, DIRECT, f08c47fec0942fa0

package/docs/README.md

@@ -33,8 +33,6 @@ footer: Created by Otto Paulsen and contributors
 footerHtml: true
 ---
 
-<AdsenseAdd type="artikkel"/>
-
 This is a collection of nodes for the popular [Node-RED](https://nodered.org/) that you can use to save money on variable electricity prices. Node-RED is a widely used low-code programming tool that can be used together with many smart home solutions to create automations.
 
 Please remember to take a look at our [privacy rules](./privacy.md).

package/docs/changelog/README.md

@@ -7,6 +7,12 @@ sidebarDepth: 1
 
 List the most significant changes.
 
+
+## 4.2.2
+
+ - Remove ads from doc.
+ - Remove console.log msg from node.
+
 ## 4.2.1
 
  - Bugfix version 4.2.0. Change was not effective.
@@ -16,6 +22,8 @@ List the most significant changes.
  - Format time on node status with HH:MM format. No AM/PM any more.
  - Remove warning for `No schedule` in debug output.
 
+ 
+
 ## 4.1.5
 
  - Fixed bug based on [this issue](https://github.com/ottopaulsen/node-red-contrib-power-saver/issues/184). Now correctly uses the value for `outputOutsidePeriod` when the planning period spans midnight, and there is no data available before midnight. In this case, the period from midnight to end time cannot be planned, so `outputIfNoSchedule` will be used until end time, and `outputOutsidePeriod` will be used from then. See the issue for more details.
@@ -24,6 +32,8 @@ List the most significant changes.
 
 - Update dependencies.
 
+
+
 ## 4.1.3
 
 - Fix bug that saved some data in wrong context storage.
@@ -37,6 +47,8 @@ List the most significant changes.
 
 - Update dependencies
 
+
+
 ## 4.1.0
 
 - Fix bug with override function. It did not override longer than until next scheduled change. Now it overrides until set to auto again.
@@ -50,6 +62,8 @@ There are a couple of new nodes that open for many interesting use cases.
 A rewrite like this may lead to changes in behavior, intended or not.
 There are some breaking changes, but most users should not be affected by them.
 
+
+
 ### New features
 
 - New node `ps-schedule-merger` or `Schedule Merger`, used to merge schedules from multiple Best Save and/or Lowest Price nodes,
@@ -71,6 +85,8 @@ There are some breaking changes, but most users should not be affected by them.
 - Some bug-fixes may be regarded as breaking.
 - There may be some changes to what data that is stored in the context.
 
+
+
 ### Bug fixes
 
 - Fix so the `If no schedule, send` config works as one should expect for the end of the schedule.
@@ -140,6 +156,8 @@ There are some breaking changes, but most users should not be affected by them.
 
 - Update github actions to deploy automatically to the npm library.
 
+
+
 ## 3.5.0
 
 - Select what context storage to store data in the node configuration.
@@ -186,6 +204,8 @@ There are some breaking changes, but most users should not be affected by them.
 - Fix node status so it says "No price data" when there is no price data available.
 - Added an FAQ section to the doc.
 
+
+
 ## 3.2.3
 
 - Remove unused imports
@@ -231,6 +251,8 @@ There are some breaking changes, but most users should not be affected by them.
 - Fix bug in Lowest Price node when period goes over midnight.
 - Fix documentation - lots of pages were failing.
 
+
+
 ## 3.0.7
 
 - Fix Nord Pool current state node input.
@@ -273,6 +295,8 @@ There are some breaking changes, but most users should not be affected by them.
 - New documentation.
 - Change node category to Power Saver.
 
+
+
 ## 2.1.0
 
 - Accept config as input, making it possible to dynamically change config
@@ -291,6 +315,8 @@ There are some breaking changes, but most users should not be affected by them.
 
 - Bugfix
 
+
+
 ## 2.0.2
 
 - Fix so Nord Pool data can be read directly from the current state node
@@ -310,3 +336,4 @@ There are some breaking changes, but most users should not be affected by them.
 ## 1.0.9
 
 - Fix bug in saving last hour of the day.
+

package/docs/contribute/README.md

@@ -59,4 +59,4 @@ Example contributors: [Stefan](https://github.com/oakhill87/node-red-contrib-pow
 
 ###
 
-<AdsenseAdd type="nederst"/>
+

package/docs/examples/README.md

@@ -1,4 +1,3 @@
-<AdsenseAdd type="øverst"/>
 
 # Examples
 
@@ -24,4 +23,4 @@
 
 ###
 
-<AdsenseAdd type="nederst"/>
+

package/docs/faq/README.md

@@ -51,4 +51,4 @@ Be aware that the norwegian [FHI](https://www.fhi.no/nettpub/legionellaveiledere
 
 ###
 
-<AdsenseAdd type="nederst"/>
+

package/docs/faq/best-save-viewer.md

@@ -17,7 +17,7 @@ Then paste it here and see the result below:
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ## Explanation
 
@@ -33,6 +33,9 @@ Other information about the calculation etc.
 
 Here you can see some summary and average for each date in the data set. Hover over the column title for explanation.
 
+
+
+
 ### Hours
 
 Here is your dta represented per hour, as well as potential savings calculated by the tool. Negative numbers are hidden, but you can select to show them.
@@ -47,6 +50,8 @@ There are the same number of columns as you have configured as `Max in sequence`
 The cells show how much you will save per hWh by turning that hour off for `x` hours,
 starting at that hour. It is the difference between the price at that hour and the price x hours later. Click on a cell to see the cells used in the calculation.
 
+
+
 #### Saving for sequence of x hours
 
 These cells show how much you can save per kWh in average per hour by turning off a sequence of x hours starting at that hour. Click on a cell to see the cells used in the calculation.
@@ -59,7 +64,7 @@ If the number is black, it could be used, but only if all other criteria are sat
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ## Something seems wrong
 

package/docs/guide/README.md

@@ -8,6 +8,8 @@ sidebar: "auto"
 
 This is a collection of nodes for the popular [Node-RED](https://nodered.org/) that you can use to save money on variable electricity prices. Node-RED is a widely used low-code programming tool that can be used together with many smart home solutions to create automations.
 
+
+
 The solution can be used to control switches or other entities in a smart home system, and for example turn on when the price is low, and turn off when the price is high.
 There are different ways to calculate what hours to turn on and off, and these are implemented as **strategy nodes**. Each strategy node can be configured to fit different purposes.
 
@@ -19,6 +21,8 @@ Tibber and Nord Pool are only available in the nordics, so if you live outside t
 
 Grid tariff is normally not part of the electricity price, so if this varies by the hour, it must be added before sent to the strategy nodes for calculation. This can be done by putting a `ps-xxx-add-tariff` node between the price receiver and the strategy.
 
+
+
 The strategy nodes have 3 outputs. Output 1 is used to "turn on", output 2 is used to "turn off", and on output 3, the calculated schedule and some other information is sent. You can use this to make graphs, or just send it to a debug node to view it.
 
 Example:
@@ -33,7 +37,7 @@ The node collection fits very well with Home Assistant (HA), as Node-RED is freq
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ## Getting started
 
@@ -47,6 +51,8 @@ May also be installed via npm:
 
 Make sure that you upgrade now and then to get the latest version. See [changelog](../changelog/README.md) for changes.
 
+
+
 ### Get price data
 
 This solution is useless without price data. In the nordics, there are at least two very common places to get price data from:
@@ -116,6 +122,8 @@ If you are a Tibber customer, use the `tibber-query` node from the [Tibber API](
 
 See more details in the [documentation](../nodes/ps-receive-price#tibber-input) for the `ps-receive-price` node.
 
+
+
 Se documentation for [node-red-contrib-tibber-api](https://flows.nodered.org/node/node-red-contrib-tibber-api) for details about the Tibber query.
 
 ::: tip Tibber query
@@ -135,7 +143,7 @@ Data can be sent from both the `current state` node or the `events: state` node.
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ### Add grid tariff
 
@@ -154,6 +162,8 @@ If your grid is not supported, you may code this yourself.
 If the grid tariff is the same the whole day, you can skip this step i the flow.
 :::
 
+
+
 ### Calculate and run schedule
 
 This is the step where the value is produced. Based on the prices received, the optimal schedule for you is calculated automatically, based on your configuration. You can choose between the following strategies:
@@ -177,6 +187,8 @@ Choose the lowest price strategy if you need the power to be on for x hours, but
 Choose the heat capacitor strategy for controlling for example room heating, where you can turn the heat a little down when electricity is expensive, and a little up when it is cheap, using trading principles (only that you know up front when the prices will change).
 :::
 
+
+
 ### Use schedule signals
 
 Use the outputs to control switches, thermostats or other entities to control your power consumers.
@@ -202,7 +214,7 @@ There are many ways you can use the output:
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ### Display schedule
 
@@ -228,7 +240,7 @@ There are more details and more information in the documentation for each [node]
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ## Migration from v2
 
@@ -239,6 +251,8 @@ You may directly replace the `Power Saver` node by two of the new nodes (`ps-rec
 
 See more details in the [documentation for the `ps-strategy-best-save`](../nodes/ps-strategy-best-save.md) node.
 
+
+
 ## Disclaimer
 
 This software is offered for free as open source. You use it totally on your own risk. The developers take no responsibility of any consequences caused by use or misuse of this software.

package/docs/nodes/README.md

@@ -1,4 +1,3 @@
-<AdsenseAdd type="øverst"/>
 
 # Nodes
 
@@ -6,7 +5,7 @@ Here is an overview of the nodes, and links to detailed descriptions for eah of
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ## Strategy nodes
 
@@ -38,7 +37,7 @@ A strategy for setting a fixed daily or weekly schedule.
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ## Utility nodes
 
@@ -54,6 +53,8 @@ Node to convert different types of input data to the format used by the strategy
 
 Node to combine multiple schedules into one schedule.
 
+
+
 ## Grid tariff nodes
 
 ### [ps-general-add-tariff](./ps-general-add-tariff)
@@ -68,6 +69,8 @@ Node to add a variable grid tariff (or any value) to the prices before sending t
 
 Node to add Elvia grid tariff to the prices before sending them to the strategy nodes.
 
+
+
 ## Other nodes
 
 These are a couple of other nodes for using the Elvia API, but these are not important to the Power Saver, so they are not given any further documentation here.
@@ -82,4 +85,4 @@ Use this to get the Elvia grid tariff for a selected tariff type.
 
 ###
 
-<AdsenseAdd type="nederst"/>
+

package/docs/nodes/dynamic-commands.md

@@ -1,6 +1,3 @@
-###
-
-<AdsenseAdd type="øverst"/>
 
 # Dynamic commands
 
@@ -13,6 +10,8 @@ This applies to the following nodes:
 
 Commands can be sent together with config or price data. You can command multiple commands in one message, but then put them all in the same commands-object.
 
+
+
 ## Commands
 
 ### sendSchedule
@@ -45,7 +44,7 @@ When you do this, the current schedule is actually recalculated based on the las
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ### reset
 
@@ -70,6 +69,8 @@ This operation cannot be undone.
 However, it is normally not a big loss, as you can just feed the node with new price data and start from scratch.
 :::
 
+
+
 ### replan
 
 By sending this command, you can have the node read the last received prices from the context storage,
@@ -88,4 +89,4 @@ instead of fetching prices again.
 
 ###
 
-<AdsenseAdd type="nederst"/>
+

package/docs/nodes/dynamic-config.md

@@ -8,6 +8,8 @@ This applies to the following nodes:
 - Heat Capacitor
 - Schedule Merger
 
+
+
 Dynamic config is sent on the input as a message with a payload containing a `config` object and optionally a `name`.
 Example:
 
@@ -33,7 +35,7 @@ The `name` is the exact same value as you set as name in the nodes config.
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ## Output values
 
@@ -47,6 +49,8 @@ When a config is sent like this, and without price data, the schedule will be re
 
 However, you can send config and price data in the same message. Then both will be used.
 
+
+
 ## Override
 
 It is possible to send an override message to a strategy node (Best Save or Lowest Price) and to the Schedule Merger node.
@@ -72,6 +76,8 @@ Legal values for override are:
 | `"off"`  | The node will only send output `off`                                                     |
 | `"auto"` | The node will work according to the schedule. This is the standard and the default mode. |
 
+
+
 ## Config saved in context
 
 The nodes config is saved in the nodes context.
@@ -81,4 +87,4 @@ When Node-RED starts or the flow is redeployed, the config defined in the node r
 
 ###
 
-<AdsenseAdd type="nederst"/>
+

package/docs/nodes/old-power-saver-doc.md

@@ -1,5 +1,7 @@
 # node-red-contrib-power-saver v2 (deprecated)
 
+
+
 A Node-RED node to save money when power prices are changing. Saving is done by postponing power consumption until the price is lower.
 
 You can configure maximum number of hours to save in a sequence, and minimum time to recover after a maximum saving period.
@@ -20,6 +22,8 @@ This node is currently rather new, and has been tried for a few weeks, enough to
 
 Feel free to try it, and report back problems or ideas as [Github issues](https://github.com/ottopaulsen/node-red-contrib-power-saver/issues).
 
+
+
 ## Installation
 
 Install in Node-RED via the Manage Palette menu.
@@ -30,6 +34,8 @@ May also be installed via npm:
 
 Make sure that you upgrade now and then to get the latest version. See [changelog](CHANGELOG) for changes.
 
+
+
 ## Input
 
 3 different types of input are accepted:
@@ -42,6 +48,8 @@ Choose the one that fits you best. Of course, all inputs are JSON, but the Tibbe
 
 From version 2.1.0, you can also send a config object as input for dynamically changing the node config.
 
+
+
 ### Tibber input
 
 If you are a Tibber customer, you can use the `tibber-query` node from the [`node-red-contrib-tibber-api` node](https://flows.nodered.org/node/node-red-contrib-tibber-api). Set it up with the following query:
@@ -71,6 +79,8 @@ Send the result from the `tibber-query` node with the query above directly to th
 
 [See example with Tibber, a switch and MQTT](doc/example-tibber-mqtt.md)
 
+
+
 ### Nordpool input
 
 This is especially designed to work for Home Assistant (HA), and the [Nord Pool custom component](https://github.com/custom-components/nordpool). The Nord Pool component provides a _sensor_ that gives price per hour for today and tomorrow (after 13:00). Send the output from this sensor directly to the `power-saver` node. Make sure this is done whenever the node is updated, as well as when the system starts up.
@@ -81,6 +91,8 @@ Data can be sent from both the `current state` node or the `events: state` node.
 
 [See example with Nord Pool and `events: state` node](doc/example-nordpool-events-state.md)
 
+
+
 ### Other input
 
 If you cannot use any of the two above (Tibber or Nord Pool), create the input to the node with the payload containing JSON like this:
@@ -100,6 +112,8 @@ If you cannot use any of the two above (Tibber or Nord Pool), create the input t
 }
 ```
 
+
+
 ## Output
 
 ### Output 1
@@ -114,6 +128,8 @@ A payload with the word `false` is sent to output 2 whenever the power / switch
 
 When a valid input is received, and the schedule is recalculated, the resulting schedule, as well as some other information, is sent to output 3. You can use this to see the plan and verify that it meets your expectations. You can also use it to display the schedule in any way you like.
 
+
+
 Example of output:
 
 ```json
@@ -163,6 +179,8 @@ Example of output:
 
 The `schedule` array shows every time the switch is turned on or off. The `hours` array shows values per hour containing the price (received as input), whether that hour is on or off, the start time of the hour and the amount per kWh that is saved on hours that are turned off, compared to the next hour that is on.
 
+
+
 ## Configuration
 
 Currently there is only one strategy for saving. This is the _mostSaved_ strategy. This strategy turns off the hours where the price difference is largest compared to the next hour that is on. The idea is that the power you are not using when the switch is turned off, will be used immediately when the switch is turned on. This would fit well for turning of a water heater or another thermostat controlled heater.
@@ -175,6 +193,8 @@ You can configure the following:
 - Wether to send on/off just after a reschedule is done without waiting until the next scheduled switch.
 - What to do if there is no valid schedule any more (turn on or off).
 
+
+
 ### Dynamic config
 
 It is possible to change config dynamically by sending a config message to the node. The config messages has a payload with a config object like this example:
@@ -198,6 +218,8 @@ The config sent like this will be valid until a new config is sent the same way,
 
 When a config is sent like this, the schedule will be replanned based on the last previously received price data. If no price data has been received, no scheduling is done.
 
+
+
 ## Algorithm
 
 The calculation that decides what hours to turn off works as follows:
@@ -212,6 +234,8 @@ The calculation that decides what hours to turn off works as follows:
 
 I say "in most cases", because there is a chance that a group of two or more sequences combined can give a better plan than a single sequence preceeding those two, but where the selection of the one sequence causes the group to be discarded. If anyone encounters this situation, I would be happy to receive the price data set, and try to improve the algorithm even further.
 
+
+
 ## Integration with MagicMirror
 
 Are you using [MagicMirror](https://magicmirror.builders/)? Are you also using [Tibber](https://tibber.com/)? If so, there is a module for MM called [MMM-Tibber](https://github.com/ottopaulsen/MMM-Tibber), that easily can be used to show savings from this node.
@@ -222,6 +246,8 @@ The purple lines show savings per kWh.
 
 Read more about this in the [MMM-Tibber documentation](https://github.com/ottopaulsen/MMM-Tibber#show-savings).
 
+
+
 ## Change Log
 
 See [CHANGELOG.md](CHANGELOG.md)
@@ -232,4 +258,4 @@ Contributions are welcome. Please start by creating a Github Issue with suggeste
 
 ###
 
-<AdsenseAdd type="nederst"/>
+

package/docs/nodes/ps-elvia-add-tariff.md

@@ -14,7 +14,7 @@ You need an Elvia API subscription key to use this node. See [configuration](#el
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ## Description
 
@@ -22,6 +22,8 @@ When grid tariff changes from hour to hour, this should normally also be conside
 
 ![Elvia flow](../images/elvia-flow.png)
 
+
+
 ## Configuration
 
 ::: warning Elvia API subscription key
@@ -36,6 +38,8 @@ The first time you use this node, you must create a `ps-elvia-config` entry. Cli
 
 ![Elvia configuration](../images/elvia-config-no-config.png)
 
+
+
 Then enter the Elvia API subscription key:
 
 ![Elvia configuration](../images/elvia-config-subscription-key.png)
@@ -53,7 +57,7 @@ The next time you use this node, you can select the same config as you created t
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ## Input
 
@@ -65,4 +69,4 @@ The output is the [common strategy input format](./strategy-input.md)
 
 ###
 
-<AdsenseAdd type="nederst"/>
+

package/docs/nodes/ps-general-add-tariff.md

@@ -11,7 +11,7 @@ Node to add a value, for example a variable grid tariff, to the price before it
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ## Description
 
@@ -26,6 +26,8 @@ When using two nodes in series to support for example different rates for weeken
 make sure each day is handled by only one node, else both nodes will add to the price.
 :::
 
+
+
 Here is how this node is normally used:
 
 ![general flow](../images/add-tariff-flow.png)
@@ -36,6 +38,8 @@ If there is one price now, and another price from a specific date, you can use t
 
 ## Configuration
 
+
+
 ### Add and delete periods
 
 You can have from 1 to 24 periods during the day, with different values to add for each hour. Click the `Add period` button to add more periods. Click the `X` button to delete a period.
@@ -49,6 +53,8 @@ Be careful to use the correct unit when entering the price here. If the price is
 If the price is `36 cents` enter `0.36`.
 :::
 
+
+
 ### Days
 
 Check which days the price is valid for. For the price to be added, both the time and the day must be correct.
@@ -70,7 +76,7 @@ If this is empty, the config is valid until forever.
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ## Input
 
@@ -84,4 +90,4 @@ If there is a config property in the input payload, it is passed on to the outpu
 
 ###
 
-<AdsenseAdd type="nederst"/>
+

package/docs/nodes/ps-receive-price.md

@@ -7,6 +7,8 @@ next: ./ps-schedule-merger.md
 
 ![ps-receive-price](../images/node-ps-receive-price.png)
 
+
+
 ## Description
 
 The `ps-receive-price` node is used to convert prices from Tibber or Nord Pool to the format used by the strategy nodes. It takes its input directly from the output of the following nodes (see details below):
@@ -29,7 +31,7 @@ There is no configuration except from node name.
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ## Input
 
@@ -58,6 +60,8 @@ If you are a Tibber customer, you can use the `tibber-query` node from the [`nod
 }
 ```
 
+
+
 Send the result from the `tibber-query` node with the query above directly to the `ps-receive-price` node. Make sure it is refreshed when new prices are ready. Prices for the next day are normally ready at 13:00, but refreshing every hour can be a good idea.
 
 [See example with Tibber, a switch and MQTT](../examples/example-tibber-mqtt.md)
@@ -92,6 +96,8 @@ Go to the [Tibber Developer pages](https://developer.tibber.com/), sign in, and
 }
 ```
 
+
+
 Then copy the `id` of the house you want to use prices for. It may look like this:
 
 ```
@@ -126,7 +132,7 @@ This is the query you shall put in the `tibber-query` node.
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ### Nord Pool input
 
@@ -142,6 +148,8 @@ When using the `current state` node, configure the output properties to set `msg
 
 [See example with Nord Pool and `events: state` node](../examples/example-nordpool-events-state.md)
 
+
+
 ### Other input
 
 If you cannot use any of the two above (Tibber or Nord Pool), create the input to the node with the payload containing JSON like this:
@@ -161,10 +169,12 @@ If you cannot use any of the two above (Tibber or Nord Pool), create the input t
 }
 ```
 
+
+
 ## Output
 
 The output is the [common strategy input format](./strategy-input.md), so it can be sent directly to the strategy nodes, or via any `ps-xxx-add-tariff` node.
 
 ###
 
-<AdsenseAdd type="nederst"/>
+

package/docs/nodes/ps-schedule-merger.md

@@ -7,6 +7,8 @@ next: ./ps-general-add-tariff.md
 
 ![ps-schedule-merger](../images/node-ps-schedule-merger.png)
 
+
+
 ## Description
 
 This node can be used to merge schedules from multiple strategy nodes, and create one resulting schedule. It can be useful for example to have multiple lowest price nodes to cover different periods of the day. Send all schedules as input to this node and get one schedule as output. It works for schedules from Lowest Price, Best Save and Fixed Schedule.
@@ -21,6 +23,8 @@ The schedules that are merged must be for the exact same period and have the exa
 If a schedule with prices for a different period is received, all saved schedules are deleted, and not used any more.
 :::
 
+
+
 The merge can be done using one of two functions:
 
 - OR
@@ -42,6 +46,8 @@ sure the switch is turned on or off, and then merge the schedule from the Fixed
 the schedule from for example the Lowest Price node, using the Schedule Merger node.
 :::
 
+
+
 ## Configuration
 
 ![Schedule Merger Config](../images/schedule-merger-config.png)
@@ -57,7 +63,7 @@ the schedule from for example the Lowest Price node, using the Schedule Merger n
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ### Dynamic config
 
@@ -77,6 +83,8 @@ The following config values can be changed dynamically:
 
 See [Dynamic Config](./dynamic-config.md) for details and how to send dynamic config.
 
+
+
 ### Dynamic commands
 
 You can send dynamic commands to this node, for example to make it resend output.
@@ -113,6 +121,8 @@ You can make your own input by supplying a payload containing an hours array. Ex
 }
 ```
 
+
+
 ## Output
 
 There are three outputs. You use only those you need for your purpose.
@@ -129,6 +139,8 @@ A payload with the value set in config, default `false`, is sent to output 2 whe
 
 When valid input is received, and the schedule is recalculated (after the timeout), the resulting schedule, as well as some other information, is sent to output 3. You can use this to see the plan and verify that it meets your expectations. You can also use it to display the schedule in any way you like.
 
+
+
 Example of output:
 
 ```json
@@ -215,12 +227,16 @@ Example of output:
 
 The `schedule` array shows every time the switch is turned on or off. The `hours` array shows values per hour containing the price (received as input), whether that hour is on or off and the start time of the hour. The `saving` value is always `null`.
 
+
+
 ## Usage ideas
 
 ### Multiple Lowest Price
 
 If you want a switch to be on for example two of the cheapest hours between 00:00 and 08:00, and then the two cheapest hours between 12:00 and 20:00, you can do this by combining the schedule from two Lowest Price nodes, one for each of the mentioned periods. Merge the two using a Schedule Merger node with the `OR` function. Make sure to send `off` if no schedule for all nodes.
 
+
+
 ### Day-filter for strategy nodes
 
 If you have a strategy node, for example Lowest Price or Best Save, that you want to have effect only on weekdays,

package/docs/nodes/ps-strategy-best-save.md

@@ -8,6 +8,8 @@ next: ./ps-strategy-lowest-price.md
 
 Strategy node to postpone power consumption until the price is lower.
 
+
+
 ## Description
 
 This strategy turns off the hours where the price difference is largest compared to the next hour that is on. The idea is that the power you are not using when the switch is turned off, will be used immediately when the switch is turned on (during the first hour). This would fit well for turning off a water heater or another thermostat controlled heater.
@@ -18,6 +20,8 @@ Be aware that the norwegian [FHI](https://www.fhi.no/nettpub/legionellaveiledere
 
 The picture at the bottom of the page, under [Integration with MagicMirror](#integration-with-magicmirror), illustrates this by the purple strokes, taking the price from the top of the price curve to the level of the first hour after the save-period.
 
+
+
 ## Configuration
 
 ![Best Save Config](../images/best-save-config.png)
@@ -39,7 +43,7 @@ NB! The `Min recover` only has effect if the previous save-period is of length `
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ### Dynamic config
 
@@ -61,6 +65,8 @@ The following config values can be changed dynamically:
 
 See [Dynamic Config](./dynamic-config.md) for details and how to send dynamic config.
 
+
+
 ### Dynamic commands
 
 You can send dynamic commands to this node, for example to make it resend output.
@@ -79,6 +85,8 @@ When a payload with `priceData` is received, this is saved to the nodes context
 The source is saved as `lastSource`. If config- or command-messages are received without price data,
 the data saved in context is used for replanning.
 
+
+
 ## Output
 
 There are three outputs. You use only those you need for your purpose.
@@ -91,13 +99,15 @@ A payload with the value set in config, default `true`, is sent to output 1 when
 
 A payload with the value set in config, default `false` is sent to output 2 whenever the power / switch shall be turned off.
 
+
+
 ### Output 3
 
 When a valid input is received, and the schedule is recalculated, the resulting schedule, as well as some other information, is sent to output 3. You can use this to see the plan and verify that it meets your expectations. You can also use it to display the schedule in any way you like.
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 Example of output:
 
@@ -157,6 +167,8 @@ Example of output:
 
 The `schedule` array shows every time the switch is turned on or off. The `hours` array shows values per hour containing the price (received as input), whether that hour is on or off, the start time of the hour and the amount per kWh that is saved on hours that are turned off, compared to the next hour that is on.
 
+
+
 ### Output saved in context
 
 The `schedule` and the `hours` arrays from Output 3 are both saved to the nodes context in an object with key `lastPlan`. This may be used in the plan for the next day, for example if an off-period at the end of one day continues into the next day. In that case, the `saving` values for the last hours in the day have to be recalculated, since the next hour on is changed when the new day is calculated.
@@ -165,7 +177,7 @@ You can see the saved data if you select the node in Node-RED, and view "Context
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ## Algorithm
 
@@ -181,6 +193,8 @@ The calculation that decides what hours to turn off works as follows:
 
 I say "in most cases", because there is a chance that a group of two or more sequences combined can give a better plan than a single sequence preceeding those two, but where the selection of the one sequence causes the group to be discarded. If anyone encounters this situation, I would be happy to receive the price data set, and try to improve the algorithm even further.
 
+
+
 ## Data used for calculation
 
 Normally data is received for one or two whole days, and all this data is used to do the calculation. In addition, if the node has run before, so there is historical data, the last period on or off before the period data is received for, is considered in the calculation, so that the rules in the configuration are followed also between days.
@@ -195,6 +209,8 @@ It is common to have two different context storages defined, `memory` and `file`
 It is also common to have a `default` context storage defined, and often this points to either `memory` or `file`.
 However, the configuration can be different from this.
 
+
+
 You can find this configuration in the `settings.js` file for Node-RED, usually in the node-red config folder.
 In Home Assistant, this is normally `/config/node-red/settings.js`.
 
@@ -213,6 +229,8 @@ Please read the [Node-RED documentation](https://nodered.org/docs/user-guide/con
 
 The data that is saved is the config, the last used prices and the last calculated schedule.
 
+
+
 When Node-RED restarts, the config is reset to what is defined in the node config, so by default,
 nothing is read from the context storage after a restart. However, if you send a `replan` command to the
 nodes input, a plan is recalculated, using the last received prices. One way to do this is to use an `inject` node,
@@ -230,7 +248,7 @@ This is an alternative to fetching new prices and send as input.
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ## Integration with MagicMirror
 
@@ -248,4 +266,4 @@ If you like to analyze the data output by the node, take a look at the [Best Sav
 
 ###
 
-<AdsenseAdd type="nederst"/>
+

package/docs/nodes/ps-strategy-fixed-schedule.md

@@ -11,6 +11,8 @@ Strategy node to set a fixed schedule.
 This can be used by itself, but it is also perfect to combine with other strategies
 and the [Schedule Merger](./ps-schedule-merger.md) node in order to force periods of the day either on or off.
 
+
+
 ## Description
 
 This strategy can be used to set a period of the day or the week fixed to on or off.
@@ -23,6 +25,8 @@ Here is an example of how to combine it with the Lowest Price node:
 
 ![ps-strategy-fixed-schedule-example](../images/ps-strategy-fixed-schedule-example.png)
 
+
+
 ## Configuration
 
 ![Fixed Schedule Config](../images/fixed-schedule-config.png)
@@ -41,7 +45,7 @@ Here is an example of how to combine it with the Lowest Price node:
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ### Dynamic config
 
@@ -64,6 +68,8 @@ The following config values can be changed dynamically:
 
 See [Dynamic Config](./dynamic-config.md) for details and how to send dynamic config.
 
+
+
 ### Dynamic commands
 
 You can send dynamic commands to this node, for example to make it resend output.
@@ -77,6 +83,8 @@ The node requires the price-data input in order to know what times to generate s
 This is especially important when merging the schedule using the Schedule Merger node,
 as all schedules that are merged must be for the exact same period.
 
+
+
 ## Output
 
 There are three outputs. You use only those you need for your purpose.
@@ -97,7 +105,7 @@ The aoutput is similar to the output from the other strategy nodes.
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ## Usage ideas
 
@@ -110,4 +118,4 @@ Lowest Price schedule using the Schedule Merger node with the `OR` function.
 
 ###
 
-<AdsenseAdd type="nederst"/>
+

package/docs/nodes/ps-strategy-heat-capacitor.md

@@ -9,6 +9,8 @@ next: ./ps-strategy-fixed-schedule.md
 
 A strategy for moving consumption from expensive to cheap periods utilizing climate entities.
 
+
+
 ## Description
 
 The heat capacitor strategy utilizes a large body of mass, like your house or cabin, to procure heat at a time where electricity is cheap, and divest at a time where electricity is expensive.
@@ -19,6 +21,8 @@ It is a good application for cabins/heated storage spaces, as the entity never a
 
 ![Temperature profile vs. cost](../images/heat-capacitor-temperatureVsPrice.png)
 
+
+
 ## Configuration
 
 ![Node Configuration](../images/temperature-manipulation-config.png)
@@ -39,7 +43,7 @@ The node consumes price information and outputs $\Delta T$ on its first output a
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ### The impact of **Time +1C**
 
@@ -51,6 +55,8 @@ To get started, 90 minutes can be used for air heaters. Later, one can study the
 
 The setpoint, $S_p$, indicates the ideal temperature.
 
+
+
 ### Max temperature adjustment
 
 A max temperature adjustment $M_{ta}$ value of $0.65~^{\circ}C$ will change the setpoint temperature by $\pm0.65~^{\circ}C$. Please note that a larger number will indicate a longer heating time (Time +1C = 60 and Max Temp Adj.= $0.75~^{\circ}C$ results in a heating time of $60\times0.75\times 2= 90$ minutes
@@ -72,6 +78,8 @@ In the scenario where one should invest at 03:00 at night, and divest at 08:00 i
 - 08:00 to 09:00: $-2~^{\circ}C$
 - 09:00 and onward: $-1~^{\circ}C$
 
+
+
 ### Min Savings
 
 The heating and cooling periods can be seen as buy - sell pairs. That is, heat is procured at time t, and the same heat is sold at t+dt. The savings can then be estimated as the price difference $S=price(t+dt) - price(t)$. If this saving is less that the minimum savings requirement, it will be removed. The algorithm removes these in a prioritized order, starting with the pair with the smallest gain.
@@ -100,6 +108,8 @@ The config sent like this will be valid until a new config is sent the same way,
 
 When a config is sent like this, and without price data, the schedule will be replanned based on the last previously received price data. If no price data has been received, no scheduling is done. You can send config and price data in the same message. Then both will be used.
 
+
+
 ## Output
 
 There are three outputs. You use only those you need for your purpose.
@@ -132,6 +142,8 @@ The number of degrees which has been added or subtracted to the setpoint
 }
 ```
 
+
+
 ### Output 3
 
 The current schedule as well as some other information. You can use this to see the plan and verify that it meets your expectations. You can also use it to display the schedule in any way you like.
@@ -153,6 +165,8 @@ The "trades" key contains a list of dictionaries indicating the trades:
 
 A trade consists of a `buy action` and a `sell action`. You buy electricity in the heating period, and sell it during the cooling period. `buyPrice` indicates the price at which the electricity is bought, while `sellPrice` indicates the price at which it is sold. This yields the `tradeValue`, which is how much is gained by moving one kWh from the expensive to the cheap period. If you run two 1kWh heaters and is able to turn it off from a 50% load for an hour, you earn 1kWh _ 2 _ 50% \* 0.2558 = 0.2558.
 
+
+
 The temperature variations from the setpoint are shown in a list at the end of the dictionary. The array has minute resolution, meaning that the first value is valid from 07.02.2022 00:00 till 00:01. As such, this is an indexed list, and the `buyIndex` and `sellIndex` values is a reference to the index in this array.
 
 Full example:
@@ -356,4 +370,4 @@ Full example:
 
 ###
 
-<AdsenseAdd type="nederst"/>
+

package/docs/nodes/ps-strategy-lowest-price.md

@@ -9,10 +9,14 @@ next: ./ps-strategy-heat-capacitor.md
 
 Strategy node to turn on power the hours when the price is lowest during a given period, and turn off the other hours.
 
+
+
 ## Description
 
 The node can work on a specific period from 1 to 24 hours during a 24 hour period. Inside this period, you can decide how many hours that shall be on. The rest of the period will be off. Outside the period, you can select that the output shall be either on or off. You can also decide that the hours on shall be consecutive (one continuous period) or spread around in multiple on-periods.
 
+
+
 ## Configuration
 
 ![Node Configuration](../images/lowest-price-config.png)
@@ -35,6 +39,8 @@ If you want to use a period of 24 hours, set the From Time and To Time to the sa
 ::: tip Example with Consecutive On-Period
 One example to need a consecutive on-period can be if you want to control the washing machine. Let's say it needs 3 hours, and you want it to run between 22:00 and 06:00. Set `From Time = 22:00`, `To Time = 06:00` and check the `Consecutive On-Period` flag. This will turn on the cheapest 3-hour period from 22:00 to 06:00.
 
+
+
 NB! It is not recommended to run the washing machine when you are sleeping or away.
 :::
 
@@ -66,7 +72,7 @@ If you leave `Max price` blank, it has no effect.
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 ### Dynamic config
 
@@ -92,6 +98,8 @@ The following config values can be changed dynamically:
 
 See [Dynamic Config](./dynamic-config.md) for details and how to send dynamic config.
 
+
+
 ### Dynamic commands
 
 You can send dynamic commands to this node, for example to make it resend output.
@@ -113,13 +121,15 @@ A payload with the value set in config, default `true`, is sent to output 1 when
 
 A payload with the value set in config, default `false` is sent to output 2 whenever the power / switch shall be turned off.
 
+
+
 ### Output 3
 
 When a valid input is received, and the schedule is recalculated, the resulting schedule, as well as some other information, is sent to output 3. You can use this to see the plan and verify that it meets your expectations. You can also use it to display the schedule in any way you like.
 
 ###
 
-<AdsenseAdd type="artikkel"/>
+
 
 Example of output:
 
@@ -195,6 +205,8 @@ Example of output:
 
 The `schedule` array shows every time the switch is turned on or off. The `hours` array shows values per hour containing the price (received as input), whether that hour is on or off, the start time of the hour and the amount per kWh that is saved on hours that are turned off, compared to the next hour that is on.
 
+
+
 ## Restarts and saved context
 
 The config, last received prices and the last calculated schedule are saved to the nodes context.
@@ -217,6 +229,8 @@ contextStorage: {
 }
 ```
 
+
+
 By default, this node saves context to the `default` context storage. In the example above, this is memory.
 Then it is not preserved over a restart.
 Please read the [Node-RED documentation](https://nodered.org/docs/user-guide/context) for more details about this.
@@ -238,6 +252,8 @@ and set `msg.payload` to the following JSON value:
 
 This is an alternative to fetching new prices and send as input.
 
+
+
 ## Tips & tricks
 
 ### Multiple nodes works together
@@ -247,6 +263,8 @@ combine the output from them into one schedule using the Schedule Merger node:
 
 ![Combine two lowest price nodes](../images/combine-two-lowest-price.png)
 
+
+
 ### Highest price
 
 If you want to find the `x` hours with the highest prices, do as follows:
@@ -257,4 +275,4 @@ If you want to find the `x` hours with the highest prices, do as follows:
 
 ###
 
-<AdsenseAdd type="nederst"/>
+

package/docs/nodes/strategy-input.md

@@ -2,6 +2,8 @@
 
 The common input for strategy nodes is a payload with a `priceData` array containing an object for each hour. Each object has a `value` which is the price, and a `start` which is the start time for the hour.
 
+
+
 Example:
 
 ```json
@@ -40,4 +42,4 @@ This format is used for:
 
 ###
 
-<AdsenseAdd type="nederst"/>
+

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "node-red-contrib-power-saver",
-  "version": "4.2.1",
+  "version": "4.2.2",
   "description": "A module for Node-RED that you can use to turn on and off a switch based on power prices",
   "main": "index.js",
   "scripts": {

package/src/strategy-lowest-price.html

@@ -47,7 +47,6 @@
         value: null,
         required: false,
         validate: function (v) {
-          console.log("validating " + v);
           return v == null || v == "" || (!isNaN(parseFloat(v)) && isFinite(v));
         },
       },