Thanks for this explanation. But I still believe there is something wired.
I tested the following scenarios (everytime with a new openhab container and a cleaned userdata folder)
- Scenario 1-3 are single pythonscripting (default & marketplace) installations and works perfectly
- Scenario 4 installs jsscripting and pythonscripting (default), needs a restart, are explainable and acceptable
- Scenario 5 & 6 installs jsscripting and pythonscripting (marketplace) and uninstalls pythonscripting automatically
- Scenario 7 installs jsscripting and pythonscripting (marketplace), needs a restart, are explainable and acceptable
all of that is reproducible
Scenarios
1. Single default Python Scripting via webUI ( Successful)
- There is nothing configured in addoncs.cfg and nothing inside the addons folder
- Installing of the default Python Scripting via WebUI
- Everything was installed and the python script files are loaded and executed successful
openhab> bundle:list | grep "Python Scripting" 285 │ Active │ 80 │ 5.0.0 │ openHAB Add-ons :: Bundles :: Automation :: Python Scripting openhab> feature:list | grep "Python Scripting" openhab-automation-pythonscripting │ 5.0.0 │ x │ Started │ openhab-addons-5.0.0 │ Python Scripting - Everything works perfect for at least 5 minutes. Then I jumped over to the next scenario.
2. Single marketplace Python Scripting Next via webUI ( Successful)
- There is nothing configured in addoncs.cfg and nothing inside the addons folder
- Installing of the Python Scripting Next via WebUI
- Everything was installed and the python script files are loaded and executed successful
openhab> bundle:list | grep "ython" 282 │ Active │ 80 │ 5.0.0.202507241323 │ openHAB Add-ons :: Bundles :: Automation :: Python Scripting 285 │ Active │ 80 │ 0 │ wrap_file__openhab_userdata_tmp_kar_org.openhab.automation.pythonscripting-5.0.0-SNAPSHOT_org_lastnpe_eea_eea-all_2.4.0_eea-all-2.4.0.jar openhab> feature:list | grep "ython" openhab-automation-pythonscripting │ 5.0.0.SNAPSHOT │ x │ Started │ org.openhab.automation.pythonscripting-5.0.0-SNAPSHOT │ Python Scripting org.openhab.automation.pythonscripting │ 5.0.0.SNAPSHOT │ x │ Started │ org.openhab.automation.pythonscripting-5.0.0-SNAPSHOT │ openHAB Add-ons :: Bundles :: Automation :: Pytho openhab-automation-pythonscripting │ 5.0.0 │ │ Uninstalled │ openhab-addons-5.0.0 │ Python Scripting - There was a error message like “[t.core.internal.addons.AddonResource] - Exception while installing add-on: Configuration Admin service has been unregistered”, but I guess it is unrelated
- Everything works perfect for at least 5 minutes. Then I jumped over to the next scenario.
3. Single marketplace Python Scripting Next via addons folder ( Successful)
- There is nothing configured in addoncs.cfg
- Putting of the Python Scripting Next Snapshot kar file into the addons folder
- Everything was installed and the python script files are loaded and executed successful
openhab> bundle:list | grep ython 281 │ Active │ 80 │ 5.0.0.202507241323 │ openHAB Add-ons :: Bundles :: Automation :: Python Scripting 285 │ Active │ 80 │ 0 │ wrap_file__openhab_userdata_tmp_kar_org.openhab.automation.pythonscripting-5.0.0-SNAPSHOT_org_lastnpe_eea_eea-all_2.4.0_eea-all-2.4.0.jar openhab> feature:list | grep ython openhab-automation-pythonscripting │ 5.0.0.SNAPSHOT │ x │ Started │ org.openhab.automation.pythonscripting-5.0.0-SNAPSHOT │ Python Scripting org.openhab.automation.pythonscripting │ 5.0.0.SNAPSHOT │ │ Uninstalled │ org.openhab.automation.pythonscripting-5.0.0-SNAPSHOT │ openHAB Add-ons :: Bundles :: Automation :: Pytho openhab-automation-pythonscripting │ 5.0.0 │ │ Uninstalled │ openhab-addons-5.0.0 │ Python Scripting - Everything works perfect for at least 5 minutes. Then I jumped over to the next scenario.
4. Default JSScripting via webUI and default Python Scripting via webUI ( ERROR & after restart Successful)
- There is nothing configured in addoncs.cfg and nothing inside the addons folder
- Installing of the default JSScripting followed by default Python Scripting via WebUI
- JSScripting works
- Python Scripting throws an exception
“java.lang.NullPointerException: Cannot invoke “org.graalvm.polyglot.Language.getName()” because “language” is null”- this could happen, because the graal language is not initialized
- I checked that all bundles (including the graal bundles are active)
openhab> bundle:list | grep "Python Scripting" 285 │ Active │ 80 │ 5.0.0 │ openHAB Add-ons :: Bundles :: Automation :: Python Scripting openhab> feature:list | grep "Python Scripting" openhab-automation-pythonscripting │ 5.0.0 │ x │ Started │ openhab-addons-5.0.0 │ Python Scripting - this could happen, because the graal language is not initialized
- If I installed first Python Scripting and then JSScripting, JSScripting was throwing an exception
“java.lang.IllegalArgumentException: Could not find option with name js.commonjs-require.” - JSScripting & Python Scripting was working properly after a openhab restart without any exception for at least 5 minutes. Then I jumped over to the next scenario.
This is acceptable, because it is explainable
5. Default JSScripting via webUI and marketplace Python Scripting Next via webUI ( ERROR)
- There is nothing configured in addoncs.cfg and nothing inside the addons folder
- Installing of the default JSScripting followed by marketplace Python Scripting Next via WebUI
- JSScripting works
- Python Scripting throws an exception
“java.lang.IllegalStateException: Graal python language not available”- this could happen, because the graal language is not initialized
- I checked that all bundles (including the graal bundles are active)
- but this can normaly be solved with an openhab restart
openhab> bundle:list | grep ython 285 │ Active │ 80 │ 5.0.0.202507241323 │ openHAB Add-ons :: Bundles :: Automation :: Python Scripting 288 │ Active │ 80 │ 0 │ wrap_file__openhab_userdata_tmp_kar_org.openhab.automation.pythonscripting-5.0.0-SNAPSHOT_org_lastnpe_eea_eea-all_2.4.0_eea-all-2.4.0.jar openhab> feature:list | grep ython openhab-automation-pythonscripting │ 5.0.0.SNAPSHOT │ x │ Started │ org.openhab.automation.pythonscripting-5.0.0-SNAPSHOT │ Python Scripting org.openhab.automation.pythonscripting │ 5.0.0.SNAPSHOT │ x │ Started │ org.openhab.automation.pythonscripting-5.0.0-SNAPSHOT │ openHAB Add-ons :: Bundles :: Automation :: Pytho openhab-automation-pythonscripting │ 5.0.0 │ │ Uninstalled │ openhab-addons-5.0.0 │ Python Scripting - this could happen, because the graal language is not initialized
- Python Scripting Next was uninstalled automatically after ~30 seconds
openhab> bundle:list | grep ython 288 │ Active │ 80 │ 0 │ wrap_file__openhab_userdata_tmp_kar_org.openhab.automation.pythonscripting-5.0.0-SNAPSHOT_org_lastnpe_eea_eea-all_2.4.0_eea-all-2.4.0.jar openhab> feature:list | grep ython openhab-automation-pythonscripting │ 5.0.0.SNAPSHOT │ │ Uninstalled │ org.openhab.automation.pythonscripting-5.0.0-SNAPSHOT │ Python Scripting org.openhab.automation.pythonscripting │ 5.0.0.SNAPSHOT │ x │ Started │ org.openhab.automation.pythonscripting-5.0.0-SNAPSHOT │ openHAB Add-ons :: Bundles :: Automation :: Pytho openhab-automation-pythonscripting │ 5.0.0 │ │ Uninstalled │ openhab-addons-5.0.0 │ Python Scripting
6. Default JSScripting via webUI and marketplace Python Scripting Next via addons folder ( ERROR)
- There is nothing configured in addoncs.cfg
- Installing of the default JSScripting followed by marketplace Python Scripting Next via addons folder
- JSScripting works
- Python Scripting throws an exception
“java.lang.IllegalStateException: Graal python language not available”openhab> bundle:list | grep ython 285 │ Active │ 80 │ 5.0.0.202507241323 │ openHAB Add-ons :: Bundles :: Automation :: Python Scripting 288 │ Active │ 80 │ 0 │ wrap_file__openhab_userdata_tmp_kar_org.openhab.automation.pythonscripting-5.0.0-SNAPSHOT_org_lastnpe_eea_eea-all_2.4.0_eea-all-2.4.0.jar openhab> feature:list | grep ython openhab-automation-pythonscripting │ 5.0.0.SNAPSHOT │ x │ Started │ org.openhab.automation.pythonscripting-5.0.0-SNAPSHOT │ Python Scripting org.openhab.automation.pythonscripting │ 5.0.0.SNAPSHOT │ x │ Started │ org.openhab.automation.pythonscripting-5.0.0-SNAPSHOT │ openHAB Add-ons :: Bundles :: Automation :: Pytho openhab-automation-pythonscripting │ 5.0.0 │ │ Uninstalled │ openhab-addons-5.0.0 │ Python Scripting - Python Scripting Next was uninstalled automatically after ~30 seconds
openhab> bundle:list | grep ython 288 │ Active │ 80 │ 0 │ wrap_file__openhab_userdata_tmp_kar_org.openhab.automation.pythonscripting-5.0.0-SNAPSHOT_org_lastnpe_eea_eea-all_2.4.0_eea-all-2.4.0.jar openhab> feature:list | grep ython openhab-automation-pythonscripting │ 5.0.0.SNAPSHOT │ │ Uninstalled │ org.openhab.automation.pythonscripting-5.0.0-SNAPSHOT │ Python Scripting org.openhab.automation.pythonscripting │ 5.0.0.SNAPSHOT │ x │ Started │ org.openhab.automation.pythonscripting-5.0.0-SNAPSHOT │ openHAB Add-ons :: Bundles :: Automation :: Pytho openhab-automation-pythonscripting │ 5.0.0 │ │ Uninstalled │ openhab-addons-5.0.0 │ Python Scripting - Behavior is similar to scenario 5
7. Default JSScripting via addons.cfg and marketplace Python Scripting Next via addons folder and enabled via addons.cfg too ( ERROR & after restart Successful)
- Installing of the default JSScripting via addons.cfg followed by marketplace Python Scripting via addons folder and addons.cfg too
- JSScripting works
- Python Scripting throws an exception
- The rest is similar to scenario 4
- This means after a restart everything works
This is acceptable too, because it is explainable
Conclusion
-
Every Add-on alone works perfectly. Independently if they are installed via webUI or addons folder and if they are the default ones or not.
-
The problems begins if jsscriptiung and pythonscripting comes together
- & If both Add-ons are the default ones and installed via webUI it works perfectly after a restart (the explanation is the not initialized graal language)
- If Python Scripting is the marketplace version and installed via webUI it never works. It will always be uninstalled
- If Python Scripting is the marketplace version and installed via addons folder it never works too. It will always be uninstalled
- & If Python Scripting is the marketplace version and installed via addons folder and enabled via addons.cfg it works after a restart too. (the explanation is the not initialized graal language)
If both are the default ones, after a restart is everything is fine. This is ok, because it is explainable.
If Pythonscripting is the marketplace one, both Add-ons have to be activated in addons.cfg. There is no other way to get this combination working