Version 1.0.1 All went offline
See original GitHub issueJust updated, perfectly working before, now nothing works (raps 3b+):
[4/28/2020, 00:07:12] [Config] Rebooting linux server with command: "sudo -n shutdown -r now"
[4/28/2020, 00:07:13] [HB Supervisor] Stopping services...
[4/28/2020, 00:07:13] Got SIGTERM, shutting down Homebridge...
[4/28/2020, 00:07:13] [Temperature & Humidity] Stopped scanning.
[4/28/2020, 00:07:13] [Temperature & Humidity] Stop scanning. (poweredOff)
[4/28/2020, 00:07:15] [Temperature & Humidity] Start scanning.
[4/28/2020, 00:07:16] [Temperature & Humidity] Error: Could not start scanning, state is poweredOff (not poweredOn)
at Noble.scan (/usr/local/lib/node_modules/homebridge-mi-hygrothermograph/node_modules/@abandonware/noble/lib/noble.js:97:19)
at Noble.startScanning (/usr/local/lib/node_modules/homebridge-mi-hygrothermograph/node_modules/@abandonware/noble/lib/noble.js:126:10)
at Scanner.start (/usr/local/lib/node_modules/homebridge-mi-hygrothermograph/lib/scanner.js:36:13)
at Timeout._onTimeout (/usr/local/lib/node_modules/homebridge-mi-hygrothermograph/lib/scanner.js:72:14)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7)
[4/28/2020, 00:07:18] [Config] Terminal session ended.
[4/28/2020, 00:07:40] [HB Supervisor] Homebridge Path: /usr/local/lib/node_modules/homebridge/bin/homebridge
[4/28/2020, 00:07:40] [HB Supervisor] UI Path: /usr/local/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
[4/28/2020, 00:07:40] [HB Supervisor] Starting Homebridge with extra flags: -I
[4/28/2020, 00:07:40] [HB Supervisor] Started Homebridge with PID: 649
[4/28/2020, 00:07:42] Loaded config.json with 6 accessories and 3 platforms.
[4/28/2020, 00:07:42] ---
[4/28/2020, 00:07:45] Loaded plugin: homebridge-config-ui-x
[4/28/2020, 00:07:45] Registering platform 'homebridge-config-ui-x.config'
[4/28/2020, 00:07:45] ---
[4/28/2020, 00:07:45] Loaded plugin: homebridge-mi-hygrothermograph
[4/28/2020, 00:07:50] [Config] Homebridge Config UI X v4.16.0 is listening on :: port 8080
[4/28/2020, 00:07:53] Registering accessory 'homebridge-mi-hygrothermograph.Hygrotermograph'
[4/28/2020, 00:07:53] ---
[4/28/2020, 00:08:03] Loaded plugin: homebridge-platform-wemo
[4/28/2020, 00:08:03] Registering platform 'homebridge-platform-wemo.BelkinWeMo'
[4/28/2020, 00:08:03] ---
[4/28/2020, 00:08:04] Loaded plugin: homebridge-tahoma
homebridge-tahoma API version: 2.5
[4/28/2020, 00:08:04] Registering platform 'homebridge-tahoma.Tahoma'
[4/28/2020, 00:08:04] ---
[4/28/2020, 00:08:05] Loaded plugin: homebridge-mqtt-switch-tasmota
[4/28/2020, 00:08:05] Plugin '@bluephlame/homebridge-mqtt-switch-tasmota' tried to register with an incorrect plugin identifier: 'homebridge-mqtt-switch-tasmota'. Please report this to the developer!
[4/28/2020, 00:08:05] Registering accessory '@bluephlame/homebridge-mqtt-switch-tasmota.mqtt-switch-tasmota'
[4/28/2020, 00:08:05] ---
[4/28/2020, 00:08:05] Loading 3 platforms...
[4/28/2020, 00:08:05] [WeMo] Initializing BelkinWeMo platform...
[4/28/2020, 00:08:05] [My TaHoma Box] Initializing Tahoma platform...
[4/28/2020, 00:08:05] [My TaHoma Box] Fetch accessories...
[4/28/2020, 00:08:05] [My TaHoma Box] Login Connexoon server...
[4/28/2020, 00:08:05] [Config] Initializing config platform...
[4/28/2020, 00:08:05] [Config] Running in Service Mode
[4/28/2020, 00:08:05] Loading 6 accessories...
[4/28/2020, 00:08:05] [Schlafzimmer] Initializing mqtt-switch-tasmota accessory...
[4/28/2020, 00:08:05] [Schlafzimmer] Nazwa do RESULT POWER
[4/28/2020, 00:08:05] [Leo's Zimmer] Initializing mqtt-switch-tasmota accessory...
[4/28/2020, 00:08:05] [Leo's Zimmer] Nazwa do RESULT POWER
[4/28/2020, 00:08:05] [Vorne] Initializing mqtt-switch-tasmota accessory...
[4/28/2020, 00:08:05] [Vorne] Nazwa do RESULT POWER1
[4/28/2020, 00:08:05] [Hinten] Initializing mqtt-switch-tasmota accessory...
[4/28/2020, 00:08:05] [Hinten] Nazwa do RESULT POWER2
[4/28/2020, 00:08:05] [Balkon] Initializing mqtt-switch-tasmota accessory...
[4/28/2020, 00:08:05] [Balkon] Nazwa do RESULT POWER3
[4/28/2020, 00:08:05] [Temperature & Humidity] Initializing Hygrotermograph accessory...
[4/28/2020, 00:08:05] [Temperature & Humidity] address option is not set. When running multiple sensors this will cause interference. See README for instructions.
[4/28/2020, 00:08:06] [My TaHoma Box] Unable to refresh states (not logged in)
[4/28/2020, 00:08:06] [WeMo] Online: LED Kueche [08863BC5D1CC]
[4/28/2020, 00:08:06] [WeMo] Online: LED Flur [08863BC5E3B8]
[4/28/2020, 00:08:06] [WeMo] Online: WeMo Motion [08863BC4A58C]
[4/28/2020, 00:08:06] [Temperature & Humidity] Start scanning.
[4/28/2020, 00:08:07] [My TaHoma Box] [Box] type: Pod > Pod, protocol: internal
[4/28/2020, 00:08:07] [My TaHoma Box] No definition found for Pod > Pod in mapping.json file
[4/28/2020, 00:08:07] [My TaHoma Box] [Küche] type: RollerShutter > PositionableRollerShutter, protocol: io
[4/28/2020, 00:08:07] [My TaHoma Box] Instanciate Küche as WindowCovering
[4/28/2020, 00:08:07] [My TaHoma Box] [Leo] type: RollerShutter > PositionableRollerShutter, protocol: io
[4/28/2020, 00:08:07] [My TaHoma Box] Instanciate Leo as WindowCovering
[4/28/2020, 00:08:07] [My TaHoma Box] [Schlafzimmer] type: RollerShutter > PositionableRollerShutter, protocol: io
[4/28/2020, 00:08:07] [My TaHoma Box] Instanciate Schlafzimmer as WindowCovering
[4/28/2020, 00:08:07] [My TaHoma Box] [Wohnzimmer Tür] type: RollerShutter > PositionableRollerShutter, protocol: io
[4/28/2020, 00:08:07] [My TaHoma Box] Instanciate Wohnzimmer Tür as WindowCovering
[4/28/2020, 00:08:07] [My TaHoma Box] [Wohnzimmer Fenster] type: RollerShutter > PositionableRollerShutter, protocol: io
[4/28/2020, 00:08:07] [My TaHoma Box] Instanciate Wohnzimmer Fenster as WindowCovering
[4/28/2020, 00:08:07] Initializing platform accessory 'Wohnzimmer Fenster'...
[4/28/2020, 00:08:07] Initializing platform accessory 'Wohnzimmer Tür'...
[4/28/2020, 00:08:07] Initializing platform accessory 'Schlafzimmer'...
[4/28/2020, 00:08:07] Initializing platform accessory 'Leo'...
[4/28/2020, 00:08:07] Initializing platform accessory 'Küche'...
Setup Payload:
X-HM://0023QSNASLK4B
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
I removed Homebridge in hope of fixing the problem, and tried to readd, no matter if I delete the persists and accessories or simply create a new user -> Homebridge can’t be connected, no connection to that device 😦
Please advise! Maybe how can I roll back?
Issue Analytics
- State:
- Created 3 years ago
- Comments:39 (8 by maintainers)
Top Results From Across the Web
After working for a few days all devices went offline in 1.0.4
4 version for a few days now which worked great, all my devices went offline yesterday. Funny thing is, that some get a...
Read more >Unable to resolve dependency for ':app@debug ...
Go to File->Other Settings->Default Settings->Build, Execution, Deployment->Build Tools->Gradle->Uncheck Offline work option.
Read more >Network connectivity problem since updating to new firmware ...
After going to the new firmware Version of 1.0.8 on all 4 units is when all the units started going offline at random...
Read more >creating an offline installation fails - Visual Studio Feedback
I am trying to create an offline installer for Studio 2019 v16.9 (professional). The quickest way to reproduce this is.
Read more >pixma mx490 is listed as offline - Canon Community
I connect the printer to the wireless and it says it is connected and then when I go to print it says the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for update 1.0.3 - it did the trick ) By the way, now devices status (in 1.0.3) are showing instantly, while on 0.4 had to wait refresh. Using Raspberry PI
YES! That did the trick.