Home Automation - Smartkit

i am new to home assistant and am finding it an interesting but steep learning curve. I have integrated a number of sonoff switches with the AlexxIT sonoff control on github. I have set up some automations to switch on the switches at certain times of the day and everything works.

Now that loadshedding is back, sometimes the automations do not work as power is off at the sonoff switch at the due automation time.

Any idea how I can set up an automation to see if the sonoff is powered between certain times and if it is not, to turn the switch on when power is restored?
I'm in a very similar position with Home Assistant and Sonoff switches using AlexxITs integration.

Most of the automations I find are for use with Tasmota, and are often applied with Node Red.

The eWeLink app still works with unflashed Sonoff kit, so I just use the Power-on State switch on the app to switch power through when mains power is restored. I also use the loop function on the app to delay switching power through to motors etc as I haven't been able to find an automation yet to do that.

Are you using YAML or Node Red for your automations?
 
I'm in a very similar position with Home Assistant and Sonoff switches using AlexxITs integration.

Most of the automations I find are for use with Tasmota, and are often applied with Node Red.

The eWeLink app still works with unflashed Sonoff kit, so I just use the Power-on State switch on the app to switch power through when mains power is restored. I also use the loop function on the app to delay switching power through to motors etc as I haven't been able to find an automation yet to do that.

Are you using YAML or Node Red for your automations?
I am currently using YAML, have installed node red but not played with it yet. My raspberry Pi remains on during loadshedding so I now can some time to play with it
 
Anyone else having issues with load shedding info in Home Assistant? It's screwing with my automations. Constantly goes from no loadshedding to loadshedding - not sure if the problem is with accessing Eskoms site - or HA. I added a 30s timeout to the curl statement, but - it's still jumping up and down.
 
Anyone else having issues with load shedding info in Home Assistant? It's screwing with my automations. Constantly goes from no loadshedding to loadshedding - not sure if the problem is with accessing Eskoms site - or HA. I added a 30s timeout to the curl statement, but - it's still jumping up and down.
I think its their API.

I have nodered collect the stage and populate an input in HA and it also shows like 1.0 now and jumps down to -2.0 at times for a minute or so then back to 1.0 etc.

Now my nodered is set up such, that if it fails to connect, the flow stops and so there should be no change to the value in HA. So the fact that it changes means I was able to connect to the api and it actually changed.
 
Anyone else having issues with load shedding info in Home Assistant? It's screwing with my automations. Constantly goes from no loadshedding to loadshedding - not sure if the problem is with accessing Eskoms site - or HA. I added a 30s timeout to the curl statement, but - it's still jumping up and down.

what do you have? i have this

- platform: command_line
name: eskom ls
command: "curl https://loadshedding.eskom.co.za/LoadShedding/GetStatus"
value_template: '{{ value | round(0) | abs - 1 }}'
unit_of_measurement: "Stage"
scan_interval: 600

eskom_ls.JPG
 
Same, excepting for a timeout on the curl statement, and no scan interval - I'll add the scan interval, see if it helps.
 
Anyone used a Sonoff device to connect to their electric fence (for arming/disarming purposes).
If so, how did you do it?
 
Have to say I am very impressed with the Sonoff camera I got from Smartkit. Going to be very useful as a baby monitor.
 
i know it was brought up, but I do not recall an outcome - has anyone managed to monitor the status of the gpio on an sv for some application without an HA integration? i.e like stand alone?
bumping this - anyone come up with an elegant solution to using a basic/sv to trigger and monitor status without using some sort of "physical" hub like HA etc. i.e something stand alone.
anyway to do this with any other type of device, eg a shelly etc?

So, i beleive that in the shelly app you can actually do exactly what i want with a shelly1!
 
How would I add this to my configuration.yaml? I've added it under sensor: but it doesn't show up.


You likely need to go look for it in Unused Entities. It won’t just show up by itself.
 

