Xenon-s / ioBroker.device-reminder

Notifications at device start or end by telegram, Alexa, Whatsapp, sayit, pushover, email
MIT License
27 stars 8 forks source link

Not possible to configure adapter instance after installation #322

Closed Dirte420 closed 11 months ago

Dirte420 commented 11 months ago

Describe the bug
I installed the device-reminder adapter (v1.2.9) in iobroker but for some reason it is not possible to configure the instance. I already tried to delete the instance and create a new one but the behavior is the same. Also when completely uninstalling and re-installing the adapter, I still have the same problem.

Directly after creating an instance I get redirected to instance settings where I can see the message Please activate the device-reminder.0 instance!

When refreshing the page or navigating to Instances I can see a warning on the instance which says that there is no connection to device/service.

When opening the instance settings for the first time I only see icon of the adapter but no config settings. If I click Save and Close, from this time on I see an empty table.

The behaviour is totally reproducible on my host, everytime I try it.

In the logs I can see the warning Update detected! Please open the Admin UI (instances -> device-reminder) and follow the instructions!

But as already described it is not possible to configure anything

To Reproduce
Steps to reproduce the behavior:

  1. install device-reminder adapter v1.2.9
  2. go to instance configuration

Expected behavior
Since I dont see anything done wrong on my side, I would expect being able to configure the instance.

Screenshots & Logfiles
2023-10-20 09_12_27-instances - iobroker-pi

2023-10-20 09_12_42-Posteingang - dh@keba com - Outlook

2023-10-20 09_13_15-instances - iobroker-pi

2023-10-20 09_13_45-logs - iobroker-pi

2023-10-20 09_58_41-instances - iobroker-pi

Versions:

Xenon-s commented 11 months ago

Sorry really, but after a short search on Google you would have seen immediately that the 1.2.9 is completely outdated and no longer works with the new JS controller 5.x and I've been working on a new version for weeks. Also there was this issue already several times here. Either you install the new 3.0.0 via github link or you have to wait 1-2 days, then the adapter is in the latest version.

Dirte420 commented 11 months ago

I did search for known problems but did not find anything useful. But thanks for information