Home Automation - Smartkit

rorz0r said:
Do you regularly sit in the living room, fully clothed, drinking coffee and feel the need to adjust your shower temperature?

99e9ad2911e832b8d7c5e940cae1f822.jpg
Click to expand...

I can see some bugger in the lounge telling Alexa to change the temperature to 10 degrees while you are halfway into your shower.
 
ToxicBunny said:
Clearly they do over in whatever country that is...
Click to expand...
Lol.

So basically it preheats to the desired temp and flushes out the Cold water so when you enter the water is at the right temp.

Didn't think of someone changing the temp while you are inside it .
 
This is valid if it also measures time/flow.
So, after 5 minutes / 60 litres, set temperature to zero
 
And surely it needs a camera to detect which person is in the shower, and possibly more than one at a time...
 
Okay so I got my pre-Tasmota'd Basics from Smartkit this morning.

Of course immediately I went to fiddle and in my infinite wisdom decided to just flash to the latest firmware and get it done with as I always like to stay current.

Without paying attention just hit the URL upgrade that was pre-populated....and then it flashed the Minimal firmware by default.

Seemingly no major drama as it flashed just fine and starts up without an issue...BUT it won't connect to my Wifi now even though it did just fine to do the upgrade in the first place.

Is there are hidden URL link to get to the upload firmware screen without needing to connect to Wifi first? Since I can access the interface on it's own SSID.

I've created a new Guest SSID on my network with one word SSID and password just to cut out complexity but no dice.

Next step is to try the WPS method tonight.


Bare in mind I don't have the tools at present to flash conventionally so I'm at the mercy of web interface. But if there is a way to go via SSH or some such that's an option too.
 
// -- Wifi ----------------------------------------
#define WIFI_IP_ADDRESS "0.0.0.0" // [IpAddress1] Set to 0.0.0.0 for using DHCP or IP address
#define WIFI_GATEWAY "192.168.2.254" // [IpAddress2] If not using DHCP set Gateway IP address
#define WIFI_SUBNETMASK "255.255.255.0" // [IpAddress3] If not using DHCP set Network mask
#define WIFI_DNS "192.168.2.27" // [IpAddress4] If not using DHCP set DNS IP address (might be equal to WIFI_GATEWAY)

#define STA_SSID1 "" // [Ssid1] Wifi SSID
#define STA_PASS1 "" // [Password1] Wifi password
#define STA_SSID2 "" // [Ssid2] Optional alternate AP Wifi SSID
#define STA_PASS2 "" // [Password2] Optional alternate AP Wifi password
#define WIFI_CONFIG_TOOL WIFI_WPSCONFIG // [WifiConfig] Default tool if wifi fails to connect
// (WIFI_RESTART, WIFI_SMARTCONFIG, WIFI_MANAGER, WIFI_WPSCONFIG, WIFI_RETRY, WIFI_WAIT)

So you're gonna need to use WPS. There's no default wifi setup in the minimal build.
 
Sinbad said:
// -- Wifi ----------------------------------------
#define WIFI_IP_ADDRESS "0.0.0.0" // [IpAddress1] Set to 0.0.0.0 for using DHCP or IP address
#define WIFI_GATEWAY "192.168.2.254" // [IpAddress2] If not using DHCP set Gateway IP address
#define WIFI_SUBNETMASK "255.255.255.0" // [IpAddress3] If not using DHCP set Network mask
#define WIFI_DNS "192.168.2.27" // [IpAddress4] If not using DHCP set DNS IP address (might be equal to WIFI_GATEWAY)

#define STA_SSID1 "" // [Ssid1] Wifi SSID
#define STA_PASS1 "" // [Password1] Wifi password
#define STA_SSID2 "" // [Ssid2] Optional alternate AP Wifi SSID
#define STA_PASS2 "" // [Password2] Optional alternate AP Wifi password
#define WIFI_CONFIG_TOOL WIFI_WPSCONFIG // [WifiConfig] Default tool if wifi fails to connect
// (WIFI_RESTART, WIFI_SMARTCONFIG, WIFI_MANAGER, WIFI_WPSCONFIG, WIFI_RETRY, WIFI_WAIT)

So you're gonna need to use WPS. There's no default wifi setup in the minimal build.
Click to expand...

Strange because the Wifi-Manager shows up and the SSID is there, gets DHCP IP address and everything. Can connect to web interface and enter SSID/Auth details but upon restart it goes back to sonoff**** SSID only.

But cool if that's the simplest answer then will have to do WPS as much as I hate it.


****

Where is that log excerpt from?
 
SauRoNZA said:
Strange because the Wifi-Manager shows up and the SSID is there, gets DHCP IP address and everything. Can connect to web interface and enter SSID/Auth details but upon restart it goes back to sonoff**** SSID only.

But cool if that's the simplest answer then will have to do WPS as much as I hate it.


****

Where is that log excerpt from?
Click to expand...

That's from the source code of the tasmota-minimal build on github
 
Sinbad said:
That's from the source code of the tasmota-minimal build on github
Click to expand...

Okay let me go dig around there. Will probably find my answers.

The bigger joke is that I suspect it already was on latest and that my eye caught the Development Build field of V6.0 on the main page.

/fail

Comes from rushing to get it on the network before work so I can fiddle with it while at work.

****

I find that for the main builds and nothing specific to the minimal. Link maybe?

So I would imagine the binary's have some config in already.

But WPS will be first port of call.
 
Last edited:
If minimal doesn't save config by design, then no. ;(
 
Sinbad said:
If minimal doesn't save config by design, then no. ;(
Click to expand...

Surely one can just change that parameter somehow? Maybe through the web commands?

Jirre doesn't help that I'm still noob.

Guess I'll **** around with the other two first before trying to fix this one.
 
SauRoNZA said:
Surely one can just change that parameter somehow? Maybe through the web commands?

Jirre doesn't help that I'm still noob.

Guess I'll **** around with the other two first before trying to fix this one.
Click to expand...

Any config updates generally need a reboot to become active.
 
Okay the one unit aside I've managed to scratch my head aplenty about MQTT and Home Assistant but managed to get the two other units up and connected and working and triggering individually.

Now before I read the entire internet figured I would ask these questions...

1. Retain Power - Why do I need to enable this? I'm not quite understanding what it does. Also why do you add the opposite of this with "retain : false" on HA side or is that something else?

2. Retain Button - Is this purely to keep the button functionality? And if so how does it relate to my setting Button Topic and Switch Topic?

I've simply made MQTT Topic, Button Topic and Switch Topic all the same. Would there be any logic to do this otherwise?
 
Sinbad said:
Any config updates generally need a reboot to become active.
Click to expand...

I cracked it.

Had to manually go to /up on the URL and then you can load it from file.

The odd part is that my Windows machine wouldn't even see the SSID nevermind try to connect to it. iPhone wouldn't get DHCP but with manual IP manages to connect to interface.

More ridiculous is that I then needed to upload it to iCloud as it's the only device to work.
 
Anyone using Google Home devices with home-assistant?

With the latest release I can't get mine working. If I turn discovery on, they're found - but adding them manually, nothing - no errors.
 
Mine works fine for TTS out and mic commands in. Using the cloud services.
 
Same here, no problems. Three lights controlled with Sonoff/Tasmota/HA that turns on/off fine with GHome. Also using the Cloud service.

Mmm, then again, haven’t checked since I upgraded to 0.72 two evenings ago.
 
If you have upgraded, have you changed your configuration to the new component for cast?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X