Just checked and there still isn’t a TRV device type in the register device Node Red node. Nor is there a capability of target temperature so I can fake one. I don’t know why this device type is still not present. I thought it’d be added by now. I last looked when the TRV was fairly new and was unsurprised it was absent. Now I am.
Thanks for the proposal! But it might take some time before we evaluate and schedule new Node-Red features for the next major version.
I’ve turned it into a feature request, so our team can track it.
Thx again.
couldn’t you at least create some “generic status” report for all the zigbee devices that you have not implemented yet?
You just need to report to node-red every message sent from the device. Shouldn’t be do “difficult”, we don’t need formatting or beautiful things. Just to know what the devivc sent.
Can you specify the problem?
Like what kind of device and what kind of capability?
And what node would you want it to show?
I think the TRV is a type thermostat on the API. Haven’t read that part of the document closely enough but I think you could create a virtual thermostat and then create a TRV as a subtype. There is Generic “sensor” device type and loads more capabilities in the newest API. Create a Register-Device node and then select the iHost as server. Loads of new capabilities.
I don’t think they mean a specific capability. For example as the ESP 32 C6 Dev Kit or H2 Dev Kit can both do Zigbee a tinkerer could potentially add any capability. At the moment it’d have to pretend to be a standard device type but it’d be nice was there just a generic Sensor digital I/O or ADC type we could use instead. Not sure the arduino library makes it easy yet and mostly it’s via the espressif IDE.
I literally just got one of these
On Kickstarter with a
It communicates over UART but means the “Warcher” AI could output almost any capability, which the C6 could then send over Zigbee to an iHost, so I think a generic digital IO or ADC/DAC would mean any capability added to a C6/H2 etc could be added.
It’d be nice to add generic capabilities so we could add home made devices to the iHost Zigbee Network.
I was thinking on the TRV since that is what ward said that “it might take some time before they evaluate and schedule new Node-Red features”.
I had tried to configure Node-Red reading my NSPanel Pro some time ago and had a hard time since many things seam to be incomplete or bad configured. It looks like they ported (in a very clumsy way) what was working in the iHost, into the NSPanel Pro. Actually I started to just send the get commands manually for things that didn’t work (for example, I registered virtual devices for testing, then I couldn’t delete them since the delete function did not work, so I figure out how to directly delete it with a put command (I don’t remember the details but I put it somewhere here in the forum in a reply to someone with a similar problem).
I would just expect that the get devices node lists ALL the devices connected to my Panel, and if one is still not “supported” (meaning they didn’t configure its capabilities), it should show as a generic device. Actually, for ALL devices I would like to see ALL the info that the device sends, not something “filtered and embelesed” with json capabilities and nice brackets…
Sorry about the inconvenience we caused.
Can you specify your needs into a list?
So we can send it to our team and evalute it in future version of node-red cube plugin.