resolution of uriFragment ‘|::0.2.0.2.0.0.0.6.6::0::/1’ failed.
java.lang.NullPointerException: null
This is my new rule. As soon as the BOLD part is uncommented, i get this error. If i comment it out, no error.
This kind of Logic (including item and sitemap) is already in use and working.
Filename: tagesmodus.rules (i copied an existing rule, renamed and replaced content)
rule “r_Tagesmodus_1”
when
Item i_v_Tagesmodus changed
then
if(i_v_Tagesmodus.state==4)
{ i_v_Tagesmodus.postUpdate(100)
}
end
items:
Number i_v_Tagesmodus
Switch i_v_Tagesmodus_Auto_Aktiv
Any guess what this could be?
This is the working one
rule “r_1OG_Wohnzimmer_Beschattung_Gesamt_1”
when
Item i_v_Beschattung_Wohnzimmer_Gesamt changed
then
if(i_v_Beschattung_Wohnzimmer_Gesamt.state==1)
{
i_v_Beschattung_Wohnzimmer_Gesamt.postUpdate(100)
}
end
The working rule was created before update to 2.5.3. I dont see any differences between the working one (created before update to 2.5.3) and the new one giving the error (created after update to 2.5.3)
Did you ever find the reason for this behaviour? I have the same error. But It just started with OpenHAB so I assume a fresh install will not really make any difference (just installed it three days ago…).
As soon as I try to "Schalter_EG.sendCommand(ON) I am getting this Nul Pointer Exception, just aas you.
I couldnt find out, but after a fresh install it worked again.
In your case i anyway would give it a try, do a fresh install and maybe first do a test by just adding what you need to send this command (only one thing, only this single item and this single rule).
For me, it was important to take fresh emtpy folders and just put the files (things, items, sitemap, rules) back in.
you mean a complete new start with a new SD_card image?
That’s a lot of work!
I recently got this error as well, but will try with clean cache and multiple restarts first.
Same error here. Started today…everything seems to be working, but logs are flooded with this. Did anyone find a fix? Apart from reinstalling everything…
I’m amazed it’s been four years and nobody’s posted the log lines. Still a problem, here they are:
2024-12-04 14:48:37.621 [ERROR] [xbase.resource.BatchLinkableResource] - resolution of uriFragment ‘|::0.0.12::0::/1’ failed.
java.lang.NullPointerException: Cannot read field “actionServices” because the return value of “org.openhab.core.model.script.ScriptServiceUtil.getInstance()” is null
at org.openhab.core.model.script.ScriptServiceUtil.getActionServices(ScriptServiceUtil.java:123) ~[?:?]
at org.openhab.core.model.script.scoping.ActionClassLoader.loadClass(ActionClassLoader.java:36) ~[?:?]
at java.lang.Class.forName0(Native Method) ~[?:?]
at java.lang.Class.forName(Class.java:467) ~[?:?]
- after that, it’s just java vomit.
I get these errors at reboot of OpenHab. After the java vomit clears, the system does continue to initialize and come up.
I cloned my git config files into a new OH4.3.1 install and triggered thousands of lines like this:
ERROR org.eclipse.xtext.xbase.resource.BatchLinkableResource resolution of uriFragment '|::0.2.4.2.0.0.7.0.7.6.1.6::0::/1' failed.
The part in the ’ ’ changed as the lines flooded the log, but was always similar.
There were some occasional appearances of these, which were huge long lines repeating the phrase Error executing EValidator about five times and occasionally throwing in a :
Below the hundreds of lines just like the above, there was this line, hinting at which .rules file was causing the issue:
INFO org.openhab.core.model.core.internal.ModelRepositoryImpl Validation issues found in configuration model 'hvac.heatpump.rules', using it anyway: Error executing EValidator Error executing EValidator Error executing EValidator Error executing EValidator Error executing EValidator Error executing EValidator Error executing EValidator...
I’ve truncated that line when I pasted it because it repeated the phrase about 50 times, interspersed with mentions of every local variable in one of the rules like this:
The value of the local variable outside is not used
At the top of my rules file there were three global variables - removing them made the issue go away.