In earlier versions of extension I got the wonderful function that the actual state of an item appeared during hovering over the item name in item-files. But unfortunately this does not work since extensions version 0.7.
I searched also in nearly all threats to get some information about this behaviour, but I didn’t find anything. So I put this into my pocket of my to do’s for any time in the future. But today I found this feature still advertised in the docs on Git Hub, so it should work and I the failure is sitting in front of the keyboard.
Is there anybody to support me for this issue?
Any further details needed?
I am editing the texture files for openhabian (things, items, rules etc.) directly in VS Code. Assuming that this will work with ssh? Or do you think that this should separate mentioned in the file settings.json of VS Code (see after editing of my request)?
The corresponding items did show a valid hover in my case.
Maybe this helps or maybe you can then show us some error messages that show the behavior on your system.
Make sure to clean the log before testing with because the console is quickly getting messy with many messages.
Hi @Confectrician,
your idea is going deep into details, so I made some tests before answering.
My problem is that the hovering (btw. nice expression) is not possible, since beginning of this year (maybe by update to t+extension ver 0.7? So, it worked in the the past. And for me, it was a helpful support for generating reliable rules. But I did not know, that the hovering should be also possible for the items-files.
Switching to Developer Tools and erased the logs in the console tab. Now I tried to hover again in the rule file, but the same logs appeared as before erasing the logs, please look at attached print screen.
I hope that you see some details. But for me it does not look fine, so several failure logs, but no logs as expected from your side. So I think that the failure is in my installation, but where?
Do you have any further ideas? Thanks in advance for your support.
I reduced the VS Code settings to 2 lines:
“openhab.host”: “192.168.178.42”,
“openhab.port”: 8080,
nothing changed!
Hm where did i lead you to do this with my explanations?
(Sorry if i did, but i can’t read it somewhere.)
You definetely need to have the rest api enabled (which may be true by default).
The hovering uses the rest api to fetch the item states.
Can you please make sure again that it is enabled in settings?
The log does show no activity of the hover mechanism at all.
But we have to check again, after rest api is definetely turned on from you.
If you have deactivated it now by accident, it won’t even look for items states to hover.
Hi @Confectrician,
sorry for being late and answering your support tonight.
I reduced the settings in settings.json by the support by @denominator, but this did not work and there no change in the behaviour (“no hoovering”). So I switched it back including the call for REST-API. But I am not sure, if this calls are used incorrect manor in settings.json?
And I also checked the developer tools again, unfortunately there was no hoovering, but a lot of failures. I assume, that the source of my problems is in that part of the log. But I don’t know where! In the past it worked fine with hoovering and I appreciated this function. But sometimes in the past it disappeared.
Hi do you have any idea why the extension works, can view runtime item state when hovering over DSL items but can’t view the same items in javascript rules e.g in /etc/openhab/automation/test.js? Running OH 4.3.0 on RPi. Javascript rules do operate as expected.
because the console is quickly getting messy with many messages.
