Also the player id is displayed as a signed int, but is an uint
Player ID: -1483700108

Device has an IPv6 address

https://www.belkin.com/us/products/smarthome-iot/c/wemo/

IP addresses are changing all the time, it is a accepted behaviour of router. Average users doesnt assign static IP addresses to the Hue bridge - reconfiguring is a bit too much work to discover the new IP address - the plug-in is supposed to do it automatically and with the same auth token

Netatmo Connection: Change interface gateway to account
In-/Outdoorstation: Add connectable interface

Steps to reproduce:

• set up a ws2812
• stop nymea
• unplug hardware
• start nymea
• remove device

=> it crashes in deviceRemoved() -> serialPort->flush()

presumably because the serialPort is never added to m_serialPorts.

Having the user deal with "--w1" and stuff is too complicated, or let's say, does not qualify for nymeas "easy to the user" standards.

There should be a set of ComboBoxes, Checkboxes and whatnot with a nice description what they do and they should compose the actual command line args themselves.

https://forum.nymea.io/t/ic2-ds18b20-temperature-sensors/280/9

in the simulation plugin, the executeAction for the Garage Door device class is not implemented and returns a DeviceClassNotFound error

Should probably use a setupMethod instead of params for username/password

When removing a serialport commander devices while the USB-serial port has been disconnected it will result in a segfault

Having set "Optical sensor enabled" to false, the sensortag still updates the light intensity state continuously

I connected nymea to my MaxCube. Unfortunately, only the wall thermostats were taken over. My radiator thermostats are not shown.

nymea needs a reboot to make the Hue connection work again

Child device descriptors need to have parentId properly set.

Nuki via BT shows offline / ‚not connected‘ although it actually is reachable. I‘m aware of the fact that the BT connection is initiated on demand to save battery - but the offline Notification is a bit disturbing on my devices screen.
Maybe a 30 min availability check would do a better job?

I also realised that the refresh trigger sometimes only works on a second attempt. So there should be 3 attempts if one auto-refresh fails.

String comparison was moved in the udp input to the rule engine

install nymea and kodi on the same machine, the discovery won't work in this case.

When setting up an action to be preformed on the Kodi plugin for the action Open an item on this thing... streamable items in Kodi add-ons are not able to be selected.

This can be tested with the Youtube add-on.

The 'Power'-action is wrong and should actually only be an event.

I realised it when I tried to turn power on on a radiator -but a few seconds after, it turned off again.
After repeating this, I realised that Tado only reacts on the target temperature - and switches on / off if lower or beyond that temperature.

So changing the Power action to an event would allow to see if it is currently heating or not.
I would also rename it to heating (or 'heating up') - to make this status more obvious.

Turning it off or on is anyway possible by selecting the Mode: OFF / Tado / Manual

I use the TP-Link switches in my setup and was wondering if you could add support for this along with other Kasa devices

Some strings start with capital letters some not

only one today thing is allowed.

A typo in the action name

As there is only a key (no user), displayPin is what should be used to enter the key.

The toggle button state can not be set by a rule to a specific value
inside the execute action function the state is only toggled
and not the value taken from the action param as it is supposed to be.

When the nymea host goes offline temporarily, Tado web connection doesn't recover.
Also reconfigure is not offered, so removal and repairing is required.

The Hue bridge (V1) seems to have a bug that whenever the bridge gets disconnected from the LAN it loses the connection to all the clients. In case of the Hue app, I add a "new" bridge and do the push button authorization again - I could do that as well with nymea -> delete bridge -> discover bridge .. , but I've set-up a couple of rules depending on the Hue devices and then re-adding the bridge would require me to set-up the rules again. A rediscovery, re-authorization of the already added Hue bridge would solve that issue.

With the schedule function of the Doorbird app, http requests can be triggered. Triggers can be motion, button and rfid. The rfid feature is the main reason to integrate the doorbird in a smart home. It will need a comprehensive description in the readme.

The same may apply to create method "user".

I did a workaround by storing the parent id as a device param.
When the parent device has been removed I told the device manager to remove all devices with the according deviceId as param.

Now it seems with the latest API change I can no longer access the devicemanager within a plug-in