A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 132

Backtrace:

File: /home/brettonw/public_html/application/controllers/Blog.php
Line: 7
Function: __construct

File: /home/brettonw/public_html/index.php
Line: 319
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 294

Backtrace:

File: /home/brettonw/public_html/application/controllers/Blog.php
Line: 7
Function: __construct

File: /home/brettonw/public_html/index.php
Line: 319
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 168

Backtrace:

File: /home/brettonw/public_html/application/controllers/Blog.php
Line: 7
Function: __construct

File: /home/brettonw/public_html/index.php
Line: 319
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 237

Backtrace:

File: /home/brettonw/public_html/application/controllers/Blog.php
Line: 7
Function: __construct

File: /home/brettonw/public_html/index.php
Line: 319
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 317

Backtrace:

File: /home/brettonw/public_html/application/controllers/Blog.php
Line: 7
Function: __construct

File: /home/brettonw/public_html/index.php
Line: 319
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 358

Backtrace:

File: /home/brettonw/public_html/application/controllers/Blog.php
Line: 7
Function: __construct

File: /home/brettonw/public_html/index.php
Line: 319
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 282

Backtrace:

File: /home/brettonw/public_html/application/controllers/Blog.php
Line: 7
Function: __construct

File: /home/brettonw/public_html/index.php
Line: 319
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 294

Backtrace:

File: /home/brettonw/public_html/application/controllers/Blog.php
Line: 7
Function: __construct

File: /home/brettonw/public_html/index.php
Line: 319
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 304

Backtrace:

File: /home/brettonw/public_html/application/controllers/Blog.php
Line: 7
Function: __construct

File: /home/brettonw/public_html/index.php
Line: 319
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 314

Backtrace:

File: /home/brettonw/public_html/application/controllers/Blog.php
Line: 7
Function: __construct

File: /home/brettonw/public_html/index.php
Line: 319
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 315

Backtrace:

File: /home/brettonw/public_html/application/controllers/Blog.php
Line: 7
Function: __construct

File: /home/brettonw/public_html/index.php
Line: 319
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 316

Backtrace:

File: /home/brettonw/public_html/application/controllers/Blog.php
Line: 7
Function: __construct

File: /home/brettonw/public_html/index.php
Line: 319
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 317

Backtrace:

File: /home/brettonw/public_html/application/controllers/Blog.php
Line: 7
Function: __construct

File: /home/brettonw/public_html/index.php
Line: 319
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 375

Backtrace:

File: /home/brettonw/public_html/application/controllers/Blog.php
Line: 7
Function: __construct

File: /home/brettonw/public_html/index.php
Line: 319
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 110

Backtrace:

File: /home/brettonw/public_html/application/controllers/Blog.php
Line: 7
Function: __construct

File: /home/brettonw/public_html/index.php
Line: 319
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Session cannot be started after headers have already been sent

Filename: Session/Session.php

Line Number: 143

Backtrace:

File: /home/brettonw/public_html/application/controllers/Blog.php
Line: 7
Function: __construct

File: /home/brettonw/public_html/index.php
Line: 319
Function: require_once

Welcome

Controlling of lights in the office or factory from home by using Zigbee

Case study



Zigbee wireless lighting control system, includes Zigbee gateway, Zigbee high bay, and smart phone at least. Owning these three “devices”, we can realize a local lighting control.
1. The gateway must be powered on, when power on the gateway will emit a Zigbee wireless network signal similarly with a WIFI hot-spot.
2. Connect the network of smart phone to Zigbee wireless hot-spot, to build the communication with gateway.
3. Then we can use the lighting control APP in smart phone to control the high bay turn on/off, or dim.
4. Lighting control instruction will be sent from smart phone APP, passed to gateway, then given to high bay, who will execute the instruction, turn on/off, dim or others.



Above is called Local Lighting Control or Field Lighting Control, because the three devices must be in the communication covering distance (maybe 200m). In fact, adding some device, we can realize a Long-Distance Lighting Control. That is wireless router.
1. Make sure the router connects well to Internet, use smart phone APP to make a network (Zigbee hot-spot with WIFI signal from wireless router) binding setting.
2. Then we can use the APP to control the high bay from anywhere, yes from anywhere, using 2G/3G/4G/WIFI or others wireless networks which connect well to Internet.
3. Similarly, the lighting control instruction will be sent from smart phone APP, passed into Internet, received by wireless router, then passed to gateway, then given to high bay who will execute.



It means, you can control the lights in your office or factory from home or any other places in the world, only need a smart phone connects well to Internet.