-
Notifications
You must be signed in to change notification settings - Fork 25
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
PiConnect Improvements #24
Comments
i see what you mean by using HTTP to send updated to PiConnect site, i think HTTP is non runner in my humble opinion, only handful people would ever enjoy with these many transaction to web server. remember one thing even commercial products have down time and their up time isnt 99.99% just for reference have look here https://outage.report/nest for nest outage. |
@dvdcut i was thinking the same and i have done some coding to produce jason
|
@pihome-shc any further work completed on this? |
yes i have basic framework completed on client and server one rpi is as client and another as server working ok so far but i need to test it in production. I need input from your guys, may be one private repository as i don't want to disclose server side jut in case there is bug and some one try to exploit it. |
on changing or creating zone sync value set to 0 to sync with Piconnect #24
#24 making zone_current_state table compatible with PiConnect
Making code compatible with PiConnect #24
Hi all,
At this stage PiConnect works over http request which is very CPU intensive i m looking for ideas to improve PiConnect i m by no mean expert but after reading few blogs and watching some YouTube videos i think websocket is better options and MQTT on public is domain is another option, what you guys thing and which way PiConnect should go?
The text was updated successfully, but these errors were encountered: