Open J-Paul0815 opened 3 months ago
Please add a log with level DEBUG. An please add the log using code tags -not as screenshot.
Sure, thanks for looking
`2024-08-02 09:35:20.360 - debug: mclighting.0 (603) ws://192.168.0.101:81/ receive a pong : ping
2024-08-02 09:35:23.829 - debug: mclighting.1 (618) ws://192.168.0.99:81/ receive a pong : ping
2024-08-02 09:35:30.359 - debug: mclighting.0 (603) ws://192.168.0.101:81/ receive a pong : ping
2024-08-02 09:35:33.827 - debug: mclighting.1 (618) ws://192.168.0.99:81/ receive a pong : ping
2024-08-02 09:35:40.358 - debug: mclighting.0 (603) ws://192.168.0.101:81/ receive a pong : ping
2024-08-02 09:35:43.828 - debug: mclighting.1 (618) ws://192.168.0.99:81/ receive a pong : ping
2024-08-02 09:35:50.362 - debug: mclighting.0 (603) ws://192.168.0.101:81/ receive a pong : ping
2024-08-02 09:35:53.828 - debug: mclighting.1 (618) ws://192.168.0.99:81/ receive a pong : ping`
If a device works but it says it doesn't, then in my opinion that's a bug and not a question.
If a device works but it says it doesn't, then in my opinion that's a bug and not a question.
Lookking at history shows that question was set when requesting a log.
Thanks for reminder I'll remove the label.
After Update to Version 0.2.0 The instances shows "not connected"
Expected behavior
Instances shows "connected"
Screenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.
Versions:
The web interface can be opened normally (port 80). The call to IP_ADDRESS:81 results in: "This is a Websocket server only!" If mclighting.1.fx_mode is changed, mclighting.1.fx_mode_name is also updated (correctly). The LED strip reacts as expected, I can't find anything unusual. The device also reacts correctly when writing to mqtt.0.McLighting01.in (e.g. "39") and the correct response "OK /39" comes in mqtt.0.McLighting01.out All of this meets my expectations.
What does not meet my expectations: mclighting.1.info.connection is false
There is nothing unusual in the log (for me), no matter what the LOG level, at least that indicates "not connected":