Yeah the nodered flow on the target device is for handling shutdown(sleep) and status reporting back to HomeAssistant, so in HA the computer is a simple switch with on/off states

Oh neat!

I made a custom solution for WOL and remote shutdown using nodered and MQTT, but this is so cleaner than maintaining a custom solution

I’m in this picture and I don’t like it

One way is to make a new “entity”, that’s not actually linked to your previous temperature sensor. I’m not familiar with how to tie them together in a “device” like how ZigBee2mqtt auto discovery does.

So just add a new “sensor”/“entity”

  - name: "Sala_battery"
    unique_id: "temp_sala_battery"
    state_topic: "zigbee2mqtt/temp_sala"
    value_template: "{{ value_json.battery }}"
    unit_of_measurement: "%"

Use MQTT Explorer to listen to your ZigBee2mqtt broker topic “zigbee2mqtt/temp_sala” to get the exact field name (battery, battery_state or some such)

Color temperature is actually quite OK with simple remotes. Like the IKEA remote control used left and right arrows to change between stark white, warm yellow and happy medium.

Problem is non-smart bulbs with smart wall-switch can’t change color temperature. Theoretically I suppose there could be a switch/bulb combo, where the switch is Zwave/ZigBee enabled, and somehow communicate with the bulb. But I don’t think anything like that exists. It’d probably be very expensive if it did

Cheaper? :O This is the super-deluxe splurge option compared to some cheap IKEA ZigBee bulbs

Got any recommendations? ZigBee, Zwave, or something else?

One nice thing about having the bulbs smart is changing the color temperature. Is there any way of doing that from the wall-switch? It’s kinda what’s been stopping me from upgrading from smart bulbs to smart switches

So DIY home-assistant based cloud-relay is better than custom made purpose built cloud-relay by muliti billion dollar company? xD

Which is both hilarious and a testament to the power of Home-assistant and open source (and I suppose it says something about how much Hyundai cares about their app)

You might be on the wrong track with the last paragraph. Does the mosquito broker even support “devices”? Doesn’t it just support generic topics and messages?

It sounds like for whatever reason rtl_433 is not pushing messages to your MQTT broker. Check with MQTT Explorer if you haven’t already

Double check your MQTT connection settings in rtl_433. Also try changing QOS settings to see if it helps

For language_not_allowed the selected language of your comment must be among allowed languages on the community/instance your commenting on. This whole Language thing can be a bit confusing depending on the settings of your instance.

I think the jerboa client (and others?) does NOT let you select the language of your comment, so comment once from the Web interface, make sure you select language (English). After I did that I can now comment from Jerboa, so I guess my instance remembers the settings.

Also go in to your profile settings and tick “undetermined” language setting, in addition to English and whatever else you use

Here are some links I had a similar issue: good explanation, and issue solve by my Instance admin: https://reddthat.com/post/1976

Ferdig.uk changing from English only to also undetermined https://feddit.uk/post/37778

The developer of RedReader was planning to port it to Lemmy. This was before RedReader was given an exemption for the API prices though. Hopefully he still is heading that direction, but Lemmy support might have been put on the backburner until he’s done the changes required for the new API policy

RedReader was my app of choice alongside RiF , so I’m super excited if it gets Lemmy support