v0.3.0 - Jam Protection #23
Replies: 4 comments 7 replies
-
|
The new Version is showing up in the ioBroker Adapter Panel 😅 (beta/latest only!) |
Beta Was this translation helpful? Give feedback.
-
|
in my adapter browser wamo is not listed for the stable repository. Only with beta/latest repo, the 0.2.13 appears: |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, but this is absolutely correct because I didn’t went through the administrative process to get the adapter into the stable repositories list yet. 🙄 But you should definitely see version 0.3.0 if you switch to beta/latest. |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, when I switch to the beta repository, only 0.2.13 is displayed. In the release repo the adapter is not listed at all. |
Beta Was this translation helpful? Give feedback.
-
|
This is strange because on Github I see the release and on npm as well? I have to aske somebody from the ioBroker team. Maybe I have to do something else there. But usually in the beta repositories pushing a new version to nmp should do the trick. |
Beta Was this translation helpful? Give feedback.
-
Which version of the |
Beta Was this translation helpful? Give feedback.
-
|
I'm running Admin 6.3.5 |
Beta Was this translation helpful? Give feedback.
-
|
To be honest, I don't have any idea whats the problem on your ioBroker installation. Maybe your Nodes version? You shold be on >=16.x. ioBroker.dev shows npm 0.3.0 and if I check the statistics, the number of installed 0.3.0 versions is growing as well. Maybe you should try to install it direct from NMP. If you install it from there, which version do you get? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I've installed / updated via URL. from github. Now with 0.3.0 my log is overflowing with query timer messages:
while I have not checked any of the additional logging messages in the extended option settings. |
Beta Was this translation helpful? Give feedback.
-
|
Currently there is no option to hide all log.info messages. Maybe I will find some time to add this option into the settings before the next release. |
Beta Was this translation helpful? Give feedback.
-
|
New option to hide Trigger logging messages is implemented and will be available in next release.
|
Beta Was this translation helpful? Give feedback.
-
This Jam Protection release adds a scheduled move of the main valve which can be activated and scheduled in the adapter settings area (Tab: Tasks)
Be verry careful with this functionality because it will close and open the main valve in order to prevent it to get stuck in open position and therefore will not close in case of an leakage.
The Jam Protection can be planed using a CRON schedule which will also be configured in the adapter settings Tasks tab.
Be verry careful there as well, because if you schedule a jam protection for example every 1 Minute you are having big trouble because your main valve will close and open every minute!
During the Jam Protection activity, no regular states (Valve, Alarms etc.) will be updated in order to prevent false trigger you may have set on of those states.
If the main valve is already in closed position, the Jam Protection activity will not be performed in order to prevent opening the main valve.
If there is water consumption at start of Jam Protection the action will be delayed for 1 minute. After 10 faild attempts (water still flowing) Jam Protection will be aborted.
Disclaimer / Warning
If during the Jam Protection activity communication to the device gets lost or the WAMO adapter or ioBroker itself crashes or will be stopped, the main valve will stay in the last commanded position! This means if something gets wrong, the valve could be closed and needs to be opened by yourself using the related app or the button on the device itself.
This discussion was created from the release Jam Protection.
Beta Was this translation helpful? Give feedback.
All reactions