Skip to content
This repository has been archived by the owner on May 10, 2024. It is now read-only.

Ability to disable emergency mode #11

Closed
xyzroe opened this issue Jan 26, 2022 · 9 comments
Closed

Ability to disable emergency mode #11

xyzroe opened this issue Jan 26, 2022 · 9 comments
Labels
enhancement New feature or request

Comments

@xyzroe
Copy link
Owner

xyzroe commented Jan 26, 2022

Some people have problems with false activation of emergency mode when their local internet gateway does not respond to ping from ZigStar.

Add the ability to disable ping control or completely disable emergency mode.

@xyzroe xyzroe added the enhancement New feature or request label Jan 26, 2022
xyzroe added a commit that referenced this issue Jan 30, 2022
- Add support for DS18B20 sensor. Works only on TTGO using GPIO 33. Shows in web browser
    and sends via MQTT with AutoDiscovery. Works only when the sensor is connected.

- Number of active socket clients reduced to 5 to avoid hangs. Maybe #10

- Number of active socket clients now sends via MQTT with auto-discovery. Using MQTT Refresh Interval. #9

- Automatically reconnect to a Wi-Fi hotspot after being disconnected, but you still need
    the hotspot to be available during the gateway reboot, otherwise it will start its own hotspot. #8

- Add a checkbox to disable emergency mode in Wi-Fi settings. #11

0.6.2

- Set MQTT reconnect interval same as MQTT update interval to avoid web server freezing,
    while broker is unavailable.

- Added web authentication. Issue #4
    Set to OFF by default, enable on general settings page.

- Blocking saving an empty hostname, login and password to the web interface.
    Replaced with standard values ( ZigStarGM / admin / admin )
xyzroe added a commit that referenced this issue Jan 31, 2022
- Fix version number

- Fix web interface rendering error

0.6.3

- Add support for DS18B20 sensor. Works only on TTGO using GPIO 33. Shows in web browser
    and sends via MQTT with AutoDiscovery. Works only when the sensor is connected.

- Number of active socket clients reduced to 5 to avoid hangs. Maybe #10

- Number of active socket clients now sends via MQTT with auto-discovery. Using MQTT Refresh Interval. #9

- Automatically reconnect to a Wi-Fi hotspot after being disconnected, but you still need
    the hotspot to be available during the gateway reboot, otherwise it will start its own hotspot. #8

- Add a checkbox to disable emergency mode in Wi-Fi settings. #11
@xyzroe
Copy link
Owner Author

xyzroe commented May 23, 2022

duplicate #13

@kubax
Copy link

kubax commented May 31, 2022

Just wanted to leave a quick workaround for this "bug".

I (very) recently got myself a ZigStar device, and had the exact problem. I did manually configure the network and then had the problem with the emergency wifi enabled.

first of all, it would be better to have a configurable emergency wifi with encryption, but that might not be able on this device.

BUT to fix it until the option you mentioned is implemented, i did just enter a device as the gateway that does not route trafic (because i don't see any need for the zigstar device to reacht the internet) but that is always online. In my case i used a NAS device, but could be anything.

Maybe you could let us manually choose which device to ping to check if the device is up.

Also thanks for your work!

@xyzroe
Copy link
Owner Author

xyzroe commented May 31, 2022

If your home network on which encryption is used is saved in the Wi-Fi settings, then when you turn on emergency mode, you will be connected to this network with encryption.

I see no practical point in creating an access point from ZigStar. Only for configuration, and there is no point in encryption.

You can allow ping from the local network on your gateway, all problems will be solved. There are no security issues with this.

Indeed, as one of the ways - use another device instead of a gateway.
Thanks for your advice to the community.

Perhaps in the future I will add a similar functionality.
Thanks for the ideas and feedback.

@korolevskiyhap
Copy link

korolevskiyhap commented Jun 3, 2022

I think many people are misunderstand difference between emergency and normal wifi connection mode.

Emergency is WIFI Access point, right?
And if both wifi connection and ethernet is configured and present -- they both will be connected without emergency (in normal mode).

@xyzroe
Copy link
Owner Author

xyzroe commented Jun 3, 2022

ZigStar is not recommended to use wifi in working mode. But it is possible.

Emergency mode turns on wifi in case of loss of wired connection.

If you have saved your network settings, ZigStar will first try to connect to it.
If successful, it will be connected as a client to your network until the wired connection is resumed.

If the wireless network is not available or no settings are saved, then ZigStar raises its access point.
After resuming the wired connection, it turns it off.

@monster1025
Copy link

monster1025 commented Jun 3, 2022

Okay, so it works really strange now.
My gateway\router is responding to ping requests:

% ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=3.079 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=3.306 ms

Here is my zigstar-gateway status, it connected simultaneously to wifi and ethernet (same network and gateway\router):
https://ibb.co/wMs4JR8

"Disable emergency mode (AP)" is disabled (not checked). Also here is config:

{"enableWiFi":1,"ssid":"****","pass":"*******","dhcpWiFi":1,"ip":"","mask":"","gw":"","disableEmerg":"0"}

According to Home Assistant status of zigstar-gateway "Emergency mode = Off".
But it connected to wifi and ethernet same time.

@xyzroe
Copy link
Owner Author

xyzroe commented Jun 3, 2022

I don't see anything strange.
You have the checkbox Enable Wi-Fi client mode checked
Therefore, there is a connection to the wifi, regardless of the state of the wired connection.

@monster1025
Copy link

monster1025 commented Jun 3, 2022

Oh, missed it! thanks a lot! Without "Enable Wi-Fi client mode" works as expected - connects to wifi on ethernet failure.

@xyzroe
Copy link
Owner Author

xyzroe commented Aug 3, 2022

7798ec3

@xyzroe xyzroe closed this as completed Aug 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants