No, you can't do that using Sonoff since it is an on-off switch with relay.
You need an Triac to do that. Normally the brightness control applications for AC will be done through Triac by changing the firing angle.
Your command seems to be out of sync with the rest.
sudo systemctl stop home-assistant@pi
First it seems incomplete at the end at best and moreover why are you using stop to restart? Why not use restart.
sudo systemctl restart firstname.lastname@example.org
From what I'm reading you need bridges for specific devices, unless they support Z-Wave or Zigbee (may well be wrong on this...).
In general, you need a "bridge" for everything - including Z-Wave and ZigBee. A bridge may be as simple as a USB dongle and some software, or it may be a stand-alone box, but there must be something to handle the radio and ...
Every networked device connected to your router has a MAC address, which is specifically linked to one device, unlike local IP addresses in your private network, which are assigned by your router and don't have to be permanent.
Generally, local IPs are assigned sequentially, often starting at 192.168.0.1, then 192.168.0.2 and so on, as described by How-To ...
In the configuration.py file, i hope you are using double quotes while parsing string arguments as the output which you are receiving, maximum time we miss those quotes only while changing arguments.
If this doesn't help please go through the appended link:
The most obvious answer would be to use the azimuth parameter, and check for 180 (south). The sun component also has a 'rising' state (before noon), and next_noon time.
If you follow the link to the US Naval observatory, you can print out a table of solar position for any particular location, on any particular date. For my location (52N), I see the sun ...
If you have sent data from the device to the HomeAssistant over MQTT, then you can do it for sure the other way around. MQTT is completely bidirectional, there is no notion of server and clients as in HTTP, but broker and clients, and all clients are first class citizens.
You have to determine what topic the HomeAssistant uses to send the data (let's say /...
I am running Home Assistant on a Raspberry Pi and have had a lot of success using the Aeotec Gen5 Z-Wave control stick (USB). I bought several of the GoControl WNK01-21KIT kits and the door sensors have been working really well, but that is just one of many Z-Wave door sensor options.
I don't know what happened, but reviewing the logs on my router, I was able to discern that the device DID obtain a DHCP address, but I overrode that with a fixed IP instead, following instructions on the GitHub page for the CLI.
First, if you just have 1 garage door opener, why are you generating a random client id every time? using a fixed clientID would be the right thing to do here.
The only time a random clientID makes any sense is when you are using a transient client e.g. a webpage using MQTT over Websockets.
Second, you appear to be double looping your reconnect function. ...
There are devices made specially for dimming using only on-off impulses to set the brightness. A common pattern is to use a short on/off signal for on/off, and a longer on/off signal to increase brightness in n % steps.
So provided you can make the Sonoff switch on and off sufficiently fast, and reliably to get the timing right, adding a device like this or ...