jameskitt616
jameskitt616
Pretty sure i had that same issue on regular standalone neko. Before i used neko rooms.
Maybe it's possible to pass an hostname/domain to neko and it re-resovles the IP in case of DNS warning? or sth similar to this.
I found a temporary workaround to re-enable them: 1. Edit `/usr/share/hassio/homeassistant/.storage/core.entity_registry` (or appropriate to your local config location) 2. Find the Group you disabled (probably by Name) 3. Find in...
The default placeholder could be more sth like `e.g. localhost, 10.x.x.x, mysql, 192.168.x.x` The more examples, the better people understand, same goes for the redis host btw
But there is, Tax Value in the Payment settings? 
Nah this is the current master, i assumed people did not remove it in the dev branch
Is there any fix, workaround, progress on this? or any rough ETA how long it will stay broken? Neko is sadly pretty unusable like that.
I think i found the culprit. Upon starting to see if i can reproduce it by building a separate neko-rooms system, i recalled that i only had the issue when...
I sadly do not know what version i had before, I dont upgrade on every nginx release. I only got `keepalive_timeout 65;` set in my nginx config and http2 enabled.
Would appreciate as well, just updated my PC and notice that this extension is gone again