You likely need to go look for it in Unused Entities. It won’t just show up by itself.
How would I add this to my configuration.yaml? I've added it under sensor: but it doesn't show up.

what @SauRoNZA said.

so i have that entry in my sensor.yaml

then on the ui i have this under badges.

- entity: sensor.eskom_ls
 
So, I have a few Sonoff SV setup for pulse mode to open gates. During load shedding the computer, MQTT and wireless shut off, while the SV's stay powered the while time. When the PC and AP turn back on, one of them reconnects to Wifi while the other doesn't and need to be power cycled before it connects again. Does anyone know of a command which might be affecting this behaviour?
 
So, I have a few Sonoff SV setup for pulse mode to open gates. During load shedding the computer, MQTT and wireless shut off, while the SV's stay powered the while time. When the PC and AP turn back on, one of them reconnects to Wifi while the other doesn't and need to be power cycled before it connects again. Does anyone know of a command which might be affecting this behaviour?
What else is different between the 2 SVs? Same firmware?

I have my HA and mqtt on inverter as is wifi.
 
What else is different between the 2 SVs? Same firmware?

I have my HA and mqtt on inverter as is wifi.
Exact same firmware, just different console commands.
Now I'm trying to figure out which is responsible for wifi reconnections.
 
So, I have a few Sonoff SV setup for pulse mode to open gates. During load shedding the computer, MQTT and wireless shut off, while the SV's stay powered the while time. When the PC and AP turn back on, one of them reconnects to Wifi while the other doesn't and need to be power cycled before it connects again. Does anyone know of a command which might be affecting this behaviour?

I’ve always changed the WIFI_RETRY options with Tasmoadmin so never used the commands but it’s bound to be one of these.

Code:
 WifiConfig 
0 = disable Wi-Fi Manager and reboot (used with alternate AP)
2 = set Wi-Fi Manager as the current configuration tool and start Wi-Fi Manager (web server at 192.168.4.1) for 3 minutes, then reboot and try to connect Wi-Fi network
4 = disable Wi-Fi Manager but retry the other AP without rebooting
5 = disable Wi-Fi Manager and wait until that AP is available again without rebooting
6 = Wi-Fi parameters can only be entered via commands in the serial console
7 = set Wi-Fi Manager (web server at 192.168.4.1) as the current configuration tool restricted with the only option to reset settings. 
This setting is recommended for devices without an external control/reset button.
 No longer supported 
1 = set SmartConfig (Android/iOS) as the current configuration tool, start SmartConfig for 3 minutes and reboot and try to connect to Wi-Fi
3 = set WPS as configuration tool, try WPS for 3 minutes and reboot and try to connect to Wi-Fi
 
anyone using PAI and finding random sensors? 5 of these are actually mine


  • Kitchen Wood Doo
  • Zone 05
  • Front East Patio
  • PJ Patio Door
  • Roof PIR
  • Patio Door
  • Flat
  • Main Beams
  • Kitchen Door
  • Garage Top
  • Lounge PIR
  • Kitchen Back Doo
  • Entrance Yard
  • Flat Beam
  • Bedroom 2
  • Panic
  • OS Front Left
  • Lounge
  • Area 1
  • Zone 06
  • Garage Ground
  • Office
  • Run status
  • Front Door
  • Dining
  • OS Front Right
  • Garage/Braai
  • Pub
  • Front driveway a
  • Passage PIR
  • Dining PIR
  • Entrance Lobby
  • Run status
  • Side Yard
  • Patio
  • Garage Door
  • Kitchen Yard
  • Kitchen Door
  • main bedroom
  • PJ Lounge
  • Study
  • Inside
  • Area 2
  • Flat
  • Back East
  • TV Lounge PIR
  • Back west
  • Kitchen
  • OS Back
  • Storeroom
  • Driveway
  • Front Door
  • OS Flat
  • Home
  • Kitchen
  • Back Yard
  • store door
 
Top
Sign up to the MyBroadband newsletter
X