Update deyeidc to 0.1.4

[raschy]

Please update my adapter ioBroker.deyeidc to version 0.1.4.

This pull request was created by https://www.iobroker.dev c0726ff.

[github-actions]

Automated adapter checker

ioBroker.deyeidc

-

👍 No errors found

Adapter releases: https://www.iobroker.dev/adapter/deyeidc/releases
Adapter statistic: https://www.iobroker.dev/adapter/deyeidc/statistics

History and usage information for release 0.1.3:

0.1.3 created 2.1.2025 (8 days old)
64 users (4.52%)

0.1.1 (stable) created 12.10.2024 (90 days old)
855 users (stable) (60.42%)

Please verify that this PR really tries to update to release 0.1.3!

Add comment "RE-CHECK!" to start check anew

[github-actions]

ioBroker repository information about STABLE-0-Day-PR tagging

Your PR has been tagged with the label STABLE-0-day-PR. This indicates that the release requested to be added to the stable repository has been created within one day after releasing the new version. Currently this release has not even been published at LATEST repository. So this release is too young for immediate processing.

Normally, a release should be available at LATEST repository for at least one or two weeks without any serious new issues detected within this timeframe. Your PR will be closed for now. Please create a new PR after the new version has been available at LATEST repository for at least one or two weeks, has a considerable number of installations and no serious new issues.

IMPORTANT:
Of course, it is possible to release a new version immediately if it is a hotfix for a serious problem, i.e. some errors cause adapter crashes or incompatible api changes of external websites blocking normal usage. In this case, please indicate this fact as a comment and mention mcm1957 and eventually Apollon77 explicitly. Please describe the reason (i.e. by referencing an issue). Hotfixes should minimize the changes, even dependency updates should be avoided if not related to the fix. New functionality and major (breaking) updates are most likely never a hotfix.

Please note that ANY (even hotfixes) should be available at LATEST repository for at least 1 day and have some (few) installations to avoid hotfixes with serious problems at stable repository. Exceptions to this minimal delay must be discussed individually.

Feel free to contact me (mcm1957) if you have any more questions.

[raschy]

Sorry for the hurry. I had not seen a way to get version 0.1.4 into the latest. So maybe a RE-CHECK will help here or just wait and see?

[mcm1957]

LATEST Repository is update twice a day automatically from latest versions at npm. Theres no action required to update releases at LATEST repository (besides deploying a new release at npm). As you created 0.1.4 just now ist should be available at LATEST this afternoon.

If the release is working for users feel free to create at stable request in one ore two weeks. Any release (exception emrgency releseases / hit fixes) must be available at latest for some time to be testes be BETA (LATEST) Testers.

[raschy]

Thank you. A new version of npm has been successfully deployed.