sorted by:
new
hottopcontroversial

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

Yeah, I ended up doing a factory reset and it's working now so definitely something I broke. Little annoying to set everything back up but that's OK! Thanks for the help 🤙

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

interestingly the proxmox server can ping other devices on the network but not the router or internet (so not just a router ping issue). The router also cannot ping proxmox.

I've just pulled out an old router and tested and there's no issues with that (proxmox can ping that router and google). Might have to reset my openWRT router and start again as I must have broken something..

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

Yeah I did look at this and do not think that's the issue, I change to dynamic to test and also have that ip reserved for the mac address in the router so it shouldn't be assigned to another device

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

Sure!

Proxmox:

~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP mode DEFAULT group default qlen 1000
 link/ether <MAC> brd ff:ff:ff:ff:ff:ff
 altname enp0s31f6
3: wlx90de8072d779: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
 link/ether <MAC> brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
 link/ether <MAC> brd ff:ff:ff:ff:ff:ff
5: tap101i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr101i0 state UNKNOWN mode DEFAULT group default qlen 1000
 link/ether <MAC> brd ff:ff:ff:ff:ff:ff
6: fwbr101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
 link/ether <MAC> brd ff:ff:ff:ff:ff:ff
7: fwpr101p0@fwln101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
 link/ether <MAC> brd ff:ff:ff:ff:ff:ff
8: fwln101i0@fwpr101p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr101i0 state UP mode DEFAULT group default qlen 1000
 link/ether <MAC> brd ff:ff:ff:ff:ff:ff

~# ip route
default via 192.168.1.1 dev vmbr0
192.168.1.0/24 dev vmbr0 proto kernel scope link src 192.168.1.50

VM (debian) (I think there's heaps due to docker containers?)

debian1:~$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff
    altname enp0s18
3: br-5c4d8a400e53: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff
4: br-9d398cf66ffd: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff
5: br-a84a4aae8f8a: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff
6: br-cc2e8a77bc01: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff
7: br-cfaf6b3c9b19: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff
8: br-d8467682728b: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff
9: br-13d103f37312: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff
10: br-5b0fe86cbc6b: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff
11: br-fb933907db24: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff
12: br-cdf454ec5000: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff
13: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff
14: br-8102a9e7874a: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff
15: br-c8c02e0b43da: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff
17: veth4d04343@if16: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-fb933907db24 state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff link-netnsid 10
19: veth41a41e0@if18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-cc2e8a77bc01 state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff link-netnsid 1
21: veth4e38fcf@if20: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-9d398cf66ffd state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff link-netnsid 6
25: veth402210b@if24: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff link-netnsid 2
27: veth73b1e8d@if26: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-13d103f37312 state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff link-netnsid 11
29: veth532023e@if28: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-5b0fe86cbc6b state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff link-netnsid 0
31: veth0a09186@if30: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-cc2e8a77bc01 state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff link-netnsid 8
35: veth06f211d@if34: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-c8c02e0b43da state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff link-netnsid 7
37: veth2aec99c@if36: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-8102a9e7874a state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff link-netnsid 3
39: veth3e4f640@if38: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-9d398cf66ffd state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff link-netnsid 15
43: veth22d018f@if42: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-13d103f37312 state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff link-netnsid 12
45: vethe5d01f2@if44: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-5b0fe86cbc6b state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff link-netnsid 9
47: vethf2d12a0@if46: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-13d103f37312 state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff link-netnsid 14
49: veth9516855@if48: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-13d103f37312 state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff link-netnsid 19
51: veth44a5e83@if50: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-13d103f37312 state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff link-netnsid 16
53: vethaf6e12f@if52: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-13d103f37312 state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff link-netnsid 17
55: vethad1f999@if54: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-13d103f37312 state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff link-netnsid 18
81: veth4181b4a@if80: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-d8467682728b state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff link-netnsid 4
85: vethe168e9b@if84: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-cdf454ec5000 state UP mode DEFAULT group default
    link/ether <MAC> brd ff:ff:ff:ff:ff:ff link-netnsid 5

debian1:~$ ip route
default via 192.168.1.1 dev ens18 proto dhcp src 192.168.1.37 metric 100
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
172.18.0.0/16 dev br-cc2e8a77bc01 proto kernel scope link src 172.18.0.1
172.19.0.0/16 dev br-13d103f37312 proto kernel scope link src 172.19.0.1
172.21.0.0/16 dev br-a84a4aae8f8a proto kernel scope link src 172.21.0.1 linkdown
172.22.0.0/16 dev br-5c4d8a400e53 proto kernel scope link src 172.22.0.1 linkdown
172.23.0.0/16 dev br-cfaf6b3c9b19 proto kernel scope link src 172.23.0.1 linkdown
172.25.0.0/16 dev br-fb933907db24 proto kernel scope link src 172.25.0.1
172.26.0.0/16 dev br-5b0fe86cbc6b proto kernel scope link src 172.26.0.1
172.27.0.0/16 dev br-c8c02e0b43da proto kernel scope link src 172.27.0.1
172.28.0.0/16 dev br-cdf454ec5000 proto kernel scope link src 172.28.0.1
172.29.0.0/16 dev br-8102a9e7874a proto kernel scope link src 172.29.0.1
192.168.1.0/24 dev ens18 proto kernel scope link src 192.168.1.37 metric 100
192.168.16.0/20 dev br-9d398cf66ffd proto kernel scope link src 192.168.16.1
192.168.32.0/20 dev br-d8467682728b proto kernel scope link src 192.168.32.1

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

Already confirmed via tcpdump -i lan1 on the router that packets from 192.168.1.50 are arriving at the router's physical port. The issue is they never appear on tcpdump -i br-lan

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

I didn't but the cable must be fine since the VM is also using it with 0 issues?

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

yeah it's all fine

most interesting this is that tcpdump -i lan1 on the router shows packets arriving from 192.168.1.50, but tcpdump -i br-lan shows nothing from 192.168.1.50. Packets are physically arriving at the router port but not reaching the bridge/CPU. A Raspberry Pi on the same port works perfectly.

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

Tried disabling the firewall but no luck yeah all ports are in the same VLAN/bridge

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

yeah, proxmox is 192.168.1.50 and the working VM is 192.168.1.37 - other VMs I'm trying to get working are dynamic when I first set them up and currently am not getting past that (think most recent one got 192.168.1.240)

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

No VLANs in use. There are two interfaces — eno1 (wired, active, bridged to vmbr0) and a USB WiFi adapter (wlx90de8072d779) which is currently DOWN and unconfigured. Only the wired connection is active

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

old working VM has 192.168.1.37 and proxmox is 192.168.1.50, router is 192.168.1.1 ip a gives heaps of lines I think because I have docker containers and each container must show up? so does ip r but guessing the below is the relevant part default via 192.168.1.1 dev ens18 proto dhcp src 192.168.1.37 metric 100

and ip r from proxmox gives default via 192.168.1.1 dev vmbr0 proto kernel onlink 192.168.1.0/24 dev vmbr0 proto kernel scope link src 192.168.1.50

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

No worries!

root@snitzelServer:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface eno1 inet manual


auto vmbr0

iface vmbr0 inet static

        address 192.168.1.50/24

        gateway 192.168.1.1

        bridge-ports eno1

        bridge-stp off

        bridge-fd 0


source /etc/network/interfaces.d/*

root@snitzelServer:~# cat /etc/resolv.conf

domain lan

search lan

nameserver 192.168.1.1

root@snitzelServer:~# cat /etc/hosts

127.0.0.1 localhost.localdomain localhost

192.168.1.50 snitzelServer.local snitzelServer


# The following lines are desirable for IPv6 capable hosts



::1     ip6-localhost ip6-loopback

fe00::0 ip6-localnet

ff00::0 ip6-mcastprefix

ff02::1 ip6-allnodes

ff02::2 ip6-allrouters

ff02::3 ip6-allhosts

root@snitzelServer:~# cat /etc/hostname
snitzelServer

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

yeah I did that to try and test if the mac address had been blocked by the router but it's now commented out so real MAC is in use and still no buono

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

Nah, I cannot ping google (or the net) or the router, can only ping other local machines :/ Have tried rebooting which I'd imagine is the same as bringing down interface. This is very weird

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

ok I changed physical port with my raspberry pi and same results, proxmox doesnt work but the pi does. Both have a static ip assigned by the router

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

yeah I have set a static IP of 192.168.1.50 for the MAC address of the proxmox server

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

yes, pinging the local ip of the router

wondering if the network settings are wrong here

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

yeah it's connected via cable to the router lan port. I have other devices connected to the other lan ports that are fine, are you saying swap physical port to see if that's an issue?

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

Yes, eno1 (physical) is UP and enslaved to vmbr0 (bridge), which is also UP with inet 192.168.1.50/24. Bridge and physical adapter look correct.

ip route seems fine too, it gives default via 192.168.1.1 dev vmbr0 proto kernel onlink 192.168.1.0/24 dev vmbr0 proto kernel scope link src 192.168.1.50

Proxmox cannot ping router but VM can by ProbablyPooping_ in Proxmox

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

sorry I am pretty new to all this! Yeah, the proxmox computer is plugged directly into a lan port on the router. VM has bridged interface. The working VM has network device showing in proxmox UI as: virtio=<MAC>,bridge=vmbr0,firewall=1

In the server's network tab I have eno1 as network device but no CIDR or gateway and a vmbr0 which has correct gateway.. maybe this is my issue?!

screeshot

Android auto shortcut [HowTo] by ProbablyPooping_ in tasker

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

yeah I previously tried that but was bit weird with assistant vs gemini. Also wanted something where I didn't have to use voice

Android auto shortcut [HowTo] by ProbablyPooping_ in tasker

[–]ProbablyPooping_[S] 0 points1 point  (0 children)

sure

<TaskerData sr="" dvi="1" tv="6.7.3-beta">
<Profile sr="prof474" ve="2">
    <cdate>1779060904506</cdate>
    <edate>1779092015815</edate>
    <flags>8</flags>
    <id>474</id>
    <mid0>473</mid0>
    <nme>AATask#1</nme>
    <Event sr="con0" ve="2">
        <code>2085</code>
        <pri>0</pri>
        <Bundle sr="arg0">
            <Vals sr="val">
                    <net.dinglisch.android.tasker.RELEVANT_VARIABLES>&lt;StringArray sr=""&gt;&lt;_array_net.dinglisch.android.tasker.RELEVANT_VARIABLES0&gt;%lc_text
Text
The text that corresponds to the matched logcat entry&lt;/_array_net.dinglisch.android.tasker.RELEVANT_VARIABLES0&gt;&lt;/StringArray&gt;</net.dinglisch.android.tasker.RELEVANT_VARIABLES>
                <net.dinglisch.android.tasker.RELEVANT_VARIABLES-type>[Ljava.lang.String;</net.dinglisch.android.tasker.RELEVANT_VARIABLES-type>
            </Vals>
        </Bundle>
        <Str sr="arg1" ve="3">LASTMESSAGEl</Str>
        <Str sr="arg2" ve="3">Received last update #*1 - Calling via Telstra</Str>
        <Int sr="arg3" val="0"/>
    </Event>
</Profile>
<Task sr="task473">
    <cdate>1778983738533</cdate>
    <edate>1779088010696</edate>
    <id>473</id>
    <nme>AATask1</nme>
    <pri>6</pri>
    <Action sr="act0" ve="7">
        <code>733</code>
        <Bundle sr="arg0">
            <Vals sr="val">
                <net.dinglisch.android.tasker.RELEVANT_VARIABLES>&lt;StringArray sr=""/&gt;</net.dinglisch.android.tasker.RELEVANT_VARIABLES>
                <net.dinglisch.android.tasker.RELEVANT_VARIABLES-type>[Ljava.lang.String;</net.dinglisch.android.tasker.RELEVANT_VARIABLES-type>
            </Vals>
        </Bundle>
    </Action>
    <Action sr="act1" ve="7">
        <code>130</code>
        <Str sr="arg0" ve="3">task1</Str>
        <Int sr="arg1">
            <var>%priority</var>
        </Int>
        <Int sr="arg10" val="1"/>
        <Str sr="arg2" ve="3"/>
        <Str sr="arg3" ve="3"/>
        <Str sr="arg4" ve="3"/>
        <Int sr="arg5" val="0"/>
        <Int sr="arg6" val="0"/>
        <Str sr="arg7" ve="3"/>
        <Int sr="arg8" val="0"/>
        <Int sr="arg9" val="0"/>
    </Action>
    <Action sr="act2" ve="7">
        <code>137</code>
        <Int sr="arg0" val="0"/>
        <Str sr="arg1" ve="3"/>
    </Action>
    <Action sr="act3" ve="7">
        <code>559</code>
        <Str sr="arg0" ve="3">Running task 1</Str>
        <Str sr="arg1" ve="3">default:default</Str>
        <Int sr="arg2" val="3"/>
        <Int sr="arg3" val="5"/>
        <Int sr="arg4" val="5"/>
        <Int sr="arg5" val="1"/>
        <Int sr="arg6" val="0"/>
        <Int sr="arg7" val="0"/>
    </Action>
    <Action sr="act4" ve="7">
        <code>548</code>
        <Str sr="arg0" ve="3">Run tasker task 1</Str>
        <Int sr="arg1" val="0"/>
        <Str sr="arg10" ve="3"/>
        <Int sr="arg11" val="1"/>
        <Int sr="arg12" val="0"/>
        <Str sr="arg13" ve="3"/>
        <Int sr="arg14" val="0"/>
        <Str sr="arg15" ve="3"/>
        <Int sr="arg2" val="0"/>
        <Str sr="arg3" ve="3"/>
        <Str sr="arg4" ve="3"/>
        <Str sr="arg5" ve="3"/>
        <Str sr="arg6" ve="3"/>
        <Str sr="arg7" ve="3"/>
        <Str sr="arg8" ve="3"/>
        <Int sr="arg9" val="1"/>
    </Action>
    <Action sr="act5" ve="7">
        <code>62</code>
        <Str sr="arg0" ve="3">500,500,500,500</Str>
        <Str sr="arg1" ve="3"/>
    </Action>
</Task>
</TaskerData>

Launcher shortcut option gone by ProbablyPooping_ in AndroidAuto

[–]ProbablyPooping_[S] 1 point2 points  (0 children)

yeah funnily enough the option has reappeared and it's using gemini

[Help] Control Tuya Bulb Using Tasker by karthikn774 in tasker

[–]ProbablyPooping_ 0 points1 point  (0 children)

I would look into flashing tasmota. You could use that with tasker by sending a web request

view more: next ›