Skip to content
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

Samsung windfree Elite stop working from today morning #19

Open
michalidesko opened this issue Oct 28, 2022 · 4 comments
Open

Samsung windfree Elite stop working from today morning #19

michalidesko opened this issue Oct 28, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@michalidesko
Copy link

michalidesko commented Oct 28, 2022

Describe The Bug:
After a year of flawless operation today just stop working

To Reproduce:
Open Homekit - Turn on a/c or set something - Nothing happened. Same when i try http://homebridge.local/accessories .
SmartThings app work nice.

Logs:
Dont see [homebridge-samsung-air-conditioner-smart-things] logs

Plugin Config:

{
"name": "homebridge-samsung-air-conditioner-smart-things",
"token": "TOKEN",
"temperatureUnit": "C",
"showHumidity": false,
"windFreeSupported": false,
"platform": "HomebridgeSamsungACSmartThings"
},

Environment:

  • Plugin Version: homebridge-samsung-air-conditioner-smart-things v1.0.9

  • Homebridge Version: homebridge-config-ui-x v4.50.1

  • Node.js Version: [v16.15.0]

  • NPM Version: pi@homebridge:/var/lib/homebridge $ npm -g outdated
    Package Current Wanted Latest Location Depended by
    corepack 0.10.0 0.15.0 0.15.0 node_modules/corepack global
    npm 8.5.5 8.19.2 8.19.2 node_modules/npm global

  • Operating System: Raspbian GNU/Linux Bullseye (11)

@michalidesko michalidesko added the bug Something isn't working label Oct 28, 2022
@ambroselittle
Copy link

ambroselittle commented Oct 29, 2022

Mine stopped working recently, too. I tried:

  • generating a new token
  • restarting the bridge
  • restarting the hub
  • removing/re-adding the bridge in Home (multiple times)
  • Removing the bridge and reinstalling plugin/bridge (on diff port)

Now when I add the bridge, it doesn't prompt to add the A/C unit. Acts like it's not even there.

Logs:

0/29/2022, 4:20:57 PMsamsungsmartthings stopping
10/29/2022, 4:21:02 PMSamsung SmartThings starting
10/29/2022, 4:21:17 PMSamsung SmartThingsLoaded plugin 'homebridge-samsung-air-conditioner-smart-things'
10/29/2022, 4:21:17 PMSamsung SmartThingsLoading 1 platforms...
10/29/2022, 4:21:17 PMSamsung SmartThingshomebridge-samsung-air-conditioner-smart-thingsFinished initializing platform:
10/29/2022, 4:21:18 PMSamsung SmartThingsBridge is running on port 51855.

@ambroselittle
Copy link

This PR should fix: #20

I tested running locally, and it is good. Also tried to future proof a bit against this issue by adding the label/name matcher.

@ambroselittle
Copy link

@teodoradima I confirmed installing my branch manually on HOOBS that it works, FWIW. Let me know if you've decided to not maintain. I can figure out how to publish a new one based on mine if so.

In case anyone else wants to use my branch in the meantime, here's what I did.

CLI Docs

Before Starting: Remove your old bridge from Home and from HOOBS.

Steps:

  1. ssh hoobs@hoobs.local (Docs)
  2. sudo hbs bridge create (I called mine "SmartThings")
  3. sudo hbs plugin add https://github.com/ambroselittle/homebridge-samsung-air-conditioner-smart-things.git#fix-device-discovery (pick the bridge from Step 2)

In theory, that should do it, but it doesn't. You'll get WARNING: No plugins installed. when starting the bridge. The reason is that the plugin needs to be built:

  1. cd /var/lib/hoobs/smartthings/node_modules/homebridge-samsung-air-conditioner-smart-things
  2. sudo npm I
  3. sudo npm run build

The above should build it and create the ./dist folder on HOOBS.

Now restart the bridge you created. Of course, you'll need to add the config as usual with your SmartThings API token. Once you have that, you should see something like this in logs after restarting:

10/30/2022, 11:25:05 PM SmartThings starting
10/30/2022, 11:25:15 PM SmartThings Loaded plugin 'homebridge-samsung-air-conditioner-smart-things'
10/30/2022, 11:25:15 PM SmartThings Loading 1 platforms...
10/30/2022, 11:25:15 PM SmartThings homebridge-samsung-air-conditioner-smart-things Finished initializing platform:
10/30/2022, 11:25:16 PM SmartThings Bridge is running on port 50826.
10/30/2022, 11:25:16 PM SmartThings homebridge-samsung-air-conditioner-smart-things Found 3 devices from Samsung. Checking for A/C devices...
10/30/2022, 11:25:16 PM SmartThings homebridge-samsung-air-conditioner-smart-things Found 1 A/C devices: 'Air'
10/30/2022, 11:25:16 PM SmartThings homebridge-samsung-air-conditioner-smart-things Adding new accessory: Air

If it doesn't find it, you can try adding this to the platform config:

"deviceName": "Air",

The name should match what you named it in the SmartThings app. Restart the bridge.

You should then be able to add in Home as usual.

@gvchagas
Copy link

gvchagas commented Nov 28, 2022

Same problem here. I only have two plugins (tuya web platform and this one). during this last week I performed several tests:

  • I uninstalled the plugin;
  • Generated a new token, with the same and another name;
  • Installed it as a separate bridge;
  • Formatted my setup, reinstalling HomeBridge;
  • Switched between Ethernet and Wi-Fi;
  • Reconfigured the air conditioning;
  • Change the DNS advertiser.
    Nothing had any effect and the device doesn't even show up anymore.
    I use HomeBridge on a RaspberryPi.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants