I wouldn’t order that one.
No i didnt. I ended up getting a refund via paypal. Some people paid via bank transfer, requested a refund and they reported still waiting for it.
I would urge you not to order that one (slaesh stick) .
Go with the lama zzh or tube’s hubs
ok. thanks
Go with the lama zzh
Dang. out of stock atm.
The official Tube site says it is a Router/Repeater. The link above this post says Coordinator. I am wanting to replace my existing coordinator. The tube is all I need and it will act as a coordinator?
Coordinators are here: Coordinators | Tube's ZB Store
thank you my friend!
i will look on it. I need also the source code that i will get from github if i am right.
Hello again, i managed to configure the module but how can i see it on HA? I add the repo but how to see the front end and add devices?
Thanks again
Are you using the addon or some other install method?
Thanks again,
The zigbee2MQTT from supervisor? Where to find the front end? I am missing something i think 
In the setup page (via supervisor page) choose Show in Sidebar, then click on Zigbee in the sidebar.
oh i would never found it my self ! Now appears as “bad gateway” message but i think i have to add in .yaml the port.
Have you started zigbee2mqtt?
Try again after a few seconds.
yes normally, start with boot. i will try restart also.
Except if i need to add in .yaml also the port but think this optional. only frontend: is the neccessary?
What yaml file are you referring to?
My addon setup is
data_path: /share/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
base_topic: zigbee2mqtt
server: 'mqtt://core-mosquitto'
user: mosquitto
password: xxxxxxx
serial:
port: /dev/ttyACM0
advanced:
log_level: info
pan_id: xxxx
channel: 11
network_key:
- 1
- 3
- 5
- 7
- 9
- 11
- 13
- 15
- 0
- 2
- 4
- 6
- 8
- 10
- 12
- 13
availability_blocklist: []
availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
port: 8099
experimental:
new_api: true
socat:
enabled: false
master: 'pty,raw,echo=0,link=/dev/ttyZ2M,mode=777'
slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
restartdelay: 1
initialdelay: 1
options: '-d -d'
log: false
I thought that i would not needed to add something in configuration.yaml file or in the
/config/zigbee2mqtt/configuration.yaml
Probably i was wrong.
Hi, I am pretty new to HA and MQTT but I really like it so far! Some things are new or unclear to me so I hope some of you can help me out once in a while.
I’ve found out it is possible to set the retain option for my devices, but I am wondering:
Is it necessary to specify a retention value when using the retain option? What happens if I don’t?
You are in the zigbee2mqtt thread, is this a zigbee2mqtt question?
Hi, I have just updated Core to 2021.06.4 (from Core 2021.02.3) and zigbee2mqtt to v1.19.1-1 (from v.1.16.1). I notice these warning message are floating the HA logger. As I know, these errors starting to appear for some users starting Core 2021.04.
Upon further debug with MQTT explorer, I notice the update available and click topics are actually published by zigbee2mqtt. And it creates the update available and click sensor. I’m not sure what are these sensors for as I’m not using them at all and as I recalled, these sensors are not exist before the updates. I’m just using the switch entities to toggle the switch all the while.
So, are the update available and click sensors is safe to remove? What are them for? Will removing these sensors will stop the warning messages?
Please advise and thanks.
Logger: homeassistant.helpers.template
Source: helpers/template.py:1366
First occurred: June 13, 2021, 7:41:55 PM (1470 occurrences)
Last logged: 10:11:23 AM
Template variable warning: 'dict object' has no attribute 'update_available' when rendering '{{ value_json.update_available}}'
Template variable warning: 'dict object' has no attribute 'click' when rendering '{{ value_json.click }}'
Update available entities
Click entities
The switch entities that I’m using
1 Like
I think that is indicating that there is a firmware update available - Z2M is increasing the devices it can update firmware on all the time.
After an upgrade to 1.19 I got this for some xiaomi devices [1] , but when I go to update them it doesn’t actually do so.
[1] These ones ZNCZ02LM