hmm…I don’t have a IKEA bulb to test with. Do you have more/other devices with equal problems?
A kaku, NEST.
Nothing works. I only get value changes in paperUI when i change something in the app.
@Marcel_Wolf Could you try installing the latest version from the homie2 branch?
Next disable all devices (settings > devices) except ‘staande-lamp’ and try setting the value from within OpenHab.
Let me know.
Reinstalled latest homie2 branch
Disabled all the devices accept ‘Staande lamp’.
Reinstalled Homie MQTT device.
Gives same problem
Anything useful in the log (settings > log)?
I have sort of the same problem. In short:
- I can control my Homey devices from OpenHAB, and thus also Google Home =)
- However. OpenHAB never detects device state changes from Homey. Not even if I do a full broadcast.
In MQTT-explorer (on / off device for example):
- Device state change triggered from openHAB publishes “true” to the “…/set” topic. Homey acts on the change and turns on the device. “True” gets published to “…/onoff” topic.
- Device state change triggered from Homey publishes “true” to “…/onoff” topic. Nothing on the “…/set” topic. The “…/set” topic for any given device doesn´t even exist until something is published from openHAB.
Will proceed with troubleshooting after work. I suspect it´s an issue with my openHAB config, but not really sure how to investigate further. OpenHAB re-start is first thing on my task list.
Oh, and thanks for an awesome app HarriedeGroot!
We did some debugging already. But the issue of commands not being handled, is not resolved yet…
Probably there’s a small bug in the app2app interface with the MQTT Client. The client reports a successful topic subscription, but does not actually subscribe (no messages are received & send to the hub). When we added a simple flow with a card listening to a general topic (#), the hub received messages again.
Needs further investigation.
Think I found a bug?
If I enable a virtual device under devices tab, the update of all devices stops.
If I understand correct the reason for my problem is a known bug in openHAB mqtt-binding. Atleast the problem seems to be identical to what is being duscussed on eclipse github: https://github.com/eclipse/smarthome/issues/6828
The problem is aknowledged by developers, but the fix seem to be several weeks ahead.
"when freshly added all devices work until OpenHab is restarted at which point all my temperature reports go to NaN and stay that way despite normal MQTT traffic. I have noticed however, that the “control” channels still work, so toggling switches in OpenHab sends out the required MQTT command, and the Homie devices respond - but my temperatures and configuration “readback” that the Homie devices transmit periodically are ignored.
Again, removing and re-adding the devices cause them to start working again until OpenHab is restarted."
Have you tried the Milestone version of OpenHab? This fixed the same errors when i tried
Good catch! Deserves some investigation.
Which virtual device (build in/VD app) did you use? And what kind of virtual device (button/switch, etc.) caused this behavior?
Thanks Bananfluen! OpenHAB 2.5.0.M1 did the trick. Have tried a couple of OH-restarts and the connection comes back (after restart of client and hub app on Homey).
Can it also be that non english letters cause problems? Here in Norway we use Æ,Ø,Å letters. Think that this thing dont like it
This app: https://apps.athom.com/app/com.arjankranenburg.virtual
Used a switch.
@HarriedeGroot thanks for the great work, I have some questions/request
for testing it is usefull disable all devices in MQTT Hub and enable only one or two devices. Is it possible to add in the devices TAB a switch “disable all devices” and “enable all devices”
On the settings TAB the Broadcast button is a bit strange, not really clear when pressed on it if the button is activated.
Is it possble to transfer the status of variabels from Homey logica? so they can be used in OpenHAB?
- Good suggestion, I’ve put it on the list
- It broadcasts all available devices & their current state, so external applications can discover them. Can be useful to get the OpenHAB MQTT device online or update the channel datatypes if ‘dummy’ is displayed.
- Probably, needs investigation. As a workaround you can create a virtual device operating on the variable.
I’ll add some additional info about the different settings in the settings instructions tab.