I get that, although I didn’t appreciate it would persist through a restart and appreciate the heads up.
The issue is the payload, posted earlier, or perhaps more accurately my not understanding how to handle it.
When the device responds normally the topic is stat/mydeviceid/POWER with a payload of ON or OFF
simple enough and works with the switch channel configured in Paper UI
If the device is physically manipulated, with its switch, or power cycled this message is never sent so Openhab cant process it.
I think I see what you are getting at RE
and I will alter the device config now.
Honestly I don’t understand how it will help, if the issue is no message in the first place or a message that Openhab isn’t responding to, but then I don’t understand a great deal right now so if nothing else I will learn something.
OK Screenshots I could probably do that, I just didn’t think it would add much
(Also I haven’t worked out how to do that on this system yet)
There are no files, I looked couldn’t find them and then found documentation saying paperUI spores everything in Jason and not to muck about with it, so I didn’t.
I have One thing, at least 1 in play… There are other bindings and of course the broker but am not using anything else, yet, and the broker is working.
I am assuming a QOS of 1 or 2 and retained set TRUE will help, at the expense of network traffic, which will not be a problem anyway?
The rest…!
Screenshot_2020-04-05_19-10-14|690x377
You can see the ON and OFF I added in the switch, everything else is point and click at the defaults, bar for names.
Those hundreds of posts about parsing Jason…
Honestly I would need to know…
what I wanted, and what Jason was (some form of Java scripting I assume, reading to do)
how it was going to work,
If there was a more direct way to go, you know like adding a switch
O and what in those posts is entirely wrong now the system has changed.
I get that I need to learn and in fact I want to.
I also didn’t want to start with complex stuff, walk first and all that, but if a simple switch, added through the recommended UI, is not performing and the documentation specifically tells noobs not to fiddle with files, asking questions seems reasonable.
Most of what was confusing me was apparently legacy stuff, obvious now I know but not yesterday.
Ideally I would want to generate config files to add things/channels/links/ but everything I have read thus far tells me not to go there. I think I said that earlier.
I had hoped to add 1 thing, look at its valid config and use that to make more but apparently that isn’t an option anymore.
My switch is working and my script is capturing the reports, although I may not need it now.
Will reconfogure MQTT, reconfigure the device and add a few more devices.
I don’t want to irritate anyone, I just don’t understand why such a basic config, barely a test setup, could, be or would, be buggy… I therefore assumed it was my error.
Al