[SOLVED] Lots of "Received HTTP GET request at 'items/<some text>' for the unknown item '<some text>'" since M4

Since upgrade to M4 I see a lot of strange log entries like these:

2019-11-10 09:30:42.104 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP GET request at 'items/acIsOn' for the unknown item 'acIsOn'.
2019-11-10 09:31:06.557 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP GET request at 'items/turnOff' for the unknown item 'turnOff'.
2019-11-10 09:31:08.714 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP GET request at 'items/turnOff' for the unknown item 'turnOff'.                                                                            2019-11-10 09:31:09.234 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP GET request at 'items/turnOff' for the unknown item 'turnOff'.
2019-11-10 09:31:09.643 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP GET request at 'items/turnOff' for the unknown item 'turnOff'.
2019-11-10 09:31:13.167 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP GET request at 'items/acIsOn' for the unknown item 'acIsOn'.
2019-11-10 09:31:13.369 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP GET request at 'items/acIsOn' for the unknown item 'acIsOn'.
2019-11-10 09:31:23.369 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP GET request at 'items/sendCommand' for the unknown item 'sendCommand'.
2019-11-10 09:31:26.444 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'daikin.rules' 
2019-11-10 09:35:53.199 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP GET request at 'items/msg' for the unknown item 'msg'.
2019-11-10 09:36:00.499 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP GET request at 'items/rule' for the unknown item 'rule'.
2019-11-10 09:36:00.806 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP GET request at 'items/rule' for the unknown item 'rule'.
2019-11-10 09:36:01.127 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP GET request at 'items/rule' for the unknown item 'rule'.
2019-11-10 09:36:01.477 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP GET request at 'items/rule' for the unknown item 'rule'.
2019-11-10 09:36:03.141 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP GET request at 'items/rule' for the unknown item 'rule'.
2019-11-10 09:36:22.957 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP GET request at 'items/state' for the unknown item 'state'.
2019-11-10 09:36:42.356 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP GET request at 'items/doorIsOpen' for the unknown item 'doorIsOpen'.
2019-11-10 09:36:43.257 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP GET request at 'items/tempBedroom' for the unknown item 'tempBedroom'.
2019-11-10 09:37:40.789 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP GET request at 'items/state' for the unknown item 'state'.
2019-11-10 09:38:03.469 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP GET request at 'items/is' for the unknown item 'is'.  

These ‘aledged’ items are elements of the rules file, like this part for example:

  ...
// Get current temperature readings
var Number tempBedroom = (MB_AC_TempIn.state as QuantityType<Number>).doubleValue
var Number tempOutside = (MB_AC_TempOut.state as Number).doubleValue

// Set status variables to default state
var Number doorIsOpen = 0
var Number acIsOn = 0

// Set default state of the action variables
var Number turnOn = 0
var Number turnOff = 0
  ...etc...
        else {
            if (AC_Vacation.state == ON) {
                logDebug(tag, "Vacation mode is on, turn off AC and exit Daikin rule")
                MB_AC_Power.sendCommand(OFF)
  ...etc...

There are no errors when loading the rules or items file. I’ve done all the usual stuff like clear temp and cache.
Also, the word ‘is’ as shown in the last log entry only appears on comment lines or in strings.

Currently I have no clue where to look to fix this. Any suggestion is welcome…

You beat me to it by 30 seconds. I was just about to mention that it must be due to the VSCode extension… ;o)

It does make quite a noise :smiley:, but the strange thing is that it also tries to find ‘items’ that are text inside a string…

1 Like

Hi,

You may already read that the “problem” is known.
I think we have to solve this before doing a new extension release. :slight_smile:
It will lead to many questionsike this one otherwise.

2 Likes

Just in case someone flys through this thread.

Problem should be solved with: