Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No devices #53

Closed
scargill opened this issue Nov 22, 2021 · 2 comments
Closed

No devices #53

scargill opened this issue Nov 22, 2021 · 2 comments

Comments

@scargill
Copy link

scargill commented Nov 22, 2021

I have a perfect working installation of this Zigbee2MQTT node set running overseas. I've just returned to the UK, upgraded my UK Node-Red on RPI4 to the latest Node-Red (everything up to date - Node 14, NR 2.....

I installed Node-Red-Contrib-Zigbee2MQTT (as normal, as user Pi) using the Node-Red palette Manager (just as I did on my original RPi4 a couple of months ago) - and in Node-Red added a couple of sensors (using an INJECT node straight into MQTT to allow adding) - then renamed devices to something useful again using an INJECT node into MQTT).

The N-R-C-Zigbee2MQTT bridge node seems fine as I have a debug output on it - and it is showing various logging messages in the debug... and if I manually trigger, for example, one of my Aqara temperature sensors, a package comes from the bridge node to show the temperature - and if I rename the device again as above, the bridge node gets the updated "friendly" name - BUT - couple of problems... in bridge node properties - the version number is showing a minus sign instead of a version number - and WAY more importantly - the bridge node - properties - devices tab shows NO devices -and using REFRESH ALL DATA has no effect on that. I have NO idea where to start looking for why this is happening... hence I can't use the other nodes - HELP

image

@Jandro-Grao
Copy link

Jandro-Grao commented Dec 5, 2021

Found the solution some post below, just change legacy_api false to true in configuration.yaml
Working fine now
solucion

@andreypopov
Copy link
Owner

try 2.0.0 version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants