@mlobstein - it seems that polling is failing for some reason. I increased the polling rate to 5s, and enabled debugging…
Seeing this repeatedly with the PJ powered OFF and ON:
15:27:47.119 [DEBUG] [rojector.internal.BenqProjectorDevice] - Query: 'pow=?'
15:27:47.223 [DEBUG] [rojector.internal.BenqProjectorDevice] - Response: '>*pow=?
*POW=ON
'
15:27:47.224 [DEBUG] [internal.handler.BenqProjectorHandler] - Error executing command 'Power', Invalid respose for command: pow=?
I also noticed that various other items such as Source do not update if they are changed manually with the PJ remote. Playing with the items via the Main UI regularly logs this:
15:31:49.163 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'NetworkDeviceBx10010192_Latency' changed from 18.0 ms to 17.0 ms
15:31:49.484 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'NetworkDeviceBx10010192_LastSeen' changed from 2021-02-27T15:30:49.140-0500 to 2021-02-27T15:31:49.480-0500
15:31:53.676 [DEBUG] [rojector.internal.BenqProjectorDevice] - Query: 'pow=?'
15:31:53.779 [DEBUG] [rojector.internal.BenqProjectorDevice] - Response: '>*pow=?
*POW=ON
'
15:31:53.781 [DEBUG] [internal.handler.BenqProjectorHandler] - Error executing command 'Power', Invalid respose for command: pow=?
15:31:53.784 [DEBUG] [rojector.internal.BenqProjectorDevice] - Query: 'sour=?'
15:31:53.886 [DEBUG] [rojector.internal.BenqProjectorDevice] - Response: '>*sour=?
*SOUR=HDMI2
'
15:31:53.889 [DEBUG] [internal.handler.BenqProjectorHandler] - Error executing command 'Source', Invalid respose for command: sour=?
15:31:53.892 [DEBUG] [rojector.internal.BenqProjectorDevice] - Query: 'appmod=?'
15:31:53.994 [DEBUG] [rojector.internal.BenqProjectorDevice] - Response: '>*appmod=?
*APPMOD=STD
'
15:31:53.996 [DEBUG] [internal.handler.BenqProjectorHandler] - Error executing command 'PictureMode', Invalid respose for command: appmod=?
15:31:53.999 [DEBUG] [rojector.internal.BenqProjectorDevice] - Query: 'appmod=?'
15:31:54.103 [DEBUG] [rojector.internal.BenqProjectorDevice] - Response: '>*appmod=?
*APPMOD=STD
'
15:31:54.105 [DEBUG] [internal.handler.BenqProjectorHandler] - Error executing command 'AspectRatio', Invalid respose for command: appmod=?
15:31:54.108 [DEBUG] [rojector.internal.BenqProjectorDevice] - Query: 'freeze=?'
15:31:54.210 [DEBUG] [rojector.internal.BenqProjectorDevice] - Response: '>*freeze=?
*FREEZE=OFF
'
15:31:54.212 [DEBUG] [internal.handler.BenqProjectorHandler] - Error executing command 'Freeze', Invalid respose for command: freeze=?
15:31:54.217 [DEBUG] [rojector.internal.BenqProjectorDevice] - Query: 'blank=?'
15:31:54.319 [DEBUG] [rojector.internal.BenqProjectorDevice] - Response: '>*blank=?
*BLANK=OFF
'
However all of the expected commands do in fact work (including DirectCMD commands). While testing everything the binding has to offer, as long as my PJ model has that feature/setting, it works well! A nicety would be have the ability to hide the many other command options for a better user experience, but no worries there… Only major problem observed so far here revolves around the failed polling of the many states, and of course the aforementioned ?*Block item issue.
Another tidbit regarding polling - I tried to inspect the TCP activity on my OH Server by running this repeatedly (filtering for the port defined in the PJ’s thing configuration), and it does show the communication is happening. I definitely did install the feature too BTW (feature:install openhab-transport-serial).
sudo netstat -nputw |grep 20108
tcp6 0 0 10.0.10.161:49310 10.X.XXX.XXX:20108 ESTABLISHED 667/java
From what I can tell the polling request is hitting the network stack, as I would expect, but is failing to properly parse the response… Because of this, when toggling Power ON via the Main UI, it quickly switches back to OFF. A rapid ON/OFF toggle is the only way to actually power it down. The other oddity is that while the Thing shows as ONLINE, making any changes to the Thing Configuration results in it changing to UNKNOWN and then getting stuck in an OFFLINE state, until another Power ON command is sent via the Main UI.
Glad to help however possible!
Best regards,
.