Closed JustasStas closed 2 years ago
I would recommend you to try to reset your device. Also if you have other plugin or software accessing that device then you should increase the polling interval. The hardware of those devices is usually very weak and they tend to freeze when too many requests are send to them.
Tried to increase interval to 30, doesn't help
But did you reset your device first? Also can you post your config.json entry so I can validate that?
Yes. I reseted: "devices": [ { "name": "Air Purifier", "ip": "192.168.0.237", "token": "XXX", (token entered, just do not want to share) "pollingInterval": 30, "deepDebugLog": false, "buzzerControl": false, "ledControl": false, "childLockControl": false, "modeControl": true, "fanLevelControl": true, "showTemperature": true } ], "platform": "miot"
Hmmm, config looks good! Not sure why your device behaves like that, it seems to me like you might have other software also polling the device which just overloads it.
@merdok The zhimi.airp.mb3a seems to be unsupported currently, could that be the cause?
I duplicated
lib/modules/airpurifier/devices/zhimi.airpurifier.mb3.js
to lib/modules/airpurifier/devices/zhimi.airpurifier.mb3a.js
and updated the MIOT url to https://miot-spec.org/miot-spec-v2/instance?type=urn:miot-spec-v2:device:air-purifier:0000A007:zhimi-mb3a:1
which seems to be working, but not sure if anything else needed to get full functionality?
@bjmd yeah, the spec for that device is currently missing, but that should actually not be an issue since the plugin will automatically fetch and generate the file if it is missing. Did it not work for you before you duplicated the file?
@merdok The spec was available at the MIOT url when I tested, is that what you meant by currently missing?
I can't remember exactly, but I believe I was getting an error saying that it was an unknown device and then I was missing functionality. I'm happy to test again if you need?
@bjmd the plugin connects to that url gets the data and dynamically creates a local implementation. In that case you will get a warning since it might be possible that some stuff could have not been resolved automatically and some manual adjustment is needed. But if everything is working then it can safely be ignored.
You can try it again and post a debug log from homebridge startup, then we will see if the automatic fetch happened correctly.
Added in version 1.1.0
Hey. I set up all data but i keep getting these errors