Skip to content
This repository has been archived by the owner on Apr 28, 2022. It is now read-only.

Experimental #305

Closed
wants to merge 27 commits into from
Closed

Experimental #305

wants to merge 27 commits into from

Conversation

yash2607
Copy link

@yash2607 yash2607 commented Jan 7, 2019

i need this for my project.

* Server Side - serves websocket (ws://IP/ws), mqtt, webserver
* Client Side - requires a server, not standalone!
* tons of bugs fixed. now communication netween nodes works and message
is processed correctly.
* found delays in WS2812FX!
* Updated README
Added
* Auto Mode from McLighting
* Button Mode from McLighting

NEEDS TESTING, not tested!
* server needs compilation with IwIP 1.4 Higher Bandwidth
* Go back to painlessMesh-master
* tested auto mode, works!
* tested button mode, works!
stateOn needs to be false when automode is off
* Address #147
* Minimal RESTful API support
* Should have same RESTful API as McLighting
* No support for individual RESTful API for set speed, set brighness
* No legacy modes
Server
* Added versioning
* Added destruction of DNS and server after AsyncWiFiManager is done
* Use ArdunoJSON to send reply
* Fix MQTT reconnect issue when not connected to internet
* Broadcast MQTT HA status on MQTT connect
Clients
* Added versioning
*  Reply for McLighting web-request for mode now reads from SPIFFs
<<
faster
*  Fixed more MQTT hangups, max MQTT retries is set to 3
*
Only send MQTT message if connected to MQTT server
*  Fixed: When
connection topology has changed, no need to re-broadcast
*  Added DNS
support
DNS server and mesh dont mesh
Update README for recommendation to use IwIP v1.4
* Retract "When connection topology has changed, no need to
re-broadcast", it turns out we need to rebroadcast!
* Fix brighness 0-255 scale
Pushed this just to have an async version online. Will have to modify
ArduinoJSON stuff.
@dermalikmann
Copy link
Collaborator

MeshyMcLighting will probably be dropped since @debsahu is working on and E1.31 in #289 and #287.
Furthermore we can't just simply merge a (probably) not 100% stable version into master (hence the name experimental)

If you really need this in your project right now fork the project and merge it yourself. You can then use your version and don't depend on us to merge this.

I leave it to you and/or @debsahu and @toblum to close this issue.

@debsahu
Copy link
Collaborator

debsahu commented Jan 7, 2019

Just like @M4Lik suggested: On top right corner, click on fork and you will have a copy of this project. Then you can merge experimental to master branch on your fork.

@debsahu debsahu closed this Jan 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants