You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
was running the device over a year now sucessfully.
A few days ago it stopped working.
I can ping the device, but the configured ssh server port is gone, also the zigbee server installed is no longer working.
I reattached the ttl debug cable to login and see whats going on but the root password is no longer working.
I reran the commands to get the KEK and the AUSKEY, but its the same. I saved them with the actual password and port infos in my keepass database.
My guess is that the firmware was updated automatically and they changed the procedure how the root password is initially set?
I have 3 other spare gateways left i could use. But i want to understand first, whats going on.
Any Idea? Interested in debugging, i could share a terminal within Teams or something similiar.
The text was updated successfully, but these errors were encountered:
When i try to update the connection in home assistant, its not working, i can see debug output that the connection was opened, but its closed after a few seconds.
Hi,
was running the device over a year now sucessfully.
A few days ago it stopped working.
I can ping the device, but the configured ssh server port is gone, also the zigbee server installed is no longer working.
I reattached the ttl debug cable to login and see whats going on but the root password is no longer working.
I reran the commands to get the KEK and the AUSKEY, but its the same. I saved them with the actual password and port infos in my keepass database.
My guess is that the firmware was updated automatically and they changed the procedure how the root password is initially set?
I have 3 other spare gateways left i could use. But i want to understand first, whats going on.
Any Idea? Interested in debugging, i could share a terminal within Teams or something similiar.
The text was updated successfully, but these errors were encountered: