Kai
(Kai Kreuzer)
December 10, 2019, 8:48pm
32
my Philips Hue dimmer and Tap switches events will not work.
Sorry if this is maybe a stupid question, but did anybody ever file a bug report about this?
Looking at Pull requests · openhab/openhab2-addons · GitHub , I cannot see anything related…
I can understand the decision of cweitkamp who did the last change in the hue binding and doesn’t use the dimmer switches anymore
You mean @cweitkamp broke the code and decided to not fix it, because the feature isn’t relevant for him? From all I know about his work over the past years, I cannot believe this…
2 Likes
Celaeno1
(Alex)
December 10, 2019, 8:52pm
33
@Kai
Please read this:
@Celaeno1 I appreciate your eagerness to find a solution for this problem. But I am afraid I do not have the time to investigate much on it at the moment. In general I guess that we are facing two different problems here. First one is the Philips Hue Event issue. This is probably cause by the polling strategy implemented in the binding - it polls the Hue Bridge in a fixed time interval. For this issue I have to admit that I am not very motivated to do research as I get rid of sensor / remote con…
I very well appreciate all the work of Christoph . Thanks a lot. But unfortunately above is true.
One issue is filed here:
opened 10:42AM - 09 Apr 19 UTC
closed 07:34PM - 10 Dec 20 UTC
bug
DSL rules
Hej there,
I (and others) run into the following error when trying to fetch t… he name of the event that has been triggered using command: var trigger = **receivedEvent.getEvent()**
**2019-04-06 17:28:19.811 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Rule ‘Lamp2’: ‘getEvent’ is not a member of ‘org.eclipse.smarthome.core.thing.events.ChannelTriggeredEvent’; line 46, column 20, length 24**
OH version is 2.4
See detailed description and code examples:
https://community.openhab.org/t/solved-getevent-is-not-a-member-error-since-oh-2-4/61791/11
https://community.openhab.org/t/solved-getevent-is-not-a-member-error-since-oh-2-4/61791/12
(Thread says "solved" but that is not the case)
Thanks
Kai
(Kai Kreuzer)
December 10, 2019, 9:00pm
34
Which is unrelated to the hue binding itself and which does not seem to be reproducible…
But there’s no issue entered over all these months about the hue binding?
mstormi
(Markus Storm)
Split this topic
December 11, 2019, 10:54am
35
rkrisi
(Kristof Rado)
December 10, 2019, 9:14pm
40
The MQTT problem seems to got sorted out by us with the help of @J-N-K . He will also create a PR for it.
3 Likes
job
(Joachim Boeddeker)
December 11, 2019, 12:39am
59
Strange, i have this issue since M6 (still existing in RC1), i need to go back to M5 to get mqtt updates again.
MQTT Not working.
Just to help those with this issue it has been opened on github here
and here.
I have reverted back for the moment with
sudo apt install openhab2=2.5.0~M6-1
cleared the cache and restarted.
J-N-K
(Jan N. Klug)
December 11, 2019, 11:33am
65
@David_deMarco Does that mean that the fix is not working for you?
Hi JNK
Have not applied the fix as could not find clear info on how to apply it. Happy to apply and test if you can point me in the right direction. Confirm stable on M6 (I’ll update the post above)
ironfly
(Claus Buck)
December 11, 2019, 3:29pm
67
Same to me, as well with Mosquitto.
all commandTopics works fine, but none of the stateTopics.
rkrisi
(Kristof Rado)
December 11, 2019, 3:30pm
68
You can find the instructions on the GitHub issue you’ve linked:
Please update the “openHAB Core :: Bundles :: MQTT Transport” bundle with https://janessa.me/esh/org.openhab.core.io.transport.mqtt-2.5.0-fs.jar this one and report back. Instructions https://janessa.me/esh . option 2.
4 Likes
stfn82
(Stefan)
December 11, 2019, 7:27pm
69
Somehow I have 2 MQTT transport bundles:
262 │ Active │ 80 │ 2.5.0.RC1 │ openHAB Core :: Bundles :: MQTT Transport
269 │ Active │ 80 │ 1.14.0.RC1 │ openHAB MQTT Transport Bundle
I’ve deleted the 1.14 and upgraded the other one to 2.5.0.201912101757.
So far everything seems OK. Maybe this was the cause of my MQTT issues I experienced with M6.
I upgraded from M5 to M6 on openHABian rpi 3b+. It’s not very stable.
Sometimes it refuses to start:
syslog:
Dec 05 12:33:23 openhab karaf[762]: org.apache.felix.resolver.reason.ReasonException: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=openhab-ui-dashboard; type=karaf.feature; version="[2.5.0.M5,2.5.0.M5]"; filter:="(&(osgi.identity=openhab-ui-dashboard)(type=karaf.feature)(version>=2.5.0.M5)(version<=2.5.0.M5))" [caused by: Unable to resolve openhab-ui-…
yozik04
(yozik04)
December 11, 2019, 7:35pm
70
MQTT: For me only topics that are retained do not work. But normal ones work fine.
It looks like you had MQTT21 & MQTTv2 both installed
J-N-K
(Jan N. Klug)
December 11, 2019, 8:35pm
72
What exactly is not working? Please provide debug logs (or better trace).
1 Like
yozik04
(yozik04)
December 11, 2019, 9:02pm
73
@David_deMarco linked an issue that was already merged. I’ll wait when next snapshot be out and will retest. For me only part of subscriptions were not working for some reason. No idea why.
This issue has been resolved by upgrading to the latest stable version.
Thanks @rkrisi I missed that bit (jetlag and system upgrade not good idea). Full steps in one place to help others given MQTT is used so much now. (updated with improved karaf command )
sudo systemctl stop openhab2
sudo sudo openhab-cli clean-cache
sudo systemctl start openhab2
Confirmed here that MQTT state updates now failing.
Open the Karaf console:
openhab-cli console
bundle:update org.openhab.core.io.transport.mqtt https://janessa.me/esh/org.openhab.core.io.transport.mqtt-2.5.0-fs.jar
logout
restart openhab - do not clear the cache
sudo systemctl restart openhab2
Confirmed that MQTT states are now working again - Can’t comment on retained messages. Note I also had some suspect issues with openhab-cli not stopping Openhab so playing it safe here.
thanks @J-N-K for prompt fix
Update: I had to reboot my rpi3 and the connection to the MQTT Broker failed with
OFFLINE - COMMUNICATION_ERROR io.netty.channel.AbstractChannel$AnnotatedNoRouteToHostException: No route to host: /10.88.87.180:1883
A manual stop and start of openhab resolved the issue.
1 Like
There is an issue with usb-serial devices on RC1 as reported by @Andrew_Rowe , @davorf and I experienced it on Windows 10 and Raspberry PI (using openhabian 1.5) : the serial items (zwave controller and RFXcom for me) keeps reinitializing on openhab level, it is fine on the command line (using lsusb, dmesg etc…). It was causing very high memory and cpu usage and even using swap, the pi was unusable after a few hours.
Switching to latest snapshot, for me it is 1774, fixes the issue
1 Like
wborn
(Wouter Born)
December 12, 2019, 12:19am
76
That’s strange because 1774 doesn’t have any differences compared to RC1 regarding those bindings and the serial communications code AFAIK.
There’s a 1775 snapshot build now that’s the same as RC1 plus the MQTT fix and some ScriptEngineFactory changes.
Maybe you can check if the issue is resolved after restarting openHAB without clearing the cache?
1 Like
ironfly
(Claus Buck)
December 12, 2019, 9:31am
77
This solves also my issue below!