Manually another hue white is working. Is setting up the device manually the only way or can I do something about the error?
Sorry for the delay; I tested today with latest snapshot and I think it works ok. I also moved my mosquitto server to docker (moved… I removed my local installation and started a clean new one), and upgrade zigbee2mqtt; it may have helped getting rid of all old messages.
@DesertF0x , I would try a clean openhab instance with latest snapshot and give it a try.
@ccutrer , thanks a lot for your time and your hard work.
Yay! I’m glad! Yes, the latest snapshot has had a lot of improvements. Even just a couple weeks ago I fixed an issue where it wasn’t properly re-creating all the channels immediately on boot, and had to wait for the MQTT discovery messages to come in. I think that was the cause of the occasional “channel not supported message” (because the item was getting linked before the channel was created).
I am on the latest stable version and I am getting that message:
12:22:07.517 [WARN ] [mqtt.generic.AbstractMQTTThingHandler] - Channel mqtt:homeassistant_zigbee2mqtt_5F0x001788010d734ebb:9e68bf1327:LichtBad:brightness not supported!
when I command the connected Item. And no command is send to MQTT.
Reading “brightness not supported” sounds weird to me as it is such a basic thing.
@DesertF0x , I tried last snapshot
.
services:
openhab:
image: "openhab/openhab:4.3.0-snapshot-debian"
container_name: openhabStable
restart: always
volumes:
- "/etc/localtime:/etc/localtime:ro"
- "/etc/timezone:/etc/timezone:ro"
- "/run/mysqld:/run/mysqld"
- "./addons:/openhab/addons"
- "./conf:/openhab/conf"
- "./userdata:/openhab/userdata"
- "./backups:/openhab/backups"
cap_add:
- NET_ADMIN
- NET_RAW
ports:
# #- 8102:8101
# - 9083:9081
- 8889:8080
- 4449:8443
- 5557:5007
environment:
CRYPTO_POLICY: "unlimited"
EXTRA_JAVA_OPTS: "-Duser.timezone=Europe/Madrid"
# OPENHAB_HTTP_PORT: "8889"
# OPENHAB_HTTPS_PORT: "4449"
USER_ID: 136
GROUP_ID: 147
I don’t know if I will have to do anything to return to stable, but at least everything works now.
Ok, I will wait for it to become stable. I do not have time to deal with other issues that might be in the unstable version.