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

Sonoff SC: Support for Itead Sonoff SC #155

Closed
ThomDietrich opened this issue Dec 23, 2016 · 14 comments
Closed

Sonoff SC: Support for Itead Sonoff SC #155

ThomDietrich opened this issue Dec 23, 2016 · 14 comments

Comments

@ThomDietrich
Copy link

Hey Theo,
back with yet another new product.

Are you personally interested in extending your firmware for it?

@arendst
Copy link
Owner

arendst commented Dec 23, 2016

No not at the moment but that may change...

@ThomDietrich
Copy link
Author

ThomDietrich commented Dec 23, 2016

I'd actually be willing to motivate this issue by sponsoring one device for you (or one half).
Is this something you are interested in or would you rather not receive donations for this open source project?

Bountysource

Best! Thomas

@jaysuk
Copy link

jaysuk commented Dec 24, 2016

I just want to make sure you know this isn't a typical sonoff product. It doesn't run the sensors off an ESP. It has an atmega328 chip connected to the sensors which then feeds the data to an ESP to transmit the data to the internet.
The code for the atmega328 is available on iteads wiki but there is no code for the ESP.
It the ESP would have to be programmed to collect the data a d transmit it that way, assuming it's useable data. The temperature sensor is a rubbish DHT11

@ThomDietrich
Copy link
Author

I've looked at the data sheet and the schematic. I don't think it will be remarkably hard to adopt arendst firmware for that. Of course we can only be sure after it was tested.
The DHT11 is sure not the best sensor but I wouldn't define it as useless or rubbish...

@arendst
Copy link
Owner

arendst commented Dec 24, 2016

I've read somewhere that they are already planning to replace the DHT11 by a DHT22. Still no high-tech but at least better than before.

I might receive a unit so hold on with your funding...

@ThomDietrich
Copy link
Author

ThomDietrich commented Dec 24, 2016

The only thing making me sad is, that the unit doesn't have a CO2 sensor. I'd expect the "environment monitor" in my bedroom to be equipped with one :-/ But it's no wonder, $19.90 is not enough to even buy one of these on the street.

@derlucas
Copy link

i ordered two of that Sonoff SC units and can supply hires photos of this.

@farconada
Copy link

I'm very interested in it too
It will be great to installarends Sonoff firmware

@derlucas
Copy link

derlucas commented Dec 28, 2016

I started a firmware for Sonoff SC based on Homie-ESP8266. Maybe you can start from there:
https://github.com/derlucas/homie-sonoff/tree/master/sonoff-homie-sc

I changed the original ATMega328p firmware to tell the sensor values on a regular base. The ESP runs Homie Firmware and sends the Data from Serial over to MQTT.

@farconada
Copy link

IMHO the esp8266 firmware should respect the original interface with the arduino firmware provided by itead, so you could have separate developments

@arendst arendst changed the title Support for Itead Sonoff SC Sonoff SC: Support for Itead Sonoff SC Dec 30, 2016
@farconada
Copy link

I've placed my bounty to buy a Sonoff SC to @arendst

@xoseperez
Copy link

I have also been working on the Sonoff SC, with a firmware based on my ESPurna firmware for Sonoff devices and alike.

I have added DHT22 support, MQTT and Domoticz integration. Also I'm using the mic to monitor claps and send custom MQTT messages so you can clap your lights on/off.

An explanation of the whole process is here: http://tinkerman.cat/sonoff-sc-with-mqtt-and-domoticz-support/

@JoeWiseman
Copy link

I know it might not be the right place to ask, but is there any way to use a brighness sensor along with the existing Sonoff-devices (e.g. Sonoff TH) in combination with the firmware given here?
I've red that the "brightness sensor" just give the a "dusky, normal and bright", so it would be better to get a numerical value in e.g. lux.
Would be great if anyone did some experience with that and is willing to share it.
Regards
Joe

@ThomDietrich
Copy link
Author

First support via: arendst/Tasmota@79b6385, see arendst/Tasmota#112

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants