GithubHelp home page GithubHelp logo

smartthings's People

Contributors

cjcharles0 avatar endor-force avatar robinwinbourne avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

smartthings's Issues

Connect to ST

Hello Cj,
I went to connect my Powerlink pro Visonic to the ESP8266 and at this time all is correct.
Thanks for your work!
Now I want to use my Samsung A50 and ST to connect to the alarm. I don't understand how I do install "device handler" into ST (Part 2-7 of your instructions).
Can you explain more?

Restarting MQTT Server does not initialize reconnection.

When restarting MQTT Server the code will not reconnect.

The only way i found for reconnection is to go to /advanced in web ui and just submit the page again.

Before restart of MQTT server:
Setings.useMQTT: 1
mqtt_last_reconnect: 0
mqtt_setup: 1
mqtt.connected: 1
mqtt.state: 0

After restart of MQTT server:
Setings.useMQTT: 1
mqtt_last_reconnect: 697162 (and increasing)
mqtt_setup: 1
mqtt.connected: 0
mqtt.state: -2

FGBS-001 Contact 2 not working

Hi Guys,
I have just created a new handler for my FGBS-001 from your code for use with the latest smart things app I only seem to get "Contact 1" to work.
"Contact2" just shows Checking ... and does not respond to any input change.
Regards Roger Morris

Connecting to ELK via serial

Received the Wemos D1 R2 configured for serial connection. Setup of the Wemos was easy, however stuck at making the serial connection. Can you provide instructions on how to physically connect the Wemos to the panel?

Fibaro UBS (FGBS-001) with new ST app

Hi Chris,
Any change of updating this to work with the new SmartThings app?
In the new app there is no option to create the child devices and the SmartThings Classic has now been discontinued.
I'm surprised Fibaro hasn't published an official device handler for this...
Thanks!

visonic pmax library not up to date?

When compiling with the source code from github there are compile errors.
cjcharles, can you please verify that the pmax library in github corresponds or is updated to the same version you use when compiling?

These two throws error when compiling:

            Powerlink_ListenNotEnrol = Settings.ListenNotEnrol;
            Powerlink_SlowComms = Settings.SlowComms;

Set and connection issue

Hi,
I have followed all the detailed instructions and everything has checked out okay until I get to the last two main steps:-
7.Save settings on this device, and now press Refresh IPs button - you should see the IP address boxes all populate. Now you can press Configure and this will send all information to the NodeMCU so the NodeMCU should now start working.
8.Finally you can now press Create Thermostat devices and it will create the required thermostats for each Neostat, using the naming rules from step 6.

I can press save and that's all fine (only works on Classic app this bit!) but all of the screen options are greyed out so the IP addresses are already populated so the Refresh IPs doesn't really appear to do anything. The Configure button and Crete thermostate are also greyed so I cannot complete.

Could you help me out here please. I have checked that the hub and the bridge are all connected and allocated the correct IPs.

Source doesn't compile

Hey!

Trying to compile the Arduino code, but keep running into issues.

First up is line 331 being commented, leading to a compile error:

ESP-PowerMaxESP8266:417:17: error: 'Powerlink_PIN_Code' was not declared in this scope
                 Powerlink_PIN_Code = longPIN;
                 ^
ESP-PowerMaxESP8266:422:17: error: 'Powerlink_PIN_Code' was not declared in this scope

After uncommenting line 331, it errors on:

ESP-PowerMaxESP8266:910:20: error: 'Pmax_ARMHOME_INSTANT' was not declared in this scope
     pm.sendCommand(Pmax_ARMHOME_INSTANT);
                    ^
exit status 1
'Pmax_ALARM' was not declared in this scope

After disabling that, I'm getting:

'Pmax_ARMHOME_INSTANT' was not declared in this scope

It continues on, is there any newer code you haven't committed?

Trouble connecting

Hi,
I am still having some issues after install.
All of the screen options are greyed out so the Refresh IPs doesn't really appear to do anything. The Configure button and Crete thermostat are also greyed so I cannot complete.

Could you help me out here please. I have checked that the hub and the bridge are all connected and allocated the correct IPs.

Has anyone though of just creating a PCB to do the work?

Hi All.

First of all, sorry a I know this isn't really a git issue.

I bought the WeMos D1 from here (preprogrammed) some time ago. Didn't work with the alarm panel so had to add the uno as well.

After a power failure, the alarm refused to communicated with the unit. I may have then fried the D1 mini as the whole setup is so cumbersome, getting it off the wall is a nightmare.

Has no one looked at just creating a PCB with an ESP module on it, an Uno and a voltage regulator? Seems like it's a failure simple project and it would be that small it would probably fit inside the alarm panel then as well.

can't get classic app to work

hi, everything went fine until step 10... I see the options (I'm using an iphone) but when I click on them, nothing happens. I'm not sure if this is because it doesn't work on the iphone or not, but right now I have the hub connected but no thermostats.
Is there any way that I can add the thermostats without using the classic app - either on the new app or online? thanks in advance for any ideas!

Neohub interface to SmartThings hub V3 - latest SmartThings app

Hi Charles, I purchased a chip and working fine on V2 and classic SmartThings moved to V3 hub and new app, re-installed to new location set up, the NeoStat bridge is in devices but scan does not pick up the Thermostats and not offered as a brand.... does the interface not work For the new app? Thanks Paul

MQTT Settings gone after reboot of device

Hi,

After i've saved my settings on the /advanced page, the device are showing the proper values, if i return to the same page, just after.

However, after a reboot, the settings is gone again.

And also, it's not connecting to my MQTT broker.

I've defined my MQTT IP in Smart Home Controller IP - and filled out MQTT Username and MQTT Password:, too.

Am i doing something wrong, here?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.