Closed chris-hoe closed 2 years ago
Expert Mode is on, but i can´t select a version from the list. It looks like
Easier: Admin - Adapter - Enable expert mode - click the github icon/custom install ... first tab "install from npm"
That didn't work for me - the installed version was always shown as 0.1.5 even after the installation from npm. The only way I was able to get back to 0.1.4 was the way I described earlier.
if it now works again, can you try GitHub again please? Just to be sure? ...
I didn´t found it on npm...i will try it from github again.
Actually installed from github looks like
Log
philips-air.0 | 2022-03-23 22:24:15.436 | debug | GET /sys/dev/status to 192.168.0.160 -- | -- | -- | -- philips-air.0 | 2022-03-23 22:24:15.435 | info | Received: 672872F2 philips-air.0 | 2022-03-23 22:24:15.433 | debug | Response data incoming: {"type":"Buffer","data":[54,55,50,56,55,50,70,50]} philips-air.0 | 2022-03-23 22:24:15.431 | debug | Response incoming philips-air.0 | 2022-03-23 22:24:15.370 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-03-23 22:23:45.387 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-03-23 22:23:45.385 | info | Received: 64E1D495 philips-air.0 | 2022-03-23 22:23:45.384 | debug | Response data incoming: {"type":"Buffer","data":[54,52,69,49,68,52,57,53]} philips-air.0 | 2022-03-23 22:23:45.381 | debug | Response incoming philips-air.0 | 2022-03-23 22:23:45.371 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-03-23 22:23:15.394 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-03-23 22:23:15.393 | info | Received: 766D2417 philips-air.0 | 2022-03-23 22:23:15.391 | debug | Response data incoming: {"type":"Buffer","data":[55,54,54,68,50,52,49,55]} philips-air.0 | 2022-03-23 22:23:15.389 | debug | Response incoming philips-air.0 | 2022-03-23 22:23:15.371 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-03-23 22:22:45.418 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-03-23 22:22:45.416 | info | Received: 399B0B19 philips-air.0 | 2022-03-23 22:22:45.409 | debug | Response data incoming: {"type":"Buffer","data":[51,57,57,66,48,66,49,57]} philips-air.0 | 2022-03-23 22:22:45.403 | debug | Response incoming philips-air.0 | 2022-03-23 22:22:45.388 | debug | started philips-air.0 | 2022-03-23 22:22:45.367 | debug | start with 192.168.0.160 {"host":"192.168.0.160","aliveTimeout":"30000","reconnectInterval":"30000"} philips-air.0 | 2022-03-23 22:22:45.299 | info | starting. Version 0.1.5 (non-npm: iobroker-community-adapters/ioBroker.philips-air#cfca6f34e0259c59ca341a89fcdb87d274b5ba5a) in /opt/iobroker/node_modules/iobroker.philips-air, node: v14.19.0, js-controller: 4.0.21 philips-air.0 | 2022-03-23 22:22:44.703 | debug | Plugin sentry Initialize Plugin (enabled=true) philips-air.0 | 2022-03-23 22:22:44.579 | debug | States connected to redis: 127.0.0.1:9000 philips-air.0 | 2022-03-23 22:22:44.553 | debug | States create User PubSub Client philips-air.0 | 2022-03-23 22:22:44.551 | debug | States create System PubSub Client philips-air.0 | 2022-03-23 22:22:44.532 | debug | Redis States: Use Redis connection: 127.0.0.1:9000 philips-air.0 | 2022-03-23 22:22:44.504 | debug | Objects connected to redis: 127.0.0.1:9001 philips-air.0 | 2022-03-23 22:22:44.497 | debug | Objects client initialize lua scripts philips-air.0 | 2022-03-23 22:22:44.448 | debug | Objects create User PubSub Client philips-air.0 | 2022-03-23 22:22:44.447 | debug | Objects create System PubSub Client philips-air.0 | 2022-03-23 22:22:44.443 | debug | Objects client ready ... initialize now philips-air.0 | 2022-03-23 22:22:44.353 | debug | Redis Objects: Use Redis connection: 127.0.0.1:9001Ok, meeehhh ...thank you .. I come back when we have next idea :-)) Happy 0.1.4 usage for now
Ok, Just to make sure I did one last try for now on GitHub ... Please check again (but go to 0,1.4 before always!!!)
One moment, i´m not so fast :-) and i have only a little bit of iobroker skills. I´m a newbie. Sorry :-(
noooo stress
Installed from github 0.1.4
After a while, the Device get disconnected
And after another while, the device reconnected
Connect & Disconnect are toogling
After installing the 0.1.5 (no toogling, only disconnect)
Log after 0.1.5
philips-air.0 | 2022-03-23 23:07:18.808 | debug | GET /sys/dev/status to 192.168.0.160 -- | -- | -- | -- philips-air.0 | 2022-03-23 23:07:18.807 | info | Received: 52A3D7CC philips-air.0 | 2022-03-23 23:07:18.805 | debug | Response data incoming: {"type":"Buffer","data":[53,50,65,51,68,55,67,67]} philips-air.0 | 2022-03-23 23:07:18.803 | debug | Response incoming philips-air.0 | 2022-03-23 23:07:18.790 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-03-23 23:06:48.808 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-03-23 23:06:48.807 | info | Received: 2D561434 philips-air.0 | 2022-03-23 23:06:48.804 | debug | Response data incoming: {"type":"Buffer","data":[50,68,53,54,49,52,51,52]} philips-air.0 | 2022-03-23 23:06:48.802 | debug | Response incoming philips-air.0 | 2022-03-23 23:06:48.789 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-03-23 23:06:18.805 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-03-23 23:06:18.804 | info | Received: 603BB2E0 philips-air.0 | 2022-03-23 23:06:18.802 | debug | Response data incoming: {"type":"Buffer","data":[54,48,51,66,66,50,69,48]} philips-air.0 | 2022-03-23 23:06:18.800 | debug | Response incoming philips-air.0 | 2022-03-23 23:06:18.789 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-03-23 23:05:48.816 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-03-23 23:05:48.814 | info | Received: 4FD5D666 philips-air.0 | 2022-03-23 23:05:48.812 | debug | Response data incoming: {"type":"Buffer","data":[52,70,68,53,68,54,54,54]} philips-air.0 | 2022-03-23 23:05:48.809 | debug | Response incoming philips-air.0 | 2022-03-23 23:05:48.789 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-03-23 23:05:18.832 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-03-23 23:05:18.830 | info | Received: 67216683 philips-air.0 | 2022-03-23 23:05:18.826 | debug | Response data incoming: {"type":"Buffer","data":[54,55,50,49,54,54,56,51]} philips-air.0 | 2022-03-23 23:05:18.822 | debug | Response incoming philips-air.0 | 2022-03-23 23:05:18.806 | debug | started philips-air.0 | 2022-03-23 23:05:18.785 | debug | start with 192.168.0.160 {"host":"192.168.0.160","aliveTimeout":"30000","reconnectInterval":"30000"} philips-air.0 | 2022-03-23 23:05:18.713 | info | starting. Version 0.1.5 (non-npm: iobroker-community-adapters/ioBroker.philips-air) in /opt/iobroker/node_modules/iobroker.philips-air, node: v14.19.0, js-controller: 4.0.21 philips-air.0 | 2022-03-23 23:05:18.124 | debug | Plugin sentry Initialize Plugin (enabled=true) philips-air.0 | 2022-03-23 23:05:18.024 | debug | States connected to redis: 127.0.0.1:9000 philips-air.0 | 2022-03-23 23:05:18.001 | debug | States create User PubSub Client philips-air.0 | 2022-03-23 23:05:18.000 | debug | States create System PubSub Client philips-air.0 | 2022-03-23 23:05:17.986 | debug | Redis States: Use Redis connection: 127.0.0.1:9000 philips-air.0 | 2022-03-23 23:05:17.959 | debug | Objects connected to redis: 127.0.0.1:9001 philips-air.0 | 2022-03-23 23:05:17.952 | debug | Objects client initialize lua scripts philips-air.0 | 2022-03-23 23:05:17.913 | debug | Objects create User PubSub Client philips-air.0 | 2022-03-23 23:05:17.912 | debug | Objects create System PubSub Client philips-air.0 | 2022-03-23 23:05:17.909 | debug | Objects client ready ... initialize now philips-air.0 | 2022-03-23 23:05:17.846 | debug | Redis Objects: Use Redis connection: 127.0.0.1:9001I don´t know, if i make it right...
Go to the "Adaptors" tab, turn on expert mode, click on the Philips Air adapter and select "Update to revision" and pick the 0.1.4 version from the list.
I must select "beta repositories"...now it is possible...
All good, ok then it was really not that code place that I suspected ... we need to seach further
Go to the "Adaptors" tab, turn on expert mode, click on the Philips Air adapter and select "Update to revision" and pick the 0.1.4 version from the list.
I must select "beta repositories"...now it is possible...
@boos87 - sorry, yes, you are right - I forgot to mention that part. :-(
All good, ok then it was really not that code place that I suspected ... we need to seach further
@Apollon77 - alright, if you have again something you want to be tested let me know.
We think about how it makes most sense :-)
Ok, I close here because effectively fixed ... but will write when we have more to test
@chris-hoe @boos87 Ok, I have now a potential solution for the last upgrade issue. Could you please try GitHub version again (will show up as 0.1.6? Does it still work with it?
@chris-hoe @boos87 any chance for a check? ;-)
Hi, I´m sorry, i was on vaccation the last week, so I had no chance to test the adapter. Now, i have install the version 0.1.6 from github. The device doesn´t connect.
Now, when i try to download the Log-File, my Raspberry Pi 4 is restarting. It is now the fourth time. I don´t know, if there is a context between the new version of the adapter and the restarting of the pi.
The debug-log from the screen:
philips-air.0 | 2022-04-23 23:50:00.432 | debug | GET /sys/dev/status to 192.168.0.160 -- | -- | -- | -- philips-air.0 | 2022-04-23 23:50:00.431 | info | Received: 0C0C0B40 philips-air.0 | 2022-04-23 23:50:00.430 | debug | Response data incoming: {"type":"Buffer","data":[48,67,48,67,48,66,52,48]} philips-air.0 | 2022-04-23 23:50:00.429 | debug | Response incoming philips-air.0 | 2022-04-23 23:50:00.416 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-04-23 23:49:30.437 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-04-23 23:49:30.436 | info | Received: 03CC29D1 philips-air.0 | 2022-04-23 23:49:30.434 | debug | Response data incoming: {"type":"Buffer","data":[48,51,67,67,50,57,68,49]} philips-air.0 | 2022-04-23 23:49:30.432 | debug | Response incoming philips-air.0 | 2022-04-23 23:49:30.416 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-04-23 23:49:00.438 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-04-23 23:49:00.437 | info | Received: 1C0E82AF philips-air.0 | 2022-04-23 23:49:00.436 | debug | Response data incoming: {"type":"Buffer","data":[49,67,48,69,56,50,65,70]} philips-air.0 | 2022-04-23 23:49:00.434 | debug | Response incoming philips-air.0 | 2022-04-23 23:49:00.417 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-04-23 23:48:30.444 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-04-23 23:48:30.442 | info | Received: 157A9B47 philips-air.0 | 2022-04-23 23:48:30.440 | debug | Response data incoming: {"type":"Buffer","data":[49,53,55,65,57,66,52,55]} philips-air.0 | 2022-04-23 23:48:30.437 | debug | Response incoming philips-air.0 | 2022-04-23 23:48:30.417 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-04-23 23:48:00.435 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-04-23 23:48:00.434 | info | Received: 380A9D69 philips-air.0 | 2022-04-23 23:48:00.433 | debug | Response data incoming: {"type":"Buffer","data":[51,56,48,65,57,68,54,57]} philips-air.0 | 2022-04-23 23:48:00.432 | debug | Response incoming philips-air.0 | 2022-04-23 23:48:00.417 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-04-23 23:47:30.432 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-04-23 23:47:30.431 | info | Received: 556F4EAD philips-air.0 | 2022-04-23 23:47:30.430 | debug | Response data incoming: {"type":"Buffer","data":[53,53,54,70,52,69,65,68]} philips-air.0 | 2022-04-23 23:47:30.429 | debug | Response incoming philips-air.0 | 2022-04-23 23:47:30.417 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-04-23 23:47:00.434 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-04-23 23:47:00.434 | info | Received: 5FFA541C philips-air.0 | 2022-04-23 23:47:00.432 | debug | Response data incoming: {"type":"Buffer","data":[53,70,70,65,53,52,49,67]} philips-air.0 | 2022-04-23 23:47:00.431 | debug | Response incoming philips-air.0 | 2022-04-23 23:47:00.416 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-04-23 23:46:30.462 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-04-23 23:46:30.461 | info | Received: 4ACA3A51 philips-air.0 | 2022-04-23 23:46:30.456 | debug | Response data incoming: {"type":"Buffer","data":[52,65,67,65,51,65,53,49]} philips-air.0 | 2022-04-23 23:46:30.452 | debug | Response incoming philips-air.0 | 2022-04-23 23:46:30.434 | debug | started philips-air.0 | 2022-04-23 23:46:30.413 | debug | start with 192.168.0.160 {"host":"192.168.0.160","aliveTimeout":"30000","reconnectInterval":"30000"} philips-air.0 | 2022-04-23 23:46:30.338 | info | starting. Version 0.1.6 (non-npm: iobroker-community-adapters/ioBroker.philips-air#7dc009d74f0b3fccd7814399a4c7891f6d3f3991) in /opt/iobroker/node_modules/iobroker.philips-air, node: v14.19.0, js-controller: 4.0.21 philips-air.0 | 2022-04-23 23:46:29.661 | debug | Plugin sentry Initialize Plugin (enabled=true) philips-air.0 | 2022-04-23 23:46:29.552 | debug | States connected to redis: 127.0.0.1:9000 philips-air.0 | 2022-04-23 23:46:29.529 | debug | States create User PubSub Client philips-air.0 | 2022-04-23 23:46:29.528 | debug | States create System PubSub Client philips-air.0 | 2022-04-23 23:46:29.510 | debug | Redis States: Use Redis connection: 127.0.0.1:9000 philips-air.0 | 2022-04-23 23:46:29.478 | debug | Objects connected to redis: 127.0.0.1:9001 philips-air.0 | 2022-04-23 23:46:29.470 | debug | Objects client initialize lua scripts philips-air.0 | 2022-04-23 23:46:29.419 | debug | Objects create User PubSub Client philips-air.0 | 2022-04-23 23:46:29.418 | debug | Objects create System PubSub Client philips-air.0 | 2022-04-23 23:46:29.415 | debug | Objects client ready ... initialize now philips-air.0 | 2022-04-23 23:46:29.359 | debug | Redis Objects: Use Redis connection: 127.0.0.1:9001Ok, Danke, sind also immer noch "nicht funktionierend". Gut wir suchen weiter
Yes, unfortunately it doesn´t work. So i think, the new version in context with the debug leads to a crash of my Pi 4with 4GB. I have deactivate the instance from Philips and the Pi works without problems.
@boos87 @chris-hoe Ok, hopefully last try ... @JKRhb was finally able to identify and hopefully fix the issue ...
Hi, i have tried the version on github.
Debug-Log:
philips-air.0 | 2022-04-24 20:03:28.639 | debug | GET /sys/dev/status to 192.168.0.160 -- | -- | -- | -- philips-air.0 | 2022-04-24 20:03:28.638 | info | Received: 28452DB3 philips-air.0 | 2022-04-24 20:03:28.635 | debug | Response data incoming: {"type":"Buffer","data":[50,56,52,53,50,68,66,51]} philips-air.0 | 2022-04-24 20:03:28.633 | debug | Response incoming philips-air.0 | 2022-04-24 20:03:28.622 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-04-24 20:02:58.640 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-04-24 20:02:58.638 | info | Received: 3217C2BE philips-air.0 | 2022-04-24 20:02:58.636 | debug | Response data incoming: {"type":"Buffer","data":[51,50,49,55,67,50,66,69]} philips-air.0 | 2022-04-24 20:02:58.633 | debug | Response incoming philips-air.0 | 2022-04-24 20:02:58.622 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-04-24 20:02:28.640 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-04-24 20:02:28.638 | info | Received: 463DD4E4 philips-air.0 | 2022-04-24 20:02:28.636 | debug | Response data incoming: {"type":"Buffer","data":[52,54,51,68,68,52,69,52]} philips-air.0 | 2022-04-24 20:02:28.633 | debug | Response incoming philips-air.0 | 2022-04-24 20:02:28.622 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-04-24 20:01:58.636 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-04-24 20:01:58.636 | info | Received: 60E7EA00 philips-air.0 | 2022-04-24 20:01:58.634 | debug | Response data incoming: {"type":"Buffer","data":[54,48,69,55,69,65,48,48]} philips-air.0 | 2022-04-24 20:01:58.633 | debug | Response incoming philips-air.0 | 2022-04-24 20:01:58.621 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-04-24 20:01:28.772 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-04-24 20:01:28.769 | info | Received: 295E791B philips-air.0 | 2022-04-24 20:01:28.746 | debug | Response data incoming: {"type":"Buffer","data":[50,57,53,69,55,57,49,66]} philips-air.0 | 2022-04-24 20:01:28.727 | debug | Response incoming philips-air.0 | 2022-04-24 20:01:28.688 | debug | started philips-air.0 | 2022-04-24 20:01:28.583 | debug | start with 192.168.0.160 {"host":"192.168.0.160","aliveTimeout":"30000","reconnectInterval":"30000"} philips-air.0 | 2022-04-24 20:01:28.387 | info | starting. Version 0.1.6 (non-npm: iobroker-community-adapters/ioBroker.philips-air#872c5f4ef5e4e23016958d8f1afd0b5080bbe02a) in /opt/iobroker/node_modules/iobroker.philips-air, node: v14.19.0, js-controller: 4.0.21 philips-air.0 | 2022-04-24 20:01:26.496 | debug | Plugin sentry Initialize Plugin (enabled=true) philips-air.0 | 2022-04-24 20:01:26.328 | debug | States connected to redis: 127.0.0.1:9000 philips-air.0 | 2022-04-24 20:01:26.282 | debug | States create User PubSub Client philips-air.0 | 2022-04-24 20:01:26.278 | debug | States create System PubSub Client philips-air.0 | 2022-04-24 20:01:26.250 | debug | Redis States: Use Redis connection: 127.0.0.1:9000 philips-air.0 | 2022-04-24 20:01:26.188 | debug | Objects connected to redis: 127.0.0.1:9001 philips-air.0 | 2022-04-24 20:01:26.170 | debug | Objects client initialize lua scripts philips-air.0 | 2022-04-24 20:01:26.078 | debug | Objects create User PubSub Client philips-air.0 | 2022-04-24 20:01:26.076 | debug | Objects create System PubSub Client philips-air.0 | 2022-04-24 20:01:26.064 | debug | Objects client ready ... initialize now philips-air.0 | 2022-04-24 20:01:25.964 | debug | Redis Objects: Use Redis connection: 127.0.0.1:9001No connection to the device...
meehhhhh :-(
Any one of you capable to run Wireshark to sniff network traffic?
@Apollon77: yes, I can do that. What exactly do you want me to look at?
Ideally:
@Apollon77: sorry, I had to leave for a business trip until end of this week. I can't do the test before next week.
All fine ... I think we might have another test then
Ok, here we go .... GitHub has another test version ... Please check when you find time
Hi Apollon77,
sorry, the new version doesn´t work. No connection.
philips-air.0 | 2022-05-13 22:36:29.297 | debug | GET /sys/dev/status to 192.168.0.160 -- | -- | -- | -- philips-air.0 | 2022-05-13 22:36:29.296 | debug | Received: 2B511F92 philips-air.0 | 2022-05-13 22:36:29.294 | debug | Response data incoming: {"type":"Buffer","data":[50,66,53,49,49,70,57,50]} philips-air.0 | 2022-05-13 22:36:29.292 | debug | Response incoming philips-air.0 | 2022-05-13 22:36:29.285 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-05-13 22:35:59.308 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-05-13 22:35:59.303 | debug | Received: 00B7DAEA philips-air.0 | 2022-05-13 22:35:59.300 | debug | Response data incoming: {"type":"Buffer","data":[48,48,66,55,68,65,69,65]} philips-air.0 | 2022-05-13 22:35:59.298 | debug | Response incoming philips-air.0 | 2022-05-13 22:35:59.286 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-05-13 22:35:29.315 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-05-13 22:35:29.313 | debug | Received: 1BD7F3C6 philips-air.0 | 2022-05-13 22:35:29.300 | debug | Response data incoming: {"type":"Buffer","data":[49,66,68,55,70,51,67,54]} philips-air.0 | 2022-05-13 22:35:29.297 | debug | Response incoming philips-air.0 | 2022-05-13 22:35:29.286 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-05-13 22:34:59.344 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-05-13 22:34:59.343 | debug | Received: 70A46EBD philips-air.0 | 2022-05-13 22:34:59.341 | debug | Response data incoming: {"type":"Buffer","data":[55,48,65,52,54,69,66,68]} philips-air.0 | 2022-05-13 22:34:59.339 | debug | Response incoming philips-air.0 | 2022-05-13 22:34:59.285 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-05-13 22:34:29.300 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-05-13 22:34:29.299 | debug | Received: 4D6AA8FC philips-air.0 | 2022-05-13 22:34:29.296 | debug | Response data incoming: {"type":"Buffer","data":[52,68,54,65,65,56,70,67]} philips-air.0 | 2022-05-13 22:34:29.294 | debug | Response incoming philips-air.0 | 2022-05-13 22:34:29.284 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-05-13 22:33:59.345 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-05-13 22:33:59.344 | debug | Received: 01369F60 philips-air.0 | 2022-05-13 22:33:59.343 | debug | Response data incoming: {"type":"Buffer","data":[48,49,51,54,57,70,54,48]} philips-air.0 | 2022-05-13 22:33:59.341 | debug | Response incoming philips-air.0 | 2022-05-13 22:33:59.283 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-05-13 22:33:29.301 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-05-13 22:33:29.300 | debug | Received: 211D7677 philips-air.0 | 2022-05-13 22:33:29.299 | debug | Response data incoming: {"type":"Buffer","data":[50,49,49,68,55,54,55,55]} philips-air.0 | 2022-05-13 22:33:29.297 | debug | Response incoming philips-air.0 | 2022-05-13 22:33:29.284 | debug | POST /sys/dev/sync to 192.168.0.160 philips-air.0 | 2022-05-13 22:32:59.345 | debug | GET /sys/dev/status to 192.168.0.160 philips-air.0 | 2022-05-13 22:32:59.343 | debug | Received: 2B5B5F51 philips-air.0 | 2022-05-13 22:32:59.339 | debug | Response data incoming: {"type":"Buffer","data":[50,66,53,66,53,70,53,49]} philips-air.0 | 2022-05-13 22:32:59.335 | debug | Response incoming philips-air.0 | 2022-05-13 22:32:59.303 | debug | started philips-air.0 | 2022-05-13 22:32:59.280 | debug | start with 192.168.0.160 {"host":"192.168.0.160","aliveTimeout":"30000","reconnectInterval":"30000"} philips-air.0 | 2022-05-13 22:32:59.209 | info | starting. Version 0.1.6 (non-npm: iobroker-community-adapters/ioBroker.philips-air#2e634a52604d75b687d7b183397e817d3865c0e6) in /opt/iobroker/node_modules/iobroker.philips-air, node: v14.19.0, js-controller: 4.0.21 philips-air.0 | 2022-05-13 22:32:58.590 | debug | Plugin sentry Initialize Plugin (enabled=true) philips-air.0 | 2022-05-13 22:32:58.481 | debug | States connected to redis: 127.0.0.1:9000 philips-air.0 | 2022-05-13 22:32:58.458 | debug | States create User PubSub Client philips-air.0 | 2022-05-13 22:32:58.457 | debug | States create System PubSub Client philips-air.0 | 2022-05-13 22:32:58.443 | debug | Redis States: Use Redis connection: 127.0.0.1:9000 philips-air.0 | 2022-05-13 22:32:58.409 | debug | Objects connected to redis: 127.0.0.1:9001 philips-air.0 | 2022-05-13 22:32:58.402 | debug | Objects client initialize lua scripts philips-air.0 | 2022-05-13 22:32:58.359 | debug | Objects create User PubSub Client philips-air.0 | 2022-05-13 22:32:58.358 | debug | Objects create System PubSub Client philips-air.0 | 2022-05-13 22:32:58.355 | debug | Objects client ready ... initialize now philips-air.0 | 2022-05-13 22:32:58.259 | debug | Redis Objects: Use Redis connection: 127.0.0.1:9001GGRRMPPPFFFFFF%&%UIHGUZ%%&/%/&%&/(&$%(/&$(&/$(/&$(/&$$678 :-( Thank you ...
@chris-hoe Any chance for Wireshark when you have time?
Yes, I plan to do that on Monday.
On May 14, 2022 12:14:25 AM Ingo Fischer @.***> wrote:
@chris-hoe Any chance for Wireshark when you have time? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
Hi @Apollon77, finally I've found the time to capture the adapter commuication. See attached captures. philips-air.zip
Thank @chris-hoe, I think that should help a lot with debugging :) I think the crucial lines are these:
As it seems to me, the socket of the client seems to be closed too early, which leads to the discarding of the observe responses.
Hmm, seems as if the server uses the wrong port in its responses, which causes the ICMP messages. I haven't been able to figure out why that is the case.
The observe code itself does not seem to have any problems, I adapted it for the example below which works fine:
const { EventEmitter } = require('events')
const coap = require('coap')
const eventEmitter = new EventEmitter()
eventEmitter.on('debug', (data) => console.log(data))
const address = 'californium.eclipseprojects.io'
// const address = '20.47.97.44' // Using an IP address also works
function subscribeOnStatus () {
return new Promise((resolve, reject) => {
eventEmitter.emit('debug', `GET /sys/dev/status to ${address}`)
const statusRequest = coap.request({
method: 'GET',
pathname: '/obs',
host: address,
protocol: 'coap:',
observe: true,
confirmable: false
})
statusRequest.on('response', res => {
res.on('error', err => {
console.error('Error by receiving: ' + err)
eventEmitter.emit('error', 'Error by receiving: ' + err)
res.close()
reject(err)
})
res.on('data', chunk => {
eventEmitter.emit('debug', `Subscription data incoming: ${JSON.stringify(chunk)}`)
resolve && resolve()
resolve = null
})
})
statusRequest.on('error', err => {
console.error('Error by sending: ' + err)
eventEmitter.emit('error', 'Error by sending: ' + err)
reject(err)
})
statusRequest.end()
})
}
subscribeOnStatus()
Hmm. Had another look into the Wireshark logs. The successful and unsuccessful runs seem very similar. The key difference is that during the unsuccessful one, the server keeps sending observe responses to the same port, which is not active anymore. In the successful ones, the port changes to the new port after a renewed observe GET request. The POST request looks it is working, so an exchange seems possible in general.
Any idea what could cause this behavior? Maybe the AC3829/10 needs to be restarted before the connection attempt?
@JKRhb but how it can be the device if the only difference is the node-coap lib used?! is the client sending the same stuff in both cases?
@JKRhb but how it can be the device if the only difference is the node-coap lib used?! is the client sending the same stuff in both cases?
I had another look and there is actually one small difference between the two observe requests: In the requests that work, the observe value of zero (i.e. the start value) is encoded with an option length of zero, therefore the option value is actually omitted from the packet. In the requests that don't work, the option value of zero is encoded as one byte, where all bits are set to zero (see the screenshots below). So I guess the AC3829/10 cannot handle observe options where the zero is represented by ... zeros.
Working request:
Request that doesn't work:
So, hopefully we are now at the end of the road .... Please try GitHub adapter version. Thank you
Looks good - connects now. Wireshark capture attached - filtert this time, I figured how this works. ;-) Only possible issue: the installation from Github gave a few new warnings I haven't seen before:
$ iobroker url iobroker-community-adapters/ioBroker.philips-air --host iobroker --debug install iobroker-community-adapters/ioBroker.philips-air NPM version: 6.14.17Installing iobroker-community-adapters/ioBroker.philips-air... (System call) node-aead-crypto@2.2.1 preinstall /opt/iobroker/node_modules/node-aead-crypto> node lib/preinstall.jsnode-aead-crypto not needed on this system, since all ciphers are natively supported npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (node_modules/osx-temperature-sensor):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: node-aead-crypto@2.2.1 (node_modules/node-aead-crypto): npm WARN optional SKIPPING OPTIONAL DEPENDENCY: node-aead-crypto@2.2.1 preinstall:
node lib/preinstall.js
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1+ iobroker.philips-air@0.1.6added 2 packages from 3 contributors, removed 1 package and updated 2 packages in 841.43s 119 packages are looking for funding runnpm fund
for details upload [13] philips-air.admin /opt/iobroker/node_modules/iobroker.philips-air/admin/i18n/de/translations.json i18n/de/translations.json application/json upload [12] philips-air.admin /opt/iobroker/node_modules/iobroker.philips-air/admin/i18n/en/translations.json i18n/en/translations.json application/json upload [11] philips-air.admin /opt/iobroker/node_modules/iobroker.philips-air/admin/i18n/es/translations.json i18n/es/translations.json application/json upload [10] philips-air.admin /opt/iobroker/node_modules/iobroker.philips-air/admin/i18n/fr/translations.json i18n/fr/translations.json application/json upload [9] philips-air.admin /opt/iobroker/node_modules/iobroker.philips-air/admin/i18n/it/translations.json i18n/it/translations.json application/json upload [8] philips-air.admin /opt/iobroker/node_modules/iobroker.philips-air/admin/i18n/nl/translations.json i18n/nl/translations.json application/json upload [7] philips-air.admin /opt/iobroker/node_modules/iobroker.philips-air/admin/i18n/pl/translations.json i18n/pl/translations.json application/json upload [6] philips-air.admin /opt/iobroker/node_modules/iobroker.philips-air/admin/i18n/pt/translations.json i18n/pt/translations.json application/json upload [5] philips-air.admin /opt/iobroker/node_modules/iobroker.philips-air/admin/i18n/ru/translations.json i18n/ru/translations.json application/json upload [4] philips-air.admin /opt/iobroker/node_modules/iobroker.philips-air/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json upload [3] philips-air.admin /opt/iobroker/node_modules/iobroker.philips-air/admin/index_m.html index_m.html text/html upload [2] philips-air.admin /opt/iobroker/node_modules/iobroker.philips-air/admin/philips-air.png philips-air.png image/png upload [1] philips-air.admin /opt/iobroker/node_modules/iobroker.philips-air/admin/style.css style.css text/css upload [0] philips-air.admin /opt/iobroker/node_modules/iobroker.philips-air/admin/words.js words.js application/javascript Update "system.adapter.philips-air.0" Process exited with code 0
philips-air-0.1.6new_sucessful-connect-when-started.pcapng.zip
Coooool. the warnings come from other packages in your whole npm tree ... can be ignored
... but when installing the 0.1.4 version, those warnings are not shown. Maybe the 0.1.6 has additional dependencies?
Interesting ... but effectively ... all good
Thank you for your mega support on fiiguring thsi out ... v1.0.6 goes into Beta repo/npm today ... please check this officially again ... but I expect it to still work (fingers crossed)
@Apollon77: Version 0.1.7 works with my AC2729/10. Great, thank you very much for your support!!!
Since the latest update to 0.1.3, this adapter doesn't connect to my AC3829/10 anymore. With version 0.1.0 I had installed before, connection has always been a bit unstable and the adapter needed a restart from time to time but in general it worked okay.
Debug log isn't very useful to identify the problem (at least to me):
philips-air.0 | 2022-03-21 14:23:03.977 | debug | started -- | -- | -- | -- philips-air.0 | 2022-03-21 14:23:03.957 | debug | start with 10.100.255.35 {"host":"10.100.255.35","aliveTimeout":"30000","reconnectInterval":"30000"} philips-air.0 | 2022-03-21 14:23:03.889 | silly | States system redis pmessage system.adapter.philips-air.0.logLevel/system.adapter.philips-air.0.logLevel:{"val":"silly","ack":true,"ts":1647868983869,"q":0,"from":"system.adapter.philips-air.0","lc":1647868837519} philips-air.0 | 2022-03-21 14:23:03.770 | debug | Schedule restart: 0 15 * * * philips-air.0 | 2022-03-21 14:23:03.659 | info | starting. Version 0.1.3 in /opt/iobroker/node_modules/iobroker.philips-air, node: v14.19.1, js-controller: 4.0.21 philips-air.0 | 2022-03-21 14:23:02.253 | debug | Plugin sentry Initialize Plugin (enabled=true) philips-air.0 | 2022-03-21 14:22:55.465 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason philips-air.0 | 2022-03-21 14:22:55.462 | debug | Plugin sentry destroyed philips-air.0 | 2022-03-21 14:22:55.460 | info | terminating philips-air.0 | 2022-03-21 14:22:55.455 | info | Got terminate signal TERMINATE_YOURSELF philips-air.0 | 2022-03-21 14:22:55.453 | silly | States system redis pmessage system.adapter.philips-air.0.sigKill/system.adapter.philips-air.0.sigKill:{"val":-1,"ack":false,"ts":1647868975111,"q":0,"from":"system.host.iobroker","lc":1647868975111} philips-air.0 | 2022-03-21 14:22:55.465 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason philips-air.0 | 2022-03-21 14:22:55.462 | debug | Plugin sentry destroyed philips-air.0 | 2022-03-21 14:22:55.460 | info | terminating philips-air.0 | 2022-03-21 14:22:55.455 | info | Got terminate signal TERMINATE_YOURSELF philips-air.0 | 2022-03-21 14:22:55.453 | silly | States system redis pmessage system.adapter.philips-air.0.sigKill/system.adapter.philips-air.0.sigKill:{"val":-1,"ack":false,"ts":1647868975111,"q":0,"from":"system.host.iobroker","lc":1647868975111}Looks like everything is working okay ... except that no values are coming in and the "Instances" tab is showing this adapter as "Not connected to device or service" (last checkmark is red instead of green). Anything I can do to help fix this bug? I really would love to get my values recorded again! ;-)