-
Notifications
You must be signed in to change notification settings - Fork 16
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
Switch is not available #28
Comments
What are the versions of S1E and S1E2HA? |
Both S1E and S1E2HA are updated to the latest according to the project. These are all recent operations. |
hello ,@niceboygithub Through the 'top' command in telnet, I have found that the two processes: are consistently consuming a total of 20% of the memory when using the problematic switches. The switches that are working normally do not exhibit similar memory usage. |
I recall that I used the ”gw_global_tool.ttl“ to remove the password and flash the firmware. I did not go through the interrupt uboot process. Will this have any impact? |
hi, @niceboygithub This is the state after running the top command. Mem: 41512K used, 15348K free, 0K shrd, 857416K buff, 857464K cached |
I have exactly the same problem |
I have five S1E devices. Two of them have been successfully connected to MQTT and are functioning normally. However, two of the relay switches are showing an "unavailable" status, as shown in the picture. Additionally, one of the devices failed to be added properly.
Previously, all five switches had been connected to MQTT, and at that time, all the relay switches were displaying an "unavailable" status. Interestingly, two of the switches later unexpectedly returned to a normal state under unknown circumstances.
The text was updated successfully, but these errors were encountered: