By going to the command channel and send e.g get_prop[“load_voltage”]
What also helps is to send the plugin apk (from your backup where you got your key, the files with somenumber.apk filename.)
I can than try my emulator for your devices.
You can enable the command channel by going to paperUI, open your your thing.
Than when you see the list of channels, click on show all, and the enhanced channels can be selected. Enable the command channel (it is a advanced channel, so otherwise invisible)
You can than paste the commands there, wait a bit and the value of the channel will be updated with the response.
(I think in the vacuum thread there are some screenshots as well).
Okay, I tried it out, I had the same result, no responce, here is my definition of the thing:
btw. I notice I that I need to send a couple of on off cycles to the strip before I normally see it turn on or off. I don’t see anything strange in my log, tell me if I can send you some information on this to help.
Normally the action commands respond simply with response “ok”. So if you get that, I assume the device is going to switch. Do you see the same in the app?
@Andrew_Pawelski
Can you pls send the debug log . I don’t own such a device so I can’t test this before releasing.
In the log it is bit more clear what is happening.
Normally after entering this, after a bit, the value is updated with the
response from your device.
Depends bit on how many commands are in the queue, but mostly this happens
in <10 sec.
This response is what I would like to know. The 200 response is something
internal from OH, not something your device is providing
That’s indeed very odd.
What’s strange as well to me is that the mode & temp in your screenshot is not updated either.
Which would mean either the communication is not working fine or the screenupdate has a problem.
Can you share what is happening in the debug log when these commands are running, as that may give indication
Theres nothing going on in the debug log that I can see and it doesnt do it all the time i have it running a fish pump on in the morming off in the evening and last night it sent an off command that OH says it is off but the Mi App shows it on (as is the case as the pump is still running) today it worked perfectly
Okay here is the inital log for ON/OFF cycles. The first few times I run it do responce then, suddenly everything works:
2017-10-20 20:16:13.329 [ItemCommandEvent ] - Item 'XiaomiMiPowerStrip6Plugs_PowerOnOff' received command ON
2017-10-20 20:16:13.342 [ItemStateChangedEvent ] - XiaomiMiPowerStrip6Plugs_PowerOnOff changed from OFF to ON
2017-10-20 20:16:19.379 [ItemCommandEvent ] - Item 'XiaomiMiPowerStrip6Plugs_PowerOnOff' received command OFF
2017-10-20 20:16:19.388 [ItemStateChangedEvent ] - XiaomiMiPowerStrip6Plugs_PowerOnOff changed from ON to OFF
2017-10-20 20:16:21.537 [ItemCommandEvent ] - Item 'XiaomiMiPowerStrip6Plugs_PowerOnOff' received command ON
==> /var/log/openhab2/openhab.log <==
2017-10-20 20:16:24.399 [WARN ] [ore.internal.events.OSGiEventManager] - Dispatching event to subscriber 'org.eclipse.smarthome.core.thing.internal.ThingManager@62811e' takes more than 5000ms.
==> /var/log/openhab2/events.log <==
2017-10-20 20:16:24.409 [ItemStateChangedEvent ] - XiaomiMiPowerStrip6Plugs_PowerOnOff changed from OFF to ON